Description of problem: Compile with IPV6_DEFAULT: $ gluster v set rep nfs.disable off $ gluster v set rep nfs.register-with-portmap on $ mount.nfs 192.168.1.102:/rep /mnt # => successfully as expected $ mount.nfs [fe80::20c:29ff:feb9:fc0a%eth0]:/rep /tmp/nfs # => successfully as expected $ umount /mnt $ umount /tmp/nfs $ gluster v set rep nfs.register-with-portmap off $ mount.nfs 192.168.1.102:/rep /mnt # => failed as expected mount.nfs: requested NFS version or transport protocol is not supported $ mount.nfs [fe80::20c:29ff:feb9:fc0a%eth0]:/rep /tmp/nfs # should failed but successfully The root cause is that, we missed rpcsvc_program_unregister_rpcbind6 in nfs_program_unregister_portmap_all function Version-Release number of selected component (if applicable): master How reproducible: 100% Additional info: Migration from https://github.com/gluster/glusterfs/issues/463 (as it was a bug rather than the feature).
REVIEW: https://review.gluster.org/20263 (nfs: add missing rpcsvc_program_unregister_rpcbind6) posted (#3) for review on master by Amar Tumballi
COMMIT: https://review.gluster.org/20263 committed in master by "Amar Tumballi" <amarts> with a commit message- nfs: add missing rpcsvc_program_unregister_rpcbind6 Otherwise, event if nfs.register-with-portmap is disabled, we could also use ipv6 to mount nfs through portmap. Change-Id: I7546e03d942dfaf2252d57e17be9c1cca986a715 fixes: bz#1593651 Signed-off-by: Xie Changlong <xiechanglong.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report. glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/