Kubelet failed to start with the "kubelet.service: Control process exited, code=exited status=255" error.

Solution Verified - Updated -

Issue

  • After a node reboot during Cluster upgrade, Kubelet is unable to start and exits with exit code 255 and the message:
Dec 20 05:01:57 xxxx-master-0 systemd[1]: kubelet.service: Consumed 3ms CPU time
Dec 20 05:01:57 xxxx-master-0 systemd[1]: Starting Kubernetes Kubelet...
Dec 20 05:01:57 xxxx-master-0 systemd[1]: kubelet.service: Control process exited, code=exited status=255
Dec 20 05:01:57 xxxx-master-0 systemd[1]: kubelet.service: Failed with result 'exit-code'.
Dec 20 05:01:57 xxxx-master-0 systemd[1]: Failed to start Kubernetes Kubelet.
Dec 20 05:01:57 xxxx-master-0 systemd[1]: kubelet.service: Consumed 2ms CPU time

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