Bug 583526

Summary:	Management methods disallowed in Clusters must be re-enabled
Product:	Red Hat Enterprise MRG	Reporter:	Ted Ross <tross>
Component:	qpid-cpp	Assignee:	Ted Ross <tross>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Reznicek <freznice>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.2	CC:	esammons, freznice, tross
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, a design issue in the broker caused certain management operations (queue.purge, session.detach, session.close, connection.close) to be unstable when operating in a cluster. These operations were disabled during any cluster operation. With this update, the aforementioned operations are now available during any cluster operation.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-14 16:10:55 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:
Bug Depends On:	601895
Bug Blocks:

Description Ted Ross 2010-04-19 02:32:01 UTC

Description of problem:

In 1.2, several management methods which have side effects (like Queue.purge) are disabled when running as a cluster.  These methods must be re-enabled for cluster operation now that the inconsistent-object-id problem has been resolved.


Steps to Reproduce:
1.  Attempt to purge a queue using the Python Console API on a cluster
2.
3.
  
Actual results:

An error will be returned saying that the method is forbidden.

Expected results:

The operation should complete normally and consistently across nodes of the cluster.

Additional info:

Comment 1 Ted Ross 2010-04-23 19:08:41 UTC

Fixed upstream in revision 937472.

Comment 2 Frantisek Reznicek 2010-08-05 14:42:10 UTC

The issue has been fixed (python qmf console/client as well as qpid-tool is able to purge in standalone / clustered environment), tested on RHEL 4.8 / 5.5 i386 / x86_64 on packages:
python-qmf-0.7.946106-8.el5
python-qpid-0.7.946106-11.el5
qmf-0.7.946106-11.el5
qmf-devel-0.7.946106-11.el5
qpid-cpp-client*-0.7.946106-11.el5
qpid-cpp-mrg-debuginfo-0.7.946106-11.el5
qpid-cpp-server*-0.7.946106-11.el5
qpid-java-client-0.7.946106-7.el5
qpid-java-common-0.7.946106-7.el5
qpid-tools-0.7.946106-8.el5
rh-qpid-cpp-tests-0.7.946106-11.el5
ruby-qmf-0.7.946106-11.el5
ruby-qpid-0.7.946106-2.el5

-> VERIFIED

Comment 3 Ted Ross 2010-10-08 21:48:51 UTC

    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: There was a design issue in the broker that caused certain management operations (queue.purge, session.detach, session.close, connection.close) to be unstable when operating in a cluster.
consequence: These operations were disabled during cluster operation.
fix: The underlying design issues was resolved such that these operations are now safe.
result: The operations are now available during cluster operation.

Comment 4 Martin Prpič 2010-10-10 11:14:08 UTC

    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,4 +1 @@
-cause: There was a design issue in the broker that caused certain management operations (queue.purge, session.detach, session.close, connection.close) to be unstable when operating in a cluster.
+Previously, a design issue in the broker caused certain management operations (queue.purge, session.detach, session.close, connection.close) to be unstable when operating in a cluster. These operations were disabled during any cluster operation. With this update, the aforementioned operations are now available during any cluster operation.-consequence: These operations were disabled during cluster operation.
-fix: The underlying design issues was resolved such that these operations are now safe.
-result: The operations are now available during cluster operation.

Comment 6 errata-xmlrpc 2010-10-14 16:10:55 UTC

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