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

Title:
  Booting LVM instance too big for the volume generates an exception

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Attempting to boot an LVM backed instance that exceeds available disk
  space results in ProcessExecutionError exception leading to an ERROR
  state instead of clean termination.

  Observed in Nova 209c0a29 on DevStack b160640d. To generate the
  failure configure Nova for LVM ephemeral storage with

  [libvirt]
  images_volume_group = nova-lvm
  images_type = lvm

  Make the nova-lvm volume relatively small, say 5G, and boot an
  m1.small instance.

  Exception back trace is as follows: http://pastebin.com/ePG3s58P.
  ----------------------------------------------------------------

  It is not entirely clear why the booting process is allowed to get as
  far as actually attempting to create instance disk since the scheduler
  really should return 0 matching hosts, as the disk is obviously too
  small.  However, once create_lvm_image() raises "RunTimeError:
  Insufficient Space on Volume Group nova-lvm. ...", the booting process
  attempts to recover gracefully by terminating the instance. At some
  point in the termination the (non-existent) instance volume is
  cleared, resulting in an execution of 'nova-rootwrap
  /etc/nova/rootwrap.conf blockdev --getsize64 /' , which does not match
  any of the root-wrap filters and generates ProcessExecutionError.

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