Bug 1261866 – HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh related operations

Bug 1261866 - HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh related operations

Summary:	HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh...

Status:	ASSIGNED

Aliases:	None

Product:	nfs-ganesha
Classification:	Community
Component:	FSAL_GLUSTER (Show other bugs)
Sub Component:
Version:	devel
Hardware:	All All

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Kaleb KEITHLEY
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:	1355956 1376874
Blocks:	1261873
	Show dependency tree / graph

Reported:	2015-09-10 06:46 EDT by Jiffin
Modified:	2018-05-24 17:31 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Clones:	1261873 (view as bug list)
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jiffin 2015-09-10 06:46:45 EDT

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

Note You need to log in before you can comment on or make changes to this bug.