Blivet-GUI Partitioning does not check that a /boot partition is created, but Anaconda will fail to install grub2 without one

[krzentner]

What happened?

I suspect this issue applies to at least all ublue installers, although I encountered it specifically with Bazzite 40 (using bazzite-stable.iso).
I selected Blivet-GUI to setup partitions. Because I was using a ext4 root partition (unencrypted), I did not create a separate /boot partition. Blivet-GUI told me I needed to fill the /boot/efi mountpoint, so I created a biosboot and EFI partition, and mounted the EFI partition in /boot/efi.
Part way through boot, anaconda tries to configure grub2, and crashes because /boot/grub2 does not exist.
I was able to work around this issue by installing a new drive into my computer and using the automatic partitioning.

I expected either Blivet-GUI to give me an error message saying to create a /boot partition (probably the easier option to implement), or for Anaconda to install grub2 into my root partition (an unencrypted ext4 volume).

I'm not sure if this is the right place to file this bug report. Unfortunately, I also do not have logs, although I will try to reproduce the issue on another computer.

Relevant log output

Please attach or paste the logs from the Anaconda Installer https://docs.fedoraproject.org/en-US/quick-docs/anaconda/anaconda_logging/

[krzentner]

I've managed to reproduce this on a second system. Here are the resulting log files:
ls_R_sysroot_boot.txt
packaging.log
program.log
storage.log
anaconda.log
journalctl.log

[dosubot]

Hi, @krzentner,

I'm helping the Main Repos team manage their backlog and am marking this issue as stale. Your report indicates that the Blivet-GUI partitioning tool fails to prompt for a /boot partition, which prevents Anaconda from installing grub2 during the installation process with the Bazzite 40 installer. You've successfully reproduced this issue on another system and provided log files for further investigation, along with suggestions for potential solutions.

Could you please let us know if this issue is still relevant to the latest version of the Main Repos repository? If it is, feel free to comment here to keep the issue open. Otherwise, you can close it yourself, or it will be automatically closed in 7 days.

Thank you!