IBM Support

The ICP nodes status are NotReady

Troubleshooting


Problem

While ICP cluster running, the ICP nodes become NotReady status when you run kubectl get nodes command to check the cluster status. In some cases, you could be see all ICP nodes are NotReady status in your cluster.

 

Symptom

You can check ICP nodes status by kubectl get nodes command. You could see some or all will be NotReady status in your cluster.

# kubectl -s 127.0.0.1:8888 get nodes
NAME            STATUS     ROLES     AGE       VERSION
172.28.142.8    Ready         <none>     4d           v1.9.1+icp-ee
172.28.142.9    NotReady    <none>     4d           v1.9.1+icp-ee
172.28.142.10  NotReady    <none>     4d           v1.9.1+icp-ee
#

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
27 July 2018

UID

ibm10716787