summaryrefslogtreecommitdiff
path: root/releasenotes/notes/supermicro-redfish-override-enabled-aa51686ed33d3061.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/supermicro-redfish-override-enabled-aa51686ed33d3061.yaml')
-rw-r--r--releasenotes/notes/supermicro-redfish-override-enabled-aa51686ed33d3061.yaml15
1 files changed, 15 insertions, 0 deletions
diff --git a/releasenotes/notes/supermicro-redfish-override-enabled-aa51686ed33d3061.yaml b/releasenotes/notes/supermicro-redfish-override-enabled-aa51686ed33d3061.yaml
new file mode 100644
index 000000000..f3af2a169
--- /dev/null
+++ b/releasenotes/notes/supermicro-redfish-override-enabled-aa51686ed33d3061.yaml
@@ -0,0 +1,15 @@
+---
+fixes:
+ - |
+ When Ironic configures the BootSourceOverrideTarget setting via Redfish,
+ on Supermicro BMCs it must always configure BootSourceOverrideEnabled or
+ that will revert to default (Once) on the BMC, see `story 2008547
+ <https://storyboard.openstack.org/#!/story/2008547>`_ for details.
+ This is different than what is currently implemented for other BMCs in
+ which the BootSourceOverrideEnabled is not configured if it matches the
+ current setting (see `story 2007355
+ <https://storyboard.openstack.org/#!/story/2007355>`_).
+
+ This requires that node.properties['vendor'] be 'supermicro' which will
+ be set by Ironic from the Redfish system response or can be set
+ manually.