Description of problem: configure.ac currently has these lines for the ipv6-default switch. > AC_ARG_WITH([ipv6-default], > AC_HELP_STRING([--with-ipv6-default], [Set IPv6 as default.]), > [with_ipv6_default=$with_libtirpc], [with_ipv6_default=no]) This disables ipv6-default when no switch is given at all but otherwise checks if libtirpc was requested, regardless of whether you have given --with-ipv6-default or --without-ipv6-default. You could also specify --without-libtirpc --with-ipv6-default and it would silently disable both, although this combination is not possible in any case. Version-Release number of selected component (if applicable): 4.0.0, master (940f870f). How reproducible: Always. Steps to Reproduce: ./configure --without-ipv6-default Actual results: IPV6 default : yes Use TIRPC : yes Expected results: IPV6 default : no Use TIRPC : yes Additional info: This is important because ipv6-default breaks Gluster for systems that have IPv6 disabled.
REVIEW: https://review.gluster.org/19692 (build: Fix configure --without-ipv6-default behaviour) posted (#1) for review on master by James Le Cuirot
COMMIT: https://review.gluster.org/19692 committed in master by "Amar Tumballi" <amarts> with a commit message- build: Fix configure --without-ipv6-default behaviour The current behaviour disables ipv6-default when no switch is given at all but otherwise checks if libtirpc was requested, regardless of whether you have given --with-ipv6-default or --without-ipv6-default. I believe the intention was to enable when libtirpc is requested by default but otherwise respect the switch given. This is important because ipv6-default breaks Gluster for systems that have IPv6 disabled. BUG: 1553926 Change-Id: I76b91ae2699574b2e5b777453732bb5cbd79bbca Signed-off-by: James Le Cuirot <chewi>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/