PR#303: f36 bootupd - workstation-ostree-config

workstation-ostree-config

#303 f36 bootupd

Merged 2 years ago by siosm. Opened 2 years ago by walters.

https://pagure.io/forks/walters/workstation-ostree-config.git f36-bootupd into f36

common: Move bootupd to arch specific package list

Timothée Ravier • 2 years ago

9b0ac69

common: add bootupd

Jonathan Lebon • 2 years ago

fb7be0d

fedora-common-ostree.yaml

file modified

+2 -1

		`@@ -49,8 +49,8 @@`

		`default_target: graphical.target`

		`- # Keep this in sync with fedora-atomic-host.json from fedora-atomic`
		`packages-aarch64:`
		`+ - bootupd`
		`- grub2-efi`
		`- ostree-grub2`
		`- efibootmgr`
		`@@ -65,6 +65,7 @@`
		`- grub2`
		`- ostree-grub2`
		`packages-x86_64:`
		`+ - bootupd`
		`- grub2-efi-ia32`
		`- grub2-efi-x64`
		`- grub2-pc`

walters commented 2 years ago

common: add bootupd

We need to make it easier to update the bootloader on these variants
because unlike on traditional systems, it's not updated automatically
with the rest of the system. Add bootupd for that.

This would allow fixing issues like:
- https://github.com/coreos/rpm-ostree/issues/3715
- https://github.com/fedora-silverblue/issue-tracker/issues/120#issuecomment-979268679

It won't be enabled by default and as mentioned in that comment requires
work in Anaconda to be seamless. But at least with this users should be
able to adopt and update:

https://github.com/coreos/bootupd/blob/main/README-design.md

See also the tracker issue where we did this for Fedora CoreOS:

https://github.com/coreos/fedora-coreos-tracker/issues/510
(cherry picked from commit d34e2ee500fc4a920baa6aa2aab53265f255b884)

common: Move bootupd to arch specific package list

We only have bootup for x86 & aarch64.

Fixes: d34e2ee common: add bootupd
(cherry picked from commit 1515900d35d32183ef0982e19e91c30c06920f41)

walters commented 2 years ago

common: add bootupd

We need to make it easier to update the bootloader on these variants
because unlike on traditional systems, it's not updated automatically
with the rest of the system. Add bootupd for that.

This would allow fixing issues like:
- https://github.com/coreos/rpm-ostree/issues/3715
- https://github.com/fedora-silverblue/issue-tracker/issues/120#issuecomment-979268679

It won't be enabled by default and as mentioned in that comment requires
work in Anaconda to be seamless. But at least with this users should be
able to adopt and update:

https://github.com/coreos/bootupd/blob/main/README-design.md

See also the tracker issue where we did this for Fedora CoreOS:

https://github.com/coreos/fedora-coreos-tracker/issues/510
(cherry picked from commit d34e2ee500fc4a920baa6aa2aab53265f255b884)

common: Move bootupd to arch specific package list

We only have bootup for x86 & aarch64.

Fixes: d34e2ee common: add bootupd
(cherry picked from commit 1515900d35d32183ef0982e19e91c30c06920f41)

tpopela commented 2 years ago

This generally looks good to me (any particular reason why this is targeting F36 only and not F37 as well?), @walters what is the experience so far from FCOS with bootupd? Are there any known issues that users are hitting?

siosm commented 2 years ago

Yes, we need this one for F37 too.
We have someone trying out bootupd in Silverblue and hitting issues: https://github.com/fedora-silverblue/issue-tracker/issues/355

siosm commented 2 years ago

But this does not stop us from adding it and we can fix issues as they come