After doing a hard reset on an OpenShift node, why is it taking so much time for the node to return to `Ready` state ?
Issue
- crio high CPU load after worker node boot and kubelet does not start
- crio initial start takes multiple hours on large cluster nodes after a node has been reseted
Environment
- Red Hat OpenShift Container Platform (RHOCP) 4.*
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.