2023.1 Series (9.2.0 - 9.4.x) Release Notes¶

9.4.3¶

Fixes an issue where configuration drive volumes which are mountedby the operating system could remain mounted and cause a lock to beheld, which may conflict with actions such asrebuild.The agent now always makes sure the folder used by Glean and Cloud-initis not mounted.

Fixes bug 2066308, an issue where Ironic Python Agent would callevaluate_hardware_support multiple times on hardware manager plugins.Scanning for hardware and disks is time consuming, and caused timeoutson badly-performing nodes.

Deployers implementing their ownHardwareManagers must to audit their code for unsafe uses ofqemu-img and related methods.

Ironic-Python-Agent now checks any supplied image format value against the detected format of the image file and will prevent deployments shouldthe values mismatch.

Images previously misconfigured as raw despite being in another format, in some non-default configurations, may have been mistakenly converted ifneeded. Ironic-Python-Agent will no longer perform conversion in any casefor images with metadata indicating in raw format.

Ironic-Python-Agentalways inspects any non-raw user image content for safety before running any qemu-based utilities on the image. This is utilized to identify the format of the image and to verify the overall safety of the image. Any images with unknown or unsafe feature uses are explicitly rejected. This can be disabled in both IPA and Ironic by setting[conductor]disable_deep_image_inspection toTrue for the Ironicdeployment. Image inspection is the primary mitigation for CVE-2024-44082 being tracked inbug 2071740.Operators may desire to set[conductor]conductor_always_validates_images on Ironic conductors to mitigate the issue before they have upgraded their Ironic-Python-Agent.

Ironic-Python-Agent now explicitly enforces a list of permitted image types for deployment, defaulting to “raw” and “qcow2”. Other image types may work, but are not explicitly supported and must be enabled. This can be modified by setting[conductor]permitted_image_formats for all Ironic services.

Fixes multiple issues in the handling of images as it related to execution of theqemu-img utility. When using this utility to convertan unsafe image, a malicious user can extract information from a node while Ironic-Python-Agent is deploying or converting an image. Ironic-Python-Agent now inspects all non-raw images for safety, and neverruns qemu-based utilities on raw images. This fix is tracked as CVE-2024-44082 andbug 2071740.

Images with metadata indicating a “raw” disk format may have been transparently converted from another format. Now, these images will have their exact contents imaged to disk without modification.

Fixes a failure case where a deployed instance may be unable to accessthe configuration drive post-deployment. This can occur when blockdevices only support 4KB IO interactions. When 4KB block IO sizesare in use, the ISO9660 filesystem driver in Linux cannot be usedas it is modeled around a 2KB block. We now attempt to verify, andrebuild the configuration drive on a FAT filesystem when we cannotmount the supplied configuration drive. Operators can force the agentto 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 thechecksum fails verification. the agent now includes the checksumactivity as part of the file download operation, and willautomatically retry downloads when the checksum fails inaccordance with the existing download retry logic.This is largely in response to what appears to be intermittenttransport failures at lower levels which we cannot otherwisedetect.

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

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

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

Fixes, or at least lessens the case where a running Ironic agent can stackup numerous lookup requests against an Ironic deployment when a node islocked. In particular, this is beause the lookup also drives generation ofthe agent token, which requires the conductor to allocate a worker, andgenerate the token, and return the result to the API client.Ironic’s retry logic will now wait up to60 seconds, and if an HTTPConflict (409) message is received, the agent will automatically pauselookup operations for thirty seconds as opposed continue to attemptlookups which could create more work for the Ironic deploymentneedlessly.

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 updateNVIDIA NICs firmware images and settings,* update_nvidia_nic_firmware_image* update_nvidia_nic_firmware_settings