Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1508876

Summary:	[RGW:NFS] After a ganesha process kill, nfs-ganesha.service fails to start on it's own.
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vidushi Mishra <vimishra>
Component:	Ceph-Ansible	Assignee:	Ali Maredia <amaredia>
Status:	CLOSED NOTABUG	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.0	CC:	adeza, amaredia, anharris, aschoen, cbodley, ceph-eng-bugs, edonnell, flucifre, gmeno, hnallurv, kbader, kkeithle, mbenjamin, nthomas, owasserm, sankarshan, sweil, tbarron
Target Milestone:	rc
Target Release:	3.*
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.`nfs-ganesha.service` fails to start after a crash or a process kill of NFS Ganesha When the NFS Ganesha process terminates unexpectedly or it is killed, the `nfs-ganesha.service` daemon fails to start as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-03 21:50:35 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:	1494421

Description Vidushi Mishra 2017-11-02 12:35:31 UTC

Description of problem:
After a process kill for Ganesha process, it did not start on it's own and nfs-ganesha.service failed to start.

Version-Release number of selected component (if applicable):
nfs-ganesha-rgw-2.5.2-13.el7cp.x86_64
ceph version 12.2.1-37.el7cp

How reproducible:
Everytime

Steps to Reproduce:

1. Configure set-up for NFS-ganesha role. 
2. Run ansible-playbook and check if the ganesha service has come up. (cmd 'systemctl status nfs-ganesha.service' . It should be up/running)
3. Check for the nfs-ganesha process id (cmd "ps aux | grep ganesha")
4. Kill ganesha process (cmd ' kill <pid> ')
5. The nfs-ganesha.service should come up after few seconds. (It fails to load)

Actual results:
nfs-ganesha.service fails to start.

Expected results:
nfs-ganesha.service should to start after sometime.

Additional info:
As is the case with the ceph-daemons (OSDs and MON), start of nfs-ganesha service should also be handled after a process kill.

Comment 6 Kaleb KEITHLEY 2017-11-06 23:13:53 UTC

At a minimum there is `systemctl enable nfs-ganesha` which will ensure that ganesha.nfsd restarts when the box boots or reboots.

There is some systemctl magic for automatically restarting a process that crashes; you'll need to rtfm as I don't know what that is off the top of my head.

And FWIW, GlusterFS made a conscious decision not to automatically restart. At some point GlusterFS will revisit that decision. Ceph is not required to copy GlusterFS behavior.