Wallaby Series Release Notes

3.7.1

Bug Fixes

  • Adds a fallback for inserting and ejecting virtual media using the PATCH HTTP request instead of the explicit action URIs. The fallback is required for Lenovo ThinkSystem machines (i.e. SD530, ..) that only implement the PATCH method.

3.7.0

New Features

  • Adds new method get_task_monitor to retrieve TaskMonitor instance by task monitor URI.

  • Adds support for fetching and resetting individual UEFI secure boot databases.

Deprecation Notes

  • Existing two TaskMonitor-s are deprecated and replaced with one taskmonitor.TaskMonitor.

    For resources.task_monitor.TaskMonitor users changes include:

    • in_progress is replaced with method check_is_processing

    • location_header is replaced with method task_monitor_uri

    • there is no replacement for set_retry_after, taskmonitor.TaskMonitor sets this internally from Retry-After header

    For resources.taskservice.taskmonitor.TaskMonitor users changes include:

    • check_is_processing, sleep_for and static get_task_monitor added.

    • in __init__ parameter field_data is deprecated, use response

    • in __init__ parameter task_monitor is renamed to task_monitor_uri

    • task_monitor is deprecated, use task_monitor_uri

    • retry_after is deprecated, use sleep_for

    Methods create_volume, delete_volume, initialize_volume in volume module are deprecated and replaced with ones named create, delete and initialize. New methods for asynchronous operations return taskmonitor.TaskMonitor instead of deprecated resources.task_monitor.TaskMonitor.

    Method resources.updateservice.UpdateService.get_task_monitor is deprecated, use Sushy.get_task_monitor instead.

Bug Fixes

  • Automatically retries internal server errors from GET requests.

3.6.1

Bug Fixes

  • Fixes AttributeError: 'str' object has no attribute 'get' during error handling. This occurs when BMC does not return a list of messages inside @Message.ExtendedInfo, but a single item. This has been observed with iDRAC.

  • Fixes issues in the volume module where the first parameter passed to the TaskMonitor constructor was incorrect. The parameter passed was the resource object (self), but it should have been the connector object (self._conn). This affected the create_volume() and delete_volume() methods.

3.6.0

New Features

  • Adds initial support for the TaskService resource to the library. TaskService is responsible for managing tasks.

  • Update the create_volume method in the VolumeCollection class and the delete_volume and initialize_volume methods in the Volume class to take optional apply_time and timeout keyword parameters. This allows the caller of those volume methods to specify a preferred OperationApplyTime annotation and a maximum timeout for synchronous operations. For asynchronous operations, those three methods will now return a TaskMonitor instance that the caller can use to monitor the state of the task.

  • Adding a new attribute task_uri to monitor redfish firmware update since some vendors(ilo) does not provide appropriate response with task_monitor uri.

  • Adds support for UEFI secure boot: reading the current status, enabling or disabling secure boot, resetting keys.

Deprecation Notes

  • The supported_values property in the OperationApplyTimeSupportField class is deprecated. Use the mapped_supported_values property instead. The mapped_supported_values property uses the MappedListField type to map the Redfish schema-defined enumeration values to constants exposed by the Sushy package.

Bug Fixes

  • Fixes an issue in the Connector class where an exception is not raised when an asynchronous operations fails.

3.5.0

Bug Fixes

  • Fixes an issue in performing action #Bios.ResetBios when no body in POST request provided and BMC responds with HTTP 400 Bad request, for example, Dell R630 having iDRAC 2.75.75.75. See story 2008198 for details.

  • The Actions field in the Volume resource was incorrectly specified as being required. This fix makes the field optional.

  • Makes message parsing more resilient by handling the case where the message ID only contains a message key and no registry name. In this case, fall back to the Messages message registry file and then to the BaseMessages message registry file. If the message ID cannot be found, then set the message to unknown. When parsing messages, if not enough arguments were supplied, then fill in the remaining arguments with unknown.

  • Reduce the logging from sushy by logging only attributes and values set in the redfish response, not the entire json.