Bug 901332

Summary:	glustershd and nfs services are not restarted during an upgrade
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	scripts	Assignee:	Kaushal <kaushal>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	bugs, glusterbugs, gluster-bugs, kkeithle, kparthas
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:	2014-12-14 19:40:30 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 2013-01-18 00:42:23 UTC

Description of problem:
Neither the self-heal nor nfs daemons are restarted during an rpm update. 

Since glustershd is not a user-facing daemon, I recommend adding it to the stop and start functions in the glusterd init process. The pid is in /var/lib/glusterd/glustershd/run/glustershd.pid. Kill it in stop only if the process name is glusterfs. Start is handled by glusterd so no changes to start() are necessary.

gluster-nfs should have it's own init script since it's user-facing. A start could, unless there's a better way to do it, just restart glusterd. The stop would kill the process whose pid is in /var/lib/glusterd/nfs/run/nfs.pid if the name is glusterfs.

Comment 1 Niels de Vos 2014-11-27 14:54:06 UTC

The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.