grub2-mkconfig fail with composefs enabled

[karuboniru]

$ journalctl -b -3 -u ostree-finalize-staged.service --output=cat
Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
Finalizing staged deployment
Copying /etc changes: 16 modified, 8 removed, 138 added
Copying /etc changes: 16 modified, 8 removed, 138 added
Refreshing SELinux policy
Refreshed SELinux policy in 1820 ms
Finalized deployment
bootfs is sufficient for calculated new size: 149.2 MB
error: Bootloader write config: grub2-mkconfig: 子进程已退出，代码 1
ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
ostree-finalize-staged.service: Failed with result 'exit-code'.
Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
ostree-finalize-staged.service: Consumed 4.059s CPU time, no IP traffic.

子进程已退出，代码 1 should be translation of child process has exited with code 1.

---

manually running grub2-mkconfig gives:

$ sudo grub2-mkconfig -o /dev/null
/usr/sbin/grub2-probe: error: failed to get canonical path of `overlay'.

---

It seems that grub2-probe failed to understand the filesystem layout with composefs enabled.

---

Version

rpm -q ostree grub2-tools-minimal             
ostree-2024.3-2.fc40.x86_64
grub2-tools-minimal-2.06-118.fc40.x86_64

[cgwalters]

This is also discussed in coreos/rpm-ostree#4664 (comment) but is probably better tracked here. Conceptually though it's a grub issue - and I'd recommend in general that people use static grub configs.

[karuboniru]

I tried using sudo ostree config set sysroot.bootloader none and it killed my grub... Seems due to /boot/grub2/grub.cfg being a symlink to somewhere under /boot/loader which won't be generated anymore, it seems I installed this system before f37 (I can't really tell).

So, after applying the command try to check if this is the case for you.

[cgwalters]

This one really wants composefs/composefs#280

[cgwalters]

Filed a bug with a patch at https://bugzilla.redhat.com/show_bug.cgi?id=2308594

[cgwalters]

To cross-link the status quo on this is basically that for systems that aren't using static grub configs (usually via bootupd at least for Fedora derivatives) - a change landed in coreos/bootupd#790 and was enabled for at least Fedora Silverblue that effectively works around this.