Bug 1385175

Summary:	systemd service fails if quorum not established before timeout
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	packaging	Assignee:	Rinku <rkothiya>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, hgowtham, mchangir, ndevos, rkothiya, sunkumar
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 12:47:42 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:

Description Joe Julian 2016-10-14 21:16:10 UTC

Description of problem:

Since the glusterd.service is set with "Type=forking", if glusterd fails to fork within the default 90 seconds, the service fails while leaving glusterd running.

If glusterd eventually has quorum established, it will start up successfully and background itself leaving the cluster healthy but systemd status will show that the service has failed to start.

How reproducible:
always

Steps to Reproduce:
1. Set up server quorum
2. Boot a server on a distro that uses systemd
3. wait 90 seconds

Actual results:
systemd service fails and leaves glusterd running

Expected results:
I think my expectation is that glusterd will daemonize and continue to try in the background. Either that or we should just run glusterd as a foreground process  when started by systemd and change Type to simple.

Additional info:

Comment 1 Worker Ant 2020-03-12 12:47:42 UTC

This bug is moved to https://github.com/gluster/glusterfs/issues/951, and will be tracked there from now on. Visit GitHub issues URL for further details