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

[Steve Langasek]

The upload in the SRU queue for hirsute shows only that the dependency
on the python3-neutron-fwaas package has been dropped.  There are no
other references to fwaas in the package delta.  Please explain as part
of this SRU how, at the package level (rather than the charm level),
this upgrade affects users who previously had fwaas enabled in their
configs.

** Changed in: neutron (Ubuntu Hirsute)
       Status: Triaged => Incomplete

-- 
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/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 Committed
Status in OpenStack neutron-openvswitch charm:
  Fix Committed
Status in OpenStack openstack-dashboard charm:
  New
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in Ubuntu Cloud Archive wallaby series:
  Triaged
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Hirsute:
  Incomplete
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]

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