yahoo-eng-team team mailing list archive

[Markus Zoeller <mzoeller@xxxxxxxxxx>]

Public bug reported:

Issue
=====
The libvirt driver returns *always" the first port and ignores each 
further defined port for the "serial console" feature.


Steps to reproduce
==================

* enable the "serial console" feature in nova.conf
  [serial_console]
  enabled=True
* start the nova-serialproxy service (e.g. with devstack [2])
* append the extra_spec "hw:serial_port_count" with value "2" to a flavor 
* start an instancen with that flavor (for generated domain XML see [4])
* Connect to the serial console to that launched instance
  (e.g. Horizon with "console" tab or another client [3])
* Start a second attempt to connect to that instance


Expected behavior
=================

The first connection will use the default port 10000.
The second attempt will use the next available port 10001.


Actual behavior
===============

The second attemp will fail because the libvirt driver returns the 
already connected port 10000.


Logs & Env.
===========

The two attempts to connect happen at 19:04 and 19:09 in the logs. 
Please see [6] and [7] for the relevant nova-serialproxy and nova-compute
logs. The additional dumpxml [5] from libvirt is taken after the first
connection. 
I'm using libvirt version 1.2.2 within an Ubuntu14.04 VM. OpenStack
is installed and started with devstack.


References
==========

[1] Mailing list "openstack-dev"; February 2015; 
    subject "[nova] bp serial-ports *partly* implemented?"; 
    http://markmail.org/thread/2byi6adf4ynvjg6e
[2] Devstack guide; Nova and devstack;
    http://docs.openstack.org/developer/devstack/guides/nova.html
[3] larsk/novaconsole; github; https://github.com/larsks/novaconsole/
[4] pastebin; generated domain XML for the instance; 
    http://paste.openstack.org/show/182024/
[5] pastebin; virsh dumpxml <domain> for the instance after the first
    connection; http://paste.openstack.org/show/182026/
[6] pastebin; log of the nova-serialproxy service
    http://paste.openstack.org/show/182028/
[7] pastebin; log of nova-compute service
    http://paste.openstack.org/show/182029/

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: libvirt

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

Title:
  LibvirtDriver: "get_serial_console" returns always the first port of N
  defined ports

Status in OpenStack Compute (Nova):
  New

Bug description:
  Issue
  =====
  The libvirt driver returns *always" the first port and ignores each 
  further defined port for the "serial console" feature.

  
  Steps to reproduce
  ==================

  * enable the "serial console" feature in nova.conf
    [serial_console]
    enabled=True
  * start the nova-serialproxy service (e.g. with devstack [2])
  * append the extra_spec "hw:serial_port_count" with value "2" to a flavor 
  * start an instancen with that flavor (for generated domain XML see [4])
  * Connect to the serial console to that launched instance
    (e.g. Horizon with "console" tab or another client [3])
  * Start a second attempt to connect to that instance

  
  Expected behavior
  =================

  The first connection will use the default port 10000.
  The second attempt will use the next available port 10001.

  
  Actual behavior
  ===============

  The second attemp will fail because the libvirt driver returns the 
  already connected port 10000.

  
  Logs & Env.
  ===========

  The two attempts to connect happen at 19:04 and 19:09 in the logs. 
  Please see [6] and [7] for the relevant nova-serialproxy and nova-compute
  logs. The additional dumpxml [5] from libvirt is taken after the first
  connection. 
  I'm using libvirt version 1.2.2 within an Ubuntu14.04 VM. OpenStack
  is installed and started with devstack.

  
  References
  ==========

  [1] Mailing list "openstack-dev"; February 2015; 
      subject "[nova] bp serial-ports *partly* implemented?"; 
      http://markmail.org/thread/2byi6adf4ynvjg6e
  [2] Devstack guide; Nova and devstack;
      http://docs.openstack.org/developer/devstack/guides/nova.html
  [3] larsk/novaconsole; github; https://github.com/larsks/novaconsole/
  [4] pastebin; generated domain XML for the instance; 
      http://paste.openstack.org/show/182024/
  [5] pastebin; virsh dumpxml <domain> for the instance after the first
      connection; http://paste.openstack.org/show/182026/
  [6] pastebin; log of the nova-serialproxy service
      http://paste.openstack.org/show/182028/
  [7] pastebin; log of nova-compute service
      http://paste.openstack.org/show/182029/

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