Known issues and limitations for EDB Postgres

The following known issues and limitations apply to the EDB Postgres service.

Known Issues

After OCP upgrade from 4.14 to 4.15, the cloud-native-postgresql.v1.22.1 CSV (cluster service version) is in a failed state

After the OCP upgrade, it is observed that the CSV switches between failed, install ready, and pending states.

message: 'install strategy failed: rolebindings.rbac.authorization.k8s.io "postgresql-operator-controller-manager-1-18-7-service-auth-reader"

Applies to: 5.1

Identify the affected resources:

oc get csv -A | grep postgre
oc describe csv <failed cloud-native-postgresql.v1.18.7> -n <operator-namespace> | tail -n 10

Look for messages with the following phrases:

 message: 'install strategy failed: rolebindings.rbac.authorization.k8s.io "postgresql-operator-controller-manager-1-18-7-service-auth-reader"

If you see either of the preceding phrases in the log files, proceed to the next step.

Solution

If the LSN of the primary pod and the replica pod is different, delete the affected resource.

oc delete rolebinding -n kube-system postgresql-operator-controller-manager-1-18-7-service-auth-reader

Verify resource redeployment with appropriate labels indicating the Operational Level Management (OLM) management:

$ oc get rolebinding -n kube-system postgresql-operator-controller-manager-1-18-7-service-auth-reader -oyaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    olm.owner: cloud-native-postgresql.v1.18.7
    olm.owner.kind: ClusterServiceVersion
    olm.owner.namespace: cpd-operator
    operators.coreos.com/cloud-native-postgresql.cpd-operator: ""
   ...

Review the failed CSV:
The resolution is complete when the resource already exists message is not displayed. The installation process is complete when the deployment is in a ready state.