Bug #38839
closedKickstart dynamic partition table fails on UEFI systems
Description
[Summary]¶
The Kickstart dynamic partition table fails during provisioning on UEFI hosts because `/boot/efi` is not created.
[Description]¶
When using the Kickstart dynamic partition table to provision a host in UEFI mode,
the installation fails during partitioning with the following error message:
Failed to find a suitable stage1 device: EFI System Partition cannot be of type ext4. EFI System Partition must be mounted on one of /boot/efi.
[Steps to Reproduce]¶
1. Create a host configured for UEFI boot (e.g. Rocky Linux 9).
2. Assign the Kickstart dynamic partition table to the host.
3. Start provisioning.
4. Observe that Anaconda fails during the partitioning step.
[Actual Behavior]¶
The `%pre` script of the Kickstart dynamic template generates `/boot`, `/`, and `swap` partitions in `/tmp/diskpart.cfg`,
but does not create a `/boot/efi` partition.
As a result, Anaconda cannot find a valid EFI System Partition and the installation aborts.
[Expected Behavior]¶
The Kickstart dynamic partition table should detect whether the system is booted in UEFI mode
and generate a `/boot/efi` (vfat) partition along with `/boot`, `/`, and `swap` in that case,
while skipping the creation of `/boot/efi` when running under Legacy BIOS mode,
allowing installation to complete successfully under both Legacy BIOS and UEFI environments.
Updated by The Foreman Bot 3 months ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/10748 added
Updated by Anonymous 2 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|805487c790f987a68a9d3c50bd6e912953d03414.