Error when deleting a volume with snapshots not surfaced well
Bug #1020326 reported by
Gabriel Hurley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Tihomir Trifonov |
Bug Description
It is illegal to delete a volume which has "dependent" snapshots; the snapshots must be deleted first. However, this message is not surfaced to the user leaving them with no explanation why the volume can't be deleted.
Sadly, there's no data returned by the API to indicate this fact *before* attempting the deletion, so I'm not sure what the best solution is.
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
It is interesting - the Volume object has a property 'snapshot_id' which is None, but the volume has snapshot. If Nova can somehow populate this with the snapshot id, we can hide the 'Delete' action for these volumes...