Bug 1404996

Summary:	gNFS: nfs.disable option to be set to off on existing volumes after upgrade to 3.2 and on for new volumes on 3.2
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	surabhi <sbhaloth>
Component:	gluster-nfs	Assignee:	Jiffin <jthottan>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, jthottan, rcyriac, rhinduja, rhs-bugs, skoduri, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-9	Doc Type:	Release Note
Doc Text:	As of Red Hat Gluster Storage 3.2, Gluster Native NFS server is disabled when creating a new volume. Administrators can either use NFS-Ganesha with new volumes, or continue using Native NFS server by enabling it manually. Existing volumes that use Gluster Native NFS are not modified in order to prevent disruptions during upgrade.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-23 05:57:27 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:	1351528, 1351530

Description surabhi 2016-12-15 10:36:55 UTC

Description of problem:
************************

After upgrade The gnfs option on volume needs to be enabled if it was already enabled before upgrade and there should not be any question/prompt regarding ganesha.

For the new volumes the option should be disabled.

option in question : 
Currently : nfs.disable : on
Expected : nfs.disable : off  for existing volumes.

For new volumes after upgrade to 3.2 
nfs.disable: on

Version-Release number of selected component (if applicable):
glusterfs-3.8.4-8.el7rhgs.x86_64


How reproducible:


Steps to Reproduce:


Actual results:


Expected results:


1. The existing volumes on 3.1.3 if the nfs.disable option was set to off , even after upgrade it should be off.
2. On the new volumes after upgrade to 3.2 should have nfs.disable to on.




Additional info:
This is as per discussion in planning meetings last week.

Comment 4 Atin Mukherjee 2016-12-16 12:55:35 UTC

https://code.engineering.redhat.com/gerrit/#/c/93146 is a downstream only patch and now merged into the code base.

Comment 7 Manisha Saini 2017-01-16 09:04:42 UTC

Verified this Bug on 

glusterfs-cli-3.8.4-11.el7rhgs.x86_64

After Upgrade,nfs.disable option was set to "off" on existing volume in 3.1.3 and nfs.disable option is set to "on" on new volume created in 3.2

Comment 10 errata-xmlrpc 2017-03-23 05:57:27 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/RHSA-2017-0486.html