Troubleshooting IBM Cloud Pak foundational services install and upgrade
This version of documentation is no longer updated. For the latest information, see the following links:
- Continuous Delivery (CD) documentation
- Support Cycle-2 (SC-2) documentation
Review frequently encountered installation, uninstallation, and upgrade errors.
- Gather information about your foundational services installation
- Installation issues
- General troubleshooting and workarounds
- Operator shows Pending status in a namespace - OLM known issue
- Uninstallation is not successful
- Cannot create pod because of MutatingAdmissionWebhook failure
- IBM foundational service Operator fails to initialize resources
- Mirroring images to the local registry fails in an air-gapped environment
- MongoDB pod hangs after installation
- Skopeo failure in air-gapped installation script
- Pushing images to a single namespace in an air-gapped environment
- Deploying the EDB Postgres operator in a custom namespace
- cloudctl command fails to check prerequisites
- Signature validation error during CASE download
- Errors in CASE prerequisites or airgap.sh
- Registry does not support multiple communication attempt during a single authentication session
- OLM known issue: ResolutionFailed message
- Incorrect registry configuration
- IBM Cloud Pak foundational services InstallPlan fails during installation or upgrade
- Unable to mirror the repository using cloudctl CASE as a non-root user
- cloud-native-postgresql is installed with certified-operators CatalogSource
- ibm-zen-cpp-operator image fails to mirror during an air-gapped installation
- Timeout error when retrieving CASEs
- ImageContentSourcePolicy creation fails
- Operator installation or upgrade fails with DeadlineExceeded error
- Topology check returns incorrect results when running the
convert_to_multi_instance.shscript - Troubleshooting catalog issues
- Upgrade issues
- Management ingress pods fail after upgrade from a Helm release
- Operator upgrade fails with the pod in
CrashLoopBackOffstatus- OLM known issue - Zookeeper pod hangs in a
CrashLoopBackOffstate - Operator installation hangs during upgrade
- Operand Deployment Lifecycle Manager cannot update when upgrading to version 3.6.4
- Application not available error during upgrade
- Upgrade of Platform UI (
zen) operand fails - IBM Cloud Pak foundational services InstallPlan fails during installation or upgrade
- Incorrect EDB Postgres operator environment variable configuration
- Upgrade process does not complete
- Constraints not satisfiable error during upgrade
- Upgrading Events Operator in foundational services version 3.17.x and earlier or 3.23.0 and later
- Operator installation or upgrade fails with DeadlineExceeded error
- Install strategy fails after upgrading OpenShift to 4.15.x
- Recovering an old version of IBM Cloud Pak foundational services