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

Bug 1212823

Summary:	Additional checks required in ganesha-ha.sh
Product:	[Community] GlusterFS	Reporter:	Meghana <mmadhusu>
Component:	common-ha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	vagarwal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1214888 (view as bug list)		Environment:
Last Closed:	2015-10-25 15:22:17 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:
Bug Blocks:	1214888

Description Meghana 2015-04-17 12:06:35 UTC

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:

Comment 1 Anand Avati 2015-04-23 16:47:02 UTC

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)

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 15:22:17 UTC

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.