yahoo-eng-team team mailing list archive

[Ken'ichi Ohmichi <ken1ohmichi@xxxxxxxxx>]

This report was just for EC2 API test as the old Tempest patch, but now
these tests have been already removed since
https://review.openstack.org/#/c/222737/

So this report is unnecessary now.

** Changed in: tempest
       Status: In Progress => Won't Fix

-- 
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:
  Won't Fix

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