Victoria Series (3.3.0 - 3.4.x) Release Notes¶
3.4.6-2¶
Bug Fixes¶
Fixes unreliable behavior with ETag interactions with some BMCs as opportunistic use of compressed responses may cause the BMC to change an ETag response to “Weak”, which is to be expected as an ETag represents an absolute byte-by-byte response consistency, and compression cannot reliably honor that contract. Introduction of a client perceiving a “Weak” ETag may not be expected by the server, and the server may reject responses because the ETag is not a “Strong” ETag when we respond or interact with a resource.
As a result, requests no longer offer oppurtunistic compression of responses as an acceptable possibility, which overall has minimal impact, espescially when compared to the value of consistent BMC behavior and interaction.
3.4.6¶
Bug Fixes¶
Fixes issues with the refresh of
Session
based authentication where a previous refresh attempt failing could result in a fallback toBasic
authentication and would silently fail. The client library now attempts to re-authenticate.
Fixes silent failures when a refresh of an authentication
Session
fails and was unable to be re-established due to anAccessError
. Should this occur, now theAccessError
exception is explicitly raised as opposed to attempting to fall back toBasic
authentication.
Fixes issues where the
Session
andBasic
auth interface would fallback toBasic
authentication should aConnectionError
exception occur while attempting to perform an authentication action.ConnectionError
exceptions are signs of networking transport issues, and should be investigated. AConnectionError
exception is now raised.
Prevents the combined
Session
andBasic
authentication support from falling back toBasic
authentication onceSession
based authentication has been established. This should be considered a potential security issue or an environmental change requiring potential client re-initialization. This is exposed as anAccessError
exception. Continued operations against the Sushy library will attempt to reauthenticate, if possible.
3.4.5¶
Bug Fixes¶
Fixes
Processor.sub_processors
for “‘Processor’ object has no attribute ‘conn’” error.
3.4.4¶
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.4.3¶
Bug Fixes¶
Fixes TaskMonitor for hardware(ilo) that doesn’t contain content-length in the response. This fix also uses task_uri instead of task_monitor uri to monitor redfish firmware update since using task_monitor uri doesn’t provide appropriate response.
Automatically retries internal server errors from GET requests.
3.4.2¶
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.
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 an issue in the
Connector
class where an exception is not raised when an asynchronous operations fails.
Reduce the logging from sushy by logging only attributes and values set in the redfish response, not the entire json.
3.4.1¶
Bug Fixes¶
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 theBaseMessages
message registry file. If the message ID cannot be found, then set the message tounknown
. When parsing messages, if not enough arguments were supplied, then fill in the remaining arguments withunknown
.
3.4.0¶
New Features¶
Adds support for
bios
resource to allow specifying BIOS attribute update time and maintenance window when updating BIOS attributes usingset_attribute
orset_attributes
.The update is backward compatible and when new parameters not passed, they default to
None
.Also adds
maintenance_window
forbios
resource to expose default maintenance window set by the system if any.
Added the ability to monitor the progress of a firmware update by changing the
simple_update
operation to return a task monitor object.
Bug Fixes¶
Instead of trying to GET /redfish/v1/SessionService, which is usually reachable via authentication, fail, and then guess /redfish/v1/SessionService/Sessions as Sessions URL, we try first to use directly the Sessions URL provided by the root service, if available.