This bug also affects blivet-gui. Description of problem: A user may want to mount their EFI partition at /boot instead of /boot/efi if they plan to use systemd-boot instead of GRUB, but anaconda and blivet-gui both prohibit this partitioning scheme. While anaconda and blivet-gui obviously do not support systemd-boot (and thus its preferred EFI layout) it should be possible for a user to use anaconda or blivet-gui in the live CD installer to configure their partitions as desired, after which he or she can chroot into the installation and configure systemd-boot manually. Steps to Reproduce: 1. Create a primary EFI partition and set the mountpoint to /boot 2. Create a / partition for Fedora 3. Click done Actual results: Anaconda will report that "for a UEFI installation, you must include an EFI system partition on a GPT-formatted disk, mounted at /boot/efi" Expected results: Anaconda creates the partition layout as configured by the user, installs the kernel and initramfs to /boot, and skips GRUB installation. The user should be warned that no bootloader is being installed and that he or she will need to install one manually. Additional info: We shouldn't save users that forgo the automatic partition scheme and incorrectly configure their partitions for GRUB from their own stupidity at the expense of power users
Hi, I think that you should be able to achieve this configuration with a kickstart file. The commands 'bootloader' and 'mount' should provide you the required flexibility.
I worked around this by creating my luks/lvm partitioning schemes manually, then using dnf's --installroot to install fedora on the appropriate partition, after which I could chroot and set up systemd-boot.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.