yahoo-eng-team team mailing list archive

[Josias Montag <josias@xxxxxxxxxxx>]

Public bug reported:

In my network environment floating IPs are not reachable after live VM
migration. I am using the Mitaka release with neutron DVR.

1) spawn a VM
2) assign a floating IP
3) live migrate the VM
4) ping the floating IP 


Using tcpdump I identified the reason for this problem: There is no gratuitous ARP reply sent out by the new host after live migration. Thus the network switch sends the traffic to the old host.

If I manually send the GARP on the new host using:

root@compute-2:~# ip netns exec fip-a46e0978-6e87-43d4-85d3-1d7030cdaf49
arping -A -I fg-de83cc57-32 FLOATING_IP

the floating IP comes up again and everything works as expected.

Version:
Mitaka on Ubuntu Trusty
Kernel 3.19
Deployed using Fuel 9.0

** 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/1602436

Title:
  DVR: floating IP not reachable after live migration

Status in neutron:
  New

Bug description:
  In my network environment floating IPs are not reachable after live VM
  migration. I am using the Mitaka release with neutron DVR.

  1) spawn a VM
  2) assign a floating IP
  3) live migrate the VM
  4) ping the floating IP 

  
  Using tcpdump I identified the reason for this problem: There is no gratuitous ARP reply sent out by the new host after live migration. Thus the network switch sends the traffic to the old host.

  If I manually send the GARP on the new host using:

  root@compute-2:~# ip netns exec fip-
  a46e0978-6e87-43d4-85d3-1d7030cdaf49 arping -A -I fg-de83cc57-32
  FLOATING_IP

  the floating IP comes up again and everything works as expected.

  Version:
  Mitaka on Ubuntu Trusty
  Kernel 3.19
  Deployed using Fuel 9.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1602436/+subscriptions