BMYCO0011

Unable to put the node into maintenance mode as scale cluster status is not healthy.

Severity

Critical

Error conditions

The error message can be for the following conditions:

  • Failed to move node out of maintenance
  • Failed to move the node into maintenance mode because the node cordoning not succeeded
  • Failed to move the node into maintenance mode because the node exists in maintenance mode.
  • Failed to move node into maintenance mode because the cluster status might not be retrieved.
  • Failed to move the node into maintenance mode as because the IBM Storage Fusion Data Foundation cluster status is not healthy.
  • Failed to move the node into maintenance mode as because the IBM Storage Scale cluster status is not healthy.
  • Unable to move node to maintenance mode. Some other process may be preventing the node from draining, such as an open file handle, an open pod login, or a workload with a Pod Disruption Budget set to zero.
  • Failed to move node into maintenance because the MCO rollout is in progress on the cluster.
  • Multiple nodes cannot be put in maintenance mode simultaneously, if a node exists in maintenance mode.
  • Maintenance mode success.
    Note: This is an informational message and no action is required for this message.

User response

Do the following steps to diagnose the error:
  1. Check whether any node exists in maintenance mode.
  2. Move the node out of maintenance and retry.
  3. Run the oc command to check whether the scale cluster is healthy.
    oc -n ibm-spectrum-fusion-ns get scales storagemanager -oyaml | grep storageClusterStatus
  4. If the Scale cluster is not healthy, check and bring it to a healthy state.
  5. Run the oc command to check whether the Data Foundation cluster is healthy.
    oc -n ibm-spectrum-fusion-ns get odfcluster odfcluster -o yaml | grep status
  6. If the Data Foundation cluster is not healthy, check and bring it to a healthy state.