Silverblue 41 installation is missing /boot/grub2/grubenv and /etc/default/grub files

[Jmennius]

I was recently installing Fedora Silverblue 41 nightly build (Fedora-Silverblue-ostree-x86_64-41-20241012.n.0.iso) and I've noticed that the system was missing /boot/grub2/grubenv and /etc/default/grub files.

Although the system boots fine, I'm pretty sure this is a bug because grub menu is not automatically hidden, boots cannot be marked as successful and so on (grubenv is not created after the install was done under any circumstance automatically).

I was doing an installation via a kickstart file (for advanced encryption option), but I've customized a file that I got from a test install (although I think it was Beta 1.2 image).

I've contacted anaconda team (as it was creating those files before - see write_defaults() and write_config() in https://github.com/rhinstaller/anaconda/blob/4683a8965ce02443134115e3eeea58ec6df38da3/pyanaconda/modules/storage/bootloader/grub2.py#L253) and they said this is now responsibility of bootupd :)

[Jmennius]

Should I instead open a bugzilla issue instead/in addition to?

[HuijingHei]

Not sure if we should make bootupd to create these 2 files, can we reuse anaconda? Any other scenarios that we need them?
Maybe @travier @cgwalters know about this.

[travier]

We should probably create /boot/grub2/grubenv but likely not /etc/default/grub as we don't need it anymore.

[Jmennius]

We should probably create /boot/grub2/grubenv but likely not /etc/default/grub as we don't need it anymore.

Regarding defaults - not so sure.
If a user creates the file because he wants to configure something - he is most likely to not put the BLSCFG variable as well as other variables.
Right now, when there is no defaults file, ostree grub script will just exit.
If the defaults file exists it wants BLSCFG variable to be set and /boot/grub/.blscfg file to be present (which is not the case) to not generate boot entries for grub (which avoid duplicate boot entries)...