Bug 1405478

Summary:	Keepalive should be set for IPv6 & IPv4
Product:	[Community] GlusterFS	Reporter:	Shreyas Siravara <sshreyas>
Component:	rpc	Assignee:	Shreyas Siravara <sshreyas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, vbellur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-06 17:39:54 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:

Description Shreyas Siravara 2016-12-16 15:34:23 UTC

Description of problem: The code only checks for AF_INET today.


Version-Release number of selected component (if applicable): 3.6 onwards

Comment 1 Worker Ant 2016-12-16 15:37:23 UTC

REVIEW: http://review.gluster.org/16167 (socket: Keepalives should happen on IPv6 as well as IPv4) posted (#1) for review on master by Shreyas Siravara (sshreyas)

Comment 2 Worker Ant 2016-12-16 20:30:10 UTC

COMMIT: http://review.gluster.org/16167 committed in master by Vijay Bellur (vbellur) 
------
commit 136e6c81201daeb49e5ca9b893ae23b3ba5c0bdc
Author: Shreyas Siravara <sshreyas>
Date:   Tue Mar 15 19:18:35 2016 -0700

    socket: Keepalives should happen on IPv6 as well as IPv4
    
    Summary:
    - Check for AF_INET *and* AF_INET6.
    - This is a cherry-pick of D3057373 to 3.8
    
    Signed-off-by: Shreyas Siravara <sshreyas>
    Change-Id: I53eb79284eddfee6e13821c6570809f575b96769
    BUG: 1405478
    Reviewed-on: http://review.gluster.org/16167
    Reviewed-by: Jeff Darcy <jdarcy>
    Tested-by: Jeff Darcy <jdarcy>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Shyamsundar 2017-03-06 17:39:54 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report.

glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 4 Vijay Bellur 2018-11-20 03:55:10 UTC

*** Bug 1428065 has been marked as a duplicate of this bug. ***