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

Bug 568718

Summary: Is acl reload safe to use?
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Rajith Attapattu <rattapat+nobody>
Status: CLOSED ERRATA QA Contact: ppecka <ppecka>
Severity: medium Docs Contact:
Priority: urgent    
Version: 1.2CC: freznice, ppecka
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The 'acl reload' function exposed through QMF is now safe to use on an active broker.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 16:01:22 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: 582366    
Bug Blocks:    
Attachments:
Description Flags
test case for testing the safety of acl reload. none

Description Gordon Sim 2010-02-26 12:59:20 UTC
Description of problem:

Need to verify through a test that the acl reload function exposed through QMF is safe to use on an active broker.

The test should have many clients doing random work on the broker with acl checks turned on. It should then periodically trigger reloading of the acl (no need to change it unless that would prevent reload actually occurring).

Comment 1 Rajith Attapattu 2010-04-14 18:33:31 UTC
While testing this the broker core dumped. See 582366 for more details.

Comment 2 Rajith Attapattu 2010-04-14 18:36:16 UTC
Created attachment 406598 [details]
test case for testing the safety of acl reload.

1. Start the broker with the acl module and and --acl-file /tmp/policy.acl
2. The initial acl file should contain only "acl allow all all"
3. run the message_sender.py (This program will keep on publishing to
amq.direct)
4. run acl_reloader.py with --mode allow | deny a few times

Comment 3 Rajith Attapattu 2010-04-23 01:04:58 UTC
A fix has been put in place at rev 937120 in Qpid for bz 582366

I believe the reproducer attached here provides a good way to verify the safety of acl reloading.

Comment 4 ppecka 2010-05-31 13:04:02 UTC
verified on RHEL 5.5/4.8 - i386/x86_64:

rpm -qa | grep -E '(qpid|ais|sesame)' | sort -n
openais-0.80.6-16.el5_5.1
openais-debuginfo-0.80.6-16.el5_5.1
openais-devel-0.80.6-16.el5_5.1
python-qpid-0.7.946106-1.el5
qpid-cpp-client-0.7.946106-1.el5
qpid-cpp-client-devel-0.7.946106-1.el5
qpid-cpp-client-devel-docs-0.7.946106-1.el5
qpid-cpp-client-ssl-0.7.946106-1.el5
qpid-cpp-server-0.7.946106-1.el5
qpid-cpp-server-cluster-0.7.946106-1.el5
qpid-cpp-server-devel-0.7.946106-1.el5
qpid-cpp-server-ssl-0.7.946106-1.el5
qpid-cpp-server-store-0.7.946106-1.el5
qpid-cpp-server-xml-0.7.946106-1.el5
qpid-java-client-0.7.946106-3.el5
qpid-java-common-0.7.946106-3.el5
qpid-tools-0.7.946106-4.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-27
sesame-0.7.3918-2.el5

--> VERIFIED

Comment 5 Martin Prpič 2010-10-10 09:36:15 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:
The 'acl reload' function exposed through QMF is now safe to use on an active broker.

Comment 7 errata-xmlrpc 2010-10-14 16:01:22 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