Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688188 - Need glusterd configuration via ansible roles for IPV6 cases
Summary: Need glusterd configuration via ansible roles for IPV6 cases
Keywords:
Status: POST
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gluster-ansible
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1688217
TreeView+ depends on / blocked
 
Reported: 2019-03-13 10:54 UTC by SATHEESARAN
Modified: 2019-04-11 07:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1688217 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description SATHEESARAN 2019-03-13 10:54:46 UTC
Description of problem:
-----------------------
To enable IPV6 with gluster, glusterd volume file needs to be edited to uncomment, "options transport.address-family inet6" and glusterd needs to be restarted. This enabled IPV6 support with RHHI-V infrastructure.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-roles-1.0.4-4

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Use IPV6 FQDNs for hostnames

Actual results:
---------------
glusterd is not configured

Expected results:
-----------------
glusterd should be configured

Comment 2 Sachidananda Urs 2019-03-14 10:54:44 UTC
PR: https://github.com/gluster/gluster-ansible-features/pull/23 fixes the issue.

Comment 3 SATHEESARAN 2019-03-28 11:36:46 UTC
This bug is the MUST fix for the forthcoming RHHI-V release, providing the qa_ack


Note You need to log in before you can comment on or make changes to this bug.