Public bug reported: The Keepalived config becomes inconsistent, missing some/all floating IP addresses on regeneration on the current master. Upon transition this results in floating IP addresses being left configured on the previous active master.
This occasionally results in network flaps for all addresses attached to that tenants router. Neutron L3 Agent checks what IPs are configured on the local interface before it adds the Floating IP addresses, as keepalived holds the configured state we need to check against keepalived not the system. ** Affects: neutron Importance: Undecided Assignee: Sachi King (nakato) Status: New ** Tags: juno-backport-potential l3-ha ** Changed in: neutron Assignee: (unassigned) => Sachi King (nakato) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1400217 Title: L3 HA keepalived config state becomes inconsistent when managing floating ips Status in OpenStack Neutron (virtual network service): New Bug description: The Keepalived config becomes inconsistent, missing some/all floating IP addresses on regeneration on the current master. Upon transition this results in floating IP addresses being left configured on the previous active master. This occasionally results in network flaps for all addresses attached to that tenants router. Neutron L3 Agent checks what IPs are configured on the local interface before it adds the Floating IP addresses, as keepalived holds the configured state we need to check against keepalived not the system. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1400217/+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