Bug 1347212
Summary: | Long time to delete the persist volume with reclaim policy "Delete" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenqi He <wehe> |
Component: | Storage | Assignee: | hchen |
Status: | CLOSED ERRATA | QA Contact: | Wenqi He <wehe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2.0 | CC: | aos-bugs, bchilds, jhou, lxia, mawong, tdawson, wehe |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-27 09:34:05 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
Wenqi He
2016-06-16 10:04:06 UTC
I have another way to reproduce it. It also takes a long time to delete the volume. 1. Create a dynamic PVC which provisions and binds a PV 2. Create a Pod referencing this PVC 3. When the Pod is running, delete this PVC 4. Get Pod status, Pod is still 'Running', volume is still attached to the node. But PVC and PV are deleted. 5. Delete the Pod and wait to see whether the provisioned volume will be deleted from the IaaS console. Result: Volume will eventually be deleted, but it takes a pretty long time(over 15 minutes). this is likely fixed in kubernetes 1.3 with the new persistent volume controller, where sync time is much shorter. Could not reproduce in kubernetes 1.3, pv was already deleted by the time I did get pv after deleting pod & pvc. Verified with below version: openshift v3.3.0.16 kubernetes v1.3.0+507d3a7 etcd 2.3.0+git This bug is fixed, after I delete the pod and pvc, the pv is deleted by the time I deleted pvc. Thanks. Moving to verified per @Wenqi He comments. 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 |