Verified on 4.6.0-0.nightly-2021-05-07-052249. Error no longer shows up. $ oc get nodes NAME STATUS ROLES AGE VERSION ip-10-0-159-61.us-west-1.compute.internal Ready master 37m v1.19.0+d856161 ip-10-0-168-116.us-west-1.compute.internal Ready worker 26m v1.19.0+d856161 ip-10-0-171-117.us-west-1.compute.internal Ready master 35m v1.19.0+d856161 ip-10-0-190-70.us-west-1.compute.internal Ready worker 28m v1.19.0+d856161 ip-10-0-227-26.us-west-1.compute.internal Ready worker 28m v1.19.0+d856161 ip-10-0-250-106.us-west-1.compute.internal Ready master 37m v1.19.0+d856161 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2021-05-07-052249 True False 11m Cluster version is 4.6.0-0.nightly-2021-05-07-052249 $ oc get pods -A --field-selector spec.nodeName=ip-10-0-168-116.us-west-1.compute.internal NAMESPACE NAME READY STATUS RESTARTS AGE openshift-cluster-csi-drivers aws-ebs-csi-driver-node-n7mpp 3/3 Running 0 27m openshift-cluster-node-tuning-operator tuned-hjdnd 1/1 Running 0 27m openshift-dns dns-default-nhj8t 3/3 Running 0 27m openshift-image-registry node-ca-8hgp5 1/1 Running 0 27m openshift-machine-config-operator machine-config-daemon-85lrc 2/2 Running 0 27m openshift-monitoring node-exporter-x7dx5 2/2 Running 0 27m openshift-multus multus-g2tp2 1/1 Running 0 27m openshift-multus network-metrics-daemon-h5z7c 2/2 Running 0 27m openshift-sdn ovs-ft4tk 1/1 Running 0 27m openshift-sdn sdn-g8flc 2/2 Running 0 27m $ oc -n openshift-machine-config-operator logs machine-config-daemon-85lrc -c machine-config-daemon | grep "Installed Ignition"
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 (OpenShift Container Platform 4.6.29 bug fix 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/RHBA-2021:1521