yahoo-eng-team team mailing list archive

[Russell Bryant <1322180@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => juno-2

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

Title:
  Fail to launch an instance from volume by legacy bdm

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Launting an instance from bootable volume passing legacy bdm is
  available only using vda (no /dev/ prefix) as root device name. This
  is weird restriction. It prevents to create consistent instance data,
  because root_device_name instance attribute has /dev/ prefix, but
  device_name bdm attribute doesn't.

  Environment: DevStack

  Steps to reproduce:
  1 Create bootable volume
  $ cinder create --image-id xxx 1
  Note: I used cirros-0.3.2-x86_64-uec ami image.

  2 Boot instance from the volume by legacy bdm.
  $ nova boot --flavor m1.nano --block-device-mapping /dev/vda=yyy:::1 inst

  3 Wait instance status Active, go to instance console and look to 'No
  bootable device' message.

  
  The reason is in _get_bdm_image_metadata in nova/compute/api.py. There only 'vda' devices are processed as root device for legacy bdm.

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