This is similar to a bug filed a few years ago, https://bugs.launchpad.net/neutron/+bug/1677279 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.
This is similar to a bug filed a few years ago, https:/ /bugs.launchpad .net/neutron/ +bug/1677279 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.