Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Grubby fails when updating kernel in kickstart %post|
|Product:||[Fedora] Fedora||Reporter:||stef <stephane.tranchemer>|
|Component:||grubby||Assignee:||Peter Jones <pjones>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||16||CC:||bcl, collura, pjones|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-02-13 16:17:27 EST||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description stef 2012-06-13 12:04:51 EDT
Description of problem: When installing a FC16 system via kickstart, and running yum to update in %post, it does not work for the kernel. A simple 'rpm -qa | grep -i kernel' shows that he updated kernel is installed, but grub is not updated. Grubby fails during kernel installation at the %post with the following error message: grubby fatal error: unable to find a suitable template A search in bugzilla shows that Bug 657257 is very closely related, but the workaround with /dev/root does not work. CentOS seems also impacted somehow as show in http://bugs.centos.org/view.php?id=4972 The solution that consists of manually run a rpm -e on the kernel rpms then issue a "yum upgrade" again is a no-no ... I have to many systems to install to manually intervene all over again Version-Release number of selected component (if applicable): Fedora Core 16 How reproducible: always Steps to Reproduce: 1.issue a "yum upgrade" command in the kikcstart %post section of a FC16 2.launch the install 3. Actual results: updated kernel is installed but grub is not configured to use it Expected results: updated kernel is installed and grub is configured to use it by default since is it the most up-to-date Additional info:
Comment 1 Brian Lane 2012-06-13 14:02:01 EDT
Do you mean "yum update"? Why are you doing this in %post instead of just adding the update repo to the kickstart?
Comment 2 stef 2012-06-14 03:03:18 EDT
I mean "yum upgrade". Upgrade will delete obsolete packages and install replacements. the main reason is historical ... I have a lot of work to manage, no time to try every single install method. The kickstart and its components is reused years over years with new distros and last time I tried your method it triggered a bunch of bugs and didn't install correctly.
Comment 3 Fedora End Of Life 2013-01-16 12:00:13 EST
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" 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
Comment 4 Fedora End Of Life 2013-02-13 16:17:30 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.