They already created 112. It works. Not sure when the new rpms will be in the updates repo.
That step was added fairly recently, I noticed it around F35 or F36 & mustered the courage to do it only in F37. Are we saying that it should not be suggested? Or maybe prefaced with a warning? Conceptually, running the latest of everything seems like the only way to avoid bugs & address vulnerabilities, and new bugs just happen, but, @computersavvy, I’m curious what your final thoughts here are, given your initial skepticism.
My thoughts, based on the non-effect I saw with testing, is that the grub2-install is probably not required unless you see some negative performance after the upgrade. After all, grub was already installed and the system booted before you ran that command.
The upgrade process supposedly does everything needed for a successful system upgrade and unless you know a specific reason why it is necessary to do those (optional) after upgrade commands I would not perform them.
Did the system boot properly before running that command? If so then why would it be required? Apparently grub was already fully functional.
To me this fits into the category of “if it isn’t broke, don’t fix it”
I agree, however, the documentation says something differently: It is a good idea to update it between Fedora release versions.
I h ave no clue as to who wrote that part of the document or why it may be recommended. Possibly someone in the team who maintains grub can provide a definitive answer. It obviously is not a good suggestion for every case as your experience shows.
Maybe that is only broken with an xfs file system and would work well if the /boot were ext4. I cannot say.
None of the steps in that section are required; comes to think of it, the release upgrade itself isn’t required. But hanging onto old versions becomes painful with each new release. I have a VM running FC7 because “it isn’t broke” but need special exception configuration on every new host just to be able to ssh into the thing. It’s always a balance of gain vs. risk.
I re-read the document & I think it’s fine: it has ample warnings all over the place & clearly says grub2-install is optional. A few of us stepped into a new bug exposed by the particularities of our setups. Next time I decide to upgrade GRUB I’ll be more careful & make sure I have a snapshot handy or an easy way to rollback changes.
In hindsight it would have been better to not install the new grub, but one should assume that a new version would have improvements and not introduce new bugs.
I ran into this same issue running the latest version of Fedora 39 (updated today!). The following workaround solved the issue until the patch is not ready: https://bugzilla.redhat.com/show_bug.cgi?id=2254370#c67