yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1490990@xxxxxxxxxxxxxxxxxx>]

No, it's not a packaging issue, it's a neutron bug.

Since
https://review.openstack.org/#/c/202207/23/neutron/services/provider_configuration.py,
neutron presumes that config-dir points to /etc/neutron. But oslo.config
allows to use multiple config-dir options. F.e. Delorean uses this to
allow users to configure their services by dropping a custom .conf file
into a pre-designated service dir, instead of modifying stock
neutron.conf and other files: https://github.com/openstack-
packages/neutron/blob/rpm-master/neutron-server.service#L8

So now, neutron fails to locate service conf file because config-dir
points to the latest config-dir argument and not /etc/neutron.

** Also affects: neutron
   Importance: Undecided
       Status: New

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

Title:
  acceptance: neutron fails to start server service

Status in neutron:
  New
Status in puppet-neutron:
  In Progress

Bug description:
  This is a new error that happened very lately, using RDO liberty
  packaging:

  With current state of beaker manifests, we have this error:
  No providers specified for 'LOADBALANCER' service, exiting

  Source: http://logs.openstack.org/50/216950/5/check/gate-puppet-
  neutron-puppet-beaker-rspec-dsvm-
  centos7/9e7e510/logs/neutron/server.txt.gz#_2015-09-01_12_40_22_734

  That means neutron-server can't start correctly.

  This is probably a misconfiguration in our manifests or a packaging
  issue in Neutron, because we don't have the issue in Trusty jobs.

  RDO packaging version: 7.0.0.0b3-dev606

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