yahoo-eng-team team mailing list archive

[Georg Hoesch <1776481@xxxxxxxxxxxxxxxxxx>]

Groundwork done, bug still open, actual fix is in progress.

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

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

Title:
  WS-based serial port proxy prevents access to console log file

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  This bug occurs with interactive WS-based serial ports in nova. The serial
  console on the Websocket works fine, but configuring these consoles
  prevents access to the console logfile via 'openstack console log show'.
  This bug was discovered in pike with KVM-based virtualization but seems to
  be in current master as well.

  Access to the console logfile is very important because my websocket
  client is usually not permanently connected.

  Detailed analysis:
  The console logfile is still generated by KVM/libvirt. The only difference
  is that the path of the logfile node changed in the XML information for
  the instance. The relevant function get_console_output() in
  nova/virt/libvirt/driver.py fails to find the logfile (it just looks for
  @type='file', it should also look for @type='tcp').

  I'll try to provide a fix for this myself, it shouldn't be
  complicated.

  Any comments?

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