OCP 4 Node not ready after cluster upgrade or node restart
Issue
- Node is in the NotReady state after the cluster was upgraded
- Node is not becoming ready after node reboot
- Container runtime (crio) on the node is not working properly
- Unable to get a debug shell on the node using
oc debug node/<node-name>because container runtime (crio) is not working - Cannot generate sosreport from the node because container runtime (crio) is not working
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- During a upgrade when the nodes are restarting
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
