Bug 164893

Summary: error message worthless after failed action
Product: [Retired] Red Hat Network Reporter: Chester Hosey <chester.hosey>
Component: RHN/OtherAssignee: Todd Sanders <tsanders>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN StableCC: acarter, rhn-bugs
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: 2008-10-16 14:38:39 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:
Description Flags
output of rpm -qa none

Description Chester Hosey 2005-08-02 12:51:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
This action's status is: Failed.
The client picked up this action on 2005-07-25 15:47:12 EDT.
The client completed this action on 2005-07-25 15:47:13 EDT.
Client execution returned "Fatal error in Python code occured [[6]]" (code -1)

Packages to be removed:

gnome-libs-devel-1.4.1.2.90-44.1:1 
glib-devel-1.2.10-15:1 
indent-2.2.9-6 
alsa-lib-devel-1.0.6-5.RHEL4 
esound-devel-0.2.35-2:1 
gtk+-devel-1.2.10-33:1 
imlib-devel-1.9.13-23:1 
libungif-devel-4.1.3-1 
ORBit-devel-0.5.17-14:1 
libtiff-devel-3.6.1-8 
audiofile-devel-0.2.6-1:1 


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


How reproducible:
Always

Steps to Reproduce:
1. Try to interpret error message
2. Realize that it's vague
  

Actual Results:  The only line that makes an attempt to explain why the action failed follows:

> Client execution returned "Fatal error in Python code occured [[6]]" (code -1)

This does little to suggest why the action failed, or how to correct the problem.

Expected Results:  Error messages should indicate the condition(s) that caused the problem, and optionally suggest potential ways to resolve the condition(s). This message does neither.

Additional info:

Comment 1 Mihai Ibanescu 2005-08-03 12:36:14 UTC
The error message means there was a problem deep in the code. Normally there
should be a stack trace (i.e. a lot of internal information from the
interpreter) logged into /var/log/up2date

Can you please provide the version of up2date you're running (rpm -q up2date)
and attach the output of:

rpm -qa

and we'll try to reproduce it locally.

Comment 2 Chester Hosey 2005-08-03 12:45:03 UTC
Created attachment 117400 [details]
output of rpm -qa

Comment 3 Chester Hosey 2005-08-03 12:48:05 UTC
Running up2date-4.4.5.6-2

Comment 5 Brandon Perkins 2007-03-12 16:55:54 UTC
Move to Bugzilla Bug 218517: RHN 510 Hosted Triage Tracker.

Comment 6 Red Hat Bugzilla 2007-05-03 05:35:24 UTC
User wregglej's account has been closed

Comment 7 Amanda Carter 2008-10-16 14:38:39 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.