This bug was fixed in the package neutron - 2:16.0.0-0ubuntu0.20.04.2
---
neutron (2:16.0.0-0ubuntu0.20.04.2) focal; urgency=medium
* Ensure OVS and linuxbridge cleanup systemd units are not restarted
on upgrade or started on install (LP: #1885264):
- d/rules: Pass
This bug was fixed in the package neutron -
2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0
---
neutron (2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0) focal-victoria;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron
This bug was fixed in the package neutron -
2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0
---
neutron (2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0) focal-victoria;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron
This bug was fixed in the package neutron -
2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0
---
neutron (2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0) focal-victoria;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron
This bug was fixed in the package neutron -
2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0
---
neutron (2:17.0.0~git2020070709.792f4efce9-0ubuntu1~cloud0) focal-victoria;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron
bionic-ussuri/proposed testing:
neutron-ovs-cleanup not restarted on package upgrade:
$ sudo apt install --reinstall neutron-openvswitch-agent
...
$ sudo systemctl status neutron-ovs-cleanup
● neutron-ovs-cleanup.service - OpenStack Neutron OVS cleanup
Loaded: loaded
focal testing:
neutron-ovs-cleanup (on first install from update pocket)
Active: active (exited) since Wed 2020-07-08 16:36:12 UTC; 32s ago
neutron-ovs-cleanup (after package upgrade to -proposed version)
Active: active (exited) since Wed 2020-07-08 16:36:12 UTC; 1min 18s
ago
task
** Changed in: cloud-archive
Status: In Progress => Fix Committed
** Changed in: cloud-archive/ussuri
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello James, or anyone else affected,
Accepted neutron into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:16.0.0-0ubuntu0.20.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package neutron - 2:16.0.0-0ubuntu3
---
neutron (2:16.0.0-0ubuntu3) groovy; urgency=medium
* Ensure OVS and linuxbridge cleanup systemd units are not restarted
on upgrade or started on install (LP: #1885264):
- d/rules: Pass --no-stop-on-upgrade to
Updated packages upload for groovy and for focal (for SRU team review).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885264
Title:
neutron-ovs-cleanup runs on package upgrade
To manage
** Changed in: neutron (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: neutron (Ubuntu Groovy)
Status: Triaged => In Progress
** Changed in: neutron (Ubuntu Focal)
Assignee: (unassigned) => James Page (james-page)
** Changed in: neutron (Ubuntu Groovy)
** Description changed:
== Impact ==
Upgrades to OpenStack Ussuri will result in service disruption to the
network datapath for instances and other virtual networking concepts.
== Test Case ==
+ Standalone
+
+ (UCA)
+ add-apt-repository cloud-archive:train
+ apt install
** Description changed:
+ == Impact ==
+
+ Upgrades to OpenStack Ussuri will result in service disruption to the
+ network datapath for instances and other virtual networking concepts.
+
+ == Test Case ==
+
+ Deploy OpenStack Train (using Juju charms)
+ Create networking, boot instances and
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron/+git/neutron/+merge/385247
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885264
Title:
Some additional information regarding how the bug was found:
During the upgrade the ovs runs, deleting the ports. They don't come
back, even after restarting the services, which suggests an issue within
the neutron openvswitch agent in terms of re-creating ports that have
been deleted.
from the
** Changed in: cloud-archive/victoria
Status: New => Triaged
** Changed in: cloud-archive/ussuri
Status: New => Triaged
** Changed in: cloud-archive/ussuri
Importance: Undecided => Critical
** Changed in: cloud-archive/victoria
Importance: Undecided => Critical
--
You
17 matches
Mail list logo
