Postgres cluster instance is in the Fenced status

If Postgres cluster common-service-db instance is in the Fenced status, lift fencing to resolve the issue.

Symptom

You get an error in the logs.

Run the following command to view the logs:

oc logs -n <namespace-where-foundational services-operand-is-installed> -l k8s.enterprisedb.io/cluster=common-service-db

The following error is displayed in the logs:

{"level":"info","ts":"2024-09-19T06:56:22Z","msg":"Instance is fenced, won't start postgres right now","logging_pod":"common-service-db"}

Cause

Postgres cluster common-service-db instance is in a Fenced status.

Resolving the problem

Run the following command to lift fencing:

oc annotate cluster.postgresql.k8s.enterprisedb.io common-service-db k8s.enterprisedb.io/fencedInstances-

For more information, see Fencing in EDB Postgres documentation.