Public bug reported: Using Rocky, with OVS. Live migrated a VM on regular VLAN based provider network. Network connectivity was stopped, no GARP packets observed on tcpdump. Things started working after VM initiated traffic, causing MAC to be relearned.
Looking at the code, send_ip_addr_adv_notif(), in ip_lib.py is responsible for using arping utility to send out a GARP. But this is only referenced in l3-agent code. This is a provider network. No routers, no floating IPs. I see this very old bug in OVN: https://bugs.launchpad.net/networking-ovn/+bug/1545897 But we are not using OVN, and that fix was fixed in OVN code itself. This is Openstack with OVS agent. How is live migration and GARP handled for fixed IPs? ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1866139 Title: GARP not sent on provider network after live migration Status in neutron: New Bug description: Using Rocky, with OVS. Live migrated a VM on regular VLAN based provider network. Network connectivity was stopped, no GARP packets observed on tcpdump. Things started working after VM initiated traffic, causing MAC to be relearned. Looking at the code, send_ip_addr_adv_notif(), in ip_lib.py is responsible for using arping utility to send out a GARP. But this is only referenced in l3-agent code. This is a provider network. No routers, no floating IPs. I see this very old bug in OVN: https://bugs.launchpad.net/networking-ovn/+bug/1545897 But we are not using OVN, and that fix was fixed in OVN code itself. This is Openstack with OVS agent. How is live migration and GARP handled for fixed IPs? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1866139/+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