Hi,
at the moment I'm struggeling with GlusterFS shares via IPv6.
I noticed that GlusterFS needs the option xlator-option="transport.address-family=inet6" when calling the mount function.
Otherwise IPv6 hosts cannot be reached.
See: https://milindchangireblog.wordpress.com/2019/02/01/how-to-set-up-glusterfs-for-ipv6-communication
The exact error message from the GlusterFS-log is:
Via various bug trackers I have seen that corresponding adjustments were made for platforms like oVirt.
See: https://bugzilla.redhat.com/show_bug.cgi?id=1688245
Until now I haven't not found a way to pass this option via Proxmox.
Is this a known issue or did I skip a note in the documentation?
Maybe someone knows a workaround?
Tested with Proxmox VE 6.3-4 on Debian Buster and GlusterFS 5.5, 8 and 9.
best regards
poly01
at the moment I'm struggeling with GlusterFS shares via IPv6.
I noticed that GlusterFS needs the option xlator-option="transport.address-family=inet6" when calling the mount function.
Otherwise IPv6 hosts cannot be reached.
See: https://milindchangireblog.wordpress.com/2019/02/01/how-to-set-up-glusterfs-for-ipv6-communication
The exact error message from the GlusterFS-log is:
Code:
E [MSGID: 101075] [common-utils.c:497:gf_resolve_ip6] 0-resolver: error in getaddrinfo [{family=2}, {ret=No address associated with hostname}]
E [name.c:265:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host <FQDN>
Via various bug trackers I have seen that corresponding adjustments were made for platforms like oVirt.
See: https://bugzilla.redhat.com/show_bug.cgi?id=1688245
Until now I haven't not found a way to pass this option via Proxmox.
Is this a known issue or did I skip a note in the documentation?
Maybe someone knows a workaround?
Tested with Proxmox VE 6.3-4 on Debian Buster and GlusterFS 5.5, 8 and 9.
best regards
poly01