|Summary:||up2date lilo test failure|
|Product:||Red Hat Enterprise Linux 4||Reporter:||Need Real Name <securebit>|
|Component:||up2date||Assignee:||Adrian Likins <alikins>|
|Status:||CLOSED DUPLICATE||QA Contact:||Red Hat Satellite QA List <satellite-qa-list>|
|Version:||4.0||CC:||cturner, gafton, mihai.ibanescu, pjones, taw|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-02-21 18:50:46 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Need Real Name 2002-12-29 20:26:55 UTC
Description of problem: The up2date agent has an issue with updating the kernel. What happens is, once you have updated several kernels, the lilo label names become too long for lilo. It appears the naming schema for old kernels is linux-up.bak1 , linux- up.bak12, linux-up.bak123, linux-up.bak1234. The last in that list is where lilo complains about the character length of the string, 16. So after an up2date that updates the kernel you have, up2date gives an error saying lilo test failed. Version-Release number of selected component (if applicable): RedHat 7.3 on i686 LILO version 21.4-4 2.4.18-19.7.xsmp Red Hat Update Agent v2.8.39 How reproducible: 100% Steps to Reproduce: Simply supply an image within lilo.conf which exceeds the 16 character label name limit. 1. Give an image a label name >= 16 characters Label for an Image: LABEL_0123456789 2. run lilo you get) Lilo Error: Fatal: Label "LABEL_0123456789" is too long I am aware this is more a lilo thing but if you want up2date to be completelty transparent/hands off, the up2date binary should know about this label name limit and adjust what names it gives to the old kernel images. Actual results: Expected results: Additional info: The fix is easy: just rename the labels, run lilo again and reboot.
Comment 1 Adrian Likins 2003-01-15 05:33:36 UTC
I tend to think of this as a dup of #61512 (up2date verify sanity of boot loader configs before attempting to modify them) Since up2date currently assumes that the existing bootloader configs are working. Also, some versions of up2date did a crappy job of appending to the name. This should be fixed in current versions of up2date (for 8.0, possible errata for 7.x). This bug seems to be a combo of the above. *** This bug has been marked as a duplicate of 61512 ***
Comment 2 Red Hat Bugzilla 2006-02-21 18:50:46 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.