-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support bootupd
for bootloader management/updates
#6
Comments
We looked at doing UC via the pungi/koji build (I think this is what SB uses) to be consumed by osbuild as a short term hack while the osbuild support landed. Not sure where we got there. Colin also said on our sync at one point that bootupd could be decoupled from UC. |
It should be possible to start using Additional investigation will be required. |
Since Fedora IoT has switched to using unified-core for composes (see #7 ), we should be able to pursue enabling If I look at how it was done for Silverblue (https://pagure.io/workstation-ostree-config/pull-request/403), the changes to the compose look pretty straight-forward: just the inclusion of the @paulwhalen is this something we can try in Rawhide? Do you think we need a Fedora Change for it? |
We've missed the change deadline for Fedora 40, but I don't think that prevents us from enabling it. |
Looks like the Silverblue enablement hit some snags - fedora-silverblue/issue-tracker#530 |
Enabled in Rawhide and included in Fedora-IoT-41-20240223.0 PR for f40 |
Enabled in F40 composes since Fedora-IoT-40-20240227.1 PR to add in osbuild/images. |
This was later reverted due to issues with anaconda. Still enabled in F41. |
Is your feature request related to a problem? Please describe.
When we update Fedora IoT via
rpm-ostree upgrade
, the bootloader binaries remains unchanged due the fact that theostree
model does not cover changes to the bootloader. Thus, users need to manually intervene to workaround this limitation and ensure the GRUB + UEFI shim firmware are up-to-date.Describe the solution you'd like
Fedora IoT should be produced in a way that allows the use of
bootupd
to update the bootloader successfully.Describe alternatives you've considered
Current alternative is a manual intervention by the user to copy the GRUB + UEFI shim from the ostree commit to the
/boot
partition. See fedora-silverblue/issue-tracker#120 (comment)Additional context
Supporting
bootupd
requires that Fedora IoT is built using "unified-core" mode, which is not yet supported by osbuild.See also: https://gitlab.com/CentOS/cloud/issue-tracker/-/issues/6
The text was updated successfully, but these errors were encountered: