yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

** Changed in: nova
       Status: In Progress => Fix Released

** Changed in: nova
     Assignee: Paulo Matias (paulo-matias) => John Garbutt (johngarbutt)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1615613

Title:
  Live migration always fails when VNC/SPICE is listening at non-local,
  non-catch-all address

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When VNC or SPICE is configured to listen only at a specific IP
  address (e.g. on the management network in an OpenStack-Ansible
  deploy), the check performed by check_can_live_migrate_source always
  fails, because check_can_live_migrate_destination does not return the
  attributes needed to retrieve listen_addrs using
  libvirt_migrate.graphics_listen_addrs.

  
  Steps to reproduce:

   * Deploy OpenStack-Ansible from master.

   * Create an instance.

   * Try to live migrate the instance to another host.

  
  Expected result: live migration should be carried.

  Actual result (nova-compute.log):

  ERROR oslo_messaging.rpc.server MigrationError: Migration error: Your
  libvirt version does not support the VIR_DOMAIN_XML_MIGRATABLE flag or
  your destination node does not support retrieving listen addresses.
  In order for live migration to work properly, you must configure the
  graphics (VNC and/or SPICE) listen addresses to be either the catch-
  all address (0.0.0.0 or ::) or the local address (127.0.0.1 or ::1).

  
  Environment:

  * Multi-node OpenStack-Ansible deploy.

  * Nova from git (commit 32b7526b3cf40f40c5430034f75444fc64ac0e04).

  * Libvirt + KVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1615613/+subscriptions