Xena Series (10.7.0 - 10.8.x) Release Notes

10.8.0-3

Known Issues

  • The response headers for empty body HTTP 204 replies, at present, violate RFC7230. This was not intentional, but underlying libraries also make inappropriate changes to the headers, which can cause clients to experience odd failures. This is anticipated to be corrected once an underlying issue in eventlet is resolved.

Bug Fixes

  • Fixes HTTP responses so the Eventlet library, which is used to support the operation of the WSGI application, does not incorrectly inject a Transfer-Encoding header into the HTTP response, even on HTTP 204 replies, which is a violation of RFC7230. This header ultimately can cause varying client reactions which are not expected and can raise exceptions. For now, this has been remedied via an explicit return of a Content-Length header, which is also an RFC7230 violation, but it appears to be the lesser of known evils at this time.

10.8.0

New Features

  • The new [healthcheck] enabled option has been added. When this option is set to True, the healthcheck middleware is enabled in API pipeline and the additional API endpoint to monitor service availability becomes available at /healthcheck path.

Bug Fixes

  • Inspector now ignores failures to list ironic ports during pxe filter driver sync, and just skips the sync in this case. Previously such errors resulted in pxe filter driver being stuck in an uninitialized state until ironic inspector was restarted. See bug 2008971.

  • Fixes issues in Inspector where various tasks would not have retry logic applied to them and may sporadically fail. This is because the OpenStack SDK does not comprehend the NodeLocked error, which previously python-ironicclient silently handled. Basic operations such as “power reboot” and “set boot device” will now be retried automatically if they fail. For more information, please see story 2009107.

10.7.0

Bug Fixes

  • Fixes an issue where a failed inspection due to a transient failure can prevent retry attempts to inspect to be perceived as a failure. If a prior inspection fails and is in error state, when a new introspection is requested, the state is now appropriately set to starting.