Bug 958057 - Live migration fails. Libvirt says Cannot assign requested address.
Summary: Live migration fails. Libvirt says Cannot assign requested address.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 3.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ga
: 6.0 (Juno)
Assignee: Daniel Berrangé
QA Contact: Jaroslav Henner
URL:
Whiteboard:
: 1158972 1178924 (view as bug list)
Depends On: 912744
Blocks: 969483 1152637 1180600 1180602
TreeView+ depends on / blocked
 
Reported: 2013-04-30 09:37 UTC by Nikola Dipanov
Modified: 2023-09-18 09:58 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When Compute is configured to only set up VNC/SPICE servers on a specific network interface, the host's IP address is recorded in the libvirt guest XML. Previously, if the guest was migrated to a different host, the IP address of the source host remained in the guest XML and the guest failed to launch on the target host because the IP address was incorrect. With this update, the libvirt guest XML is now updated during migration to refer to the IP address of the target host. Migration can be performed for guests, even when the VNC/SPICE servers are configured to only bind to the IP address of a specific network interface.
Clone Of: 912744
: 1180600 1180602 (view as bug list)
Environment:
Last Closed: 2015-02-09 14:57:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 73428 0 None None None Never
Red Hat Product Errata RHEA-2015:0152 0 normal SHIPPED_LIVE openstack-nova enhancement advisory 2015-02-09 19:52:32 UTC

Comment 3 Nikola Dipanov 2013-05-30 17:24:48 UTC
This is actually also documented upstream, only with less security in mind then our relnote in the related bug (see http://docs.openstack.org/grizzly/openstack-compute/admin/content/configuring-migrations.html).

I believe this should be raised as a libvirt bug. as there is nothing we can do in nova to mitigate this.

There is definitely nothing we can do for this in 3.0 so I will move to 4.0 for now, and potentially block on a libvirt bug we will open if dallan/danpb agree that this is fixable there

Comment 4 Daniel Berrangé 2013-11-13 16:17:37 UTC
(In reply to Nikola Dipanov from comment #3)
> I believe this should be raised as a libvirt bug. as there is nothing we can
> do in nova to mitigate this.

OpenStack is setting a listen address in the XML when starting the guest. If this address is host specific, then openstack must change this when issuing the migration call. The libvirt migration APIs allow you to pass in a replacement XML config for the guest to be used on the target host. So this replacement XML should use the listen address of the target host.

Comment 8 Solly Ross 2014-10-29 15:05:35 UTC
FYI, this functionality was fixed upstream by commit ea7da5152cdca7ba674e2137c3899909995e2287, which merged
(via commit 65d939d9e625ffb2898b0552d25472791686b506) on July 15, 2014.

Comment 9 Pádraig Brady 2014-10-30 16:35:52 UTC
*** Bug 1158972 has been marked as a duplicate of this bug. ***

Comment 11 Daniel Berrangé 2015-01-05 16:54:32 UTC
*** Bug 1178924 has been marked as a duplicate of this bug. ***

Comment 18 Jaroslav Henner 2015-01-11 01:21:18 UTC
Before migraton:

[root@compute-1 cloud-user]# grep listen /var/lib/nova/instances/7e8e07fc-7446-4e53-97ca-a325119fdf0c/libvirt.xml
    <graphics type="vnc" autoport="yes" keymap="en-us" listen="172.16.32.111"/>

after migration:
[root@compute-2 cloud-user]# grep listen /var/lib/nova/instances/7e8e07fc-7446-4e53-97ca-a325119fdf0c/libvirt.xml 
    <graphics type="vnc" autoport="yes" keymap="en-us" listen="172.16.32.110"/>


vnc is working.

Comment 22 errata-xmlrpc 2015-02-09 14:57:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0152.html


Note You need to log in before you can comment on or make changes to this bug.