Update floating ip should consider multi_host or network_host config when live migration

Bug #1188450 reported by Jiang Yong
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Timofey Durakov

Bug Description

When migrate a instance, the method _post_live_migration will update host value of the floating ip associated with the instancd to dist host. see https://github.com/openstack/nova/blob/stable/folsom/nova/compute/manager.py#L2313 . This operation does not consider whether multi_host is false or there is a nova-network runing on the dist host when using nova-network as the network service.

melanie witt (melwitt)
tags: added: compute network
Revision history for this message
melanie witt (melwitt) wrote :

The floating ip host is supposed to be instance['host'] if network['multi_host'], instead of the migration destination host.

This bug is when using nova-network, which is en route to being deprecated, so setting priority Low.

Changed in nova:
importance: Undecided → Low
status: New → Confirmed
melanie witt (melwitt)
Changed in nova:
importance: Low → Medium
Brent Eagles (beagles)
summary: - Update floating ip should concider multi_host or network_host config
+ Update floating ip should consider multi_host or network_host config
when live migration
description: updated
Changed in nova:
assignee: nobody → Timofey Durakov (tdurakov)
Changed in nova:
status: Confirmed → In Progress
Changed in nova:
status: In Progress → Fix Released
Revision history for this message
Timofey Durakov (tdurakov) wrote :

This bug is not valid, since there are checks in code, mentioned there. Invalid at least for stable/juno and later releases

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.