97390e4276
Currently if the baremetal boot mode is unknown and the driver doesn't
support setting the boot mode then the error is logged and deployment
continues.
However if the BMC doesn't support getting or setting the boot mode
then setting the boot mode raises an error which results in the deploy
failing. This is the case for HPE Gen9 baremetal, which doesn't have a
'BootSourceOverrideMode' attribute in its system Boot field, and
raises a 400 iLO.2.14.UnsupportedOperation in response to setting the
boot mode.
This is raised from set_boot_mode as a RedfishError. This change
raises UnsupportedDriverExtension exception when the 'mode' attribute
is missing from the 'boot' field, allowing the deployment to continue.
Change-Id: I360ff8180be252de21f5fcd2208947087e332a39
(cherry picked from commit 9f221a7d42)
10 lines
446 B
YAML
10 lines
446 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Adds handling of Redfish BMC's which lack a ``BootSourceOverrideMode``
|
|
flag, such that it is no longer a fatal error for a deployment if the BMC
|
|
does not support this field. This most common on BMCs which feature only
|
|
a partial implementation of the ``ComputerSystem`` resource ``boot``,
|
|
but may also be observable on some older generations of BMCs which
|
|
recieved updates to have partial Redfish support.
|