Description of problem: Gluster should work for IPv6 only, this should be ensured by a test. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
RHGS doesn't yet support the nodes to connect through IPv6 yet. Is this BZ filed for an RFE or a bug?
We are adding IPv6 support to RHV, we want RHHI to also be able to utilize it. This would be a RFE, if you currently do not support this.
*** Bug 1664590 has been marked as a duplicate of this bug. ***
What's the status of this? Isn't it bug 1635863 ?
Tested with glusterfs-3.12.2-45.el7rhgs 1. Enabled IPV6 on the gluster servers 2. Glusterd configuration is updated with 'option transport.address-family inet6' and restarted 3. Volumes are created with IPV6 FQDNs 4. Volumes are fuse mounted with mount option - 'xlator-option="transport.address-family=inet6"' 5. Able to create VM image files and access them. All worked good, except for geo-rep session creation failed - BZ 1688239 Note that this validation is done only with RHHI-V environement.
Have updated the doc text field. Kindly review.
(In reply to Anjana from comment #19) > Have updated the doc text field. Kindly review. We also need to highlight that the IPv6 support is for IPv6 only environments. For environments with both IPv4 and IPv6, IPv4 needs to be used
Have updated the doc text. (In reply to Sahina Bose from comment #21) > We also need to highlight that the IPv6 support is for IPv6 only > environments. For environments with both IPv4 and IPv6, IPv4 needs to be used
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, 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/RHBA-2019:0658