Red Hat Bugzilla – Bug 1378677
"nfs.disable: on" is not showing in Vol info by default for the 3.1.3 volumes after updating to 3.2
Last modified: 2017-03-23 01:48:52 EDT
Description of problem: ======================= The volume option "nfs.disable: on" is not showing for the 3.1.3 volumes after updating to 3.2 ( glusterfs-3.8.4-1 ). Version-Release number of selected component (if applicable): ============================================================= This option is showing for the volumes created after updating 3.2. How reproducible: ================= Always Steps to Reproduce: =================== 1. Have 3.1.3 setup with replica-1 volume 2. Update to 3.2 ( glusterfs-3.8.4-1 ) 3. Check volume info 4. Create a new replica-2 volume 5. Compare the volume info of replica-1 and replica-2 Actual results: =============== "nfs.disable: on" is showing in Vol info by default for the 3.1.3 volumes after updating to 3.2 Expected results: ================= Volume options in the volume info should be same for multiple same volume type by default. Additional info:
Upstream mainline patch http://review.gluster.org/#/c/15568 posted for review.
RCA: The options were put up in the dictionary during volume creation and were never recreated during upgrade and hence volume info doesn't show them as default. These options are now been put up in to volume's dictionary when the op-version is bumped up.
Copying my comment from the upstream bug: The volume that was upgraded, will still have gNFS running for it, so volume info not having gNFS is expected and correct. This isn't a bug IMO, and doesn't need anything to be fixed.
upstream mainline : http://review.gluster.org/15568 upstream 3.9 : http://review.gluster.org/15652 downstream patch : https://code.engineering.redhat.com/gerrit/#/c/87434
Verified this bug using the build - 3.8.4-3 Fix is working good and i am seeing the nfs.disable:on in the volume info after updating 3.1.3 volume to 3.2 available build. 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. https://rhn.redhat.com/errata/RHSA-2017-0486.html