Volume API response should list dependent snapshots
Bug #1111839 reported by
Gabriel Hurley
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Medium
|
Ivan Kolodyazhny |
Bug Description
A volume cannot be deleted if it has dependent snapshots, yet when doing a doing a GET /volumes/ or even a GET /volumes/detail there's no indication that the volume has dependent snapshots, let alone which ones they are. Thereby the only way to discover that a volume has snapshots which depend on it is to attempt to delete and have it fail, or to list all snapshots and see if the volume's id appears anywhere. This is a terrible user experience.
Changed in cinder: | |
status: | New → Triaged |
assignee: | nobody → Mike Perez (thingee) |
Changed in cinder: | |
assignee: | Mike Perez (thingee) → xiaoxi_chen (xiaoxi-chen) |
status: | Triaged → In Progress |
Changed in cinder: | |
assignee: | Xiaoxi Chen (xiaoxi-chen) → nobody |
status: | In Progress → Triaged |
tags: | added: api low-hanging-fruit |
Changed in cinder: | |
assignee: | nobody → Liusheng (liusheng) |
Changed in cinder: | |
importance: | Undecided → Medium |
Changed in cinder: | |
milestone: | none → kilo-3 |
Changed in cinder: | |
milestone: | kilo-3 → none |
To post a comment you must log in.
Mike, you have a plan to address this bug? I am willing to contribute to this issue, and want to discuss the possible directions to address it.