Bug 1563500

Summary:	nfs-ganesha: in case pcs cluster setup fails then nfs-ganesha process should not start
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	common-ha	Assignee:	Jiffin <jthottan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.10	CC:	amukherj, asriram, bugs, divya, jthottan, kkeithle, msaini, mzywusko, nlevinki, rhinduja, rhs-bugs, sankarshan, saujain, sheggodu, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.10.12	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1226874	Environment:
Last Closed:	2018-05-07 15:05:04 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 Jiffin 2018-04-04 04:03:48 UTC

+++ This bug was initially created as a clone of Bug #1226874 +++

Description of problem:
As per the new implementation for 3.1 that we are propsoing is HA by default for nfs-ganesha server. The problem is that there have been cases when pcs cluster setup has failed in some scenarios but the point to note is that nfs-ganesha process has spawned on the nodes, whereas nfs-ganesha should also not spawn in case pcs cluster setup has failed. Otherwise we are not providing HA as default with the setup that we are doing

One of the example scenario is BZ 1225507, there may be others.

Version-Release number of selected component (if applicable):
glusterfs-3.7.0-2.el6rhs.x86_64
nfs-ganesha-2.2.0-0.el6.x86_64

How reproducible:
several times


Expected results:
We need to have a check that decides if the pcs cluster is up only then nfs-ganesha should be spawned.

Comment 1 Worker Ant 2018-04-04 04:06:25 UTC

REVIEW: https://review.gluster.org/19816 (common-ha/scripts : pass the list of servers properly to stop_ganesha_all()) posted (#1) for review on release-3.10 by jiffin tony Thottan

Comment 2 Worker Ant 2018-04-04 12:23:06 UTC

COMMIT: https://review.gluster.org/19816 committed in release-3.10 by "jiffin tony Thottan" <jthottan> with a commit message- common-ha/scripts : pass the list of servers properly to stop_ganesha_all()

Change-Id: I6d92623cd9fb450d7a27f5acc61eca0b3cbc9b08
BUG: 1563500
Signed-off-by: Jiffin Tony Thottan <jthottan>

Comment 3 Shyamsundar 2018-05-07 15:05:04 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.12, please open a new bug report.

glusterfs-3.10.12 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-April/000095.html
[2] https://www.gluster.org/pipermail/gluster-users/