Floating IP doesn't change target without nova-network restart
Bug #1102302 reported by
differentlocal
This bug report is a duplicate of:
Bug #1053344: resize/migrate in multihost mode doesn't move floating ip.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned | ||
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.
Revision history for this message
| Vish Ishaya (vishvananda) wrote | #1 |
To post a comment you must log in.
This is a known issue with folsom. You must manually remove and add floating ips.