| Summary: | Creating a route and using management tools can crash cluster members. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Alan Conway <aconway> | ||||
| Component: | qpid-cpp | Assignee: | Alan Conway <aconway> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Reznicek <freznice> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 1.3 | CC: | esammons, freznice, gsim, iboverma, jneedle, mcressma | ||||
| Target Milestone: | 1.3.2-RC2 | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | qpid-cpp-mrg-0.7.946106-27 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Running qpid-tool after starting a cluster, creating a route, and then adding a new member to the cluster caused the new cluster member to exit. This update corrects the replication of route information in a cluster with the result that new members no longer exit under these conditions.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-02-15 12:11:02 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 654872 | ||||||
| Attachments: |
|
||||||
Upstream fix r1060568 In build for 1.3.2 RC 2.
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:
Cause: Starting a cluster, creating a route then adding a new member to a cluster.
Consequence: The new member fails with "invalid-argument" exception.
Fix: Correct replication of route information in cluster.
Result: New members join without error.
The issue has been fixed, tested on RHEL 5.6 i386 / x86_64 on packages: [root@dhcp-26-233 ~]# rpm -qa | grep qpid | sort python-qpid-0.7.946106-15.el5 qpid-cpp-client-0.7.946106-27.el5 qpid-cpp-client-devel-0.7.946106-27.el5 qpid-cpp-client-devel-docs-0.7.946106-27.el5 qpid-cpp-client-ssl-0.7.946106-27.el5 qpid-cpp-mrg-debuginfo-0.7.946106-27.el5 qpid-cpp-server-0.7.946106-27.el5 qpid-cpp-server-cluster-0.7.946106-27.el5 qpid-cpp-server-devel-0.7.946106-27.el5 qpid-cpp-server-ssl-0.7.946106-27.el5 qpid-cpp-server-store-0.7.946106-27.el5 qpid-cpp-server-xml-0.7.946106-27.el5 qpid-java-client-0.7.946106-14.el5 qpid-java-common-0.7.946106-14.el5 qpid-java-example-0.7.946106-14.el5 qpid-tools-0.7.946106-12.el5 -> VERIFIED
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,7 +1 @@
-Cause: Starting a cluster, creating a route then adding a new member to a cluster.
+Running qpid-tool after starting a cluster, creating a route, and then adding a new member to the cluster caused the new cluster member to exit. This update corrects the replication of route information in a cluster with the result that new members no longer exit under these conditions.-
-Consequence: The new member fails with "invalid-argument" exception.
-
-Fix: Correct replication of route information in cluster.
-
-Result: New members join without error.
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/RHBA-2011-0217.html |
Created attachment 473380 [details] script to reproduce the issue. Description of problem: Adding a member to a cluster after creating a route, then running qpid-tool, causes the new cluster member to exit. Version-Release number of selected component (if applicable): 0.7.946106-22.el5 How reproducible: easy Steps to Reproduce: script attached. Actual results: output ends with: mrg32 ok mrg33 not running mrg34 ok Expected results: all brokers are ok Additional info: