I see this bug is similar as in https://bugzilla.redhat.com/show_bug.cgi?id=1940950#c8. Also checked kubelet is starting after crio. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-04-13-171608 True False 68m Cluster version is 4.8.0-0.nightly-2021-04-13-171608 $ oc debug node/ip-10-0-128-60.us-east-2.compute.internal Starting pod/ip-10-0-128-60us-east-2computeinternal-debug ... ... sh-4.4# journalctl | grep -e "Starting Kubernetes Kubelet" -e "Starting CRI-O" -e "crio.wipe" Apr 14 05:23:17 ip-10-0-128-60 systemd[1]: Starting CRI-O Auto Update Script... Apr 14 05:23:17 ip-10-0-128-60 crio[1353]: time="2021-04-14T05:23:17Z" level=info msg="Starting CRI-O, version: 1.21.0-53.rhaos4.8.gitec8716f.el8-dev, git: ()" Apr 14 05:23:17 ip-10-0-128-60 systemd[1]: crio-wipe.service: Succeeded. Apr 14 05:23:17 ip-10-0-128-60 systemd[1]: crio-wipe.service: Consumed 115ms CPU time Apr 14 05:23:17 ip-10-0-128-60 crio[1377]: time="2021-04-14T05:23:17Z" level=info msg="Starting CRI-O, version: 1.21.0-53.rhaos4.8.gitec8716f.el8-dev, git: ()" Apr 14 05:23:17 ip-10-0-128-60 systemd[1]: Starting Kubernetes Kubelet...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438