yahoo-eng-team team mailing list archive

[Augustina Ragwitz <1531826@xxxxxxxxxxxxxxxxxx>]

Marked as fix released, per OP's comment, a fix has been released for
python-novaclient that resolves this issue.

** Changed in: nova
       Status: Incomplete => 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/1531826

Title:
  nova boot from image with attach volume failed

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Reproducing method as following:
  1.  use CLI command create a new server .  the server boot from image, at the same time attach a volume for this server.
  the command as following:

  [root@sl3j ~(keystone_admin)]#nova boot --flavor 7c063ff7-244a-
  46d8-b166-d15eae9ea172   --image f9b1084c-2527-4f27-844e-cc21d766d32c
  --block-device source=volume,id=cbf360c2-eb2c-
  47e3-a501-795406a9542b,dest=volume,device=vdb  --nic port-id=fbc32d35
  -820a-409d-8768-aa1adea69142  test_vm

  you will find  the exception raise:

  ERROR (BadRequest): Block Device Mapping is Invalid: Boot sequence for
  the instance and image/block device mapping combination is not valid.
  (HTTP 400) (Request-ID: req-ab0f5fb2-5597-4c92-b1dd-d50364f84a57)

  2. Therefore, this VM uses the above step 1 command to create  failed
  . I use kilo_2015.1.0 version.  this command in icehouse version can
  create vm success.

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