zalando / zalando/postgres-operator

No such file or directory: '/home/postgres/pgdata/pgroot/data/postgresql.conf' -> '/home/postgres/pgdata/pgroot/data/postgresql.base.conf'

Open
#2,151 7 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? On-prem, Rancher, RKE2, Kubernetes Version: v1.24.4
  • Are you running Postgres Operator in production? yes
  • Type of issue? [Bug report, question, feature request, etc.] Bug

Attempting to setup standby cluster in preperation to migrate away from bitnami/postgresql-ha on another cluster. Using same psql version, and have user+passwords setup correctly.

Replication of data seems to occur, disk space looks about the same. But then the starting of the node fails

FileNotFoundError: [Errno 2] No such file or directory: '/home/postgres/pgdata/pgroot/data/postgresql.conf' -> '/home/postgres/pgdata/pgroot/data/postgresql.base.conf'

I think pgpool was interfering and causing my initial troubles, hence the edits and hidden comments

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the standby-cluster startup with postgres-operator:v1.8.2 on Kubernetes and inspect the reported postgresql.conf to postgresql.base.conf failure. Compare the replication and startup sequence with the provided environment details; done means identifying the cause and confirming that the standby node starts successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.