In Fedora 43, Kickstart/Anaconda seems to have lost the ability to install the "systemd-boot" bootloader. It can now only install Grub. Both the "inst.sdboot" cmdline parameter and the "--sdboot" option to the "bootloader" command are ignored. This is a regression, it was working in Fedora 42. Reproducible: Always Steps to Reproduce: 1. Run a kickstart installation of Fedora 43 (with or without "inst.sdboot" cmdline option), where you request sdboot via the "bootloader --sdboot" kickstart command. Sample kickstart script: bootloader --sdboot ignoredisk --only-use=sda network --device=link --hostname=box rootpw "very-strong-secret" url --url 'http://our.mirror.cz/repo/fedora/linux/releases/43/Everything/x86_64/os' clearpart --all --initlabel zerombr reboot part /boot/efi --size=600 part /boot --fstype=ext4 --size=1024 part / --fstype=ext4 --grow %packages @core vim-enhanced vim-default-editor %end Notes: - adding or omitting the "inst.sdboot" cmdline parameter gives the same results - the same kickstart file (except "--url") installs sdboot as expected, when using F42 installer Actual Results: After installation, the computer boots into grub. Expected Results: After installation, the computer should boot into sdboot.
What installer image did you use? Can you please attach the log files from /var/log/anaconda ?
Created attachment 2117193 [details] anaconda logs The installer image (install.img) comes from our in-house server, so I can't see its origin right now. I would guess it's probably the same as the one from the "everything-netinstall" iso (https://fedoraproject.org/misc). I will verify this with our admin team and comment here again when I have a definite answer. The logs have been attached (var-log-anaconda.tgz). This has been reported earlier, on fedora discussion (using the "everything-netinstall" iso): https://discussion.fedoraproject.org/t/systemd-boot-not-installing-with-netinstall/172170/8
Our installer image (install.img) is mirrored from here: https://ftp.halifax.rwth-aachen.de/fedora/linux/releases/43/Everything/x86_64/os/images/
Installer image direct download: https://ftp.halifax.rwth-aachen.de/fedora/linux/releases/43/Everything/x86_64/os/images/install.img sha1sum: 833706cc6ffc08decc5b025ceb27f5a92fe2a886 md5sum: 6e199ea4ece629713bfb10ddd92491d7 Our mirrored install.img has the same checksums, so it's certainly the same file.
Created attachment 2117738 [details] anaconda-logs-F42.tgz Adding logs from an F42 install. Grepping for "Created the boot loader" shows that in F43, the "EFIGRUB" boot loader is created instead of "X64EFISystemdBoot": $ grep -Fn "Created the boot loader" 42/syslog 3900:10:14:55,865 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:anaconda.modules.storage.bootloader.factory:Created the boot loader X64EFISystemdBoot. $ grep -Fn "Created the boot loader" 43/syslog 4995:01:56:00,636 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:anaconda.modules.storage.bootloader.factory:Created the boot loader EFIGRUB.
Created attachment 2117744 [details] anaconda-logs-debug.tgz Uploading an archive with both logs (F43 and F42), from the same machine (virtualbox), with inst.sdboot and inst.debug on.
In anaconda-logs-debug (previous attachment), we see that the default type is set correctly to SDBOOT: $ grep -Fnr "The default type is set" anaconda-logs-debug/43/storage.log 13:DEBUG:anaconda.modules.storage.bootloader.bootloader:The default type is set to 'BootloaderType.SDBOOT'. 115:DEBUG:anaconda.modules.storage.bootloader.bootloader:The default type is set to 'BootloaderType.SDBOOT'. But is the default class (which is used in create_boot_loader()) also correct? Let's add some logging to check: https://github.com/rhinstaller/anaconda/pull/6797
*** This bug has been marked as a duplicate of bug 2402975 ***