Bug 1457724 - IPv6 in ganesha-ha.conf doesn't work
Summary: IPv6 in ganesha-ha.conf doesn't work
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-01 07:59 UTC by Jan
Modified: 2018-06-20 18:29 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:29:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jan 2017-06-01 07:59:19 UTC
Description of problem:
IPv6 address added into ganesha-ha.conf doesn't work even that Pacemaker / Corosync supports it.

Version-Release number of selected component (if applicable):
The most current version Gluster 3.10 and NFS-Ganesha from centos-gluster310 repository
CentOS 3.10.0-514.21.1.el7.x86_64

How reproducible:
Add IPv6 into and ganesha-ha.conf and activate Ganesha.

Actual results:
"ip a" command doesn't show IPv6 address from ganesha-ha.conf (it shows IPv4 from ganesha-ha.conf without any problem.

More information:
http://lists.gluster.org/pipermail/gluster-users/2017-May/031329.html

Comment 1 Kaleb KEITHLEY 2017-06-15 16:25:46 UTC
IPaddr2 supports IPv6. port_block does not. Until port_block supports IPv6 it isn't going to work.

I'm going to leave this open for now and see what the clustering folks have to say about eventual IPv6 support for port_block.

Comment 2 Shyamsundar 2018-06-20 18:29:52 UTC
This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.


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