Description of problem: ------------------------ When attempting for RHHI-V deployment with static IPv6, gluster deployment is successful while the hosted-engine deployment fails Version-Release number of selected component (if applicable): -------------------------------------------------------------- vdsm-gluster-4.40.16-1.el8ev.x86_64 How reproducible: ----------------- Always Steps to Reproduce: ------------------ 1. Start RHHI-V deployment with static IPV6 Actual results: --------------- HE deployment fails while creating the target storage domain Expected results: ----------------- HE deployment should be successful Additional info:
Following is the comment from Sanju: ------------------------------------- I see that the command is failing if we specify a hostname instead of IPv6: [root@newhost ~]# gluster --remote-host=myhost.lab.eng.blr.redhat.com volume list Connection failed. Please check if gluster daemon is operational. [root@newhost ~]# when we add --inet6 option to the cli, it works: [root@newhost ~]# gluster --remote-host=myhost.lab.eng.blr.redhat.com --inet6 volume list testrep [root@newhost ~]# I believe, this option is added to differentiate whether the given hostname corresponds to IPv4 or IPv6 address. @Sas, Do you think any changes are needed? Thanks, Sanju ------------------------------- So vdsm-gluster code should try to use '--inet6' when the host uses IPV6 hostnames
Tested with vdsm-4.40.21-1.el8ev.x86_64 On a IPv4 only setup, this check fails and adds '--inet6' to IPv4 hostnames as well, which leads to failure to mount gluster volumes
The dependent vdsm bug is already ON_QA
Tested with vdsm-4.40.22-1.el8ev.x86_64 When using IPV6 FQDN, the additional token for gluster command '--inet6' is used when querying for volume information
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:3314