2023.1 Series Release Notes¶

9.4.0-8¶

Fixes a failure case where a deployed instance may be unable to access the configuration drive post-deployment. This can occur when block devices only support 4KB IO interactions. When 4KB block IO sizes are in use, the ISO9660 filesystem driver in Linux cannot be used as it is modeled around a 2KB block. We now attempt to verify, and rebuild the configuration drive on a FAT filesystem when we cannot mount the supplied configuration drive. Operators can force the agent to write configuration drives using the FAT filesystem using the [DEFAULT]config_drive_rebuild option.

Fixes a failure case where downloads would not be retried when the checksum fails verification. the agent now includes the checksum activity as part of the file download operation, and will automatically retry downloads when the checksum fails in accordance with the existing download retry logic. This is largely in response to what appears to be intermittent transport failures at lower levels which we cannot otherwise detect.

Fixes UEFI NVRAM record handling with efibootmgr so we can accept and handle UTF-16 encoded data which is to be expected in UEFI NVRAM as the records are UTF-16 encoded.

Fixes handling of UEFI NVRAM records to allow for unexpected characters in the response, so it is non-fatal to Ironic.

Fixes an issue with rebuilding instances on Software RAID with RAIDed ESP partitions.

Fixes, or at least lessens the case where a running Ironic agent can stack up numerous lookup requests against an Ironic deployment when a node is locked. In particular, this is beause the lookup also drives generation of the agent token, which requires the conductor to allocate a worker, and generate the token, and return the result to the API client. Ironic’s retry logic will now wait up to 60 seconds, and if an HTTP Conflict (409) message is received, the agent will automatically pause lookup operations for thirty seconds as opposed continue to attempt lookups which could create more work for the Ironic deployment needlessly.

The agent now logs the size of data transferred when downloading images, which can be helpful in troubleshooting image download issues.

Add two clean steps MellanoxDeviceHardwareManager to update NVIDIA NICs firmware images and settings, * update_nvidia_nic_firmware_image * update_nvidia_nic_firmware_settings

Ramdisk log collection now uses the hardware managers mechanism. You can provide a collect_system_logs call to extend the collection process.

When detecting a serial number of a block device, the agent now tries to use lsblk first and only falls back to udev if lsblk does not return a serial number. Based on experience it looks like lsblk might be a better source of truth than udev in regerard to serial number information.