a96ad52c7e
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
|
||
|---|---|---|
| .. | ||
| common | ||
| dhcp | ||
| l2 | ||
| l3 | ||
| linux | ||
| metadata | ||
| ovsdb | ||
| windows | ||
| __init__.py | ||
| test_agent_extensions_manager.py | ||
| test_resource_cache.py | ||
| test_rpc.py | ||
| test_securitygroups_rpc.py | ||