Bug 1036349 - When extlinux is bootloader on X86, rescue kernel not added to extlinux.conf
Summary: When extlinux is bootloader on X86, rescue kernel not added to extlinux.conf
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-01 10:47 UTC by Gene Czarcinski
Modified: 2014-06-16 13:41 UTC (History)
4 users (show)

Fixed In Version: anaconda-21.39-1
Clone Of:
Environment:
Last Closed: 2014-06-16 13:41:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
always rescan for vmlinuz-* if rescueKernelList (1.19 KB, patch)
2014-05-26 20:29 UTC, Gene Czarcinski
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1100504 0 unspecified CLOSED rescue boot entry is listed first 2021-02-22 00:41:40 UTC

Internal Links: 1100504

Description Gene Czarcinski 2013-12-01 10:47:41 UTC
Description of problem:
Although I specify the hardware as x86_64, this likely happens on all X86 installs.  This also may (or may not) be an issue on other hardware using extlinux.

As usual, anaconda installs a "rescue" kernel.  However, unlike what it does on a system using the grub2 bootloader, it does not add the entry for the rescue kernel into extlinux.conf.

Yes, I do not expect this to be fixed in Fedora 20 and, yes, this is easily fixed post install.

Version-Release number of selected component (if applicable):
Fedora 20

Comment 1 Gene Czarcinski 2014-05-26 20:29:15 UTC
Created attachment 899356 [details]
always rescan for vmlinuz-* if rescueKernelList

In order to create the rescue kernel and initramfs, kernelVersionList
is referenced creating and populating _kernelVersionList.  When
rescueKernelList is reference it is null.  The solution is to
always rescan /boot/vmlinuz-* if rescueKernelList is called.

Comment 2 David Shea 2014-06-16 13:41:47 UTC
Patch in comment 1 was pushed as 73f64a6be548a2b7db398d6bb403a021ba6ffaab


Note You need to log in before you can comment on or make changes to this bug.