Comment 12 for bug 1871850

Reviewed: https://review.opendev.org/748123
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5eeb98cdb51dc0dadd43128d1d0ed7d497606ded
Submitter: Zuul
Branch: stable/ussuri

commit 5eeb98cdb51dc0dadd43128d1d0ed7d497606ded
Author: LIU Yulong <email address hidden>
Date: Sat Apr 11 08:41:28 2020 +0800

    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 12b9149e20665d80c11f1ef3d2283e1fa6f3b693)