Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 518291 - Python management tools must handle SystemExit exception properly
Python management tools must handle SystemExit exception properly
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-qmf (Show other bugs)
1.1.6
All Linux
low Severity medium
: 1.3
: ---
Assigned To: Nuno Santos
Jiri Kolar
:
: 533165 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-19 14:19 EDT by Ted Ross
Modified: 2013-09-12 18:10 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the 'SystemExit' exception was thrown by calls to 'sys.exit(n)' in some versions of Python in the Python management tools. With this update, system exits are handled properly on all versions of the Python interpreter.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-14 11:58:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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 RHSA-2010:0773 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3 2010-10-14 11:56:44 EDT

  None (edit)
Description Ted Ross 2009-08-19 14:19:47 EDT
Description of problem:

The SystemExit exception is raised by calls to sys.exit(n) in some versions of Python.  

It is important that the scripts handle system exits properly on all versions of the Python interpreter that they will be deployed on.
Comment 2 Ted Ross 2009-11-05 08:08:51 EST
*** Bug 533165 has been marked as a duplicate of this bug. ***
Comment 3 Nuno Santos 2010-05-11 17:50:20 EDT
The issue was due to the handling of the SystemExit exception (namely trying to call SystemExit.__repr__, which doesn't exist in python 2.4.3), not due to the exception itself being raised.

But the offending code is no longer in the codebase, and I haven't been able to replicate the issue on python 2.4.3 (RHEL 5) nor on python 2.6 (RHEL 6).
Comment 5 Jiri Kolar 2010-09-20 09:27:32 EDT
fixed on qpid-tools-0.7.946106-10

validated on RHEL5.5/RHEL4  i386 / x86_64  

packages:
# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u

openais-0.80.6-16.el5_5.7
openais-devel-0.80.6-16.el5_5.7
python-qpid-0.7.946106-14.el5
qpid-cpp-client-0.7.946106-15.el5
qpid-cpp-client-devel-0.7.946106-15.el5
qpid-cpp-client-devel-docs-0.7.946106-15.el5
qpid-cpp-client-ssl-0.7.946106-15.el5
qpid-cpp-mrg-debuginfo-0.7.946106-14.el5
qpid-cpp-server-0.7.946106-15.el5
qpid-cpp-server-cluster-0.7.946106-15.el5
qpid-cpp-server-devel-0.7.946106-15.el5
qpid-cpp-server-ssl-0.7.946106-15.el5
qpid-cpp-server-store-0.7.946106-15.el5
qpid-cpp-server-xml-0.7.946106-15.el5
qpid-java-client-0.7.946106-9.el5
qpid-java-common-0.7.946106-9.el5
qpid-tools-0.7.946106-10.el5
rhm-docs-0.7.946106-5.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-53

->VERIFIED
Comment 6 Martin Prpič 2010-10-07 08:34:13 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the 'SystemExit' exception was thrown by calls to 'sys.exit(n)' in some versions of Python in the  Python management tools. With this update, system exits are handled properly on all versions of the Python interpreter.
Comment 8 errata-xmlrpc 2010-10-14 11:58:05 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html

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