Bug 1562052 - build: revert configure --without-ipv6-default behaviour
Summary: build: revert configure --without-ipv6-default behaviour
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-29 12:42 UTC by Kaleb KEITHLEY
Modified: 2018-06-20 18:03 UTC (History)
1 user (show)

Fixed In Version: glusterfs-v4.1.0
Clone Of:
Environment:
Last Closed: 2018-06-20 18:03:13 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Kaleb KEITHLEY 2018-03-29 12:42:48 UTC
Description of problem:

ipv6-default is always on, --without-ipv6-default is ignored. IOW it's impossible to disable ipv6-default.

And on a box with IPv6 enabled but with no reverse DNS then volume start fails. (Not clear to me why reverse IPv6 from /etc/hosts does not resolve as it does or did for IPv4)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Kaleb KEITHLEY 2018-03-29 12:45:38 UTC
https://review.gluster.org/19787

Comment 2 Worker Ant 2018-03-29 12:46:12 UTC
REVIEW: https://review.gluster.org/19787 (build: revert configure --without-ipv6-default behaviour) posted (#2) for review on master by Kaleb KEITHLEY

Comment 3 Worker Ant 2018-04-02 12:51:07 UTC
COMMIT: https://review.gluster.org/19787 committed in master by "Jeff Darcy" <jeff.us> with a commit message- build: revert configure --without-ipv6-default behaviour

patch https://review.gluster.org/19692 breaks gluster on systems with
IPv6 enabled but don't have IPv6 reverse DNS. Also it defaulted to
enabling ipv6-default regardless of whether --with-ipv6-default or
--without-ipv6-default were specified in the options to configure.
(Also the patch was merged without review.)

Prefer libtirpc over glibc rpc.

On newer linux with tirpc and without glibc rpc use tirpc (obviously)

on less new linux with both tirpc and glibc rpc default to use tirpc,
unless --without-tirpc is specified, in which case use glibc rpc

On less new linux without tirpc fall back to glib rpc (obviously)

ipv6-default requires libtirpc. It is off by default. It must be
explicitly enabled with --with-ipv6-default. If --with-ipv6-default is
specified, but tirpc is not available, disable it and issue a warning

Change-Id: Ib96a230fafb83ec83a71948fe55af1215a7a6ffa
BUG: 1562052
Signed-off-by: Kaleb S. KEITHLEY <kkeithle>

Comment 4 Shyamsundar 2018-06-20 18:03:13 UTC
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/


Note You need to log in before you can comment on or make changes to this bug.