Bug 1318161 - OpenShift does not check PVs before binding them
Summary: OpenShift does not check PVs before binding them
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: ---
: ---
Assignee: Bradley Childs
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks: OSOPS_V3 1267746 1317577
TreeView+ depends on / blocked
 
Reported: 2016-03-16 08:08 UTC by Jan Safranek
Modified: 2019-10-10 11:33 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1313560
Environment:
Last Closed: 2016-03-17 20:44:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Jan Safranek 2016-03-16 08:31:16 UTC 
Thanks for pv and pvc json and pod details, it's really helpful!

From the json I can see:

- The PV was manually provided by cluster admin, it's not dynamically created.
- The PV references an AWS EBS volume that does not exists.

It seems to me that it's some stale PV - cluster admin deleted the volume in AWS console and forgot to remove appropriate OpenShift object.

OpenShift does not check when an external EBS volume does not exists at the time of binding. It assumes the cluster admin keeps PV objects in sync with AWS.

I think OpenShift should not check if external storage represented by a PV really exists - it would be pretty expensive, there may be thousands of PVs to check periodically. And an EBS volume can be deleted at any time, e.g. when a claim is already bound to corresponding OpenShift PV or even when a pod is running with the volume attached.
Note You need to log in before you can comment on or make changes to this bug.