Red Hat Bugzilla – Bug 211339
typo in some of the kernel packages that add kernel name labels in new stanzas
Last modified: 2007-11-16 20:14:46 EST
Description of problem:
There is a typo in the kernel name labels in newly created stanzas within the
boot loader config file (e.g. zipl on s390, yaboot on ppc) when installing
2.4.21-47.0.1.EL kernel RPM. Notice how the label for the stanza is missing the
'L' in "EL" in the kernel name:
.qa.[root@s390-3as root]# head /etc/zipl.conf
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Intstall the errata kernel 2.4.21-47.0.1.EL for ppc and s390(x) arches
2. Open the boot loader configuration file to find an incompleted kernel name label
Kernel Name = complete kernel version name
This is problem with the kernel security Asynchronous errata here:
This would most likely be a bug in /sbin/zipl, part of the s390utils package.
(If this problem also occurs on ppc64, then an additional BZ should be entered.)
Ernie, I just tried the 2.4.21-37.0.1.EL on s390 and the same problem
occurs...so this could very well be a boot loader limitation.
It also occurs on ppc64...
Not sure why it gets cut off. I'm not sure if there are any length limitations
for sections in zipl.conf, but afaik not.
I'll double check with our IBM liasion next time he's here.
Read ya, Phil
OK, found the source of the problem:
It's actually in grubby (part of mkinitrd) that ofc actually writes zipl.conf.
There the title length is limited to 15 btes for lilo, yaboot, silo and zipl
If i remember correctly this was actually really necessary for the RHEL3 kernels
for those architectures, but i might confuse something here.
Reassigning the bug though to the proper component.
Read ya, Phil
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.