manage existing doesn't honor default volume type
Bug #1529636 reported by
Michal Dulko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
manage_existing calls are defaulting to volume_type=None in case the volume type isn't specified in the request. In my opinion we should have similar behavior as in case of create - default to the default_volume_type from configuration.
Changed in cinder: | |
assignee: | nobody → Michal Dulko (michal-dulko-f) |
status: | New → In Progress |
Changed in cinder: | |
assignee: | Michal Dulko (michal-dulko-f) → Nate Potter (ntpttr) |
Changed in cinder: | |
assignee: | Nate Potter (ntpttr) → nobody |
Changed in cinder: | |
assignee: | nobody → Nate Potter (ntpttr) |
Changed in cinder: | |
assignee: | Nate Potter (ntpttr) → Michal Dulko (michal-dulko-f) |
To post a comment you must log in.
What if the default volume type has an extra spec of "{'volume_ backend_ name': 'x'}" but we're managing the volume from backend 'y'? It seems safer to me to keep the current behavior and do a retype if needed.