Bug 617564 - Wrong record in grub after remove the last kernel
Summary: Wrong record in grub after remove the last kernel
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd   
(Show other bugs)
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-23 12:46 UTC by Sergey Vakula
Modified: 2011-10-21 23:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-10-21 23:23:34 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Sergey Vakula 2010-07-23 12:46:47 UTC
Description of problem:
If RHEL 5.5 have only one kernel and I remove his by rpm -e kernel --force, last record in grub.conf are saves. After installing new kernel by yum install kernel, that record in grub.conf still no changed. System boot fail.

Steps to Reproduce:
1. manually remove all kernels (by rpm, with --force if need)
2. yum install kernel
3. check grub.conf

Comment 1 Eric Sandeen 2010-07-26 20:24:26 UTC
More likely a mkinitrd/grubby problem than a kernel problem.

OTOH removing the only system kernel package with --force isn't treating the system very well... :)

Comment 2 Sergey Vakula 2010-07-27 07:53:06 UTC
What to do if not enough free space at /boot and this space enough for only one kernel? It is for this case apply the mechanism of removal of a single kernel manually by "rpm -e kernel --force" and the next step is installing a new kernel by "yum install kernel".

Comment 3 Brian Lane 2011-10-21 23:23:34 UTC
You shouldn't remove all of the kernels. Make sure your /boot is larger.


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