Incorrect group name in conf when deprecated_group is not specified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.config |
Fix Released
|
Undecided
|
Tan Lin |
Bug Description
When an opt is defined with a deprecated_name alias but not with
deprecated_group, the generated conf file assumes 'DEFAULT' section.
i.e say we do :-
opt = cfg.StrOpt(
conf.register_
we get the following in the generated conf file :-
Deprecated group/name - [DEFAULT]
cinder_
Instead of,
Deprecated group/name - [glance_
cinder_
On contrary, when you register such an opt, the deprecated_name is
associated against the registered group. Thus, the generated conf
is not in sync.
We found this issue when generating glance-api conf's but this
could be affecting other projects as well.
Changed in oslo.config: | |
assignee: | nobody → Sabari Murugesan (smurugesan) |
Changed in oslo.config: | |
status: | New → In Progress |
Changed in oslo.config: | |
assignee: | Sabari Murugesan (smurugesan) → Tan Lin (tan-lin-good) |
Reviewed: https:/ /review. openstack. org/288804 /git.openstack. org/cgit/ openstack/ oslo.config/ commit/ ?id=77505c7a5a3 4efddc7bdd8b6cc d371963b5f360d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 77505c7a5a34efd dc7bdd8b6ccd371 963b5f360d
Author: Sabari Kumar Murugesan <email address hidden>
Date: Fri Mar 4 15:33:21 2016 -0800
Incorrect group name when deprecated_group is not specified
When an opt is defined with a deprecated_name alias but not with group, the generated conf file assumes 'DEFAULT' section.
deprecated_
i.e say we do :- 'cinder_ os_region_ name', deprecated_ name='os_ region_ name',
help=_ ('..')) register_ opt([opt] , group=' glance_ store')
opt = cfg.StrOpt(
conf.
we get the following in the generated conf file :- /os_region_ name os_region_ name = <None>
Deprecated group/name - [DEFAULT]
cinder_
Instead of, store]/ os_region_ name os_region_ name = <None>
Deprecated group/name - [glance_
cinder_
On contrary, when you register such an opt, the deprecated_name is
associated against the registered group. Thus, the generated conf
is not in sync.
We found this issue when generating glance-api conf's but this
could be affecting other projects as well.
Closes-Bug: #1554657 c3d74fb71e327e3 2d7def8ac5d
Co-Authored-By: Tan Lin<email address hidden>
Change-Id: I9577abec87b20f