Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 533165

Summary: qpid-cluster exits with awkward exception when qpidd not clustered
Product: Red Hat Enterprise MRG Reporter: Frantisek Reznicek <freznice>
Component: qpid-qmfAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: DevelopmentCC: esammons, tross
Target Milestone: 1.2   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-05 13:08:51 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:

Description Frantisek Reznicek 2009-11-05 12:56:35 UTC
Description of problem:

When qpid-cluster python tool run against non-clustered broker exits with following error:
[root@mrg-qe-03 ~]# qpid-cluster ; echo $?
Clustering is not installed on the broker.
Traceback (most recent call last):
  File "/usr/bin/qpid-cluster", line 322, in ?
    if e.__repr__().find("connection aborted") > 0:
AttributeError: SystemExit instance has no attribute '__repr__'
1

The same behavior observed on both RHEL4.8 and RHEL5.4.

Putting target_milestone to 1.2, feel free to change if needed.


Version-Release number of selected component (if applicable):
[root@mrg-qe-03 ~]# rpm -qa | grep qpid
qpid-dotnet-0.4.738274-2.el4
qpidc-ssl-0.5.752581-32.el4
qpidc-debuginfo-0.5.752581-32.el4
qpid-java-client-0.5.751061-9.el4
python-qpid-0.5.760500-6.el4
qpidc-0.5.752581-32.el4
qpidd-ssl-0.5.752581-32.el4
rh-qpid-tests-0.5.752581-32.el4
qpidc-devel-0.5.752581-32.el4
qpid-java-common-0.5.751061-9.el4
qpidd-xml-0.5.752581-32.el4
qpidd-acl-0.5.752581-32.el4
qpidd-devel-0.5.752581-32.el4
qpidd-0.5.752581-32.el4
qpidc-perftest-0.5.752581-32.el4


How reproducible:
100%

Steps to Reproduce:
1. start qpidd 'service qpidd start'
2. run 'qpid-cluster ; echo $?'
  
Actual results:
 Corect information that qpidd does not run in clustered mode, but finally ends with Attribute error ... exit code 1

Expected results:
 Corect information that qpidd + proper exitcode.

Additional info:

[root@mrg-qe-03 ~]# qpid-cluster
Clustering is not installed on the broker.
Traceback (most recent call last):
  File "/usr/bin/qpid-cluster", line 322, in ?
    if e.__repr__().find("connection aborted") > 0:
AttributeError: SystemExit instance has no attribute '__repr__'
[root@mrg-qe-03 ~]# qpid-stat -b
Brokers
  broker          cluster       uptime  conn  sess  exch  queue
  ===============================================================
  localhost:5672  <standalone>  30s        7     7     6    20
[root@mrg-qe-03 ~]# qpid-cluster
Clustering is not installed on the broker.
Traceback (most recent call last):
  File "/usr/bin/qpid-cluster", line 322, in ?
    if e.__repr__().find("connection aborted") > 0:
AttributeError: SystemExit instance has no attribute '__repr__'
[root@mrg-qe-03 ~]# rpm -qa | grep qpid
qpid-dotnet-0.4.738274-2.el4
qpidc-ssl-0.5.752581-32.el4
qpidc-debuginfo-0.5.752581-32.el4
qpid-java-client-0.5.751061-9.el4
python-qpid-0.5.760500-6.el4
qpidc-0.5.752581-32.el4
qpidd-ssl-0.5.752581-32.el4
rh-qpid-tests-0.5.752581-32.el4
qpidc-devel-0.5.752581-32.el4
qpid-java-common-0.5.751061-9.el4
qpidd-xml-0.5.752581-32.el4
qpidd-acl-0.5.752581-32.el4
qpidd-devel-0.5.752581-32.el4
qpidd-0.5.752581-32.el4
qpidc-perftest-0.5.752581-32.el4
[root@mrg-qe-03 ~]# qpid-cluster ; echo $?
Clustering is not installed on the broker.
Traceback (most recent call last):
  File "/usr/bin/qpid-cluster", line 322, in ?
    if e.__repr__().find("connection aborted") > 0:
AttributeError: SystemExit instance has no attribute '__repr__'
1

Comment 1 Ted Ross 2009-11-05 13:08:51 UTC

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