Bug 1229279

Summary: [SELinux] [BVT]: Fix SELinux AVC errors produced while running RHGS DHT automation on RHEL 7
Product: Red Hat Enterprise Linux 7 Reporter: Prasanth <pprakash>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.1CC: annair, asrivast, jholloway, jkurik, lvrabec, mgrepl, mmalik, nsathyan, plautrba, pprakash, pvrabec, rcyriac, rhs-bugs, ssekidde, storage-qa-internal, vagarwal
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-26.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1227326
: 1231649 (view as bug list) Environment:
Last Closed: 2015-11-19 10:36:05 UTC Type: Bug
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: 1227326    
Bug Blocks: 1212796, 1231649    

Description Prasanth 2015-06-08 11:01:43 UTC
+++ This bug was initially created as a clone of Bug #1227326 +++

Description of problem:
Selinux throws a AVC errors while running DHT automated test cases

Version-Release number of selected component (if applicable):
glusterfs-fuse-3.7.0-2.el6rhs.x86_64
glusterfs-libs-3.7.0-2.el6rhs.x86_64
glusterfs-client-xlators-3.7.0-2.el6rhs.x86_64
glusterfs-api-3.7.0-2.el6rhs.x86_64
glusterfs-3.7.0-2.el6rhs.x86_64
glusterfs-cli-3.7.0-2.el6rhs.x86_64
glusterfs-server-3.7.0-2.el6rhs.x86_64


How reproducible:
Always when we run BVT


Steps to Reproduce:
1. Not a manual process
2. Running DHT BVT on rhel7.1 server with downstream glusterfs3.7 packages

Actual results:
Selinux AVC errors found

Expected results:
No AVC errors


Additional info:
The BVT test result link, that has all the avc logs:
https://beaker.engineering.redhat.com/jobs/965669

Comment 6 errata-xmlrpc 2015-11-19 10:36:05 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.

https://rhn.redhat.com/errata/RHBA-2015-2300.html