Current Series Release Notes¶
5.13.0-4¶
Upgrade Notes¶
DellJobCollection.get_unfinished_jobsnow returns jobs in any non-terminal state rather than onlyScheduled,RunningandPaused. Callers using it to decide whether the BMC is busy will see it report busy in more situations, which is the intended and more conservative behaviour. Callers using it to decide whether a specific job has finished will now get a correct answer for staged firmware jobs.
sushy.oem.dell.constants.INCOMPLETE_JOB_STATESis deprecated. It is an allowlist of only some of the incomplete job states and cannot be used to determine whether a job has finished. It is retained for backward compatibility but is no longer used internally; usesushy.oem.dell.constants.TERMINAL_JOB_STATESinstead.
Bug Fixes¶
Fixes
DellJobCollection.get_unfinished_jobsreporting a job as finished while the Lifecycle Controller was still working on it. The method matched an allowlist of three “incomplete” states (Scheduled,RunningandPaused), so a job in any other non-terminal state was silently omitted from the result. This notably affectedUserIntervention, which iDRAC reports for firmware that has been staged but not yet flashed during POST, and which is not present in this library’sJobStateenumeration at all. Callers polling for job completion could conclude that a firmware update had been applied when the flash had not started. The check is now inverted: only the terminal states listed insushy.oem.dell.constants.TERMINAL_JOB_STATEScount as finished, and any state the library does not recognise is treated as unfinished.
Fixes Sushy trying to access non-existing
/emptyURL when PCIe functions are not supported by the BMC. MissingAttributeError is raised instead (as documented).The code tries to return an empty collection instead of raising MissingAttributeError as any other accessors. However, it did not work in reality. Instead, out-of-band inspection would fail with
ResourceNotFoundError: Resource https://<host>/empty not found.
Fixes getting the supported reset types from services that publish them in an
ActionInforesource, referenced by the system reset action’s@Redfish.ActionInfoannotation, instead of annotating them inline. On such systems every reset type was previously assumed to be supported.