commit 5b7d444b3176dd3f8bf166d332781ac93670a51d
Author: LIU Yulong <email address hidden>
Date: Tue Dec 25 17:45:05 2018 +0800
Not set the HA port down at regular l3-agent restart
If l3-agent was restarted by a regular action, such as config change,
package upgrade, manually service restart etc. We should not set the
HA port down during such scenarios. Unless the physical host was
rebooted, aka the VRRP processes were all terminated.
This patch adds a new RPC call during l3 agent init, it will try to
retrieve the HA router count first. And then compare the VRRP process
(keepalived) count and 'neutron-keepalived-state-change' count
with the hosting router count. If the count matches, then that
set HA port to 'DOWN' state action will not be triggered anymore.
Reviewed: https:/ /review. openstack. org/627285 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=5b7d444b317 6dd3f8bf166d332 781ac93670a51d
Committed: https:/
Submitter: Zuul
Branch: master
commit 5b7d444b3176dd3 f8bf166d332781a c93670a51d
Author: LIU Yulong <email address hidden>
Date: Tue Dec 25 17:45:05 2018 +0800
Not set the HA port down at regular l3-agent restart
If l3-agent was restarted by a regular action, such as config change,
package upgrade, manually service restart etc. We should not set the
HA port down during such scenarios. Unless the physical host was
rebooted, aka the VRRP processes were all terminated.
This patch adds a new RPC call during l3 agent init, it will try to keepalived- state-change' count
retrieve the HA router count first. And then compare the VRRP process
(keepalived) count and 'neutron-
with the hosting router count. If the count matches, then that
set HA port to 'DOWN' state action will not be triggered anymore.
Closes-Bug: #1798475 11a640a79896337 2c8d91a06a8
Change-Id: I5e2bb64df0aaab