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):
Steps to Reproduce:
Current behavior is that if any volumes (with default nfs.disable option value i.e, off) are upgraded to >3.8.x , gNFS doesn't come up by default. But if any user has explicitly set nfs.disable off for any volume and upgrades to > 3.8.x release, gNFS server comes up automatically. We would like to fix the latter scenario (if technically possible).
Currently gNFS is not shipped with release 4.1 and release 5. Hence closing this bug as eoled