Bug 958057
Summary: | Live migration fails. Libvirt says Cannot assign requested address. | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Nikola Dipanov <ndipanov> | |
Component: | openstack-nova | Assignee: | Daniel Berrangé <berrange> | |
Status: | CLOSED ERRATA | QA Contact: | Jaroslav Henner <jhenner> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 3.0 | CC: | bsettle, derekh, dmaley, doyler, eglynn, jdonohue, jhenner, mrussell, ndipanov, pbrady, sclewis, sgordon, slong | |
Target Milestone: | ga | Keywords: | Triaged | |
Target Release: | 6.0 (Juno) | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
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.
|
Story Points: | --- | |
Clone Of: | 912744 | |||
: | 1180600 1180602 (view as bug list) | Environment: | ||
Last Closed: | 2015-02-09 14:57:09 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 912744 | |||
Bug Blocks: | 969483, 1152637, 1180600, 1180602 |
Comment 3
Nikola Dipanov
2013-05-30 17:24:48 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. FYI, this functionality was fixed upstream by commit ea7da5152cdca7ba674e2137c3899909995e2287, which merged (via commit 65d939d9e625ffb2898b0552d25472791686b506) on July 15, 2014. *** Bug 1158972 has been marked as a duplicate of this bug. *** *** Bug 1178924 has been marked as a duplicate of this bug. *** 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. 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 |