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.
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.