zalando / zalando/postgres-operator
pod labels error: still failing after 200 retries
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi Team,
While trying to create the postgres-cluster cluster takes ~5 mins to bind to the PVC due to which the postgres-cluster fails with below error,
time="2020-07-14T12:32:14Z" level=info msg="Event(v1.ObjectReference{Kind:\"postgresql\", Namespace:\"postgres-test\", Name:\"postgres-operator-cluster\", UID:\"cee078a3-0bea-4175-a6c8-7530590058ac\", APIVersion:\"acid.zalan.do/v1\", ResourceVersion:\"157085264\", FieldPath:\"\"}): type: 'Warning' reason: 'Sync' could not sync cluster: could not sync statefulsets: cluster is not ready: pod labels error: still failing after 200 retries"
Could you please suggest to increase the no of retries or the wait time till the PVC is bound and not face error.
Thanks
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 reproducing creation of the postgres-cluster and trace the pod-label retry path while the PVC remains unbound. Check how the operator handles the delayed PVC binding and the 200-retry limit; done means the cluster waits appropriately and does not fail with the pod labels error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100