Given it seems there should only be one BDM in the list and it's boot
index is 0, we shouldn't fail on the boot sequence validation, so add
some debug logging when we hit that failure.
Also copy some wording out of the 'Block Device Mapping in Nova' section
of the devref to add as code comments for the validation happening so we
have context.
TODO(mriedem): track down ndipanov to figure out why _subsequent_list
omits the last element of the list that it's processing, we need to doc
that logic in the code for maintainability.
Reviewed: https:/ /review. openstack. org/241270 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=a084dbf9f07 de2ea903ccd8aa8 4c60013aaa4193
Committed: https:/
Submitter: Jenkins
Branch: master
commit a084dbf9f07de2e a903ccd8aa84c60 013aaa4193
Author: Matt Riedemann <email address hidden>
Date: Tue Nov 3 08:08:07 2015 -0800
Add debug logging for when boot sequence is invalid in _validate_bdm
The cells job is failing to boot from volume with a bdm v2 request like:
"block_ device_ mapping_ v2": [{
"destination_ type": "volume",
"boot_ index": 0, 40f2-4225- ac4d-a1d021eb7f b1",
"source_ type": "volume",
"delete_ on_termination" : true
"uuid": "553083ac-
}]
Given it seems there should only be one BDM in the list and it's boot
index is 0, we shouldn't fail on the boot sequence validation, so add
some debug logging when we hit that failure.
Also copy some wording out of the 'Block Device Mapping in Nova' section
of the devref to add as code comments for the validation happening so we
have context.
TODO(mriedem): track down ndipanov to figure out why _subsequent_list
omits the last element of the list that it's processing, we need to doc
that logic in the code for maintainability.
Change-Id: I8adc94f3c93c14 9689fbef424665f b44ac573819
Related-Bug: #1489581