yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #72548
[Bug 1766306] Re: api-ref: block_device_mapping_v2.boot_index is required until queens
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
--
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/1766306
Title:
api-ref: block_device_mapping_v2.boot_index is required until queens
Status in OpenStack Compute (nova):
In Progress
Status in OpenStack Compute (nova) queens series:
Confirmed
Bug description:
Change https://review.openstack.org/#/c/550648/ marked the
block_device_mapping_v2.boot_index parameter for POST /servers as
optional, but it's only optional since this change in Queens:
https://review.openstack.org/#/c/524208/
Before that, you'll get an error like this if you boot from volume but
don't specify a boot_index for each BDM in the list:
2018-04-23 12:34:13,308 INFO [nova.api.openstack.wsgi] HTTP exception thrown: Block Device Mapping is Invalid: Boot sequence for the instance and image/block device mapping combination is not valid.
2018-04-23 12:34:13,310 INFO [nova.api.openstack.requestlog] 127.0.0.1 "POST /v2.1/6f70656e737461636b20342065766572/servers" status: 400 len: 164 microversion: 2.1 time: 0.129485
Therefore we should probably mark the parameter as required since the
API reference applies to older versions/releases of the API too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1766306/+subscriptions
References