LIU Yulong a96ad52c7e Not remove the running router when MQ is unreachable ... When the L3 agent get a router update notification, it will try to retrieve the router info from neutron server. But at this time, if the message queue is down/unreachable. It will get exceptions related message queue. The resync actions will be run then. Sometimes, rabbitMQ cluster is not so much easy to recover. Then Long time MQ recover time will cause the router info sync RPC never get successful until it meets the max retry time. Then the bad thing happens, L3 agent is trying to remove the router now. It basically shutdown all the existing L3 traffic of this router. This patch directly removes the final router removal action, let the router run as it is. Closes-Bug: #1871850 Change-Id: I9062638366b45a7a930f31185cd6e23901a43957 (cherry picked from commit 12b9149e20)		2020-08-26 07:00:55 +00:00
..
common	Increase log information when a RootHelperProcess fails	2020-04-21 17:12:29 +00:00
contrib	Conntrack Helper - Plugin	2019-08-29 10:41:04 +02:00
etc	Convert policy.json into policy-in-code	2018-12-13 20:37:53 +00:00
fullstack	Increase waiting time for network rescheduling	2020-04-08 11:57:11 +00:00
functional	Merge "String to byte conversion should provide the encoding type" into stable/train	2020-08-20 04:59:27 +00:00
unit	Not remove the running router when MQ is unreachable	2020-08-26 07:00:55 +00:00
var	…
__init__.py	Avoid eventlet monkey patching for the tempest plugin	2016-04-29 22:47:24 -05:00
base.py	Reset timeout exception in DietTestCase when retrying	2020-02-04 16:51:12 +00:00
post_mortem_debug.py	…
tools.py	consume WarningsFixture from neutron-lib	2019-07-09 08:32:33 -06:00