Current Series Release Notes

In Development - Unreleased

New Features

  • Adds manufacturer, model and system UUID information to the redfish sensor data collector.

Deprecation Notes

  • Using ironic.api.wsgi:initialize_wsgi_app to provide custom config file to ironic is now deprecated.

    Instead, two new environment variables IRONIC_CONFIG_DIR and IRONIC_CONFIG_FILE are introduced to provide the same functionality.

Bug Fixes

  • Reduces likelihood of intermittent firmware upgrade failures by adding comprehensive BMC state validation after firmware upgrades for the Redfish driver. After a firmware update task completes successfully, Ironic now validates that BMC resources (System, Manager, and NetworkAdapters) are consistently available before proceeding with subsequent operations.

    This change improves firmware update reliability by requiring a configurable number of consecutive successful responses from the BMC resources. The validation process helps ensure the BMC has fully stabilized after firmware updates before marking the operation as complete.

    New configuration options in the [redfish] section:

    • firmware_update_required_successes - Number of consecutive successful responses required to consider BMC validation successful (default: 3), 0 disables validation

    • firmware_update_validation_interval - Time in seconds to wait between validation attempts (default: 30)

    • firmware_update_resource_validation_timeout - Maximum time in seconds to wait for BMC resources to stabilize (default: 300), setting it to 0 disables validation.

  • When caching an image between different file systems, the hard link operation would fail. This is fixed by falling back to a copy operation.

  • Fixes an issue around handling of portgroup updates where the associated node ID is changed. While a rare operation, it exists as a capability and a bug existed from the wrong ID value being used to query the database. The correct ID value is now utilized.

  • Fixes ironic’s pxe filter logic which some operators may leverage to restrict access to resources as related to hardware discovery use cases. The launcher was inadvertently broken during the removal of eventlet.

  • Fixes an issue where the redfish-virtual-media interface is using version ranges with Dell iDRAC BMCs to report compatibility. Dell has changed the versioning structure for iDRAC10s which triggered the error. That being said, it appears the iDRAC10s are also incompatible as well. The error message now clearly indicates what versions are known to work with the stock redfish virtual media support. Users should instead use the idrac variant boot interface.

  • Fixes an issue where virtual media ISO creation (used by Redfish and iLO drivers) did not respect architecture-specific kernel and ramdisk configuration parameters. When deploy_kernel_by_arch and deploy_ramdisk_by_arch (or their rescue equivalents) were configured, the ISO generation would still use the generic parameters instead of selecting the correct kernel and ramdisk based on the node’s CPU architecture. This particularly affected ARM64 nodes that require different agent images than x86_64 nodes. For more information, see bug 2126991.

  • Fixed HttpImageService.validate_href() ImageRefValidationFailed exception if protocol is HTTP/HTTPS and the HTTP header response is a redirection other then 301 (MOVED_PERMANENTLY). HTTP/HTTPS protocol is often used under standalone Ironic configuration to identify an image source (e.g –instance-info image_source=<URI>). The HTTP server may use redirection to load balance or geographically distribute the requests, or simply point to the correct URL. The redirection may vary from 301 (MOVED_PERMANENTLY), to 302 (FOUND), or 307 (TEMPORARY_REDIRECT), and 308 (PERMANENT_REDIRECT).

  • Fixes an issue where some iDRAC10 machines requires a specific Virtual Media Slot. Ironic will attempt to automatically identify the version, and ensures the right slot is used to insert the iso. See bug 2125571 for details.

  • Fixes an issue where firmware upgrades would fail on HP iLO Generation 11 machines when the NetworkAdapters endpoint returns HTTP 400 (Bad Request) responses during the firmware component caching process. Exception handling allows the code to continue execution past that issue.

  • Fixes deploying OCI artifacts uploaded by ORAS to Quay.io (and potentially other registries) as a single manifest.

  • Improved Redfish compatibility with ASRock Rack servers by updating how boot mode and boot device settings are applied.

    Previously, calls to set_boot_device and set_boot_mode only included minimal parameters (e.g., BootOverrideTarget and BootOverrideMode), which were insufficient for certain vendor implementations like ASRockRack.

    This fix updates the Redfish driver to send the full payload, including BootSourceOverrideEnabled, BootSourceOverrideTarget, BootSourceOverrideMode, ensuring better compliance and reliability on these platforms.

  • The ipa-inspection-callback-url kernel parameter now uses the external_callback_url configuration when set. Previously, this URL used the internal address even when external_callback_url was configured, creating inconsistency with ipa-api-url which correctly used the external address.

Other Notes

  • For consistency with other OpenStack projects, Ironic API’s wsgi server can now be launched via ironic.wsgi.api:application as well as ironic.wsgi:application.