Bug 127199 - "No bootloader found" from yum
Summary: "No bootloader found" from yum
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-03 19:50 UTC by Michal Jaegermann
Modified: 2014-01-21 22:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-29 18:29:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2004-07-03 19:50:42 UTC
Description of problem:

When a new kernel shows in updates then yum installs it, as expected,
and on x86 installation prints:

Kernel Updated/Installed, checking for bootloader
Grub found - making this kernel the default

and indeed does that.  On a test x86_64 installation that message
is different:

Kernel Updated/Installed, checking for bootloader
No bootloader found, Cannot configure kernel, continuing.

This is after a new kernel was placed in /boot, its initrd
made up and a corresponding stanza added to /boot/grub/grub.conf.
Only a "making this kernel the default" step is missing.
I am not sure how yum is searching for a boot loader but
/boot/grub/grub.conf are quite similar between x86 and x86_64.

I did not not notice that effect on FC2 but only in development
series.  Not a very big deal at this stage but curious
inconsistency.

Version-Release number of selected component (if applicable):
yum-2.0.7-1.1

How reproducible:
Always

Comment 1 Seth Vidal 2005-07-29 18:29:44 UTC
closing ancient and no longer relevant


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