Bug 1409799

Summary:	NFS Server is not coming up for the 3.8 volume after updating to 3.9
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	nfs	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bsrirama, bugs, ndevos, rhs-bugs, sbhaloth, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1409782	Environment:
Last Closed:	2017-01-03 16:48:21 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:

Comment 1 Atin Mukherjee 2017-01-03 12:52:07 UTC

Bug description:

gNFS Server is not coming up for the 3.8 volume after updating to  3.9.

I had two nodes cluster in 3.8 with Dis-Rep ( 2*2 ) volume and done the upgrade to 3.9.

After updating all cluster nodes, bumped up the cluster op-version to 30901 and checked the volume status, in v status, NFS Server was showing N/A.

Comment 2 Worker Ant 2017-01-03 12:53:59 UTC

REVIEW: http://review.gluster.org/16316 (glusterd: restart all daemons on volume dict change in op-version bump) posted (#1) for review on master by Atin Mukherjee (amukherj)

Comment 3 Worker Ant 2017-01-03 13:31:13 UTC

REVIEW: http://review.gluster.org/16316 (glusterd: restart all daemons on volume dict change in op-version bump) posted (#2) for review on master by Atin Mukherjee (amukherj)

Comment 4 Atin Mukherjee 2017-01-03 16:48:21 UTC

This is not a bug as in case of an upgrade user has to explicitly enable gNFS to bring back the service up. Closing this now.