Bug 1469722 - [Ganesha] Document to enable gluster_use_execmem boolean after upgrading to RHEL 7.4 and 3.2 Async
Summary: [Ganesha] Document to enable gluster_use_execmem boolean after upgrading to ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: Documentation
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Bhavana
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks: 1472813
TreeView+ depends on / blocked
 
Reported: 2017-07-11 18:02 UTC by Manisha Saini
Modified: 2017-08-01 10:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 10:54:24 UTC
Embargoed:

Attachments (Terms of Use)

Description Manisha Saini 2017-07-11 18:02:26 UTC 
Document URL: 

http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.2-Administration_Guide-branch-master/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#idm139994383455536


Section Number and Name: 
6.2.4.4.2. Configuring the HA Cluster
->Setting up the HA cluster

Describe the issue: 

With 3.2 Async release and RHEL 7.4,gluster_use_execmem boolean needs to be enable manually at the time of fresh ganesha setup creation and while upgrading from 3.2 to 3.2 Async.


Engineering bug for the same-https://bugzilla.redhat.com/show_bug.cgi?id=1466343


Suggestions for improvement: 

Additional information:
Comment 2 Manisha Saini 2017-07-11 18:08:19 UTC 
As this boolean needs to be set before enabling ganesha,
whether this needs to be highlighted in all the 3 sections- gdeploy section,upgrade section,installation section of nfs-ganesha?


Raising need info on Soumya for the inputs
Comment 3 Soumya Koduri 2017-07-27 07:36:39 UTC 
The changes needed in upgrade section shall be handled as part of bug1470146
Comment 8 Manisha Saini 2017-07-31 13:30:30 UTC 
Thanks Bhavana.
Changes looks good to me.Moving this bug to verified state.
Note You need to log in before you can comment on or make changes to this bug.