Bug 762071 (GLUSTER-339)

Summary:	glusterfsd fails to start when there are no active interfaces having address in the address family configured.
Product:	[Community] GlusterFS	Reporter:	Raghavendra G <raghavendra>
Component:	transport	Assignee:	Raghavendra G <raghavendra>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	corentin.chary, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raghavendra G 2009-10-27 18:25:46 UTC

With listen-host not specified, the server should continue to listen on 0.0.0.0/::0 even though there are no active interfaces with addresses in the address family configured. This enables clients from different address family to run.

The bug was submitted and fixed by Corentin Chary <corentin.chary>.

Comment 1 Anand Avati 2009-11-03 11:49:00 UTC

PATCH: http://patches.gluster.com/patch/2025 in master (transport/name.c: refine the address resolution logic when listen-host is not specified.)

Comment 2 Anand Avati 2009-11-03 12:29:41 UTC

PATCH: http://patches.gluster.com/patch/2024 in release-2.0 (transport/name.c: refine the address resolution logic when listen-host is not specified.)