configuration options from the [DEFAULT] section are not applied to multiple backends
Bug #1255593 reported by
Jay Bryant
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Wishlist
|
Unassigned | ||
devstack |
Fix Released
|
Undecided
|
Matt Riedemann |
Bug Description
It is expected that volume configurations options like 'volume_clear' that are set under the [DEFAULT] section will be inherited by multiple backends if the option is not set for the backend. Currently, however, the setting from the [DEFAULT] section is ignored and not set for multiple backends.
Changed in devstack: | |
status: | New → In Progress |
assignee: | nobody → Matt Riedemann (mriedem) |
Changed in devstack: | |
status: | In Progress → Fix Released |
Changed in cinder: | |
status: | New → Confirmed |
Changed in cinder: | |
status: | Confirmed → Triaged |
Changed in cinder: | |
assignee: | nobody → Yuriy Nesenenko (ynesenenko) |
Changed in cinder: | |
assignee: | Yuriy Nesenenko (ynesenenko) → nobody |
Changed in cinder: | |
status: | Triaged → Invalid |
To post a comment you must log in.
To me this seems like a big usability win for configuration unless we know of any reason to not do it. (I can't think of any.)
I've encountered multiple cases where people assume this will happen and don't get the right options into each backend section.