BMYPC6006

A pod in the openshift-operator-lifecycle-manager namespace is not ready.

Severity

Error

Problem description

It indicates that pod in the openshift-operator-lifecycle-manager namespace is not ready. Pods in the openshift-operator-lifecycle-manager namespace are responsible for managing catalogs, packages, and operator lifecycle in the OpenShift®. If pods are not running or have errors, then it can cause operator upgrade failure in the IBM Storage Fusion HCI System.

Recommended actions

Do the following steps to resolve the issue:
  1. Check for the events of the failed pods and logs to find the root cause of failure and take an appropriate action to fix the issue. Pod restart can also resolve the problem.
  2. After all the pods in the openshift-operator-lifecycle-manager namespace are ready, 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 OpenShiftLifeCycleManagementPodStatus and set the value to true.
    oc patch configmap precheck-acks -n $FUSION_NS --type merge -p '{"data": {"OpenShiftLifeCycleManagementPodStatus": "true"}}'