[Bug 1934129] Re: disable neutron-fwaas for >= victoria

[Chris MacNaughton]

This bug was fixed in the package neutron - 2:18.1.1-0ubuntu2~cloud0
---------------

 neutron (2:18.1.1-0ubuntu2~cloud0) focal-wallaby; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 neutron (2:18.1.1-0ubuntu2) hirsute; urgency=medium
 .
   * d/p/lp1934912-set-arp-entries-only-for-single-ip.patch: Cherry-pick
     upstream patch (LP: #1934912)
 .
 neutron (2:18.1.1-0ubuntu1) hirsute; urgency=medium
 .
   [ Corey Bryant ]
   * d/control: Drop neutron-fwaas dependency as it is no longer maintained
     (LP: #1934129).
   * d/p/revert-rely-on-worker-count-for-hashring-caching.patch: Dropped.
     Fixed upstream by https://review.opendev.org/c/openstack/neutron/+/800679
     in the 18.1.1 stable release.
 .
   [ Chris MacNaughton ]
   * New stable point release for OpenStack Wallaby (LP: #1943709).
   * d/p/series: Remove reference to removed patch.


** Changed in: cloud-archive/wallaby
       Status: Fix Committed => Fix Released

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

Title:
  disable neutron-fwaas  for >= victoria

Status in OpenStack Charm Guide:
  Fix Committed
Status in Charm Helpers:
  Fix Committed
Status in OpenStack neutron-api charm:
  Fix Released
Status in OpenStack neutron-gateway charm:
  Fix Released
Status in OpenStack neutron-openvswitch charm:
  Fix Released
Status in OpenStack openstack-dashboard charm:
  New
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive victoria series:
  Fix Committed
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Hirsute:
  Fix Released
Status in neutron source package in Impish:
  Fix Released

Bug description:
  [Description]
  The neutron-fwaas project is retired and there are no updates beyond 16.0.0. The neutron-api charm still enables it by default, and the package still installs it as a dependency, and it is currently broken so we should remove it from >= V and add an optional to disable it for earlier releases.

  [Test Case]
  The following SRU process was followed:
  https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

  In order to avoid regression of existing consumers, the OpenStack team
  will run their continuous integration test against the packages that
  are in -proposed. A successful run of all available tests will be
  required before the proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary
  of the executed tests. The OpenStack team members will not mark
  ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.

  [Discussion]
  For new deploys, binary package installs of neutron-l3-agent will no longer install the python3-neutron-fwaas dependency. The fwaas plugin isn't enabled by default. If a user wants to enable the fwaas plugin, they will still be able to, they will just need to manually install the python3-neutron-fwaas package

  Existing deployments that upgrade to the new package will continue to
  have python3-neutron-fwaas installed on the system, and therefore if
  they had the fwaas plugin enabled, it will still be enabled and the
  fwaas package will still be installed. Apt, however, will list the
  fwaas packages as being no longer required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-guide/+bug/1934129/+subscriptions