My Oracle Support Banner

OKE node pool still available, but with cluster warning "node never became ready for ssh: failed to wait for successful command" (Doc ID 2501476.1)

Last updated on OCTOBER 06, 2019

Applies to:

Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.

Symptoms

OKE (Oracle Kubernetes Engine) warning on the container engine pool, even though the node pools are still available according to kubectl.

The error message is:

xxx node never became ready for ssh: failed to wait for successful command

The warning/error came even though all the nodes are accessible via SSH. The warning/error persists even after running yum update and restarted.

The issue thus looks to be with the UI only.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.