Description of problem: When a PV is deleted the PVC that is bound to it never updates. The PVC still shows as bound to the deleted pv. When the pv is then created again, it shows as available and the PVC still shows as bound to it. Version-Release number of selected component (if applicable): 3.1.1.6 How reproducible: 100% Steps to Reproduce: 1. Create pv1 2. Create pvc1 3. Since we only have one pv the pvc will bind to it 4. Delete the PV 5. Recreate the PV Actual results: - After step 4 the PVC still shows a status of bound to the PV that was deleted. - After step 5 the PV shows a available and the PVC stays the same. Expected results: - After step 4 the PVC shows a status telling the user the PV was removed. - After step 5 the PV and PVC should bind
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