Bug 1470146 - [Ganesha] After upgrading from 3.2 to 3.2 async selinux boolean ganesha_use_fusefs should be set to ON manually before enabling ganesha
Summary: [Ganesha] After upgrading from 3.2 to 3.2 async selinux boolean ganesha_use_f...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Installation_Guide
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Bhavana
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
: 1479543 (view as bug list)
Depends On:
Blocks: 1472813 1476803
TreeView+ depends on / blocked
 
Reported: 2017-07-12 12:53 UTC by Manisha Saini
Modified: 2023-09-14 04:00 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1476803 (view as bug list)
Environment:
Last Closed: 2017-08-01 10:54:30 UTC
Embargoed:

Attachments (Terms of Use)

Description Manisha Saini 2017-07-12 12:53:18 UTC 
Document URL: 
http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.2-Installation_Guide-branch-3.2-Stage/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#NFS_Ganesha_Update

Section Number and Name: 
⁠7.2. Updating the NFS Server
 ->⁠7.2.2. Updating NFS-Ganesha in the Offline Mode
      ->After step 17

Describe the issue: 

Upgrade from 3.2 to 3.2 async is failing because the selinux boolean ganesha_use_fusefs is in OFF state after upgrade.We need to document to enable this boolean manually after upgrade and before doing nfs-ganesha enable.

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

Suggestions for improvement: 

Additional information:
Comment 4 Manisha Saini 2017-07-29 16:08:21 UTC 
Changes looks good to me.Moving this bug to verified state.
Comment 6 John Call 2017-08-08 23:28:42 UTC 
*** Bug 1479543 has been marked as a duplicate of this bug. ***
Comment 8 Red Hat Bugzilla 2023-09-14 04:00:59 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.