After doing a hard reset on an OpenShift node, why is it taking so much time for the node to return to `Ready` state ?

Solution Verified - Updated -

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.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content