yahoo-eng-team team mailing list archive

[melanie witt <1456676@xxxxxxxxxxxxxxxxxx>]

The output you show is a 400 response from nova, so that means
novaclient is letting the request go out to the server (correct) but
nova is rejecting it on that side. The bug fix on the nova side was
https://github.com/openstack/nova/commit/3cff2c673c6cdf487c2a1eb2a5c6c89c6de80d11
which is included in 2015.1.0.

Could you please provide the stack trace from nova-api.log when this
happens so we can investigate?

** Also affects: nova
   Importance: Undecided
       Status: New

** No longer affects: python-novaclient

** Changed in: nova
       Status: New => Incomplete

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

Title:
  Booting an instance with --block-device fails when it should be
  successful

Status in OpenStack Compute (Nova):
  Incomplete

Bug description:
  Version:
  Kilo 2015.1.0

  openstack-nova-compute-2015.1.0-3.el7ost.noarch
  openstack-nova-common-2015.1.0-3.el7ost.noarch
  openstack-nova-console-2015.1.0-3.el7ost.noarch
  openstack-nova-scheduler-2015.1.0-3.el7ost.noarch
  python-nova-2015.1.0-3.el7ost.noarch
  openstack-nova-conductor-2015.1.0-3.el7ost.noarch
  openstack-nova-cert-2015.1.0-3.el7ost.noarch
  python-novaclient-2.23.0-1.el7ost.noarch
  openstack-nova-novncproxy-2015.1.0-3.el7ost.noarch
  openstack-nova-api-2015.1.0-3.el7ost.noarch

  Description:
  When trying to boot an instance with a block device it fails:

  nova --debug boot --flavor m1.small --image cirros --nic net-id
  =397cffaf-bf84-4a3b-8af4-95dd772546bd --block-device
  source=volume,dest=volume,id=64cf7206-e327-44a8-bc93-fc432b4a4522,bus=ide,type=cdrom,bootindex=1
  test

  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-5c85f777-348b-42d9-a618-ff2003968291)

  After a quick checkup it seems that the bug is related to https://bugs.launchpad.net/nova/+bug/1433609 
  but the fix in the python client: https://review.openstack.org/#/c/153203/ is not present in python-novaclient-2.23.0-1.el7ost.noarch which causes the same problem described above.

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