openstack/ironic
Code Issues Proposed changes

Clarify image_source with BFV

Browse Source 
Clarify the documentation and the returned error
in order to help users understand the behavior of
BFV and the storage interface.

Change-Id: I7719ae1acf5102cdd7ed39fd2fee427fdc25e78a
Story: #2001927
Task: #14455
This commit is contained in:
Julia Kreger 2018-05-03 15:33:45 -07:00
parent 3af8cfbe09
commit 863aa34145
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/contributor/ironic-boot-from-volume.rst
View File

@ -124,3 +124,9 @@ volume with tempest in the environment::
cd /opt/stack/tempest
tox -e all-plugin -- ironic_tempest_plugin.tests.scenario.test_baremetal_boot_from_volume
Please note that the storage interface will only indicate errors based upon
the state of the node and the configuration present. As such a node does not
exclusively have to boot via a remote volume, and as such `validate` actions
upon nodes may be slightly misleading. If an appropriate `volume target` is
defined, no error should be returned for the boot interface.

4
ironic/drivers/modules/deploy_utils.py
View File

@ -1050,7 +1050,9 @@ def get_image_instance_info(node):
info['ramdisk'] = node.instance_info.get('ramdisk')
error_msg = (_("Cannot validate image information for node %s because one "
"or more parameters are missing from its instance_info")
"or more parameters are missing from its instance_info and "
"insufficent information is present to boot from a remote "
"volume")
% node.uuid)
check_for_missing_params(info, error_msg)