Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #711081 +++
Description of problem:
qpid-cluster -s <ID> crashes with
'NoneType' object has no attribute 'split'
qpid-cluster is not able to stop node in the cluster.
See more details in last section (Additional info).
Version-Release number of selected component (if applicable):
qpid-tools-0.10-5.el5
How reproducible:
100%
Steps to Reproduce:
1. start cluster of one/two nodes
2. list nodes and IDs with
'qpid-cluster'
3. perform node stop by
'qpid-cluster -s <ID>'
3. echo $?
Actual results:
qpid-cluster crashes and requested node is not stopped.
Expected results:
qpid-cluster should not crash and requested node should be stopped.
Additional info:
[root@dhcp-26-234 ~]# qpid-cluster -h
usage: qpid-cluster [options] BROKER
Example: $ qpid-cluster -C broker-host:10000
options:
-h, --help show this help message and exit
-t SECS, --timeout=SECS
Maximum time to wait for broker connection (in
seconds)
-C, --all-connections
View client connections to all cluster members
-c ID, --connections=ID
View client connections to specified member
-d HOST:PORT, --del-connection=HOST:PORT
Disconnect a client connection
-s ID, --stop=ID Stop one member of the cluster by its ID
-k, --all-stop Shut down the whole cluster
-f, --force Suppress the 'are you sure' prompt
-n, --numeric Don't resolve names
0
[root@dhcp-26-234 ~]# qpid-cluster
Cluster Name: freznice-virt-cluster
Cluster Status: ACTIVE
Cluster Size: 2
Members: ID=192.168.1.3:2387 URL=amqp:tcp:10.34.26.234:5672,tcp:192.168.1.3:5672
: ID=192.168.1.4:2353 URL=amqp:tcp:10.34.26.233:5672,tcp:192.168.1.4:5672
[root@dhcp-26-234 ~]# qpid-cluster -s 192.168.1.4:2353
'NoneType' object has no attribute 'split'
[root@dhcp-26-234 ~]# echo $?
1
[root@dhcp-26-234 ~]# qpid-cluster
Cluster Name: freznice-virt-cluster
Cluster Status: ACTIVE
Cluster Size: 2
Members: ID=192.168.1.3:2387 URL=amqp:tcp:10.34.26.234:5672,tcp:192.168.1.3:5672
: ID=192.168.1.4:2353 URL=amqp:tcp:10.34.26.233:5672,tcp:192.168.1.4:5672
[root@dhcp-26-234 ~]# qpid-cluster -s 192.168.1.3:2387
'NoneType' object has no attribute 'split'
[root@dhcp-26-234 ~]# qpid-cluster -s 192.168.1.3
'NoneType' object has no attribute 'split'
[root@dhcp-26-234 ~]# qpid-cluster -s 192.168.1.2
'NoneType' object has no attribute 'split'
[root@dhcp-26-234 ~]# rpm -qf `which qpid-cluster`
qpid-tools-0.10-5.el5
--- Additional comment from aconway on 2011-06-06 11:55:12 EDT ---
Fixed on upstream trunk r1132683
--- Additional comment from aconway on 2011-06-06 12:07:54 EDT ---
Committed to mrg_2.0.x
http://mrg1.lab.bos.redhat.com/cgit/qpid.git/commit/?h=mrg_2.0.x&id=2378ef39c5a0ef17e92ebc44bf368661d8d8d463
Comment 1Frantisek Reznicek
2011-06-07 11:26:41 UTC
Tested on RHEL6.2, packages versions:
qpid-cpp-client-0.12-6.el6
qpid-cpp-client-devel-0.12-6.el6
qpid-cpp-client-rdma-0.12-6.el6
qpid-cpp-client-ssl-0.12-6.el6
qpid-cpp-debuginfo-0.12-6.el6
qpid-cpp-server-0.12-6.el6
qpid-cpp-server-cluster-0.12-6.el6
qpid-cpp-server-devel-0.12-6.el6
qpid-cpp-server-rdma-0.12-6.el6
qpid-cpp-server-ssl-0.12-6.el6
qpid-cpp-server-store-0.12-6.el6
qpid-cpp-server-xml-0.12-6.el6
qpid-java-client-0.10-11.el6
qpid-java-common-0.10-11.el6
qpid-java-example-0.10-11.el6
qpid-java-jca-0.10-11.el6
qpid-java-jca-zip-0.10-11.el6
qpid-qmf-0.12-6.el6
qpid-qmf-debuginfo-0.12-6.el6
qpid-qmf-devel-0.12-6.el6
qpid-tools-0.12-2.el6
The command 'qpid-cluster -s <ID>' worked fine during the testing. I was able to stop any node in a cluster - the one running on the same machine I ran the command on, as well as the remote one. The commands did not return any errors, exit code was always 0.
-> VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1668.html