keepalived can't perform failover if the l3 agent is down

Bug #1895950 reported by Alex Katz
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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)

Tags: l3-ha
Changed in neutron:
status: New → Confirmed
status: Confirmed → New
importance: Undecided → Medium
tags: added: l3-ha
Revision history for this message
LIU Yulong (dragon889) wrote :

L3-agent should be alive in "new-master" node to link up the gateway after this patch:

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

@LIU: yes, and I'm not sure how to deal with that since for me that is kind of regression in Neutron. But from the other hand, it's like that "by design" now and we had good reasons to do it that way.
So should we close this LP as "Won't fix" or do we want to maybe try to find some other solution for that?

Revision history for this message
Brian Haley (brian-haley) wrote :

This is similar to a bug filed a few years ago, where we noticed an issue with IPv6 RAs when the l3-agent was down. It *could* be moved into keepalived-state-change if someone wanted to take on that task, just not sure of the priority with shift towards OVN.

Revision history for this message
LIU Yulong (dragon889) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.