2025.2 Series Release Notes

11.2.1

Deprecation Notes

  • If a volume_name is present in the skip_block_devices property, the function validate_confiuguration will now fail unless all logical disks in the target_raid_config have a volume_name specified.

Security Issues

  • During bootc deployment, the container registry pull secret was written to a well-known path on the host and passed to podman run via --authfile. Because the container runs with --privileged --pid=host, tenant-controlled code in the bootc image could read the credential through /proc/1/root/<authfile-path>. When the pull secret originates from an operator or admin source (driver_info.image_pull_secret, [deploy] image_server_user/password, or [oci] authentication_config) rather than the tenant’s own instance_info.image_pull_secret, this constitutes a cross-boundary credential disclosure to tenant-controlled bootc image code. The image pull is now performed in a separate podman pull step and the auth file is deleted before the tenant container executes. The subsequent podman run uses --pull=never so that no registry credentials are required or present at container runtime. Addresses CVE-2026-54422.

  • Disable installation of bootloaders (via grub-install) by default in order to improve security posture by adding a new configuration option enable_bios_bootloader_install which defaults to False. Operators who still need this functionality can re-enable installation of bootloaders by setting enable_bios_bootloader_install to True. Addresses CVE-2026-43003.

  • The GET /v1/commands and GET /v1/commands/<uuid> API endpoints now always validate the agent_token, matching the POST endpoint. Previously, these GET endpoints only started enforcing the token once a GET request happened to supply one, so if that never occurred, e.g. in typical POST/heartbeat-driven deployments, the endpoints could remain unauthenticated indefinitely. See bug 2160196 for details.

  • Fixes a shell command injection vulnerability in the NTP clock synchronization when using chrony. The ntp_server configuration value was interpolated into a shell command string, allowing a crafted value to execute arbitrary system commands. The chrony execution path no longer uses a shell, and the ntp_server value is now validated and sanitized before use. See bug 2160050 for details.

Bug Fixes

  • Fixes matching hints with lists of WWN/Serial which was only handled in some cases - due to the issue, it was possible to choose a device listed in the skip_block_devices property as a root device.

  • Fixes an issue where the agent could not find a valid IP address when the Ironic API was running on a non-standard port. The reachability test now uses the full API URL including the port number, instead of only using the hostname. This prevents LookupAgentIPError when connecting to Ironic APIs on custom ports.

  • Fixes RuntimeError when entering rescue mode by checking if the heartbeater thread is alive before attempting to stop it.

  • The skip_block_devices property now supports RAIDs, including scenarios with multiple arrays on the same physical disk. This included 6 smaller bugs that have all been addressed.

  • The agent now tests Ironic API URL reachability via HTTP during startup before determining the advertised IP address. Unreachable API URLs are filtered out, preventing the agent from advertising an IP address that cannot actually reach the Ironic API. This improves reliability when multiple API URLs are configured or in complex network topologies. The IP reachability test uses the configured http_request_timeout (default 30 seconds) timeout for the HTTP request.

11.2.0

New Features

  • Adds a new configuration option [DEFAULT]image_download_max_duration, which enforces a maximum total duration (in seconds) allowed for downloading an image. If this threshold is exceeded, the download is aborted with a non-retryable ImageDownloadTimeoutError exception.

    A value of 0 (the default) disables this feature.

  • Adds device transport type tran that can be used as root device hint that typically suited for locate devices with different bus types like SSD and NVME.