yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

*** This bug is a duplicate of bug 1053344 ***
    https://bugs.launchpad.net/bugs/1053344

This is a known issue with folsom. You must manually remove and add
floating ips.

** This bug has been marked a duplicate of bug 1053344
   resize/migrate in multihost mode doesn't move floating ip

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1102302

Title:
  Floating IP doesn't change target without nova-network restart

Status in OpenStack Compute (Nova):
  New

Bug description:
  Hello,

  I found some strange behavior in nova-network.

  If I (or nova-compute) changed target VM of floating-ip, changes
  (iptables NAT records and ip address assignment) doesn't apply until I
  manually restart nova-network on both (source and destination) cluster
  nodes.

  It causes troubles with (e.g.) live-migration (IPs doesn't follow VMs
  during migration and connectivity with VMs being lost) and some other
  things.

  Looks like bug and I think need fixing.

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