[Gluster-Maintainers] Fwd: Bug#914125: Peering on glusterfs-server (version >5) impossible under IPv4 on Buster

[Kaushal M]

The IPV6 implementation in Gluster requires that IPV6 be enabled in the
kernel and that getaddrinfo works for AF_INET6. This is why IPV6_DEFAULT is
disabled by default, and is only enabled if GlusterFS is configured with
`--with-ipv6-default`.
This has been the case since it was introduced in 3.13.

The change v5.0 debian packages that is causing the failures seems to be
that glusterfs is configured with `--with-ipv6-default` enabled. This needs
to be disabled for now. The packages provided by other distributions do not
enable this.

The IPV6 changes were contributed to GlusterFS by Facebook, and are
designed to run on their internal networks which are all IPV6 enabled. The
`--with-ipv6-default` flag is provided for their convenience, and is
disabled by default. There hasn't been any further contributions to this to
make it suitable for everyone as there hasn't been a lot of community ask
for it.

On Thu, Nov 22, 2018 at 2:19 PM Patrick Matthäi <pmatthaei at debian.org>
wrote:

> Hi,
>
> looks like my MUA didn't send the message..
>
> Our users have problems with the --with-ipv6-default option, they are not
> able to connect at all. Could you help here?
>
> -------- Weitergeleitete Nachricht --------
> Betreff: Bug#914125: Peering on glusterfs-server (version >5) impossible
> under IPv4 on Buster
> Weitersenden-Datum: Mon, 19 Nov 2018 17:15:02 +0000
> Weitersenden-Von: Emmanuel Quemener <emmanuel.quemener at gmail.com>
> <emmanuel.quemener at gmail.com>
> Weitersenden-An: debian-bugs-dist at lists.debian.org
> Weitersenden-CC: Patrick Matthäi <pmatthaei at debian.org>
> <pmatthaei at debian.org>
> Datum: Mon, 19 Nov 2018 18:12:46 +0100
> Von: Emmanuel Quemener <emmanuel.quemener at gmail.com>
> <emmanuel.quemener at gmail.com>
> Antwort an: Emmanuel Quemener <emmanuel.quemener at gmail.com>
> <emmanuel.quemener at gmail.com>, 914125 at bugs.debian.org
> An: submit at bugs.debian.org
>
> Package: glusterfs-server
> Version: 5.1-1
>
> 1)  When I install the glusterfs-server with a version >5, peering is
>   impossible in IPv4 on buster distribution.
>
> # apt install glusterfs-server
>
> # systemctl start glusterd
>
> # systemctl start glustereventsd
>
> # gluster peer probe 140.77.79.200
> peer probe: success. Probe on localhost not needed
>
> # gluster peer probe 140.77.79.185
> peer probe: failed: Probe returned with Transport endpoint is not connected
>
> When I look inside the logs in /var/log/glusterfs/glusterd.log
>
> [2018-11-19 16:50:37.051633] E [MSGID: 101075] [common-
> utils.c:508:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Address
> family for hostname not supported)
> [2018-11-19 16:50:37.051638] E
> [name.c:258:af_inet_client_get_remote_sockaddr] 0-management: DNS
> resolution failed on host 140.77.79.185
>
> 2)  It's working on glusterfs-server version 4 but without firewalld
> package.
>
> 3)  It's working with glusterfs-server version 5.1 when I REMOVE the 2
> following options inside debian/rules AND without firewalld :
>
> DEB_CONFIGURE_EXTRA_FLAGS := \
>         --enable-firewalld \
>         --with-ipv6-default
>
> I also try without any success to use the following options to fall back
> on IPv4 options in /etc/glusterfs/glusterd.vol :
>
>     option transport-type socket/inet,rdma
>     option transport.address-family inet
>
> Best regards.
>
> EQ
>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20181129/f86ea9e9/attachment.html>