Bug 1550952 - service nfs-ganesha enable is consistently failing in RHGS 3.4
Summary: service nfs-ganesha enable is consistently failing in RHGS 3.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Jiffin
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-03-02 11:37 UTC by Jiffin
Modified: 2018-09-24 12:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 06:54:24 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2610 0 None None None 2018-09-04 06:55:33 UTC

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
Note You need to log in before you can comment on or make changes to this bug.