Bug 1565962

Summary: Disable features.selinux
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasad Desala <tdesala>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Prasad Desala <tdesala>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: rhinduja, rhs-bugs, sheggodu, storage-qa-internal, vbellur
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.12.2-8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 06:46:01 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:    
Bug Blocks: 1503137    

Description Prasad Desala 2018-04-11 07:58:13 UTC 
Description of problem:
=======================
In 3.4.0, features.selinux is enabled by default in code. Qualifying this feature is not initially in scope of 3.4.0 release and in test plan. This feature has to be disabled in 3.4.0.

Version-Release number of selected component (if applicable):
3.12.2-7.el7rhgs.x86_64

How reproducible:
always

Steps to Reproduce:
===================
1) Create a volume.
2) Run below command,
gluster v get distrepx3 all |grep -i  selinux
features.selinux                        on                    

Actual results:
==============
features.selinux is enabled by default in 3.4.0 code.

Expected results:
=================
Disable features.selinux
Comment 8 Prasad Desala 2018-04-23 09:09:32 UTC 
Verified this BZ on glusterfs version 3.12.2-8.el7rhgs.x86_64. 
Now, features.selinux is set to off by default.

gluster v get ec all | grep -i linux                                
features.selinux                        off 

Moving this BZ to Verified.
Comment 10 errata-xmlrpc 2018-09-04 06:46:01 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://access.redhat.com/errata/RHSA-2018:2607