[openstack-dev] [nova][kolla] Live migration, VNC / SPICE address?

Koniszewski, Pawel pawel.koniszewski at intel.com
Tue Aug 30 10:11:18 UTC 2016


Thanks for pointing this out, looks like it is a regression in nova introduced during Newton cycle. At some point we moved checks of graphic and serial consoles to the live migration pre-checks on source node, but we never moved piece of code that populates this data while executing pre-checks on destination node.

I proposed a fix, you can take a look whether this fixes an issue that you observed - https://review.openstack.org/#/c/362756/. If yes I will update appropriate unit tests.
The bug is tracked here https://bugs.launchpad.net/nova/+bug/1618392

Kind Regards,
Pawel Koniszewski

From: Dave Walker [mailto:email at daviey.com]
Sent: Tuesday, August 30, 2016 10:11 AM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [nova][kolla] Live migration, VNC / SPICE address?


In Kolla, we are having an issue with Nova's VNC / SPICE address and live migration.  Currently, we are declaring the IP address for vncserver_listen on each node (via ansible).  However, when a live migration is performed, it fails due to this address not being available.

The hack is to switch the vncserver_listen to be, but this is horribly insecure and breaks the network isolation that kolla supports.

Looking at the relevant code, this looks like it should be functional via VIR_DOMAIN_XML_MIGRATABLE, but it doesn't seem to be working.

Could someone from Nova help us determine the cause?  We are tracking this as bug 1596724




Kind Regards,
Dave Walker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160830/1fab2768/attachment.html>

More information about the OpenStack-dev mailing list