[Bug 1958863] Re: [SRU] neutron-l3-agent attempts to use non-existing --config-file=/etc/neutron/fwaas_driver.ini

[Corey Bryant]

** Description changed:

- Installing Openstack Xena following the official documentation for
- Ubuntu 20.04 (https://docs.openstack.org/install-guide/environment-
- packages-ubuntu.html) contains outdated init scripts for neutron, which
- cause neutron l3 agent to fail on startup.
+ [Impact]
+ Installing Openstack Xena following the official documentation for Ubuntu 20.04 (https://docs.openstack.org/install-guide/environment-packages-ubuntu.html) contains outdated init scripts for neutron, which cause neutron l3 agent to fail on startup.
  
+ [Test Case]
  Installing neutron with the following commands :
  
  add-apt-repository cloud-archive:xena
  apt update
  apt install -y neutron-server neutron-plugin-ml2 neutron-linuxbridge-agent neutron-l3-agent neutron-dhcp-agent neutron-metadata-agent
  
  will reproduce the issue. (Neutron m3 agent will fail with an exception
  of 'file not found /etc/neutron/fwaas_driver.ini'.).
  
  More information : https://bugs.launchpad.net/neutron/+bug/1958128.
+ 
+ [Regression Potential]
+ This is fixing a regression in the neutron package. neutron-fwaas support was removed in bug #1934129, however neutron-l3-agent wasn't updated to
+ deal with the removal of fwaas_driver.ini.
+ 
+ I don't foresee any regression issues with this fix if it tests
+ successfully, and I've already tested the fix prior to uploading to
+ jammy.
+ 
+ [Discussion]
+ This was reported against xena originally but affects all releases from victoria and above.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1958863

Title:
  [SRU] neutron-l3-agent attempts to use non-existing --config-
  file=/etc/neutron/fwaas_driver.ini

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in Ubuntu Cloud Archive wallaby series:
  Triaged
Status in Ubuntu Cloud Archive xena series:
  Triaged
Status in Ubuntu Cloud Archive yoga series:
  Triaged
Status in neutron package in Ubuntu:
  Triaged
Status in neutron source package in Hirsute:
  Won't Fix
Status in neutron source package in Impish:
  Triaged
Status in neutron source package in Jammy:
  Triaged

Bug description:
  [Impact]
  Installing Openstack Xena following the official documentation for Ubuntu 20.04 (https://docs.openstack.org/install-guide/environment-packages-ubuntu.html) contains outdated init scripts for neutron, which cause neutron l3 agent to fail on startup.

  [Test Case]
  Installing neutron with the following commands :

  add-apt-repository cloud-archive:xena
  apt update
  apt install -y neutron-server neutron-plugin-ml2 neutron-linuxbridge-agent neutron-l3-agent neutron-dhcp-agent neutron-metadata-agent

  will reproduce the issue. (Neutron m3 agent will fail with an
  exception of 'file not found /etc/neutron/fwaas_driver.ini'.).

  More information : https://bugs.launchpad.net/neutron/+bug/1958128.

  [Regression Potential]
  This is fixing a regression in the neutron package. neutron-fwaas support was removed in bug #1934129, however neutron-l3-agent wasn't updated to
  deal with the removal of fwaas_driver.ini.

  I don't foresee any regression issues with this fix if it tests
  successfully, and I've already tested the fix prior to uploading to
  jammy.

  [Discussion]
  This was reported against xena originally but affects all releases from victoria and above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1958863/+subscriptions