yahoo-eng-team team mailing list archive

[Jamie Lennox <jamielennox@xxxxxxxxx>]

Public bug reported:

When fetching the service_providers the code looks like [1]. So if the cfg.CONF.service_providers.service_provider field is empty we will always get a deprecation warning even if there is nothing actually configured in the neutron_*.conf files.
In the event that you have CONF.fatal_deprecations on this halts the program. 

I'm still going through to see what this value should be, but even if
it's an empty list it shouldn't fail with an incorrect deprecation
warning.

[1]
https://github.com/openstack/neutron/blob/1628fb72f8fbac15110713530728a03e8e4bd0f5/neutron/services/provider_configuration.py#L112-L122

** Affects: neutron
     Importance: Undecided
     Assignee: Jamie Lennox (jamielennox)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1633293

Title:
  Deprecation warning when service_providers empty

Status in neutron:
  In Progress

Bug description:
  When fetching the service_providers the code looks like [1]. So if the cfg.CONF.service_providers.service_provider field is empty we will always get a deprecation warning even if there is nothing actually configured in the neutron_*.conf files.
  In the event that you have CONF.fatal_deprecations on this halts the program. 

  I'm still going through to see what this value should be, but even if
  it's an empty list it shouldn't fail with an incorrect deprecation
  warning.

  [1]
  https://github.com/openstack/neutron/blob/1628fb72f8fbac15110713530728a03e8e4bd0f5/neutron/services/provider_configuration.py#L112-L122

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