BMYPC5002
A MachineConfigPool
is updating.
Severity
Error or warning
Problem description
It indicates that a MachineConfigPool
update is in progress. It impacts the
upgrade as the next machine configuration rollout in the queue fails because of its dependency on
the successful rollout of the ongoing change.
For example, an ongoing rollout is for a registry auth change for all the nodes. This change must get rolled out to all nodes before you start the upgrade so that no pod failures due to image pullback errors cause upgrade failures.
Recommended actions
Do the following steps to resolve the issue:
- The issue might occur for a short duration whenever the Machine config rollout, OpenShift® Container Platform, and Global Data Platform operations are in progress. Wait for these
operations to complete, then check that the
MachineConfigPool
is healthy and available. - If a pool remains in a degraded state for a long time, then use the following command to find
the root cause.
oc describe machineconfigpool <poolname>
- Check for the problems indicated in the description, and debug further to identify the root
cause. The following are some possible reasons:
- If a node is stuck in a
NotReady
state, restart the node to fix the issue. - Though the node completes the roll out, it might not be in a schedulable state. Compare the required and current configurations. If the configurations are the same, manually remove taint of the unscheduleable state.
- If a node is stuck in a
MachineConfigPool
is available and up to date, the upgrade precheck
detects the fix and resumes upgrade automatically.