BMYPC6001

Cluster operator is not healthy.

Severity

Error

Problem description

It indicates that the specified OpenShift® cluster operator is not available or degraded. It can impact the upgrade because different cluster operators are responsible for the various functions in the OpenShift cluster. If any function is not working due to an unavailable cluster operator, it might result in an upgrade failure.

Recommended actions

Do the following steps to resolve the issue:
  1. Check whether a machine configuration rollout is in progress as it can be a reason for the health status of the cluster operator. In this case, wait for machine configuration rollout to complete and cluster operator to turn healthy.
  2. Check whether a node is in a NotReady state as it be a reason for the health status of the cluster operator. Debug the reason for NotReady state and check that it is a part of the machine configuration rollout progress. If it is a part of the machine configuration rollout, then wait for the roll out to complete.
  3. If a node remains in a NotReady state for more than 30 minutes, then check the network for the node by pinging the IPv4 address or hostname. In case the node does not respond, then restart the node.
  4. If node is in a Ready state but scheduling is disabled, then it might be due to a machine configuration rollout, node in a maintenance mode, or ongoing firmware upgrade. Wait for the operation to complete for the node to become scheduleable.

    After the cluster operator is available and not degraded, the upgrade precheck detects the fix and resumes upgrade automatically.

If you want to override the prechecks that are blocking the upgrade, do the following steps:

It converts the Error prechecks to Warning prechecks and triggers the upgrade.
Note: Before using the precheck-acks configmap to override the pre-checks, ensure that the unhealthy resource does not affect the upgrade.
  1. Run the following command and export IBM Storage Fusion namespace as an environmental variable.
    export FUSION_NS="namespace-where-fusion-is-installed"
  2. Run the following command to create a precheck-acks configmap in the namespace where the IBM Storage Fusion is installed.
    oc create configmap precheck-acks -n $FUSION_NS
  3. In the precheck-acks config map, add the key ClusterOperatorHealth and set the value to true.
    oc patch configmap precheck-acks -n $FUSION_NS --type merge -p '{"data": {"ClusterOperatorHealth": "true"}}'