yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #76374
[Bug 1776481] Re: WS-based serial port proxy prevents access to console log file
Reviewed: https://review.openstack.org/624974
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5aaa7da32559d2fea8e0d901779d0d736bc810e2
Submitter: Zuul
Branch: master
commit 5aaa7da32559d2fea8e0d901779d0d736bc810e2
Author: Georg Hoesch <georg.hoesch@xxxxxxxx>
Date: Thu Dec 13 12:27:51 2018 +0000
allow tcp-based consoles in get_console_output
Tcp based consoles already offer a logfile but the information
resides in a different path in the hosts XML. This change adds
an additional xpath for tcp-based consoles.
Closes-Bug: #1776481
Change-Id: I9bfd14c72b1e891cb67562f6a07ceea916c3ed65
** 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/1776481
Title:
WS-based serial port proxy prevents access to console log file
Status in OpenStack Compute (nova):
Fix Released
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
References