BMYPC6002
A MachineConfigPool
is degraded.
Severity
Error
Problem description
It indicates that a MachineConfigPool
is in a degraded state in the OpenShift® cluster. It can impact the upgrade
because the different IBM Storage Fusion component upgrades
also start machine configuration roll outs and they might not succeed if
MachineConfigPool
is in a degraded state. A new machine configuration must be
rolled out when all MachineConfigPool
are healthy.
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
MachineConfigPool
remains in a degraded state for a long time, then use 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:
- A node is stuck in a
NotReady
state, then 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.
- A node is stuck in a
- After the
MachineConfigPool
is available and up to date, the upgrade precheck detects the fix and resumes upgrade automatically.