Bug 1305546 - Dynamic provisioner can create several Persistent Volume for one claim
Summary: Dynamic provisioner can create several Persistent Volume for one claim
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Storage
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jan Safranek
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 14:46 UTC by Jan Safranek
Modified: 2016-05-12 17:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 17:15:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Safranek 2016-02-08 14:46:15 UTC
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 08:35:19 UTC
Merged to OpenShift.

Comment 3 Chao Yang 2016-02-26 03:08:43 UTC
Test is passed on 
oc v1.1.3-282-gc423082
kubernetes v1.2.0-alpha.7-703-gbc4550d


Note You need to log in before you can comment on or make changes to this bug.