Richard Pioso 49ce9993e1 Fix Redfish handle no continuous override boot src ... Some hardware Redfish services have dropped support for continuously overriding the boot source when the boot mode is Unified Extensible Firmware Interface (UEFI). See this discussion: http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014543.html A workaround falls back to one-time override, restoring it on every reboot or power on. [1] However, it does not work, because, per the Distributed Management Task Force (DMTF) Redfish standard, one-time override is disabled on the next boot cycle. [2] This fixes that by explicitly setting the boot source override to one-time every time it is restored. [1] https://storyboard.openstack.org/#!/story/2007527 [2] https://redfish.dmtf.org/schemas/v1/ComputerSystem.v1_11_0.json # Conflicts: # ironic/drivers/modules/redfish/management.py Story: 2007733 Task: 39897 Change-Id: I6f5a11a77e7b16cdd0d837fdec51c3e9aeea9a31 (cherry picked from commit c56777929a)		2020-06-19 01:39:37 -04:00
..
__init__.py	Add redfish driver	2017-04-21 11:06:24 +01:00
bios.py	Follow-up for deploy steps for Redfish BIOS interface	2019-08-28 03:52:45 -04:00
boot.py	redfish-vmedia: correctly pass ipa-debug	2020-01-03 17:01:19 +00:00
inspect.py	Set boot_mode in node properties during Redfish introspection	2019-03-08 08:18:48 +01:00
management.py	Fix Redfish handle no continuous override boot src	2020-06-19 01:39:37 -04:00
power.py	redfish: handle hardware that is unable to set persistent boot	2020-05-29 02:02:57 -04:00
utils.py	Add configurable Redfish client authentication	2018-12-04 09:07:06 +01:00