Bug 1432875
| Summary: | Unable to deploy postgresql | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kam Kej <albertus85> |
| Component: | openshift-controller-manager | Assignee: | Michal Fojtik <mfojtik> |
| Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.11.0 | CC: | aos-bugs, bparees, erich, xtian |
| Target Milestone: | --- | Keywords: | OnlineStarter |
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | workloads | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-24 08:08:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kam Kej
2017-03-16 09:58:47 UTC
Log says: --> Waiting up to 10m0s for pods in deployment postgresql-12 to become ready W0316 12:03:30.330212 1 reflector.go:330] github.com/openshift/origin/pkg/deploy/strategy/support/lifecycle.go:468: watch of *api.Pod ended with: too old resource version: 1001335033 (1001351708) error: update acceptor rejected postgresql-12: pods for deployment "postgresql-12" took longer than 600 seconds to become ready The watch error is being addressed in https://github.com/openshift/origin/pull/13279 The EBS volume seems like a deployment config with RWO volume (read-write-once) and rolling update strategy (which causes the same volume to be used more than once). I would suggest to switch to recreate strategy there. (In reply to Michal Fojtik from comment #2) > The watch error is being addressed in > https://github.com/openshift/origin/pull/13279 > > The EBS volume seems like a deployment config with RWO volume > (read-write-once) and rolling update strategy (which causes the same volume > to be used more than once). I would suggest to switch to recreate strategy > there. Yes, access mode is set to RWO. But strategy is already set to recreate. I don't know why, but storage status is: Bound to volume pvc-...., even if I stop deployment. confirmed with v3.11.141, can't reproduce this issue again: postgresql-2-h5hs2 1/1 Running 0 3m [zhouying@dhcp-140-138 Downloads]$ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE postgresql Bound pvc-f90401b0-c944-11e9-b47d-0e1b9a33172a 1Gi RWO gp2 1h [zhouying@dhcp-140-138 Downloads]$ oc get po NAME READY STATUS RESTARTS AGE postgresql-2-h5hs2 1/1 Running 0 4m [zhouying@dhcp-140-138 Downloads]$ oc get dc NAME REVISION DESIRED CURRENT TRIGGERED BY postgresql 2 1 1 config,image(postgresql:10) [zhouying@dhcp-140-138 Downloads]$ oc rollout latest dc/postgresql deploymentconfig.apps.openshift.io/postgresql rolled out [zhouying@dhcp-140-138 Downloads]$ oc get po NAME READY STATUS RESTARTS AGE postgresql-2-h5hs2 0/1 Terminating 0 5m postgresql-3-deploy 1/1 Running 0 3s [zhouying@dhcp-140-138 Downloads]$ oc get po NAME READY STATUS RESTARTS AGE postgresql-3-z65rv 1/1 Running 0 1m We can both deploy on web-console or by client. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2816 |