Bug 1203086

Summary:	Dist-geo-rep: geo-rep create fails with slave not empty
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	avishwan, bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-14 17:26:53 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 Kotresh HR 2015-03-18 05:06:45 UTC

Description of problem:
Geo-replicatioon create fails with "Slave volume not empty" eventhoug slave
is empty.

e.g.
gluster vol geo-rep master fedora1::slave create push-pem

fedora1::slave is not empty. Please delete existing files in fedora1::slave and retry, or use force to continue without deleting the existing files.
geo-replication command failed

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

How reproducible:
Always

Steps to Reproduce:
1. Create and start master and slave volume.
2. Create geo-replication session

Actual results:
geo-rep create fails with slave not empty when slave is actually empty.

Expected results:
geo-rep create should not fail when slave is actually empty.

Additional info:

Comment 1 Anand Avati 2015-03-18 05:16:47 UTC

REVIEW: http://review.gluster.org/9921 (geo-rep/gverify: Ignore .trashcan while checking slave is empty.) posted (#1) for review on master by Kotresh HR (khiremat)

Comment 2 Anand Avati 2015-03-18 10:11:30 UTC

REVIEW: http://review.gluster.org/9921 (geo-rep/gverify: Ignore .trashcan while checking slave is empty.) posted (#2) for review on master by Kotresh HR (khiremat)

Comment 3 Anand Avati 2015-03-20 17:27:10 UTC

COMMIT: http://review.gluster.org/9921 committed in master by Venky Shankar (vshankar) 
------
commit 8aa13c8e285ad496ed7c8511ae0b735eed73ebd4
Author: Kotresh HR <khiremat>
Date:   Wed Mar 18 10:37:00 2015 +0530

    geo-rep/gverify: Ignore .trashcan while checking slave is empty.
    
    With trash translator, '.trashcan' is created in gluster volume
    during init. So geo-rep create used to fail, with slave not
    being empty. The gverify script should ignore '.trashcan' while
    checking whether slave is empty.
    
    Change-Id: Ib7ee265c6aa99b63c7ccf103747d47a6f756ad35
    BUG: 1203086
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/9921
    Reviewed-by: Aravinda VK <avishwan>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>

Comment 4 Niels de Vos 2015-05-14 17:26:53 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:28:28 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:35:17 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user