Pam Andrejko, Barry Mosakowski When running an OpenShift cluster, sometimes you need to update your nodes, for example if you upgrade to a new version of OCP, or apply a change with an oc patch image.config.openshift.io/cluster command, or apply an ImageContentSourcePolicy . Changes like this often require all the nodes in the cluster to be restarted. The Problem Occasionally, one of the nodes fails to restart which is problematic, because the updates need to be pushed to every node, and obviously every node in the cluster needs to be Schedulable and Ready . How do you know if you have this problem? Run the command: oc get machineconfigpool Monitor the MACHINECOUNT column which shows the total number of nodes in your cluster and compare it to the values in the R EADYMACHINECOUNT column: NAME CONFIG MACHINECOUNT READYMACHINECOUNT master rendered-master-xxxx 3 0 worker rendered-worker-yyyy 6