When l3 agent node is rebooted, if HA network port status is already
ACTIVE in DB, agent will get this status from server and then spawn
the keepalived (though l2 agent might not have wired the port),
resulting in multiple HA masters active at the same time.
To fix this, when the L3 agent starts up we can have it explicitly
set the port status to DOWN for all of the HA ports on that node.
Then we are guaranteed that when they go to ACTIVE it will be because
the L2 agent has wired the ports.
Closes-bug: #1597461
Change-Id: Ib0c8a71b6ff97e43a414f3db4882914b12170d53
(cherry picked from commit d730b1010277138136512eb6efb12ab893ca6793)
Reviewed: https:/ /review. openstack. org/473819 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=633b452e28b 7a95ced1917257c a0e200cbffa4ba
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit 633b452e28b7a95 ced1917257ca0e2 00cbffa4ba
Author: venkata anil <email address hidden>
Date: Mon Jun 5 09:56:18 2017 +0000
Set HA network port to DOWN when l3 agent starts
When l3 agent node is rebooted, if HA network port status is already
ACTIVE in DB, agent will get this status from server and then spawn
the keepalived (though l2 agent might not have wired the port),
resulting in multiple HA masters active at the same time.
To fix this, when the L3 agent starts up we can have it explicitly
set the port status to DOWN for all of the HA ports on that node.
Then we are guaranteed that when they go to ACTIVE it will be because
the L2 agent has wired the ports.
Closes-bug: #1597461 43a414f3db48829 14b12170d53 136512eb6efb12a b893ca6793)
Change-Id: Ib0c8a71b6ff97e
(cherry picked from commit d730b1010277138