The Kubelet service does not start after starting the MCP update in the EUS to EUS upgrade from OCP 4.10 to OCP 4.11
Issue
After unpausing the Machine Config Pool (MCP) in order to continue with the cluster upgrade, MCP starts the upgrade but the worker node is reported in NotReady, SchedulingDisabled state and when checking by ssh on the node, the kubelet service does not start.
$ oc get nodes |grep worker
NAME STATUS ROLES AGE VERSION
worker2 Ready infra,worker 652d v1.23.5+012e945
worker1 NotReady,SchedulingDisabled infra,worker 652d v1.23.5+012e945
worker3 Ready infra,worker 652d v1.23.5+012e945
worker4 Ready compute,worker 194d v1.23.5+012e945
worker5 Ready compute,worker 194d v1.23.5+012e945
$ oc get mcp
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE
master rendered-master-5bd2828076ee7a8d1fc5d10b2c4ef958 True False False 3 3 3 0 655d
worker rendered-worker-6d1c0c6dad71abe2c6dae941136bb302 False True False 5 0 0 0 655d
Environment
- Red Hat OpenShift Container Platform (RHOCP) 4.11
- Installer Provisioned Infrastructure (IPI)
- VMware vSphere
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.