Description of problem:
After Upgrade from 3.1.3 to 3.2, and restoring snapshot which was taken in 3.1.3. After restore gluster v status shows NFS service is not running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create 2*3 dist-repvol
2. create snapshot
3. Upgrade systems to 3.2 build and bump the op-version
4. Do snapshot restore and start the volume
NFS service is not running
NFS service should be running.
Given the snap was taken in 3.1.3, nfs.disable option was not touched. Now when this snap is restored, GlusterD didn't bring up the NFS service as nfs.disable is not set to off as per the current code logic.
@Jiffin - please confirm if this hypothesis is correct.
I think this needs to be marked as a known issue with a work around.
I have updated the doc text further for the release notes, let me know if this looks ok.
Looks good to me