Bug 1499175
| Summary: | [3.5] Deleted in use PVCs can break the scheduler | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jan Safranek <jsafrane> |
| Component: | Storage | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED ERRATA | QA Contact: | Liang Xia <lxia> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.0 | CC: | aos-bugs, aos-storage-staff, ccoleman, eparis, wehe |
| Target Milestone: | --- | ||
| Target Release: | 3.5.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1496256 | Environment: | |
| Last Closed: | 2017-10-25 13:08:02 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: | |||
| Bug Depends On: | 1496256, 1499176, 1499177, 1499178 | ||
| Bug Blocks: | 1499172, 1499174 | ||
|
Comment 1
Jan Safranek
2017-10-06 12:59:27 UTC
Checked on below version, # openshift version openshift v3.5.5.31.36 kubernetes v1.5.2+43a9be4 etcd 3.1.0 Verified new pvc can bind in another namespaces when the first one stuck at pending status due to re-create with the same pvc name. # oc get pv ; oc get pvc --all-namespaces NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM REASON AGE pvc-ec29ab1a-b007-11e7-b05c-42010af00047 1Gi RWO Delete Released 0xzlm/nfsc 8m pvc-f8f7465b-b007-11e7-b05c-42010af00047 1Gi RWO Delete Bound fyw1t/nfsc 8m regpv-volume 17G RWX Retain Bound default/regpv-claim 4h NAMESPACE NAME STATUS VOLUME CAPACITY ACCESSMODES AGE 0xzlm nfsc Pending noneexistone 0 8m default regpv-claim Bound regpv-volume 17G RWX 4h fyw1t nfsc Bound pvc-f8f7465b-b007-11e7-b05c-42010af00047 1Gi RWO 8m 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-2017:3049 |