Description of problem: New kernel isn't added into a grub.cfg after preupgrade. In /boot/grub/grub.conf is entry with title "Upgrade to Fedora 16 ...", but no f16 kernel. System boots correctly, but it boots f15 kernel. All installed packages seems to be from f16 repos. Also kernel is installed properly. Version-Release number of selected component (if applicable): preupgrade 1.1.9-1.fc15 How reproducible: Tried once Steps to Reproduce: Follow this testcase: https://fedoraproject.org/wiki/QA:Testcase_Preupgrade. Boot system, log in. Check /boot/grub/grub.conf and run 'uname -a' in grub.conf there isn't new kernal and there is upgrade entry, which shouldn't be there. Actual results: Newly installed kernel isn't in grub menu and there is forgotten entry "Upgrade ...". Grub boots old kernel (2.6.40..) by default. Expected results: New kernel is added to the grub and set as default, and entry "upgrade" isn't in grub. Additional info: When in f16 when you update kernel then it adds a new entry to the grub and sets it as default. It works properly then.
Let me simplify the bug description. If you preupgrade from F15 to F16, these are the current issues: 1. Grub is not upgraded to Grub 2 (that may be intentional). 2. Latest kernel is installed in the system, but not added to grub.cfg. It means you still boot fc15 kernel by default. (That issue is fixed once a new kernel appears in updates repository). 3. There is a left-over item in grub.cfg named "Upgrade to Fedora 16". Fortunately it's unbootable. But it should have been erased after upgrade was completed.
Created attachment 531351 [details] anaconda.log
Created attachment 531353 [details] grub.conf There is already added new kernel (Fedora (3.1.0-7.fc16.x86_64). It was added by update of kernel. Other grub entries are those which was there after upgrade.
Created attachment 531354 [details] /var/log/messages
Can you re-try with the newest preupgrade (1.1.10-1.fc15)?
OK, I updated preupgrade to 1.1.10-1.fc15 and it upgrades system properly with it. So, I'm closing this bug as it is repaired in 1.1.10-1.fc15.
Same update should be pushed for fc14 as well. Hitting this problem with preupgrade-1.1.9-1.fc14.noarch
f15 is fixed and preupgrading two versions isn't supported, so not blocker or nth. but yes, we should fix f14's preupgrade. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping