Reviewed: https://review.openstack.org/413453
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a65551ecd09b3116a13d9b6cc833be0c05b716da
Submitter: Jenkins
Branch: master
commit a65551ecd09b3116a13d9b6cc833be0c05b716da
Author: Ken'ichi Ohmichi <ken-oomi...@wx.jp.nec.com>
Date: Tue Dec 20 23:20:43 2016 -0800
Fix BDM JSON-Schema validation
Current BDM JSON-Schema validation doesn't work for invalid device
parameter in 2nd dict, because JSON-Schema definition is wrong.
This patch fixes it.
Co-Authored-By: Zhenyu Zheng <zhengzhe...@huawei.com>
Change-Id: I56348dc2b7abd9526dfbf21305755505765811c5
Closes-Bug: #1651064
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: nova/newton
Status: Confirmed => In Progress
** Changed in: nova/newton
Assignee: (unassigned) => Ken'ichi Ohmichi (oomichi)
--
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/1651064
Title:
HTTP 500 when calling os-volume_boot with invalid destination_type
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) mitaka series:
Confirmed
Status in OpenStack Compute (nova) newton series:
In Progress
Bug description:
When calling os-volume_boot with invalid bdm destination_type (e.g.
volume1 as a typo of volume) HTTP 500 will raise.
Setp 1: call os-volumes_boot API or use "nova boot" CLI with --block-
device provided(it will call os-volumes_boot)
nova-api log for my test can be found in:
http://paste.openstack.org/show/592762/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1651064/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
