Bug 1376694

Summary:	Disable gluster-NFS post upgrade to >= RHGS 3.2 release
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Soumya Koduri <skoduri>
Component:	gluster-nfs	Assignee:	Jiffin <jthottan>
Status:	CLOSED WONTFIX	QA Contact:	surabhi <sbhaloth>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, asrivast, avasudev, bugs, jthottan, kkeithle, mzywusko, ndevos, rcyriac, rhinduja, rhs-bugs, sbhaloth, skoduri, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	RHGS 3.2.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1376692	Environment:
Last Closed:	2016-12-16 13:22:20 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:	1376692
Bug Blocks:

Description Soumya Koduri 2016-09-16 07:51:34 UTC

+++ This bug was initially created as a clone of Bug #1376692 +++

Description of problem:

Since gluster-NFS is no more default NFS server for gluster volumes from 3.8.x release, it shouldn't be started by default post upgrade to >=3.8.x releases.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Atin Mukherjee 2016-09-16 18:05:43 UTC

I need to understand the requirement here, if the setup already has an active nfs mount(s) pre upgrade I dont see a reason of disabling the service post upgrade. So in that case would there be a migration path from nfs to nfs ganesha for the existing mounts?

Comment 6 Atin Mukherjee 2016-09-24 07:26:44 UTC

While I was looking at the BZ 1378677 I realized currently we don't start gNFS process in rhgs-3.2.0 post upgrade when earlier gNFS enabled. So I believe we have nothing to do here, can you cross check it Kaleb?

Comment 7 Soumya Koduri 2016-09-24 11:58:39 UTC

But Jiffin observed that when the option "nfs.disable" is explicitly set to off (not by default but if admin manually sets it) for any volume in 3.1.3, after upgrade that option will remain 'off' bringing gluster-NFS server. Jiffin shall be able to confirm it.

Comment 8 Niels de Vos 2016-09-29 14:44:44 UTC

Downstream wants a different approach than upstream:

https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.0.md#glusternfs-disabled-by-default

> Existing volumes that have gNFS enabled will remain enabled unless explicitly
> disabled.

For downstream all upgrades need to have gNFS disabled, no matter if the admin explicitly enabled gNFS before the upgrade.

Comment 17 Jiffin 2016-11-18 07:12:04 UTC

Patch posted downstream up for review https://code.engineering.redhat.com/gerrit/#/c/90425

Comment 22 Atin Mukherjee 2016-11-21 08:42:43 UTC

(In reply to Jiffin from comment #17)
> Patch posted downstream up for review
> https://code.engineering.redhat.com/gerrit/#/c/90425

Please note this is a downstream only change.

Comment 25 RHEL Program Management 2016-12-15 04:22:52 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.