Bug 109469
| Summary: | traceback in lilo code | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Bill Nottingham <notting> | ||||
| Component: | up2date | Assignee: | Adrian Likins <alikins> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.0 | CC: | bart.schelstraete, blurred.vision, rvokal, tao | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-08-24 21:00:19 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: | |||||||
| Attachments: |
|
||||||
cath the traceback with the u1 target code, but I'm not sure why the test install fails. could you attach the lilo.conf? It's on devserv, but it's been modified since then. Created attachment 96024 [details]
lilo config file
what kernels are installed for those machines? did the preexisting lilo work? On devserv, yes, the preexisting lilo did work. I'm guessing what happened was just a too-long (or duplicate?) label. I am receiving this error too, on a clean install RHEL3 the first
time up2date is run... I have this problem on 3 prd systems aswell,
all minimum install RHEL3 the first time I run up2date...
Any help I can provide (as I have 4 systems all exhibiting the same
symptoms?)
.
..
...
New Up2date available
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1165, in ?
# we're fine up to this point...
File "/usr/sbin/up2date", line 745, in main
else:
File "/usr/sbin/up2date", line 1028, in batchRun
File "up2dateBatch.py", line 82, in run
File "up2dateBatch.py", line 153, in __installPackages
File "up2date.py", line 613, in installPackages
File "up2date.py", line 662, in runPkgSpecialCases
File "up2date.py", line 753, in installBootLoader
File "up2date.py", line 768, in __install_lilo
File "lilocfg.py", line 376, in installNewImages
up2date_client.lilocfg.LiloConfError: Error installing lilo.conf The
message was:
test install of lilo failed
What is the time frame likely to fix this? this is causing major bad mojo with my kickstarts... Any ideas? Blurred there was a bug with labels of exactly 15 chars that should be fixed in current errata releases |
Description of problem: Updating to the errata kernel: 3:kernel-smp ########################################### [100%] Traceback (most recent call last): File "/usr/sbin/up2date", line 1165, in ? sys.exit(main() or 0) File "/usr/sbin/up2date", line 745, in main fullUpdate, dryRun=options.dry_run)) File "/usr/sbin/up2date", line 1028, in batchRun batch.run() File "up2dateBatch.py", line 82, in run File "up2dateBatch.py", line 153, in __installPackages File "up2date.py", line 613, in installPackages File "up2date.py", line 662, in runPkgSpecialCases File "up2date.py", line 753, in installBootLoader File "up2date.py", line 768, in __install_lilo File "lilocfg.py", line 376, in installNewImages up2date_client.lilocfg.LiloConfError: Error installing lilo.conf The message was: test install of lilo failed