Troubleshooting IBM Cloud Pak foundational services install
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 fresh installation errors.
- General troubleshooting and workarounds
- An
OperandRequestinstance has no status - Status of
common-service-dbEDB PostgreSQL cluster custom resource is stuck in theSetting up primarystate or no state - EDB PostgreSQL instance is in the
Fencedstatus - EDB PostgreSQL instance is missing the
StorageClassvalue - Operator shows Pending status in a namespace - OLM known issue
- Uninstallation is not successful
- IBM foundational service Operator fails to initialize resources
- Mirroring images to the local registry fails in an air-gapped environment
- Skopeo failure in air-gapped installation script
- Pushing images to a single namespace in an air-gapped environment
- 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
- Timeout error when retrieving CASEs
- ImageContentSourcePolicy creation fails
- Operator installation or upgrade fails with DeadlineExceeded error
- Operator installation or upgrade fails with exceeded progress deadline error
- OLM is unable to generate new install plans
- Customization of the CommonService CR is reverted by the IBM Cloud Pak operator
- Troubleshooting catalog issues
Note: When you encounter issues during re-installation, perform a clean-up first.