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)
Summary: HA : All the nodes in HA-cluster should be up to perform any of ganesha-ha.sh...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: common-ha
Version: rhgs-3.1
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Kaleb KEITHLEY
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On: 1261866
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-10 11:05 UTC by Jiffin
Modified: 2020-04-06 11:02 UTC (History)
11 users (show)

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:
Clone Of: 1261866
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Jiffin 2015-09-10 11:05:28 UTC 
+++ 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 13:28:44 UTC 
storhaug
Note You need to log in before you can comment on or make changes to this bug.