Bug 1550952

Summary:	service nfs-ganesha enable is consistently failing in RHGS 3.4
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jiffin <jthottan>
Component:	nfs-ganesha	Assignee:	Jiffin <jthottan>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	jthottan, kkeithle, msaini, rhinduja, rhs-bugs, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	Regression
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 06:54:24 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:
Bug Depends On:
Bug Blocks:	1503137

Description Jiffin 2018-03-02 11:37:19 UTC

Description of problem:
During last rebase following changes were missing from systemd configuration of nfs-ganesha
+Restart=on-failure
+RestartSec=3
+RestartPreventExitStatus=SIGABRT SIGKILL SIGSEGV

Version-Release number of selected component (if applicable):
nfs-ganesha 2.5.2

How reproducible:
always

Actual results:
Post reboot ganesha service failed to start even though it is enabled

Expected results:
nfs-ganesha should be up and running if it is enabled

Comment 6 Manisha Saini 2018-03-21 04:41:26 UTC

Verified this BZ on-

# rpm -qa | grep ganesha
nfs-ganesha-2.5.5-3.el7rhgs.x86_64
nfs-ganesha-gluster-2.5.5-3.el7rhgs.x86_64
glusterfs-ganesha-3.12.2-5.el7rhgs.x86_64


Ganesha service starts successfully post node reboot.Hence moving this BZ to verified state

Comment 8 errata-xmlrpc 2018-09-04 06:54:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2610