This bug was fixed in the package neutron - 2:17.0.0-0ubuntu3
---
neutron (2:17.0.0-0ubuntu3) groovy; urgency=medium
* d/p/ovn-fix-inconsistent-igmp-configuration.patch: Cherry-picked from
upstream stable/victoria to ensure flooding of unregistered multicast
packets to all p
Public bug reported:
$ ls -l /sys/class/net/
total 0
lrwxrwxrwx 1 root root0 Feb 26 21:51 bond0 ->
../../devices/virtual/net/bond0
-rw-r--r-- 1 root root 4096 Feb 26 21:51 bonding_masters
lrwxrwxrwx 1 root root0 Feb 26 21:51 enp5s0 ->
../../devices/pci:00/:00:01.4/:05:00.0/vi
This bug was fixed in the package neutron - 2:17.0.0-0ubuntu3~cloud0
---
neutron (2:17.0.0-0ubuntu3~cloud0) focal-victoria; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:17.0.0-0ubuntu3) groovy; urgency=medium
.
* d/p/ovn-fix-inconsistent-igmp-conf
This bug was fixed in the package neutron - 2:16.2.0-0ubuntu3~cloud0
---
neutron (2:16.2.0-0ubuntu3~cloud0) bionic-ussuri; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:16.2.0-0ubuntu3) focal; urgency=medium
.
* d/p/ovn-fix-inconsistent-igmp-config
I was trying to reproduce that issue today and I couldn't.
Looking at the code it seems for me that after Brian's change [1] those rules
are now added to the iptables_manager during creation of the router_info
instance. So it's way before ri.process() is really called. If there will be
any issue
This bug was fixed in the package nova - 2:20.5.0-0ubuntu1~cloud0
---
nova (2:20.5.0-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New stable point release for OpenStack Train (LP: #1915787).
* d/p/lp1892361.patch: Removed after change landed upstream.
.
nova (2:20.4.1-0u
Thanks for digging into the report. Based on your analysis, the VMT has
no plans to issue an advisory, since none of our supported releases is
considered vulnerable to this any longer. If new information is brought
to light which indicates there is still a means to exploit this flaw in
more recent
** Description changed:
+ [Impact]
+
When an isolated network using provider networks for tenants (meaning
without virtual routers: DVR or network node), metadata access occurs in
the qdhcp ip netns rather than the qrouter netns.
The following options are set in the dhcp_agent.ini file
Public bug reported:
In most of the functional tests there is no need to run
MaintenanceThread from the ovn mech driver. It caused a lot of error
logs in the job's output and may also cause some failures in some cases
from time to time.
** Affects: neutron
Importance: High
Assignee: Sla
Public bug reported:
Need to clean cache when router is down, otherwise the port forwarding
extension will skip all objects processing due to cache is hitting.
** Affects: neutron
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
We have a Ubuntu Ussari cloud deployed on Ubuntu 20.04 using the juju
charms from the 20.08 bundle (planning to upgrade soon).
The problem that is occuring that all l3 agents for routers using a
particular external network show up with their ha_state in standby.
I've tried re
11 matches
Mail list logo