Bug 1332707
Summary: | Persistent volumes gets deleted the claim attached still shows as bound to PV | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ryan Howe <rhowe> |
Component: | Storage | Assignee: | Jan Safranek <jsafrane> |
Status: | CLOSED ERRATA | QA Contact: | Wenqi He <wehe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.0 | CC: | aos-bugs, jsafrane, lxia, mawong, tdawson, wehe |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | 1339041 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-27 09:31:47 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
Ryan Howe
2016-05-03 20:56:43 UTC
Also happens on openshift 3.2.0.20 This should be fixed by this PR: https://github.com/kubernetes/kubernetes/pull/24331 When someone deletes a PV that is bound to a PVC, the PVC enters phase "Lost" and emits an event - the PVC has lost its PV and user has effectively lost his data. When another PV with the same name appears again, PVC moves back from "Lost" to "Bound". Added test case and tried to verify, this issue still repro on below version openshift v3.2.1.1-1-g33fa4ea kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 Jan, This hasn't been backported to ose or even origin has it? It's fixed only in upstream Kubernetes (upcoming 1.3) and it will land in Origin in upcoming rebase. can't reproduce in Kubernetes 1.3. This bug has been fixed on below version: openshift v3.3.0.9 kubernetes v1.3.0+57fb9ac etcd 2.3.0+git Changing the status to verified. 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-2016:1933 |