Current Series Release Notes

13.0.0-10

Upgrade Notes

  • Ironic Python Agent no longer invokes sgdisk, so the gptfdisk package is not required in the deployment ramdisk any more. See bug 2170355.

Bug Fixes

  • Fixes detection of SELinux when preparing a bootc deployment. The agent determined the state by running getenforce, which reports what the agent’s own userspace believes. When the agent itself runs inside a container, libselinux reports SELinux as disabled even though selinuxfs is mounted and the kernel is enforcing, so the agent omitted --security-opt label=type:unconfined_t from the podman invocation and passed --disable-selinux to bootc. The install then failed while writing the SELinux labels carried by the image with fsetxattr(security.selinux): Invalid argument. The kernel state is now read from /sys/fs/selinux/enforce, which is what governs the nested container, and getenforce is only consulted as a fallback when selinuxfs is unreachable.

  • Fixes bootc based container deployments failing to authenticate to a remote registry when the supplied pull secret was not already the base64 encoded docker config.json “auth” value. The value written to podman’s authfile auth field is now base64 encoded when required, so a raw username:password pair, or a token containing characters outside of the base64 alphabet, no longer causes podman to fail with illegal base64 data or to silently fall back to an anonymous pull. Credentials already supplied in the documented base64 format continue to be used unchanged. See bug 2168735.

  • Stop calling sgdisk -Z when destroying disk metadata. The GPT and MBR structures are already removed by wipefs --all and by zeroing the primary and backup GPT areas, which keeps working on disks with corrupt partition tables. See bug 2170355.

  • Replace sgdisk with sfdisk for GPT verification and backup-header relocation. IPA now uses sfdisk --verify and sfdisk --relocate gpt-bak-std, improving compatibility with systems that do not provide gptfdisk. See bug 2170355.

  • Replace sgdisk partition creation with parted and sfdisk. GPT config-drive partitions now use parted with PARTUUID assignment through sfdisk, while RAID ESP and BIOS-boot partitions use sfdisk --append. RAID partition sizes, alignment, GPT types, and labels are preserved. GPT config-drive creation now uses parted’s FAT32 filesystem type and GPT naming semantics, which may result in a different GPT type and partition name than the previous sgdisk path. This improves compatibility with systems that do not provide gptfdisk. See bug 2170355.

  • Replace sgdisk with sfdisk for GPT partition UUID lookup and free space detection. This improves compatibility with distributions that no longer provide the gptfdisk package. See bug 2170355.