yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  libvirt: AMI-based Linux instances /dev/console unusable

Status in OpenStack Compute (nova):
  Expired
Status in tempest:
  In Progress

Bug description:
  In Linux, the last console= option listed in /proc/cmdline becomes
  /dev/console, which is used for things like rescue mode, single-user
  mode, etc.  In the case of AMI-based Linux images, libvirt defines the
  "serial" console (tied to the console.log) last, which means a crashed
  instance ends up being unrecoverable

  Steps to Reproduce:

  1.  Upload the AMI/AKI/ARI images attached to this bug into Glance and tie them together (if how to do this is not common knowledge, I can follow-on with exact steps)
  2.  Boot an instance against the image.  It has been altered so that it will crash on startup, believing there is filesystem corruption

  Expected Behaviour:

  A "Press enter for maintenance (or type Control-D to continue):"
  prompt on the interactive console (Spice/VNC/etc.)

  Actual Behaviour:

  The aforementioned prompt appears in the libvirt console.log, and the
  instance is effectively bricked.

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