1367500 – Deleting a project, after creating an pod that creates a PVC, leaves PV broken sometimes

Bug 1367500 - Deleting a project, after creating an pod that creates a PVC, leaves PV broken sometimes

Summary: Deleting a project, after creating an pod that creates a PVC, leaves PV broke...

Keywords:
Status:	CLOSED WORKSFORME
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage
Sub Component:
Version:	3.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	medium
Target Milestone:	---
Target Release:	---
Assignee:	hchen
QA Contact:	Jianwei Hou
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2016-08-16 14:28 UTC by Eric Jones
Modified:	2019-12-16 06:22 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2016-08-17 13:21:07 UTC
Target Upstream Version:

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

Description Eric Jones 2016-08-16 14:28:18 UTC

Description of problem:
If a project is deleted shortly after creating an app/pod that creates a PVC that binds a PV occasionally leaves the PV in an error state.

Steps to Reproduce:
1. Create project
2. create mysql pod from template [0] or any other pod that creates a PVC
3. check claim status 
4. delete project
5. check volume to see state 


[0] oc new-app --template=mysql-persistent -p DATABASE_SERVICE_NAME=ericdb,MYSQL_USER=eric,MYSQL_DATABASE=eric


Actual results:
Sometimes the PV is in an error state and sometimes it is properly released.

Expected results:
Always release the PV.

Comment 1 hchen 2016-08-16 20:22:14 UTC

does it happen in openshift 3.3 with kubernetes 1.3.4?

Comment 2 Jianwei Hou 2016-08-17 03:06:22 UTC

I'm using a cinder volume for my PV with reclaim policy 'Retain'. After the project is deleted, PV is Released. Tried 3 times, didn't run into the unexpected state.

Test env:
openshift v3.3.0.19
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git

Comment 3 hchen 2016-08-17 13:21:07 UTC

Thanks. I close it for now. if it is still a problem, please reopen it.

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