Current Series Release Notes


New Features

  • Allows disabling automated cleaning per node if it is enabled globally. An existing automated_clean field will allow disabling of automated cleaning on the node object. A new baremetal:node:disable_cleaning policy is added which defaults to baremetal:node:update.

  • Retrieves BIOS configuration settings when moving a node to manageable. This allows the settings to be used when choosing which node to deploy. For more details, see story 2008326.

  • When deploying a node with software RAID with an image not from Glance, the new instance_info field image_rootfs_uuid can be used to specify the UUID of the root partition to install the bootloader on.

  • The ramdisk log filename will contain the node name when it exists.

  • Provides a new vendor passthru method for Redfish to eject a virtual_media device. A specific device can be given (either cd, dvd, floppy, or usb), or if no device is provided then all attached devices will be ejected.

Known Issues

  • When redfish-virtual-media is used, fast-track mode will not work as expected, nodes will be rebooted between operations.

Upgrade Notes

  • The default value of [api]api_workers is now limited to 4. Set it explicitly if you need a higher value.

  • Agent raid will remove the root device hint after the RAID configuration is successfully deleted.

Bug Fixes

  • No longer launches too many API workers on systems with a lot of CPU cores by default.

  • Fixes the logic which determines the partition table type to utilize with partition images account for the boot mode of the machine. If no value is set by the API user, Ironic now correctly defaults to GPT if the node has been set in UEFI mode.

  • fixes an issue that physical_network could be set to an empty string, which makes the port unusable.

  • Fixes recognition of a busy agent to also handle recognition during deployment steps by more uniformly detecting and identifying when the ironic-python-agent service is busy.

  • Fix an issue when using idrac with vmedia and trying to inspect a node.

  • Correctly handles the node’s custom network data when the noop network interface is used. Previously it was ignored.

  • Fixes incorrect injected network data location when using virtual media.

  • Fixes redfish BIOS apply_configuration clean and deploy step to fail correctly in case of error when checking if BIOS updates are successfully applied. Before the fix when BIOS updates were unsuccessful, then node cleaning or deploying failed with timeout instead of actual error in clean or deploy step.

  • Fixes idrac-wsman RAID create_configuration clean step, apply_configuration deploy step and delete_configuration clean and deploy step to fail correctly in case of error when checking completed jobs. Before the fix when RAID job failed, then node cleaning or deploying failed with timeout instead of actual error in clean or deploy step.

  • Calculating the ipmitool -N and -R arguments from ironic.conf [ipmi] command_retry_timeout and min_command_interval now takes into account the 1 second interval increment that ipmitool adds on each retry event.

    Failure-path ipmitool run duration will now be just less than command_retry_timeout instead of much longer.

  • When configured to use json-rpc, the [DEFAULT].host configuration option to ironic-conductor can now be set to an IPv6 address. Previously it could only be an IPv4 address or a DNS name.

  • No longer tries to pass BOOTIF=None as a kernel parameter when using virtual media. This could break inspection.

  • Fixes the issue that when the MAC address of a port group is not set and been attached to instance, the landed bond port cannot get IP address due to inconsistent MAC address between the tenant port and the initially allocated one in the config drive.

  • Fixes the issue that root device hint is not removed after agent raid interface has successfully deleted RAID configuration, the previous hint is not guranteed to be valid thus will cause a deployment failed.

  • Fixes a bug where a conductor could fail to complete a deployment if there was contention on a shared lock. This would manifest as an instance being stuck in the “deploying” state, though the node had in fact started or even completed its final boot.

  • After changing the boot device via Redfish, check that the boot mode being reported matches what is configured and, if not, set it to the configured value. Some BMCs change the boot mode when the device is set via Redfish, see story 2008252 for details.

  • Fixes wiping agent token on rebooting via API.

  • The virtual media ISO image building process now respects the default_boot_mode configuration option.

  • Fixes timeout in fast-track mode with redfish-virtual-media when running one operation after another (e.g. cleaning after inspection).

  • Fixes permission issues when injecting network data into a virtual media.

  • Adds timeout to HTTP image validation and downloading operations, so that the direct deploy does not hang when the remote server is not responsive. The default timeout is 60 seconds and can be changed via the new webserver_connection_timeout option.

Other Notes

  • The configdrive argument to some utils in ironic.common.images and ironic.drivers.modules.image_utils has been replaced with a new inject_files argument. The previous approach did not really work in all situations and we don’t expect 3rd party drivers to use it.