VolumeIsBusy and SnapshotIsBusy shouldn't be ignored
Bug #1413750 reported by
Ivan Kolodyazhny
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Rajat Dhasmana |
Bug Description
During volume or snapshot deletion we catch VolumeIsBusy [1] and SnapshotIsBusy [2] and ignore them setting a 'available' state.
At least, we need to try once more to run delete action.
Maybe, setting state to 'error-deleting' is also acceptable if N tries failed.
[1] https:/
[2] https:/
Changed in cinder: | |
status: | New → Confirmed |
Changed in cinder: | |
assignee: | nobody → Vilobh Meshram (vilobhmm) |
Changed in cinder: | |
status: | In Progress → New |
Changed in cinder: | |
assignee: | nobody → Rajat Dhasmana (whoami-rajat) |
To post a comment you must log in.
I agree, some things in progress I'd like to clean a lot of this up and have started with snapshot create. If I can get to the bottom of the seg-fault this introduces in the storwize tests I think we have a good general pattern to use to update all of the LVM calls.