Operator shows Pending status in a namespace - OLM known issue
An operator fails to install and continuously shows Pending
status in a namespace.
Symptom
You can view the operator status on your OpenShift cluster console.
-
From the navigation pane, click Operators > Installed Operators.
-
From the Projects drop-down list, select the namespace where IBM Cloud Pak foundational services are installed.
-
The failed operator continuously shows
Pending
status.
Cause
This is a known issue in the Operator Lifecycle Manager (OLM).
When the OLM fails to install an operator, the installPlan
fails or is hanging and it blocks the installation.
Resolving the problem
Complete the following steps to resolve the issue:
If the operator that is causing the error is either IBM NamespaceScope Operator
or Operand Deployment Lifecycle Manager (ODLM)
:
-
From your OpenShift console, uninstall the
Pending
operator.- From the navigation pane, click Operators > Installed Operators.
- For the operator with
Pending
status, click the overflow menu icon and clickUninstall
.
(Or)
Delete the subscription and CSV of the operator by using the
oc
CLI.- Log in to the cluster by using the
oc login
command. - Run the following commands to delete the subscription and CSV:
oc -n <your-foundational-services-namespace> delete sub <pending-operator-sub> oc -n <your-foundational-services-namespace> delete csv <pending-operator-csv>
-
Delete
ibm-common-service-operator
podoc delete pod <ibm-common-service-operator-pod-name> -n <your-foundational-services-namespace>
If the error is caused by other operator:
-
From your OpenShift console, uninstall the
Pending
operator.- From the navigation pane, click Operators > Installed Operators.
- For the operator with
Pending
status, click the overflow menu icon and clickUninstall
.
(Or)
Delete the subscription and CSV of the operator by using the
oc
CLI.- Log in to the cluster by using the
oc login
command. - Run the following commands to delete the subscription and CSV:
oc -n <your-foundational-services-namespace> delete sub <pending-operator-sub> oc -n <your-foundational-services-namespace> delete csv <pending-operator-csv>
-
Delete the Operand Deployment Lifecycle Manager pod.
oc delete pod <operand-deployment-lifecycle-manager-pod-name> -n <your-foundational-services-namespace>
After the Operand Deployment Lifecycle Manager
pod is restarted, the operator successfully upgrades or reinstalls.