Bug 568718 – Is acl reload safe to use?

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 568718 - Is acl reload safe to use?

Summary:	Is acl reload safe to use?

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All Linux

Priority	urgent Severity medium
Target Milestone:	1.3
Target Release:	---
Assigned To:	Rajith Attapattu
QA Contact:	ppecka
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	582366
Blocks:
	Show dependency tree / graph

Reported:	2010-02-26 07:59 EST by Gordon Sim
Modified:	2010-10-14 12:01 EDT (History)
CC List:	2 users (show)

See Also:
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 12:01:22 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
test case for testing the safety of acl reload. (1.02 KB, application/x-gzip) 2010-04-14 14:36 EDT, Rajith Attapattu	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Gordon Sim 2010-02-26 07:59:20 EST

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 14:33:31 EDT

While testing this the broker core dumped. See 582366 for more details.

Comment 2 Rajith Attapattu 2010-04-14 14:36:16 EDT

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-22 21:04:58 EDT

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 09:04:02 EDT

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 05:36:15 EDT

    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 12:01:22 EDT

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

Note You need to log in before you can comment on or make changes to this bug.