[Bugs] [Bug 1414998] New: setting for nfs-disable changed when upgrading from 3.7.x to 3.9.0

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 19 22:37:09 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1414998

            Bug ID: 1414998
           Summary: setting for nfs-disable changed when upgrading from
                    3.7.x to 3.9.0
           Product: GlusterFS
           Version: 3.9
         Component: glusterd
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: alex at nyi.net
                CC: bugs at gluster.org



Description of problem:

i was using gluster 3.7.18 and upgraded to 3.9.0 offline (i was using dispersed
volumes which didn't support online upgrades).

after i started glusterd back up on 3.9.0 i noticed my nfs share was no longer
working.. ran showmount and saw it could not communicate with rpc.  finally
came across the nfs-disable setting and the value was now ON.

Version-Release number of selected component (if applicable):
3.7.18 -> 3.9.x (gluster-server) (running on CentOS 7.2 dom0 (xenserver7))

How reproducible:
saw this on two different cluster upgrades

Steps to Reproduce:
1. install 3.7.18, create volume, verify NFS works
2. disable gluster, install 3.9.0 software
3. start glusterd back up, NFS will not be working

Actual results:
NFS services functional

Expected results:
NFS services disabled

Additional info:
per #gluster on freenode IRC:

<aleksk> i notice that with 3.9.0, the default is to have nfs.disable set to ON
for volumes
<aleksk> not only for newly created volumes but for volumes that i had created
with 3.7.x (nfs was working before but after upgrading to 3.9.0 it stopped
working and it took me a little bit to realize that the default
  changed
<aleksk> not my call to change defaults, but at the same time can't say i'm a
fan of not preserving settings from previously generated versions 
<JoeJulian> aleksk: Good point. Please file a bug report.
<glusterbot> https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS
<JoeJulian> This occurred because the 3.7 volume had no specific setting
regarding that as it was enabled by default. The upgrade process should
specifically set nfs on if it wasn't set prior to upgrading.
<aleksk> set nfs on meaning enable nfs, or set nfs-disable on ? 
<aleksk> i am not happy with the naming of the setting name either.. it's
awkward having a negative setting name 
<JoeJulian> I agree

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list