yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

As said in comment #12, the "wrong" usage of oslo.config gets fixed in
Nova with the mentioned changes. As oslo.config released a fix for this,
I don't see the need to provide a temporary fix in Nova, that's why I
change the status to "won't fix".

** Changed in: nova
       Status: In Progress => Won't Fix

** Changed in: nova
     Assignee: Tin Lam (tl3438) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1568820

Title:
  Duplicate sections in generated config

Status in OpenStack Compute (nova):
  Won't Fix
Status in oslo.config:
  Fix Released

Bug description:
  nova.conf as generated by oslo.config (for nova f05bbb1279598fa82ff5694e35d9de96315b1916) contains duplicate neutron and xenserver sections
  # PYTHONPATH=. oslo-config-generator --config-file=etc/nova/nova-config-generator.conf ; grep "^\[" etc/nova/nova.conf.sample | sort | uniq -c | grep " 2 "
        2 [neutron]
        2 [xenserver]

  This appears to be because there groups are being registered with both
  oslo_config.cfg.OptGroup and str in places

  e.g. 
  http://git.openstack.org/cgit/openstack/nova/tree/nova/api/metadata/handler.py
      CONF.register_opts(metadata_proxy_opts, 'neutron')

  and
  http://git.openstack.org/cgit/openstack/nova/tree/nova/conf/neutron.py
      neutron_group = cfg.OptGroup('neutron', title='Neutron Options')
      conf.register_group(neutron_group)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1568820/+subscriptions