Bug 1261873 – HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh related operations (add-node/delete-node)

Bug 1261873 - HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh related operations (add-node/delete-node) [NEEDINFO]

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

Status:	ASSIGNED

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	common-ha (Show other bugs)
Sub Component:
Version:	3.1
Hardware:	All All

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

URL:
Whiteboard:
Keywords:	Triaged, ZStream

Depends On:	1261866
Blocks:
	Show dependency tree / graph

Reported:	2015-09-10 07:05 EDT by Jiffin
Modified:	2017-08-23 09:28 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Known Issue
Doc Text:	Cause: Execute ganesha-ha script while one of the nodes in ha-cluster goes down. Consequence: Ganesha configuration files won't updated properly in the node which goes down.It may lead inconsistency in the cluster. Workaround (if any): After executing ganesha-ha script , it will log where it failed. So admin should make note of those nodes and update them manually. Result:
Story Points:	---
Clone Of:	1261866
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	kkeithle: needinfo? (msaini)

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

Groups: None (edit)

Description Jiffin 2015-09-10 07:05:28 EDT

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

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 3 Kaleb KEITHLEY 2017-08-23 09:28:44 EDT

storhaug

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