Red Hat Bugzilla – Bug 1296326
unable to delete cinder volumes after deleting instance
Last modified: 2016-05-03 06:30:30 EDT
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.
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.
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
Nick, any updates on this case?
Did you escalate this issue to the HP? If not, please, do that.