How To
Summary
This issue can manifest in several ways:
You see a mismatch in the data between the replicas.
The database cluster is stuck in the Waiting for the instances to become active state.
To check the status of the database cluster, run:
oc get clusters.postgresql.k8s.enterprisedb.io \
-n ${PROJECT_CPD_INST_OPERANDS}
One or more of the database pods are in the CrashLoopBackOff state or are stuck in the Running state.
To check the status of the database pods, run:
oc get pods \
-n ${PROJECT_CPD_INST_OPERANDS} \
-l k8s.enterprisedb.io/podRole=instance
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSE9G0Q","label":"IBM Cloud Pak for AIOps"},"ARM Category":[{"code":"a8m0z0000001jFJAAY","label":"Watson AIOps"}],"ARM Case Number":"TS020149285","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.10.0;4.10.1;4.11.0;4.2.0;4.2.1;4.3.0;4.4.0;4.4.1;4.5.0;4.5.1;4.6.0;4.6.1;4.7.0;4.7.1;4.8.0;4.8.1;4.9.0;4.9.1"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
29 August 2025
UID
ibm17243570