yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #85744
[Bug 1871850] Re: [L3] existing router resources are partial deleted unexpectedly when MQ is gone
This bug was fixed in the package neutron - 2:12.1.1-0ubuntu4
---------------
neutron (2:12.1.1-0ubuntu4) bionic; urgency=medium
* Fix interrupt of VLAN traffic on reboot of neutron-ovs-agent:
- d/p/0001-ovs-agent-signal-to-plugin-if-tunnel-refresh-needed.patch (LP: #1853613)
- d/p/0002-Do-not-block-connection-between-br-int-and-br-phys-o.patch (LP: #1869808)
- d/p/0003-Ensure-that-stale-flows-are-cleaned-from-phys_bridge.patch (LP: #1864822)
- d/p/0004-DVR-Reconfigure-re-created-physical-bridges-for-dvr-.patch (LP: #1864822)
- d/p/0005-Ensure-drop-flows-on-br-int-at-agent-startup-for-DVR.patch (LP: #1887148)
- d/p/0006-Don-t-check-if-any-bridges-were-recrected-when-OVS-w.patch (LP: #1864822)
- d/p/0007-Not-remove-the-running-router-when-MQ-is-unreachable.patch (LP: #1871850)
-- Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx> Mon, 22 Feb
2021 16:55:40 +0000
** Changed in: neutron (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1871850
Title:
[L3] existing router resources are partial deleted unexpectedly when
MQ is gone
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive queens series:
Fix Committed
Status in Ubuntu Cloud Archive rocky series:
Fix Committed
Status in Ubuntu Cloud Archive stein series:
Fix Released
Status in Ubuntu Cloud Archive train series:
Fix Released
Status in Ubuntu Cloud Archive ussuri series:
Fix Released
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Fix Released
Status in neutron source package in Bionic:
Fix Released
Bug description:
(For SRU template, please see bug 1869808, as the SRU info there
applies to this bug also)
ENV: meet this issue on our stable/queens deployment, but master
branch has the same code logic
When the L3 agent get a router update notification, it will try to
retrieve the router info from DB server [1]. But at this time, if the
message queue is down/unreachable. It will get exceptions related
message queue. A resync action will be run then [2]. Sometimes, from
my personal experience, rabbitMQ cluster is not so much easy to
recover. Long time MQ recover time will cause the router info sync RPC
never get successful until it meets the max retry time [3]. So the bad
thing happens, L3 agent is trying to remove the router now [4]. It
basically shutdown all the existing L3 traffic of this router.
[1] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L705
[2] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L710
[3] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L666
[4] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L671
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1871850/+subscriptions
References