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

Bug 1261866

Summary:	HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh related operations
Product:	[Retired] nfs-ganesha	Reporter:	Jiffin <jthottan>
Component:	FSAL_GLUSTER	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	devel	CC:	jthottan, kkeithle, ndevos, pasik, skoduri
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1261873 (view as bug list)		Environment:
Last Closed:	2020-06-23 12:49:15 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:	1355956, 1376874
Bug Blocks:	1261873

Description Jiffin 2015-09-10 10:46:45 UTC

Description of problem:

The changes for nfs-ganesha configuration files(ganesha.conf, export files, ganesha-ha.conf) is reflected in the HA-cluster with help of ganesha-ha.sh.
These changes won't reflect if the node in HA-cluster is down. So that admin should manually change those configuration when the node comes back to online.
Otherwise it will lead inconsistency in the HA-cluster such that each ganesha server exporting with different configuration.
 
Version-Release number of selected component (if applicable):
mainline

How reproducible:
always

Comment 1 Kaleb KEITHLEY 2020-06-23 12:49:15 UTC

I believe it is true that any node can.