Troubleshooting IBM Cloud Pak foundational services upgrade
Review the following frequently encountered upgrade errors:
- EDB operator to IBM PG operator migration fails because pods do not restart
- SAML configuration isn't retained after an upgrade
- Operator upgrade fails with the pod in
CrashLoopBackOffstatus- OLM known issue - Zookeeper pod hangs in a
CrashLoopBackOffstate - Operator installation hangs during upgrade
- Upgrade process does not complete
- Operator installation or upgrade fails with DeadlineExceeded error
- Operator installation or upgrade fails with exceeded progress deadline error
-
preload_data.shfails due to cert manager -
preload_data.shdoes not complete successfully - cp-console address is changed after CS operator is upgraded to v4, but IAM service is still in v3
- Upgrade from foundational services version 3.x to version 4.x fails due to custom certificate issue
- Administration console returns 404 after upgrading from 3.x to 4.x
- Install strategy fails after upgrading OpenShift to 4.15.x
- Intermittent looping occurs in large profiles
- ConfigMap fields are reset after an upgrade
- Invalid value error when updating the CommonService CR by using the
setup_tenant.shscript - Storage size configuration in the CommonService CR isn't applied to PostgreSQL
- EDB PostgreSQL cluster custom resource is not created during upgrade
- Events operator fails on OpenShift Container Platform
For more information on upgrading, see Upgrading foundational services.