Bug 1676412
Summary: | [TestOnly] Ensure that Self Hosted Engine works on Gluster in an IPv6 only scenario | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Dominik Holler <dholler> |
Component: | rhhi | Assignee: | Sahina Bose <sabose> |
Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | godas, rcyriac, rhs-bugs, rvdwees, sankarshan |
Target Milestone: | --- | ||
Target Release: | RHHI-V 1.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature: Support RHHI deployment in IPv6 only environments.
Following changes are needed to enable this:
* Glusterd volfile should be edited to contain "option transport.address-family inet6" and glusterd service restarted.
* Additional mount options 'xlator-option=transport.address-family=inet6' should be passed to Hosted engine storage domain in the deployment UI
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-09 06:09:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1618669, 1676886 | ||
Bug Blocks: | 1672931 |
Description
Dominik Holler
2019-02-12 08:42:47 UTC
Verified with RHV 4.3 and RHGS 3.4.4 ( glusterfs-3.12.2-47.el7rhgs ) and with ovirt-hosted-engine-setup-2.3.6-1.el7ev.noarch 1. Gluster setup is done with updating the configuration in glusterd. Glusterd volfile should contain "option transport.address-family inet6" and restarted glusterd 2. While setting up HE, additional mount option 'xlator-option=transport.address-family=inet6' HE setup is up post performing the above steps 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/RHEA-2019:1121 |