Bug 53141 - traceback during lilo of kernel installation
traceback during lilo of kernel installation
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2001-09-04 10:40 EDT by James Manning
Modified: 2015-01-07 18:51 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-04 13:42:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2001:119 normal SHIPPED_LIVE New up2date and rhn_register clients available 2001-10-03 00:00:00 EDT

  None (edit)
Description James Manning 2001-09-04 10:40:46 EDT
Description of Problem:
This is during the package installation phase after bug #53139
After the 4 packages for update are selected, the installation goes fine 
(kernel-source is last), and with both package and overall progress bars at 
100%, I get this traceback:

Traceback (innermost last):
  File "/usr/share/rhn/up2date_client/gui.py", line 749, in doInstallation
  File "/usr/share/rhn/up2date_client/up2date.py", line 2008, in 
  File "/usr/share/rhn/up2date_client/up2date.py", line 2027, in __install_lilo
    ret = lilocfg.installNewImages(kernelList,test=0)
  File "/usr/share/rhn/up2date_client/lilocfg.py", line 260, in installNewImages 
   header = finddeplocal(db,default_image)
NameError: finddeplocal

up2date is now hung, stuck in the "busy" state

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
see description and bug #53139

Additional Information:
same setup as per bug #53139
Comment 1 Adrian Likins 2001-09-04 13:42:29 EDT
yup, real bug. Just fixed. Will be in next client.

called the wrong function name...
Comment 2 David M. Cook 2002-02-13 19:06:41 EST
Fixed in


Note You need to log in before you can comment on or make changes to this bug.