config generator generates invalid configuration file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Walt Boring |
Bug Description
The cinder's config generator generates an invalid configuration file. It put the options of DEFAULT section from external libraries to the last generated section of cinder.
An example:
#
# Options defined in cinder.....
#
....
#hash_algorithm
[profiler]
#
# Options defined in cinder.service
#
# If False fully disable profiling feature. (boolean value)
#profiler_
# If False doesn't trace SQL requests. (boolean value)
#trace_
#
# From oslo.log
#
# Print debugging output (set logging level to DEBUG instead of
# default WARNING level). (boolean value)
#debug = false
# Print more verbose output (set logging level to INFO instead of
# default WARNING level). (boolean value)
#verbose = false
As we can see, the options from oslo.log[1] are placed in the [profiler] section, but they should be in the [DEFAULT].
I propose to switch to using the oslo-config-
[1] https:/
Changed in cinder: | |
assignee: | nobody → Sergey Vilgelm (sergey.vilgelm) |
status: | New → In Progress |
Changed in cinder: | |
importance: | Undecided → High |
Changed in cinder: | |
assignee: | Sergey Vilgelm (sergey.vilgelm) → nobody |
Changed in cinder: | |
assignee: | nobody → Kendall Nelson (kjnelson) |
Changed in cinder: | |
assignee: | Kendall Nelson (kjnelson) → Jay Bryant (jsbryant) |
Changed in cinder: | |
assignee: | Jay Bryant (jsbryant) → Kendall Nelson (kjnelson) |
Changed in cinder: | |
assignee: | Kendall Nelson (kjnelson) → Walt Boring (walter-boring) |
Changed in cinder: | |
milestone: | none → liberty-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-rc1 → 7.0.0 |
Sergey,
Do you have a fix for this in progress, or something you are modeling it after. I had started with this patch in the last release and missed the Window for getting it in: https:/ /review. openstack. org/#/c/ 165431/ That first attempt at a design was not well received.
I was going to some checking to see how others had solved this. Appreciate any input you can give on your plan.
Thanks!
Jay