[Bugs] [Bug 1582417] New: [Geo-rep]: Directory renames are not synced in hybrid crawl

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1582417

            Bug ID: 1582417
           Summary: [Geo-rep]: Directory renames are not synced in hybrid
                    crawl
           Product: Red Hat Gluster Storage
           Version: 3.4
         Component: geo-replication
          Severity: high
          Assignee: avishwan at redhat.com
          Reporter: rallan at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: bugs at gluster.org, csaba at redhat.com,
                    khiremat at redhat.com, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1499566



+++ This bug was initially created as a clone of Bug #1499566 +++

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:

--- Additional comment from Worker Ant on 2017-10-08 13:20:43 EDT ---

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 at redhat.com)

--- Additional comment from Worker Ant on 2017-11-10 00:37:00 EST ---

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 at redhat.com>

--- Additional comment from Shyamsundar on 2018-03-15 07:18:57 EDT ---

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/


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1499566
[Bug 1499566] [Geo-rep]: Directory renames are not synced in hybrid crawl
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=3OG1oJQ6LZ&a=cc_unsubscribe