Bug 1305546

Summary: Dynamic provisioner can create several Persistent Volume for one claim
Product: OKD Reporter: Jan Safranek <jsafrane>
Component: StorageAssignee: Jan Safranek <jsafrane>
Status: CLOSED CURRENTRELEASE QA Contact: Jianwei Hou <jhou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.xCC: aos-bugs, bchilds, chaoyang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 13:15:51 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jan Safranek 2016-02-08 09:46:15 EST
There are two race conditions in dynamic provisioner that can have these results:

* two (or more) PersistentVolumes are created for a single claim, each with its own AWS EBS, GCE PD or Cinder volume.
* one PersistentVolumes is correctly created for a single claim, but several AWS EBS, GCE PD or Cinder volumes are created in the cloud.

In both cases, too many volumes in the cloud are created and they are not deleted when the claim is removed by the user.

Version-Release number of selected component (if applicable):
3.1

How reproducible:
<10%

Steps to reproduce:
https://trello.com/c/Mol8D2Gb/79-dynamic-provisioner-sometimes-creates-two-volumes-for-one-claim

Kubernetes PRs:
https://github.com/kubernetes/kubernetes/pull/19868
https://github.com/kubernetes/kubernetes/pull/20213
Comment 2 Jan Safranek 2016-02-24 03:35:19 EST
Merged to OpenShift.
Comment 3 chaoyang 2016-02-25 22:08:43 EST
Test is passed on 
oc v1.1.3-282-gc423082
kubernetes v1.2.0-alpha.7-703-gbc4550d