Red Hat Bugzilla – Bug 901332
glustershd and nfs services are not restarted during an upgrade
Last modified: 2014-12-14 14:40:30 EST
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.
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.