Dave, 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:em...@daviey.com] Sent: Tuesday, August 30, 2016 10:11 AM To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [nova][kolla] Live migration, VNC / SPICE address? Hi, 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 0.0.0.0, 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 https://github.com/openstack/nova/blob/04cef3b5d03be3db7efab6896de867fc2cbbd03a/nova/virt/libvirt/driver.py#L5393 https://github.com/openstack/nova/blob/04cef3b5d03be3db7efab6896de867fc2cbbd03a/nova/virt/libvirt/driver.py#L5754 Thanks -- Kind Regards, Dave Walker
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
