Mounting a Red Hat Storage Volume over the GlusterFS-native protocol fails due to DNS resolution issues

Solution Verified - Updated -

Issue

A volume created on a trusted pool can not be mounted through the GlusterFS-native protocol, mounting through NFS works

In the log from the glusterfs client (/var/log/glusterfs/$mountpoint.log) the following messages appeared:

 E [common-utils.c:125:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known)
 E [name.c:245:af_inet_client_get_remote_sockaddr] 0-vol-client-0: DNS resolution failed on host rhs001.example.com
...
 W [fuse-bridge.c:525:fuse_attr_cbk] 0-glusterfs-fuse: 2: LOOKUP() / => -1 (Transport endpoint is not connected)
 I [fuse-bridge.c:4133:fuse_thread_proc] 0-fuse: unmounting /mnt/volume
 W [glusterfsd.c:924:cleanup_and_exit] (-->/lib64/libc.so.6(clone+0x6d) [0x7f1f6689370d] (-->/lib64/libpthread.so.0(+0x77f1) [0x7f1f66eef7f1] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x405cad]))) 0-: received signum (15), shutting down

Environment

  • Red Hat Storage 2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content