Bug 1109748

Summary:	gluster does not detect self-heal daemon when bind is used.
Product:	[Community] GlusterFS	Reporter:	Alexey Zilber <alexeyzilber>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4.3	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-07 13:59:36 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 Alexey Zilber 2014-06-16 10:06:05 UTC

Description of problem:
When vol option transport.socket.bind-address is set the self-heal daemon is not detected on either localhost or the peer ip.
When no transport.socket.bind-address is set, the self-heal daemon is only detected on localhost.

Version-Release number of selected component (if applicable):
CentOS 5.10 x86

How reproducible:
gluster volume status before and after adding/removing the transport.socket.bind-address option..

Steps to Reproduce:
1.gluster volume status
2.add transport.socket.bind-address & restart glusterd/glusterfsd
3.gluster volume status
4. remove transport.socket.bind-address & restart glusterd/glusterfsd
5. gluster volume status

Actual results:
Not detected

Expected results:
Self-heal daemon detected

Additional info:

Comment 1 Niels de Vos 2015-05-17 22:00:26 UTC

GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.

This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs".

If there is no response by the end of the month, this bug will get automatically closed.

Comment 2 Kaleb KEITHLEY 2015-10-07 13:59:36 UTC

GlusterFS 3.4.x has reached end-of-life.

If this bug still exists in a later release please reopen this and change the version or open a new bug.