Bug 1499566

Summary:	[Geo-rep]: Directory renames are not synced in hybrid crawl
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1582417 (view as bug list)		Environment:
Last Closed:	2018-03-15 11:18:57 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:	1582417

Description Kotresh HR 2017-10-08 17:18:33 UTC

Description of problem:
Directory renames are not synced in hybrid crawl

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

How reproducible:
Always

Steps to Reproduce:
1. Setup geo-replication
2. Set the change_detector to xsync
3. Create directory (dir1) on master and let it sync to slave
4. rename dir1 to dir2


Actual results:
dir2 would not be synced to slave. dir1 still exists on slave

Expected results:
dir1 should be renamed to dir2 on slave

Additional info:

Comment 1 Worker Ant 2017-10-08 17:20:43 UTC

REVIEW: https://review.gluster.org/18448 (geo-rep: Fix rename of directory in hybrid crawl) posted (#1) for review on master by Kotresh HR (khiremat)

Comment 2 Worker Ant 2017-11-10 05:37:00 UTC

COMMIT: https://review.gluster.org/18448 committed in master by  

------------- geo-rep: Fix rename of directory in hybrid crawl

In hybrid crawl, renames and unlink can't be
synced but directory renames can be detected.
While syncing the directory on slave, if the
gfid already exists, it should be rename.
Hence if directory gfid already exists, rename
it.

Change-Id: Ibf9f99e76a3e02795a3c2befd8cac48a5c365bb6
BUG: 1499566
Signed-off-by: Kotresh HR <khiremat>

Comment 3 Shyamsundar 2018-03-15 11:18:57 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-4.0.0, please open a new bug report.

glusterfs-4.0.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://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/