Current Series Release Notes¶

In Development - Unreleased¶

Adds a traits field to runbooks, decoupling runbook eligibility from the runbook name. A runbook may now have any logical name; the set of traits on the runbook determines which nodes are permitted to use it. API microversion 1.112 is required to use this feature.

Adds a description field to runbooks, consistent with other Ironic objects. The field is available from API microversion 1.112 onwards and is included in the runbook body when retrieved via the API.

Runbook names are no longer required to be valid OpenStack trait strings when using API microversion 1.112 or later. Any string of 1–255 characters is now accepted as a runbook name.

The iLO and iLO5 hardware types and all their interfaces (bios, boot, inspect, management, power, raid, vendor) have been removed. Users of the iLO drivers should migrate to the redfish hardware type, which provides equivalent functionality for HPE ProLiant servers.

The iRMC hardware type and all its interfaces have been removed. Users of the iRMC driver should migrate to a supported hardware type, preferably redfish.

The pysnmp-lextudio, pyasn1, and pyasn1-modules libraries have been removed from both driver and test requirements, as they are no longer needed after the removal of the SNMP and iRMC drivers.

The SNMP hardware type and power interface has been removed. Users of the SNMP power driver should migrate to a supported hardware type, preferably redfish.

An online data migration (migrate_runbook_names_to_traits) seeds the runbook_traits table from the current runbook names. This migration runs as part of ironic-dbsync online_data_migrations and can be executed in batches while the service is running. Existing runbooks whose names were valid trait strings will continue to match nodes via the new trait-based mechanism. Runbooks created before API microversion 1.112 are not affected by the node matching logic change until they are updated via the new traits endpoints.

A quirk to note for users of the new runbook traits. Runbooks created using API microversion >=1.112, then later viewed with API microversions <1.112, may have names that do not conform to the custom traits schema (CUSTOM_*) previously enforced for runbook names.

Fixes an issue where the task for NIC firmware update completed before the first poll cycle could complete. This caused firmware caching to run before the OS had fully booted, preventing updated firmware information from being stored in the database.

Fixes an issue where immediate reboots can interrupt the initialization of NIC firmware update.

[Bug 2146585] iDRAC devices report their Service Tag in the Redfish SKU field, which should be treated as the chassis serial number. The idrac-redfish driver already overrode serial_number with the SKU value, but the fix-up ran after inventory was stored and inspection rules were evaluated, causing rules to see the wrong serial_number. The override now happens inline via _get_system_vendor_info so the correct value is present before storage and rule evaluation.

Allow the set_bmc_clock management setup in the redfish interface to set the time to the conductor if the time is not explicitly provided. This makes it possible to call this step and get an accurate time. For Ironic to manage the BMC, the time must be inline with the conductor so this is a better reasonable default. This also makes it possible to use the set_bmc_clock in runbooks, as originally intended, because users cannot supply a time for the runbooks without this fix the runbook could only ever set the time to a fixed value which isn’t useful. Fixes bug 2146355.

Issue a soft power off before ejecting virtual media after inspection, regardless of the value of the [inspector]power_off configuration option. Powering off before ejecting virtual media is needed to avoid filesystem corruption errors on nodes (particularly visible on iDRAC consoles) when the operating system loses access to its boot media during shutdown. This power off is needed regardless of the value of the [inspector]power_off configuration option, which is about whether a node should be powered off after inspection.

Removes compatibility with Ironic Python Agent versions without support for in-band deploy steps (introduced in the Ussuri cycle).