Description of problem: There are some additional requirements in the ganesha-ha.sh script. Documenting it here as a bug. 1.There should be a way in which the script itself creates and populates the file ganesha-ha.sh. The user shouldn't have to create and edit this file. The script should ask for input and populate the file 2.The ganesha-ha.conf should be copied to all the nodes by the script 3. Preliminary validation of the ganesha-ha.conf 4.ganesha-ha.sh --refresh-config 5. Add-node : Create links in each directory and a new dir with all the links 6. Remove-node : Have a check if it is the last node or not. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/10355 (common-ha: copy config during setup, clean /etc/cluster during teardown) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.