yahoo-eng-team team mailing list archive

[OpenStack Infra <832507@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/407450
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1f659251c7509cab045024044a6b8d642ad85aef
Submitter: Jenkins
Branch:    master

commit 1f659251c7509cab045024044a6b8d642ad85aef
Author: Markus Zoeller <mzoeller@xxxxxxxxxx>
Date:   Tue Dec 6 11:40:25 2016 +0100

    libvirt: virtlogd: use virtlogd for char devices
    
    This change makes actual usage of the "logd" sub-element for char devices.
    The two REST APIs ``os-getConsoleOutput`` and ``os-getSerialConsole`` can
    now be satisfied at the same time. This is valid for any combination of:
    * char device element: "console", "serial"
    * char device type: "tcp", "pty"
    There is also no need to create multiple different device types anymore.
    If we have a tcp device, we don't need the pty device anymore. The logging
    will be done in the tcp device.
    
    Implements blueprint libvirt-virtlogd
    Closes-Bug: 832507
    Change-Id: Ia412f55bd988f6e11cd78c4c5a50a86389e648b0


** 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/832507

Title:
  console.log grows indefinitely

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix
Status in libvirt package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in qemu-kvm package in Ubuntu:
  Triaged

Bug description:
  KVM takes everything from stdout and prints it to console.log. This
  does not appear to have a size limit, so if a user (mistakenly or
  otherwise) sends a lot of data to stdout, the console.log file can
  fill the entire disk of the compute node quite quickly.

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