LVM: error_deleting status when deleting volume that does not exist on backend
Bug #1707004 reported by
Chuck Fouts
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
When deleting a volume, using the LVM driver, if the volume does not exist on the backend the driver throws an exception and status is set to error_deleting. Bug originally reported in Ocata.
tags: | added: drivers lvm |
To post a comment you must log in.
additional operations posted on pastebin here:
http:// paste.openstack .org/show/ 616719/
http:// paste.openstack .org/show/ 616728/
http:// paste.openstack .org/show/ 616731/
http:// paste.openstack .org/show/ 616746/
http:// paste.openstack .org/show/ 616750/
The problem came up after I deleted instances, when I could not delete the volumes this was not possible.
Openstack was installed through the packstack --allinone and because the default space was little, I created a loopback (/dev/loop1) I formatted device and made it to become a physical volume and extended the volume group created by default from the Packstack installation with new pv.