ironic/releasenotes/notes/redfish-500-fea3a8f86c0aecc7.yaml
Dmitry Tantsur a6e3a7f50c
Handle internal server errors while configuring secure boot
At least on some Dell machines, the Redfish SecureBoot resource is
unavailable during configuration, GET requests return HTTP 503.
Sushy does retry these, but not for long enough (the error message
suggests at least 30 seconds, which would be too much to just integrate
in Sushy). This change treats internal errors the same way as
mismatching "enabled" value, i.e. just waits.

Change-Id: I676f48de6b6195a69ea76b4e8b45a034220db2fa
2023-12-01 17:36:31 +01:00

7 lines
240 B
YAML

---
fixes:
- |
When configuring secure boot via Redfish, internal server errors are now
retried for a longer period than by default, accounting for the SecureBoot
resource unavailability during configuration on some hardware.