Bug 2270154 - Partially revert bootupd support for Atomic desktops (again)
Summary: Partially revert bootupd support for Atomic desktops (again)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 40
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timothée Ravier
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: BetaFreezeException, F40BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2024-03-18 16:34 UTC by Adam Williamson
Modified: 2024-03-23 16:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-23 16:48:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure workstation-ostree-config pull-request 498 0 None None None 2024-03-18 16:36:59 UTC

Description Adam Williamson 2024-03-18 16:34:25 UTC
travier wants to partially revert bootupd support again, per https://pagure.io/workstation-ostree-config/pull-request/498 , due to a couple of issues - bootupctl does not install EFI boot manager entries (we have a workaround for this in F40 currently, but it's not perfect) and does not write /etc/default/grub . See also https://gitlab.com/fedora/ostree/sig/-/issues/1 .

He asked what is necessary to do this for F40 Beta, and I said an FE bug at least is needed, so I'm filing one so we can discuss it in the current meeting.

Comment 1 Adam Williamson 2024-03-18 16:36:59 UTC
I think https://pagure.io/workstation-ostree-config/pull-request/498 alone would substantially complete this. We *could* also revert the anaconda patch, but it's probably not *necessary* at least for Beta.

Comment 2 František Zatloukal 2024-03-18 17:47:45 UTC
Discussed during the 2024-03-18 blocker review meeting: [1]

The decision to classify this bug as a AcceptedFreezeException (Beta) was made:

"We know the old way works, and the atomic desktop images are not blocking, so we're willing to defer to the maintainer's idea of what's best here since the change is limited to the atomic desktop definitions."

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-18/f40-blocker-review.2024-03-18-16.01.log.html

Comment 3 Timothée Ravier 2024-03-18 18:51:09 UTC
To summarize, we have multiple issues:

- The bootupd installation path in Anaconda does not update EFI boot entries anymore, and the workaround from https://github.com/rhinstaller/anaconda/pull/5508 is incomplete. See: https://github.com/coreos/bootupd/issues/630
- Given the way the bootupd installation path has been implemented in Anaconda, enabling bootupd also enables using static GRUB configs, which currently does not support dual booting: https://github.com/fedora-silverblue/issue-tracker/issues/530
- With static GRUB configs, /etc/default/grub is now ignored but grub2-mkconfig is still included in the image and will thus do nothing if run. This is needed for compatibility with older systems which haven't updated their bootloader yet. See: https://github.com/ostreedev/ostree/pull/3150

As it is unlikely that we'll be able to fix those issues for F40, we will remove bootupd from the images, which will revert Anaconda to the old installation path, and then we will re-add bootupd to the images after the release so that users can get their bootloaders updated.

Comment 4 Timothée Ravier 2024-03-18 18:51:57 UTC
(In reply to Adam Williamson from comment #1)
> I think https://pagure.io/workstation-ostree-config/pull-request/498 alone would substantially complete this. We *could* also revert the anaconda patch, but it's probably not *necessary* at least for Beta.

Yes, this change should be enough for the beta. We can revert the Anaconda patch after the freeze.

Comment 5 Timothée Ravier 2024-03-18 18:53:04 UTC
I've merged https://pagure.io/workstation-ostree-config/pull-request/498. This should land in tomorrow's build.

Comment 6 Adam Williamson 2024-03-18 22:00:21 UTC
"With static GRUB configs, /etc/default/grub is now ignored but grub2-mkconfig is still included in the image and will thus do nothing if run."

I'm not sure this is accurate. I think grub2-mkconfig still Does Stuff with no /etc/default/grub , but what it does may differ.

Comment 7 Timothée Ravier 2024-03-18 22:28:03 UTC
Ah yes indeed. It does nothing for the ostree part but it still does the rest, so this is likely dangerous / confusing for users.

Comment 8 Paul Whalen 2024-03-19 15:03:27 UTC
Apologies- I missed this FE request and discussion. We'll need to make the same change in IoT as well.

Comment 9 Timothée Ravier 2024-03-19 19:36:44 UTC
Sorry Paul. I posted it that I would likely do it on Matrix but forgot to ping you for this one. My bad.

Comment 10 Timothée Ravier 2024-03-23 16:48:13 UTC
I've installed a fresh Kinoite system using the 40.20240319.0 ISO with EFI boot and got a system with a "Fedora" boot entry (note the capital letter) and a `/etc/default/grub` config file so we should be good here.


Note You need to log in before you can comment on or make changes to this bug.