Bug 103261
| Summary: | kernel RPM upgrade produces elilo.conf entry, that does not work and is superfluous | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Albert Fluegel <tdsc.af> |
| Component: | mkinitrd | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | CC: | bugproxy |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | ia64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-11 15:25:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
That's odd and I don't see it on my ia64 system here. Did you upgrade the kernel by hand or with up2date? What version of mkinitrd do you have installed? Also, can you attach the output of running `/sbin/new-kernel-pkg -v --depmod --mkinitrd --install 2.4.21-1.1931.2.411.ent' Downloaded RPM using up2date -d kernel,
then installed RPM running rpm -U -v --hash kernel-X.Y.Z.rpm .
mkinitrd is 3.5.9-1
output of new-kernel-pkg:
prompt# /sbin/new-kernel-pkg -v --depmod --mkinitrd --install
2.4.21-1.1931.2.411.ent
initrdfile is /boot/efi/EFI/redhat/initrd-2.4.21-1.1931.2.411.ent.img
running depmod for 2.4.21-1.1931.2.411.ent
creating initrd /boot/efi/EFI/redhat/initrd-2.4.21-1.1931.2.411.ent.img using
2.4.21-1.1931.2.411.ent
found /boot/efi/EFI/redhat/initrd-2.4.21-1.1931.2.411.ent.img and using it with
grubby
Notes:
1.) /boot/efi/EFI does not exist, only /boot/efi/efi
2.) /boot/grub/grub.conf exists and contains:
# s+c Service Images start
title Red Hat E2.9 Rescue System (Network Boot)
root (hd0,0)
kernel /boot/vmlinuz.rhE29 initrd=/boot/initrd.img rescue root=/dev/nfs
ks=nfs:172.31.96.155:/kickstart/rules/netboot.redhate29 ksdevice=eth0
devfs=nomount ramdisk_size=8192 vga=788
initrd /boot/initrd.rhE29
title Red Hat E2.9 Installer
root (hd0,0)
kernel /boot/vmlinuz.rhE29 initrd=/boot/initrd.img ks root=/dev/nfs
ks=nfs:172.31.96.155:/kickstart/rules/kickstart.redhate29-ia64 ksdevice=eth0
devfs=nomount ramdisk_size=8192 vga=788
initrd /boot/initrd.rhE29
# s+c Service Images end
3.) found out: when /boot/grub/grub.conf does not exist, the wrong entry
would not be created
4.) The contents of /boot/grub/grub.conf doesn't matter. If the file exists
(probably with size 0) the wrong entry in /boot/efi/efi/redhat/elilo.conf
will be there
Fixed in 3.5.10 Still getting the same behavior on rogue.test.redhat.com with [root@rogue root]# rpm -q mkinitrd kernel mkinitrd-3.5.10-1 kernel-2.4.21-1.1931.2.414.ent kernel-2.4.21-1.1931.2.421.ent bash hates me, really fixed in 3.5.11 *** Bug 103859 has been marked as a duplicate of this bug. *** Closing MODIFIED bugs as fixed. Please reopen if the problem perists. |
Description of problem: Upgrading the kernel to a new RPM produces an additional entry in /boot/efi/efi/redhat/elilo.conf on Itanium systems. This entry does not work because it has a label entry, that elilo does not considers valid. The entry, that exists before, looks like this: image=vmlinuz-2.4.21-1.1931.2.393.ent label=2.4.21-1.1931.2.393.ent initrd=initrd-2.4.21-1.1931.2.393.ent.img read-only append="console=ttyS0 root=LABEL=/" after kernel upgrade, there are two entries: image=vmlinuz-2.4.21-1.1931.2.411.ent label=2.4.21-1.1931.2.411.ent initrd=initrd-2.4.21-1.1931.2.411.ent.img read-only append="console=ttyS0 root=LABEL=/" image=vmlinuz-2.4.21-1.1931.2.411.ent label=Red Hat Enterprise Linux (2.4.21-1.1931.2.411.ent) initrd=initrd-2.4.21-1.1931.2.411.ent.img read-only append="console=ttyS0 root=LABEL=/" with default set to: default=2.4.21-1.1931.2.411.ent so the second image entry is superfluous and makes elilo stop at boot and complain, that there is an error in the config file. Changing the label of the second entry to the one of the first entry makes things work, so probably it's an entry format issue. Version-Release number of selected component (if applicable): kernel-2.4.21-1.1931.2.411.ent or 2.4.21-1.1931.2.393.ent How reproducible: Steps to Reproduce: 1. rpm -U /path/to/kernel-2.4.21-1.1931.2.411.ent.rpm 2. reboot 3. watch output Actual results: elilo prints an error and prompts for input, not booting automatically after the timeout like configured Expected results: new kernel is booted Additional info: