See: https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd See: https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore
Revert "Disable bootupd integration until we use unified core" This reverts commit a1a8bbe8bb3ba6d31b9fe406e6fe026388696810.
Build succeeded.
rebased onto a91e5472607b18009f3c17d8dc8ffb7059a67a40
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/db9fe4a3cf2a4ac0b2d597f1cce80ea7
rebased onto 819da5c8ecf3c707f87ddf5309926fe0160afe76
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/b8e594cae2ff430983887d0126c35a85
Pull-Request has been merged by siosm
Ah. I think this broke stuff. Right around the time it got merged, openQA Silverblue install tests started failing:
https://openqa.fedoraproject.org/tests/2033992
the logs show:
13:51:31,366 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:anaconda.modules.common.task.task:Install the bootloader 13:51:31,366 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:anaconda.modules.storage.bootloader.utils:Installing the boot loader. 13:51:31,367 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:anaconda.modules.storage.bootloader.utils:boot loader stage1 target device is vda 13:51:31,367 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:anaconda.modules.storage.bootloader.utils:boot loader stage2 target device is vda2 13:51:31,420 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:anaconda.modules.storage.bootloader.grub2:bootloader.py: used boot args: rhgb quiet 13:51:31,422 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:program:Running in chroot '/mnt/sysroot'... grub2-editenv - set menu_auto_hide=1 boot_success=1 13:51:31,488 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:program:grub2-editenv: error: cannot open `/boot/grub2/grubenv.new': No such file or directory. 13:51:31,488 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:program:Return code: 1
then an awful lot of similar, subsequent errors where it can't find grub files it expects to find.
OK there's a lot going on in Anaconda's Bootloader::write_config for grub.
Bootloader::write_config
First clearly it'd need to learn how to use bootupctl to install if we want bootupd to own the bootloader.
bootupctl
But also there's stuff here (and the thing that's failing) is to edit the grub environment - but that hiding logic is really desktop-specific and not something we want on servers; we remove it on CoreOS and soon IoT.
grub2-set-default
grub2-mkconfig
See: https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
See: https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore
Revert "Disable bootupd integration until we use unified core"
This reverts commit a1a8bbe8bb3ba6d31b9fe406e6fe026388696810.