Bug 634643

Summary: /sbin/installkernel should not use --host-only to make initramfs
Product: [Fedora] Fedora Reporter: Nick Bowler <nbowler>
Component: grubbyAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 13CC: bcl, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 08:45:25 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Nick Bowler 2010-09-16 11:47:00 EDT
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100913 Gentoo IceCat/3.6.9 (like Firefox/3.6.9)

The /sbin/installkernel provided with Fedora 13 passes --host-only to the
new-kernel-pkg utility by default.

This option causes the utility to make decisions for what to install for a
new kernel, based on the configuration of the _current_ kernel.  The result
is that if you are compiling a kernel with a different configuration from
the current one, the generated initramfs might not boot because required
components were not included.

Correct operation should be the default, therefore this option should be

Reproducible: Always

Steps to Reproduce:
1. Boot the stock Fedora kernel.
2. Compile a new kernel with a different configuration: for example, change CONFIG_BLK_DEV_DM to 'm' (it's 'y' in the above kernel).
3. make, make modules_install, make install.
Actual Results:  
Initramfs does not include the required dm_mod module, and the system does not boot.

Expected Results:  
Initramfs includes the required dm_mod module, and the system should boot.

I never had this problem with older versions of Fedora; 'make install' always seemed to do the right thing before.
Comment 1 Bug Zapper 2011-05-31 09:19:47 EDT
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 2 Bug Zapper 2011-06-28 08:45:25 EDT
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.