Bug 1388311 - PV is not annotated with its provisioner, thus can't be automatically deleted when StorageClass is gone
Summary: PV is not annotated with its provisioner, thus can't be automatically deleted...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Bradley Childs
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-25 05:45 UTC by Jianwei Hou
Modified: 2016-10-25 08:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-25 08:38:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jianwei Hou 2016-10-25 05:45:40 UTC 
Description of problem:
The provisioned PV is not annotated with its provisioner, therefore if its StorageClass is deleted, it can not be automatically deleted by deleting its bound PVC.

Version-Release number of selected component (if applicable):
openshift v3.4.0.15+9c963ec
kubernetes v1.4.0+776c994
etcd 3.1.0-alpha.1

How reproducible:
Always

Steps to Reproduce:
1. Prepare GlusterFS cluster and heketi
2. Create StorageClass, then create a PVC, a PV is automatically provisioned and bounds to the PVC
3. oc get pv -o yaml, 
4. Delete the StorageClass
5. Delete the PVC

Actual results:
After step 3: PV is not annotated with the GlusterFS parameters

After step 5: PV becomes 'Failed'

Expected results:
After step 5: PV should be deleted.

Additional info:
Comment 1 Jan Safranek 2016-10-25 08:38:09 UTC 
As result of https://github.com/kubernetes/kubernetes/issues/34822, StorageClass now needs to be present at the point when Gluster volume is being deleted.

Passing references to secrets via PV annotations is not secure.
Note You need to log in before you can comment on or make changes to this bug.