Bug 57024 - Installing Packages failed unexpectedly on somewhat heavy task
Summary: Installing Packages failed unexpectedly on somewhat heavy task
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Adrian Likins
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-12-03 16:01 UTC by Rabbe Fogelholm
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-05-15 18:37:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rabbe Fogelholm 2001-12-03 16:01:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.6) Gecko/20011120

Description of problem:
When trying to run /usr/bin/up2date, and there were some 30 packages
selected for update, the download phase went fine but the installation
phase failed with console diagnostic as given below.



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


How reproducible:
Didn't try

Steps to Reproduce:
Sorry, cannot describe exactly how to reproduce. You would need a
RH 7.1 machine that was freshly installed this summer, then slightly
updated in August, and then subject to a /usr/bin/up2date session
this day (3rd December).
	

Actual Results:  In the console window from which I launched /usr/bin/up2date:

File "/usr/share/rhn/up2date/gui.py", line 592, in doInstallation ..
File "/usr/share/rhn/up2date/up2date.py", line 2518, in InstallPackages

    error = errors + e + "\n"

TypeError: illegal argument type for built-in operation

Additional info:

Comment 1 Rabbe Fogelholm 2001-12-03 16:06:33 UTC
I forgot ... I should have added that this failure was NOT a total
show-stopper. I proceeded to do some partial updates, selecting a single package
to start with, then the entire set of TeX pcakages, then the rest. Doing so
caused all the updates to complete without problems. I also noted that these
repeated runs of up2date did not cause any files to be downloaded, as that had
been done successfully already.


Comment 2 Adrian Likins 2002-04-30 19:39:22 UTC
This should be fixed in the current errataed packages.

Comment 3 Jay Turner 2002-05-15 12:48:05 UTC
Are you still seeing this issue?

Comment 4 Adrian Likins 2002-05-15 20:11:36 UTC
I'm positive this bug has been fixed in the current client, so closing bug.


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