Bug 1108502

Summary:	[RFE] Internalize master/slave verification (gverify)
Product:	[Community] GlusterFS	Reporter:	Venky Shankar <vshankar>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	mainline	CC:	avishwan, bugs, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 05:20:06 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:

Description Venky Shankar 2014-06-12 07:16:32 UTC

Description of problem:
Currently gverify.sh is used to perform basic sanity checks for master/slave. This is in the form of a bash script. Better would be to internalize the sanity checks in geo-rep itself (e.g. gsyncd --sanity), as it's much more cleaner in cases of non-root and the likes).

Version-Release number of selected component (if applicable):
mainline

Comment 1 Aravinda VK 2015-12-29 10:15:23 UTC

georepcli may solve this issue by doing verification from Python code itself instead of bash script
http://review.gluster.org/#/c/12460/

Comment 2 Vijay Bellur 2018-11-19 05:50:38 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/555

Please follow the github issue for further updates on this bug.