Description of problem:
gNFS Server is not coming up for the 3.1.3 volume after updating to 3.2.0.
I had two nodes cluster in 3.1.3 with Dis-Rep ( 2*2 ) volume and done the in-service update to 3.2.0 by fuse mounting the volume.
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.
NFS Server should be running for the upgraded volume as per the BZ-https://bugzilla.redhat.com/show_bug.cgi?id=1404996
I will provide the sos reports from server nodes to check the issue.
Version-Release number of selected component (if applicable):
Update from 3.1.3 to glusterfs-3.8.4-10.
Steps to Reproduce:
1. Have two node cluster and have 2 *2 volume.
2. Fuse mount the volume and start IO
3. Start In-service update ( follow the steps present in installation guide)
4. Check the volume status // you won't see NFS Server running.
NFS Server is not coming up after updating 3.1.3 volume to 3.2.0 latest build.
NFS Server should be running as per the BZ-https://bugzilla.redhat.com/show_bug.cgi?id=1404996
Upstream patch http://review.gluster.org/16316 posted for review.
RCA: op-version bump up code handled the upgrade path for all existing volumes for which gNFS was not disabled however the code didn't reconfigure the nfs daemon because of which nfs service was never started.
(In reply to Atin Mukherjee from comment #4)
> Upstream patch http://review.gluster.org/16316 posted for review.
The behaviour in upstream is different where user is supposed to explicitly enable gNFS post upgrade. So this patch will not be valid in upstream. I'll be working on a DOWNSTREAM ONLY patch to fix it.
Comment 6 is correct and hence closing this bug.
downstream patch : https://code.engineering.redhat.com/gerrit/94006
Fix is working good moving to verified state.
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.