Bug 1296326

Summary:	unable to delete cinder volumes after deleting instance
Product:	Red Hat OpenStack	Reporter:	nalmond
Component:	openstack-cinder	Assignee:	Eric Harney <eharney>
Status:	CLOSED CANTFIX	QA Contact:	nlevinki <nlevinki>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 6)	CC:	eharney, nalmond, scohen, sgotliv, srevivo
Target Milestone:	---	Keywords:	ZStream
Target Release:	5.0 (RHEL 6)
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-03 10:30:30 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:

Description nalmond 2016-01-06 21:55:04 UTC

Description of problem:
About 20 instances were deleted. These instances had cinder volumes attached as boot disks. After these instances were deleted, the cinder volumes remained in the available state and cannot be deleted with cinder delete or cinder force-delete.

How reproducible:
Only happened once, new instances and volumes are unaffected

These volumes are still in this state and need to be deleted. A root cause is also needed to prevent this from happening again.

Comment 2 Eric Harney 2016-01-12 15:41:48 UTC

2016-01-05 09:33:52.382 8865 ERROR cinder.volume.drivers.san.hp.hp_3par_common [req-548ce6d4-d7ac-439e-b34e-110f7cd18461 Type S, SDIRed ZSJJL8E 176a89a535bc45b4aed8fed48196caa6 - - -] Conflict (HTTP 409) 34 - resource in use
2016-01-05 09:33:52.400 8865 ERROR cinder.volume.manager [req-548ce6d4-d7ac-439e-b34e-110f7cd18461 Type S, SDIRed ZSJJL8E 176a89a535bc45b4aed8fed48196caa6 - - -] Cannot delete volume e5549d78-2b94-4cbf-ba8a-2a3002c8342d: volume is busy

Comment 10 Sergey Gotliv 2016-02-16 06:22:43 UTC

Nick, any updates on this case?

Comment 14 Sergey Gotliv 2016-03-05 16:46:22 UTC

Nick,

Did you escalate this issue to the HP? If not, please, do that.