Bug 1339051
Summary: | AWS EBS Volume and GCE PD should be unmounted after the pod is deleted, containerised environment only | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Weihua Meng <wmeng> |
Component: | Storage | Assignee: | hchen |
Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2.0 | CC: | aos-bugs, chaoyang, jhou, lxia, tdawson, wmeng |
Target Milestone: | --- | Keywords: | NeedsTestCase |
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:33:10 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
Weihua Meng
2016-05-24 04:10:52 UTC
Some logs from /var/log/messages when I using dynamic provisioned ebs volume, and create pod , after delete pod and pvc, the pv became Released then Failed status May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.455883 1 persistentvolume_claim_binder_controller.go:194] Synchronizing PersistentVolume[pv-aws-bx6cj], current phase: Released May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.476849 1 persistentvolume_recycler_controller.go:149] PersistentVolume[pv-aws-bx6cj] retrying recycle after timeout May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.476862 1 persistentvolume_recycler_controller.go:168] Reclaiming PersistentVolume[pv-aws-bx6cj] May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.476868 1 persistentvolume_recycler_controller.go:271] Deleting PersistentVolume[pv-aws-bx6cj] May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.476923 1 log_handler.go:33] AWS request: ec2 DeleteVolume May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.497749 1 reflector.go:366] /builddir/build/BUILD/atomic-openshift-git-0.a4463d9/_thirdpartyhacks/src/github.com/openshift/openshift-sdn/plugins/osdn/registry.go:448: Watch close - *api.Node total 60 items received May 24 01:34:36 ip-172-18-8-74 docker: I0524 01:34:36.693880 1 aws_util.go:117] Error deleting EBS Disk volume aws://us-east-1d/vol-bc28a919: error deleting EBS volumes: VolumeInUse: Volume vol-bc28a919 is currently attached to i-afa01f35 is it the same as https://bugzilla.redhat.com/show_bug.cgi?id=1335293? the following log seems so Error deleting EBS Disk volume aws://us-east-1d/vol-bc28a919: error deleting EBS volumes: VolumeInUse: Volume vol-bc28a919 is currently attached to i-afa01f35 This bug is concerning releasing the EBS. Bug 1335293 seems to be allocating volume problems. From user view, they are different. The root cause could be the same, but may be different. GCE PD has same issue. Fix is proposed to kubernetes https://github.com/kubernetes/kubernetes/pull/27380 This has been merged and is in OSE v3.3.0.9 or newer. Fixed. openshift v3.3.0.9 kubernetes v1.3.0+57fb9ac etcd 2.3.0+git set up containerized OpenShift. follow repo steps. got expected results: 5. the volume does not mount on the host. 6. the volume is in available state. 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 |