Bug 1242970 - [New] - Add a note that once bricks are created from UI restorecon has to be performed
Summary: [New] - Add a note that once bricks are created from UI restorecon has to be ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Console_Installation_Guide
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.1.0
Assignee: Rakesh
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: 1202842
TreeView+ depends on / blocked
 
Reported: 2015-07-14 13:43 UTC by RamaKasturi
Modified: 2017-11-17 05:32 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description RamaKasturi 2015-07-14 13:43:29 UTC
Document URL: http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.1-Console_Administration_Guide-en-US%20%28html-single%29/lastStableBuild/artifact/tmp/en-US/html-single/index.html#Viewing_Bricks_from_a_Host

Section Number and Name: Procedure 5.9 Creating bricks

Describe the issue: When bricks are created from UI, the file context is set to file 'system_u:object_r:file_t:s0' . context of the newly created bricks has to be changed to 'system_u:object_r:glusterd_brick_t:s0' otherwise selinux will prevent user to create special files in the mount point.

Suggestions for improvement: Add the below as important "Once the bricks are created from UI and before using them to create a volume perform the following on all the nodes in the cluster."

# semanage fcontext -a -t glusterd_brick_t '/rhgs/brick1(/.*)?'
# restorecon -Rv /rhgs/brick1
 
Replace /rhgs/brick1 with your actual brick path

Additional information:

Comment 2 Anjana Suparna Sriram 2015-07-22 11:23:46 UTC
Moving the bug to Assigned state

Comment 4 RamaKasturi 2015-07-22 17:21:44 UTC
Verified in the link provided in comment 3. Looks good to me. 

Marking this verified.


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