venkata anil 633b452e28 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 Change-Id: Ib0c8a71b6ff97e43a414f3db4882914b12170d53 (cherry picked from commit d730b10102)		2017-06-13 12:51:10 +00:00
..
agentnotifiers	Skip native DHCP notifications on status change	2017-02-18 13:24:13 +00:00
callbacks	Add missing module-level SUBNET ref	2017-01-25 19:29:51 -08:00
handlers	Set HA network port to DOWN when l3 agent starts	2017-06-13 12:51:10 +00:00
__init__.py	Remove invalid copyright headers under API module	2014-04-02 11:09:03 -07:00