Bug 812738

Summary:	gluster geo-rep commands exit with geo-replication command failed
Product:	[Community] GlusterFS	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	glusterd	Assignee:	Kaushal <kaushal>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	high
Version:	mainline	CC:	bbandari, csaba, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-24 02:29:32 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 Vijaykumar Koppad 2012-04-16 06:46:25 UTC

Description of problem: If start a geo-replication sesion like 

root@vostro:~# gluster volume geo doa /root/geo/ start

geo-replication command failed

Version-Release number of selected component (if applicable):3.3.0(master)
[dc4c44d51e3eb4b53e78840bf223911e48ce62b5]

How reproducible:always


Steps to Reproduce:
1.Create a volume of any type.
2.Start a geo-replication session( gluster volume geo-rep <volname> <patch/to/slave>

  
Actual results: Failing with geo-replication command failed


Expected results: It should succeed.

Comment 1 Kaushal 2012-04-18 04:27:29 UTC

Fixed by change http://review.gluster.com/3157 (glusterd : Fixes for breakages caused by volume-id validation) for bug https://bugzilla.redhat.com/show_bug.cgi?id=812801

Comment 2 Csaba Henk 2012-04-24 02:29:32 UTC


*** This bug has been marked as a duplicate of bug 812801 ***