Bug 45688
| Summary: | up2date bomb out when lilo.conf contain disk= and bios= options | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Milan Kerslager <milan.kerslager> |
| Component: | up2date | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED RAWHIDE | QA Contact: | Jay Turner <jturner> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | srevivo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-07-05 20:09:29 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: | |||
These options should be support in the next versions of the clients (and I believe the errataed version as well). The 7.1 stock version as the code for handling those cases commented out, as it wasnt well tested at that time. The updated version seems to handle this correctly, leaving them as global options. the lilo.conf has been added to the test suite for up2date... |
I ran up2date on my up-to-date system (RH 7.1). New kernel kernel-2.4.3-12 has been succesfully downloaded (I used -k command line option), but the up2date bombs out when trying to update my /etc/lilo.conf. The reason is that I have four lines in lilo.conf to boot from SCSI disk (with system and with root FS). I have IDE disk too, but this disk is removable. Thus I have this four lines in my lilo.conf: disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 The lilo.conf could be easily upgraded, no modification to lilo.conf is needed (these four lines are "global" options). Of course new image= section should be added. My actual lilo.conf: boot=/dev/sda map=/boot/map install=/boot/boot.b prompt timeout=50 linear #message=/boot/message default=Linux #append="ide0=ata66 ide1=ata66" disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 image=/boot/vmlinuz-2.4.3-12 label=Linux initrd=/boot/initrd-2.4.3-12.img read-only root=/dev/sda1 image=/boot/vmlinuz-2.4.2-2 label=Old initrd=/boot/initrd-2.4.2-2.img read-only root=/dev/sda1 Up2date bomb out with this traceback: Traceback (innermost last): File "/usr/sbin/up2date", line 831, in ? main() File "/usr/sbin/up2date", line 806, in main sys.exit(batchRun(onlyList, pkgNames, fullUpdate)) File "/usr/sbin/up2date", line 596, in batchRun up2date.installBootLoader(kernelsToInstall) File "/usr/share/rhn/up2date/up2date.py", line 2222, in installBootLoader ret = lilocfg.installNewImages(kernelList,test=0) File "/usr/share/rhn/up2date/lilocfg.py", line 266, in installNewImages raise LiloConfParseError("\n" + "%s" % config.unsupported) lilocfg.LiloConfParseError: lilo options that are not supported by up2date are used in the default lilo.conf. This file will not be modified. The options include: ['disk=/dev/sda', 'bios=0x80', 'disk=/dev/hda', 'bios=0x81'] Bombing out is bad, but leaving original global parameters should be possible in this case.