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
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:
- From the navigation pane, click Operators > Installed Operators.
- Select the IBM Cloud Pak foundational services operator.
- Go to the CommonServices tab, and select the common-service custom resource from the list.
- Look at the list of Bedrock Operators, and check the OperatorStatus and SubscriptionStatus of each operator.
To check the
ibm-common-service-operatorpod logs, run the following command:
oc -n <your-foundational-services-namespace> logs <ibm-common-service-operator-pod-name>
To check the
operand-deployment-lifecycle-managerpod, 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:
From the navigation pane, select Home > Search and set Resources to Subscription.
Select the failed operator's subscription, and go to the YAML view.
installedCSVin the YAML file.
installedCSVis found, delete the failed operator's subscription with the following command:
oc -n <your-foundational-services-namespace> delete sub <name-of-the-operator-subscription>
installedCSVis 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.