If You stopped L3 agent and keepalived process together, than keepalived from
other node will decide to be new master and L3 agent on this other node will
configure everything for router. That is how failover works.
But in such case there is nothing what could do cleaning of router's config on
"old" node (control01 in Your case) as You just stopped L3 agent there. So IMO
this is not an neutron issue as neutron works here as expected.
Maybe Kolla shouldn't run keepalived processes for routers in same container as
L3 agent?
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1845900
Title:
ha router appear double vip
Status in neutron:
Invalid
Bug description:
Environment:
Deploy with kolla has three controler.
Action:
select one router, and router's vip in control01.
execute docker stop neutron_l3_agent in control01
Found:
control01 and control02 both have vip.
I suspect that the neutron account does not have permission to send a signal
to keepalived. causes keepalived to withdraw forcibly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1845900/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
