Xena Series (3.8.0 - 3.12.x) Release Notes

3.12.6-5

Bug Fixes

  • Fixes bug where sushy would not pass a read/connect timeout through to requests when making requests to a redfish service. This means that an ill-timed failure could cause python processes calling sushy to freeze indefinately.

  • Fixes ‘Unsupported parameter name @Redfish.OperationApplyTime’ erroron iDRAC firmware version 6.00.02.00 or newer when deleting volumes.

  • Correctly handles errors on a request that is re-tried after refreshingan authentication token.

3.12.6

Bug Fixes

  • Add retries on iDRAC error with code SYS518 and message “iDRAC iscurrently unable to display any information because data sources areunavailable.” for all request types in addition to existing GET methods.This helps to fix a known intermittent issue when deleting set of volumesone after another and iDRAC is reloading after deleting each volume.

  • Correctly handles error codeBase.1.5.PropertyMissing when dealing withhardware that requiresTransferProtocolType for virtual mediaoperations.

3.12.5

Bug Fixes

  • Adds an extra check for cases where the BMC provides a SettingsObjectURI through @Redfish.Settings but this URI does not allow setting bootrelated attributes. Prior to sending a PATCH request to SettingsURI, aGET request is issued to verify if it contains the attributes to beupdated. In case these attributes are missing, the request is made againstSystem URI instead.Issues such as the one addressed with this change usually manifestthemselves with a Redfish response containing an error message similar tothe following:MessageId:Base.1.8.PropertyNotWritable,Message:ThepropertyBootSourceOverrideEnabledisareadonlypropertyandcannotbeassignedavalue.

3.12.4

Bug Fixes

  • To avoid timeouts with recent versions of firmwares we need to increasethe number of server side retries.For example, in idrac firmware series 5.x the time gap between operationsis almost 20 seconds instead of the 10 seconds in the 4.x series.

3.12.3

Bug Fixes

  • Fixes potential cases where exceptions from the underlyingrequestslibrary may be raised up throughsushy, resulting in clientapplications possibly not understanding that an error has occurred.The sushyConnectionError exception is now returned upon any exceptionfalling underRequestException from therequests library.

  • Fixes unreliable behavior with ETag interactions with some BMCs asopportunistic use of compressed responses may cause the BMC to changean ETag response to “Weak”, which is to be expected as an ETag representsan absolute byte-by-byte response consistency, and compression cannotreliably honor that contract. Introduction of a client perceiving a“Weak” ETag may not be expected by the server, and the server may rejectresponses because the ETag is not a “Strong” ETag when we respond orinteract with a resource.

    As a result, requests no longer offer oppurtunistic compressionof responses as an acceptable possibility, which overall has minimalimpact, espescially when compared to the value of consistent BMCbehavior and interaction.

  • Fixes an issue in the sushy connector object handling where aSushy client utilizingbasic authentication would not raisean AccessError exception once the credentials stopped working.We now explicitly check to see ifbasic authenticationis in use, and raise the exception if an AccessError isencountered.

  • Alters eTag handling in PATCH requests: First, the original eTag is used.In case of a failure, if the eTag provided was weak, it is converted toa strong format by removing the weak prefix. If this approach is notapplicable or fails, the final attempt is made omitting the eTag entirely.By taking this approach, no workarounds are applied if BMC is handlingeTags as expected and in case of failures, known workarounds areattempted, improving overall resiliency.

3.12.2

Bug Fixes

  • Makes the unstripped version of an Etag available in addition tothe stripped one in order to support vendor implementations whichrequire one or the other.

3.12.1

Bug Fixes

  • Changing boot device string for virtual media from “Cd” to “UsbCd” onSuperMicro machines to match their specific naming convention.

  • If available, uses headers with an Etag to set the boot options.

  • Fixes issues with the refresh ofSession based authentication wherea previous refresh attempt failing could result in a fallbacktoBasic authentication and would silently fail. The client librarynow attempts to re-authenticate.

  • Fixes silent failures when a refresh of an authenticationSessionfails and was unable to be re-established due to anAccessError.Should this occur, now theAccessError exception is explicitly raisedas opposed to attempting to fall back toBasic authentication.

  • Fixes issues where theSession andBasic auth interface wouldfallback toBasic authentication should aConnectionErrorexception 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 combinedSession andBasic authentication supportfrom falling back toBasic authentication onceSession basedauthentication has been established. This should be considered a potentialsecurity issue or an environmental change requiring potential clientre-initialization. This is exposed as anAccessError exception.Continued operations against the Sushy library will attempt toreauthenticate, if possible.

  • Resolved virtualmedia attach failures caused by the lack ofTransferProtocolType parameter in the request payload which is requiredby certain BMCs (e.g. on Nokia servers). This is done by adding capabilityto retry virtualmedia InsertMedia with the updated payload in such cases.

  • Fixes incompatibility with BMCs that require use of a specificSettingsObject URI specified in @Redfish.Settings resource in order toset BootSourceOverride or similar attributes. For example, this isrequired on Nokia servers.

3.12.0

New Features

  • TheVirtualMedia.insert_media call now supports credentials for theimage URI.

Bug Fixes