Hide Forgot
Description of problem: When a new kernel is installed, /etc/grub2.cfg is correctly updated (except for the Schrödinger's Cat problem) but /boot/grub2/grub.cfg is not touched. The system therefore fails to default to, or even offer the option of, booting the new kernel. Note that I'm not positive which component this bug is in - grubby is a guess. Certainly grub2-mkconfig works fine. Version-Release number of selected component (if applicable): grubby version 8.28 release 1.fc19 How reproducible: I've seen it on both the machines I have fedora 19 installed on. One of those machines showed the same problem consistently throughout the life of fedora 17. The other never had the issue with fedora 17. (See below for possible explanation of difference.) Steps to Reproduce: 1. Install fedora 19. If in doubt, use the KDE spin for x86_64 and make sure the machine is configured to boot in bios mode (not EFI). 2. Run yum upgrade to update everything and note the installation of a new kernel. 3. Examine /etc/grub2.cfg and /boot/grub2/grub.cfg. Note that the latter is unchanged whereas the former has been updated. Actual results: Only /etc/grub2.cfg is updated with an entry for the new kernel. /boot/grub2/grub.cfg is untouched. Expected results: /boot/grub2/grub.cfg is updated to include an entry for the newly installed kernel. Additional info: grub2-mkconfig -o /boot/grub2/grub.cfg works fine - it definitely isn't an issue with the config files for grub or with grub2-mkconfig itself. I suspect the issue is specific to bios booting and does not affect EFI booting. The machine which had no issues in fedora 17 is one which Anaconda randomly decided must use bios booting when I installed fedora 19 even though it used EFI booting in fedora 17. The machine where it has never worked has always booted in bios mode. I suspect this is not merely coincidence. But obviously 2 machines is hardly conclusive. yum.log doesn't show any errors or warnings. The problem is easy to correct manually on the machine I use myself but I really need an automated fix for the other as it is hard enough to get the user to notice the little icon showing updates and to actually make the effort to install them. I stand no chance of asking for a follow up at the command line in that case. So if there is any work around I could automate on that machine, I'd be very interested. (Since this bug has dogged me since fedora 17, I'm guessing it is unlikely to get fixed by an update to fedora 19 though obviously that would be ideal - I'm just assuming it must be difficult to resolve without breaking other things if it has persisted this long already.)
I'm seeing the same thing on one of my machines. Please help.
/etc/grub2.cfg isn't a symlink on these machines? It should be: lrwxrwxrwx. 1 root root 22 Jul 8 10:20 /etc/grub2.cfg -> ../boot/grub2/grub.cfg
A fresh install of F20 design-suite-x86_64 produced this same issue. Downloaded from - http://kojipkgs.fedoraproject.org//work/tasks/3418/6283418/Fedora-Live-Design-suite-x86_64-20-20131212.iso /boot/grub2/grub.cfg remains upopulated. Although grub2-mkconfig -o /boot/grub2/grub.cfg works just fine, not sure why this is occuring during the install process.
On the system that I'm having this trouble with the symlinks exist
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.