OK, let's mark this as "Won't Fix". And move to state change can be a
way to new install envrionment. But for running could, the existing
keepalived-state-change processes may need to re-create.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1895950
Title:
keepalived can't perform failover if the l3 agent is down
Status in neutron:
Won't Fix
Bug description:
If the l3 agent is down on the new master node of keepalived all the
interfaces remain down so no packets can pass through the new router.
The replication scenario is the following:
1. Shut down all the l3 agents
2. Kill the keepalived process on the master node
3. Try to access VM behind the HA router (it will fail)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1895950/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
