Kubelet fails to start, making the node NotReady during the cluster upgrade to 4.12.z

Solution Verified - Updated -

Issue

  • During the cluster upgrade to 4.12.z, the roll-out of the worker MCP makes the node NotReady, SchedulingDisabled state.

  • Upon checking the kubelet status on all the affected nodes, it is found that the kubelet was in an inactive state. The restart of kubelet service keeps failing.

Jun 29 10:15:39 worker-1.ocp.example.net systemd[1]: Starting Kubernetes Kubelet...
Jun 29 10:15:39 worker-1.ocp.example.net kubenswrapper[13533]: /usr/local/bin/kubenswrapper: line 5: /usr/bin/kubelet: No such file or directory
Jun 29 10:15:39 worker-1.ocp.example.net systemd[1]: kubelet.service: Main process exited, code=exited, status=127/n/a
Jun 29 10:15:39 worker-1.ocp.example.net systemd[1]: kubelet.service: Failed with result 'exit-code'.
Jun 29 10:15:39 worker-1.ocp.example.net systemd[1]: Failed to start Kubernetes Kubelet.
Jun 29 10:15:39 worker-1.ocp.example.net systemd[1]: kubelet.service: Consumed 4ms CPU time

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.12

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