yahoo-eng-team team mailing list archive

[OpenStack Infra <1455252@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/275801
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=898bb13304b68f33a130281d5acf425a1b23d171
Submitter: Jenkins
Branch:    master

commit 898bb13304b68f33a130281d5acf425a1b23d171
Author: Markus Zoeller <mzoeller@xxxxxxxxxx>
Date:   Tue Nov 22 17:08:14 2016 +0100

    libvirt: Acquire TCP ports for console during live migration
    
    During a live migration process we reserve serial ports on
    destination host and update domain XML during migration to
    use the new reserved ports from destination.
    
    If the migration succeeds we release ports on the source host.
    If the migration fails we release reserved ports on the
    destination host.
    
    Co-Authored-By: Sahid Ferdjaoui <sahid.ferdjaoui@xxxxxxxxxx>
    Change-Id: Ie2524191d22cca2287eb7dbaa22b74d43e43c896
    Closes-Bug: #1455252


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

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

Title:
  enabling serial console breaks live migration

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Version: openstack-nova-compute-2014.2.2-1.el7.noarch

  Enabling serial console causes the live migration process to fail with
  the following error in nova-compute.log:

  nova[12362]: 2015-05-14 21:57:21.108 ERROR nova.virt.libvirt.driver [-] [instance: a4d0bd8f-666e-4606-9e2a-4c583719719e] Live Migration failure: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
  qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=10000,server,nowait: Failed to bind socket: Cannot assign requested address
  qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=10000,server,nowait: chardev: opening backend "socket" failed

  The host IP is coming from the proxyclient_address setting which can't
  be 0.0.0.0, but even if it is changed to 0.0.0.0 the port number stays
  the same and will likely conflict on the destination. If there is no
  port conflict the live migration will succeed.

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