Bug 796331

Summary:	SELinux prevents clustered qpidd (qpidd_t) from name_connect (tcp_socket, amqp_port_t)
Product:	Red Hat Enterprise Linux 6	Reporter:	RHEL Program Management <pm-rhel>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.2	CC:	dwalsh, ebenes, freznice, iboverma, jpallich, mgrepl, mmalik, msvoboda, pm-eus
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	An incorrect SELinux policy prevented the qpidd service from connecting to the AMQP (Advanced Message Queuing Protocol) port when the qpidd daemon was configured with Corosync clustering. These selinux-policy packages contain updated SELinux rules, which allow the qpidd service to be started correctly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-07 12:45:56 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:	791294
Bug Blocks:

Description RHEL Program Management 2012-02-22 17:20:18 UTC

This bug has been copied from bug #791294 and has been proposed
to be backported to 6.2 z-stream (EUS).

Comment 4 Miroslav Grepl 2012-02-27 17:23:57 UTC

Fixed in selinux-policy-3.7.19-126.el6_2.10

Comment 6 Miroslav Svoboda 2012-03-02 14:18:42 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:
An incorrect SELinux policy prevented the qpidd service from connecting to the AMQP (Advanced Message Queuing Protocol) port when the qpidd daemon was configured with Corosync clustering. These selinux-policy packages contain updated SELinux rules, which allow the qpidd service to be started correctly.

Comment 8 errata-xmlrpc 2012-03-07 12:45:56 UTC

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-2012-0364.html