yahoo-eng-team team mailing list archive

[Dmitry Borodaenko <dborodaenko@xxxxxxxxxxxx>]

How is this a duplicate of a bug that was raised 2 months after this bug
was raised?

** Changed in: nova
       Status: Invalid => In Progress

** This bug is no longer a duplicate of bug 1279563
   Libvirt live migration fails when graphics listen is not 0.0.0.0 ("Cannot assign requested address")

-- 
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/1262450

Title:
  Nova doesn't update vnc listen address during migration with libvirt

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  Nova should update VNC listen address in libvirt.xml to the
  destination node's vncserver_listen setting on completing migration.
  Without that, the only way to make VMs accessible over VNC after
  migration is to set vncserver_listen to 0.0.0.0 as recommended in:

  http://docs.openstack.org/havana/config-reference/content/configuring-
  openstack-compute-basics.html#section_configuring-compute-migrations

  which is a suboptimal solution from security standpoint.

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