Re: [openstack-dev] [neutron][oslo] Mitaka neutron-*aas are broken when --config-dir is passed

> On 25 May 2016, at 18:47, Armando M. wrote: > > > > On 25 May 2016 at 09:02, Brandon Logan wrote: > +1 > > This sounds like a sane plane. That magical config load caused me some > problems in the past when I didn't know about it, would be

Re: [openstack-dev] [neutron][oslo] Mitaka neutron-*aas are broken when --config-dir is passed

On 25 May 2016 at 09:02, Brandon Logan wrote: > +1 > > This sounds like a sane plane. That magical config load caused me some > problems in the past when I didn't know about it, would be glad to see > it go. I thought it being deprecated and removed was planned

Re: [openstack-dev] [neutron][oslo] Mitaka neutron-*aas are broken when --config-dir is passed

Excerpts from Ihar Hrachyshka's message of 2016-05-25 14:03:24 +0200: > Hi all, > > Our internal Mitaka testing revealed that neutron-server fails to start when: > - any neutron-*aas service plugin is enabled (in our particular case, it was > lbaas); > - --config-dir option is passed to the

[openstack-dev] [neutron][oslo] Mitaka neutron-*aas are broken when --config-dir is passed

Hi all, Our internal Mitaka testing revealed that neutron-server fails to start when: - any neutron-*aas service plugin is enabled (in our particular case, it was lbaas); - --config-dir option is passed to the process via CLI. Since RDO/OSP neutron-server systemd unit files use --config-dir