Comment 26 for bug 1597461

Revision history for this message
venkata anil (anil-venkata) wrote :

https://review.openstack.org/#/c/357458/ can't completely resolve the issue.

I have a two node setup. node2 is hosting some ha master routers. I am trying to reboot node2. Before the reboot, 'status' for all ha network ports on this node2 is 'ACTIVE'(same status is stored in DB). I have rebooted the node2.
1) before the node2 is up, keepalived on host1 turned some routers to master
2) when node2 is up, he will try to run l2 and l3 agents.
3) then, l3 agent through fetch_and_sync_all_routers gets all ha router ports it was hosting, but with status 'ACTIVE' as this status was stored in DB before shutdown. Now l3 agent will spawn keepalived as ha network port status is active, though l2 agent has not wired the port(some times).
As wiring is not yet done on node2, keepalived on node2 for the ha router will transition it to master.