LVM Snapshot can't be deleted if backend lv is inactive
Bug #1602078 reported by
Nate Potter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
This seems like it's likely an issue for any driver rather than just LVM, but I have LVM enabled. I created a volume and snapshot, and then ended up manually deleting the snap with lv commands so that cinder didn't know about it. Then when trying to delete the snapshot with Cinder using the force param, it's impossible to remove the entry from Cinder's DB, because if a VolumeBackendAp
Changed in cinder: | |
assignee: | nobody → Nate Potter (ntpttr) |
summary: |
- Delete volume status checks don't work + LVM Snapshot can't be deleted if backend lv is removed |
description: | updated |
summary: |
- LVM Snapshot can't be deleted if backend lv is removed + LVM Snapshot can't be deleted if backend lv is inactive |
To post a comment you must log in.
After looking into this a little more, it seems that the problem isn't if the snapshot has been deleted with lvremove, it's when the snapshot is inactive. In this paste I deactivate the source volume for the snap, display both showing that it's inactive and not available, and then try to delete it.
http:// paste.openstack .org/show/ 531020/