Bug 1185110

Summary: "NameError: global name 'all' is not defined" on server when uploading ABRT crashes with `spacewalk-abrt --sync`
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: ServerAssignee: Jan Dobes <jdobes>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 560CC: jhutar, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-18 14:24:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1127217    
Attachments:
Description Flags
part of error_log none

Description Jan Hutař 2015-01-22 23:07:55 UTC 
Created attachment 983100 [details]
part of error_log

Description of problem:
When running `spacewalk-abrt --sync` on a client, I sometimes get ISE.


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


How reproducible:
sometimes


Steps to Reproduce:
1. client# spacewalk-abrt --sync


Actual results:
spacewalk-abrt fails and error "NameError: global name 'all' is not defined" is generated on server-side.


Expected results:
Should work.


Additional info:
https://docs.python.org/2/library/functions.html#all
says "New in version 2.5." and on RHEL5, there is Python 2.4
Comment 1 Tomas Lestach 2015-05-20 09:38:41 UTC 
Jan, spacewalk-abrt is available only in RHN Tools for RHEL 6 and 7.
Do you run it on RHEL5?
Comment 2 Jan Hutař 2015-05-20 11:08:30 UTC 
Looking into the report: sorry for not providing required info (like versions). Traceback comes from server-side (5.6.0 running on RHEL5).

# rpm -qf /usr/share/rhn/server/handlers/xmlrpc/abrt.py
spacewalk-backend-xmlrpc-2.0.3-33.el5sat
Comment 4 Jan Dobes 2017-05-18 14:24:50 UTC 
This is the same as Bug 1009399.

*** This bug has been marked as a duplicate of bug 1009399 ***