[Bug 1934129] Re: disable neutron-fwaas for >= victoria
Edward Hope-Morley
1934129 at bugs.launchpad.net
Tue Oct 19 21:09:43 UTC 2021
Deployed hirsute-wallaby with -proposed and looks good to me:
$ juju run -a neutron-gateway -- dpkg -l| grep fwaas
$ juju run -a neutron-openvswitch -- dpkg -l| grep fwaas
$ juju run -a neutron-api -- dpkg -l| grep neutron-common
ii neutron-common 2:18.1.1-0ubuntu2 all Neutron is a virtual network service for Openstack - common
$ openstack extension list 2>&1| egrep "fwaas|fire"
$
Created a vm and can ping it's fip.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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 Committed
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 Committed
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
More information about the Ubuntu-openstack-bugs
mailing list