zalando / zalando/postgres-operator
Standby cluster bootsrap bug
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hello
I’m trying to bootstrap standby cluster.
All seems to be ok, but wal-g does not see backups, because there is error in env variable: /run/etc/wal-e.d/env-standby/AWS_REGION contains string loca instead of correct string fr-par, but there is correct value in /run/etc/wal-e.d/env/AWS_REGION.
It seems for me as some templating bug inside Operator, or maybe Spilo.
I digged through Operator and Spilo sources, but didnt get the exact place where there envs is filled.
- Operator version v1.6.3
- Kubernetes
- Production
- Bug report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Operator or Spilo populates /run/etc/wal-e.d/env-standby/AWS_REGION versus /run/etc/wal-e.d/env/AWS_REGION for Operator v1.6.3 on Kubernetes. Reproduce the standby bootstrap if possible and compare the generated values; done means the standby environment contains the complete fr-par value and wal-g sees the backups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100