Current Series Release Notes¶

5.7.1-7¶

Adds comprehensive PCIeDevice resource support implementing the complete Redfish PCIeDevice v1.19.0 specification. The new pcie_devices property on System objects provides access to PCIe device collections with support for both standard Redfish collections and embedded PCIeDevices (Dell iDRAC).

Features include full schema compliance, PCIe interface information and slot details.

Support for Python 3.9 has been removed. Now Python 3.10 is the minimum version supported.

An issue was encountered on Dell hardware where the Baseboard Management Controller could respond with a HTTP 404 error temporarily during job creation, causing operations to fail unnecessarily. This occurred due to a race condition where the BMC had not yet finished creating the job when the initial request was made. The Dell OEM http_call method now automatically retries on 404 responses with configurable retry count (default: 3 retries) and delay (default: 10 seconds) to handle this transient condition gracefully. The retry behavior can be customized using the max_404_retries and retry_404_delay parameters.

Fixes an issue with the handling of idrac10 BMCs as it relates to the ComputerSystem resource. Previously, sushy was not able to identify the available boot target value. Now sushy is able to identify the boot values from a settings sub-resource and provide the needful clarity so consumers of the sushy library can identify available targets.

Improve Redfish VirtualMedia InsertMedia error handling on BMCs that require credentials but return unstructured errors (e.g., responses that omit error.code and report ActionParameterMissing only via @Message.ExtendedInfo or free-text messages). Sushy now detects these cases and retries with UserName/Password parameters, allowing ISO mounting to proceed. This also preserves compatibility with legacy error.code == *GeneralError responses that mention missing parameters.

Adds correct handling of BMC responses containing an empty string eTag. This resolves issues where sending back an empty string eTag may trigger HTTP 412 Precondition Failed error on some BMCs.