Bug 1317989

Summary:	pid file is not created if there are dns lookup problems
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.8	CC:	bugs, sarumuga
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10:49:06 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 Joe Julian 2016-03-15 17:16:22 UTC

Description of problem:
The systemd service fails due to timeout because the pid file is not created. This seems to happen when there are dns lookup problems.

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

How reproducible:
always

Steps to Reproduce:
1. Start "glusterd -p /var/run/glusterd.pid" (with volumes defined) without a way to look up hostnames of other hosts (myhostname is in nsswitch so it must be due to resolving the *other* hostnames)
2. ls /var/run/glusterd.pid

Actual results:
ls: cannot access '/var/run/glusterd.pid': No such file or directory

Expected results:
/var/run/glusterd.pid

Additional info:

Comment 1 Kaushal 2017-03-08 10:49:06 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.