Bug 1318161

Summary:	OpenShift does not check PVs before binding them
Product:	OpenShift Container Platform	Reporter:	Jan Safranek <jsafrane>
Component:	Storage	Assignee:	Bradley Childs <bchilds>
Status:	CLOSED NOTABUG	QA Contact:	Jianwei Hou <jhou>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	agrimm, aos-bugs, bchilds, dakini, haowang, hchen, jeder, jhou, jsafrane, mmccomas, mwoodson, pep, sdodson, sten, swagiaal, wzheng, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1313560	Environment:
Last Closed:	2016-03-17 20:44:21 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:
Bug Depends On:
Bug Blocks:	1303130, 1267746, 1317577

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.