BMYFW0037E

Failed to move a node into a maintenance mode because an MCO rollout is in progress on the cluster.

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 that is applicable 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.

Severity

Error

Diagnostics and resolution

Do the following steps to diagnose and resolve the issue:
  1. The issue might occur for a short duration whenever the following operations are in progress:
    • Machine config rollout
    • OpenShift® Container Platform upgrade
    • Global Data Platform upgrade

    Wait for these operations to complete, then check whether the MachineConfigPool is healthy and available.

  2. 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>
  3. Check for the problems indicated in the description, and debug further to identify the root cause. The following are some of the possible reasons:
    • 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.
  4. After the MachineConfigPool is available and up to date, the firmware upgrade workflow detects the fix and resumes upgrade automatically.