General troubleshooting and workarounds

Learn how to debug issues, and find a workaround if, after the installation, any operator is in the status other than Succeeded.


At least one of the foundational services operators is in the status other than Succeeded after the installation.

To view the statuses of foundational services operators in your OpenShift cluster console, perform the following steps:

  1. From the navigation pane, click Operators > Installed Operators.
  2. Select the IBM Cloud Pak foundational services operator.
  3. Go to the CommonServices tab, and select the common-service custom resource from the list.
  4. Look at the list of Bedrock Operators, and check the OperatorStatus and SubscriptionStatus of each operator.

Checking logs

  1. To check the ibm-common-service-operator pod logs, run the following command:

     oc -n <your-foundational-services-namespace> logs <ibm-common-service-operator-pod-name>
  2. To check the operand-deployment-lifecycle-manager pod, run the following command:

     oc -n <your-foundational-services-namespace> logs <operand-deployment-lifecycle-manager-pod-name>


If you did not find the root cause of the operator failure in the logs, the operator failure might be due to environmental issues.

Complete the following steps to apply the workaround:

  1. From the navigation pane, select Home > Search and set Resources to Subscription.

  2. Select the failed operator's subscription, and go to the YAML view.

  3. Search for installedCSV in the YAML file.

    • If no installedCSV is found, delete the failed operator's subscription with the following command:

       oc -n <your-foundational-services-namespace> delete sub <name-of-the-operator-subscription>
    • If installedCSV is found, save the name of the installedCSV, and delete the failed operator's CSV with the following command:

      oc -n <your-foundational-services-namespace> delete csv <name-of-the-operator-installedCSV>

The subscription or CSV that you deleted in step 3 will be recreated by Operand Deployment Lifecycle Manager in a few seconds.