Bug 1458664

Summary: [Geo-rep]: METADATA errors are seen even though everything is in sync
Product: [Community] GlusterFS Reporter: Kotresh HR <khiremat>
Component: geo-replicationAssignee: Kotresh HR <khiremat>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11CC: bugs, sarumuga
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.11.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1455559 Environment:
Last Closed: 2017-06-28 18:32:26 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: 1455559    
Bug Blocks:    

Description Kotresh HR 2017-06-05 07:18:28 UTC 
+++ This bug was initially created as a clone of Bug #1455559 +++

Description of problem:
Even though master and slave arequal checksum matches, METADATA errors are being logged in master with errno ENOENT.

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

How reproducible:
Always

Steps to Reproduce:
1. Setup geo-rep
2. Untar linux src on master and let it sync to slave


Actual results:
METADATA errors are logged in master with ENOENT

Expected results:
It should not be logged.

Additional info:

--- Additional comment from Worker Ant on 2017-05-25 09:09:26 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Ignore ENOENT while meta data syncing) posted (#1) for review on master by Kotresh HR (khiremat)

--- Additional comment from Worker Ant on 2017-05-31 05:15:13 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#2) for review on master by Kotresh HR (khiremat)

--- Additional comment from Worker Ant on 2017-05-31 08:02:06 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#3) for review on master by Kotresh HR (khiremat)

--- Additional comment from Kotresh HR on 2017-05-31 08:05:41 EDT ---



--- Additional comment from Worker Ant on 2017-06-02 08:10:42 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#4) for review on master by Kotresh HR (khiremat)

--- Additional comment from Worker Ant on 2017-06-02 08:12:52 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#5) for review on master by Kotresh HR (khiremat)

--- Additional comment from Worker Ant on 2017-06-02 08:16:27 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#6) for review on master by Kotresh HR (khiremat)

--- Additional comment from Worker Ant on 2017-06-02 11:23:41 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#7) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2017-06-04 04:27:23 EDT ---

COMMIT: https://review.gluster.org/17389 committed in master by Aravinda VK (avishwan) 
------
commit 324e81d6fea324d512431a2604086326b8848e9b
Author: Kotresh HR <khiremat>
Date:   Thu May 25 07:28:07 2017 -0400

    geo-rep: Fix meta data sync on symlink
    
    chmod doesn't support 'no dereference' option.
    It always deference the symlink. But 'chown'
    does support metadata changes on symlink itself,
    which was not taken care while syncing. This
    patch fixes the same.
    
    Change-Id: Ic9985f4e39d15b5a9deb379841bcfb2c263d3e6c
    BUG: 1455559
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: https://review.gluster.org/17389
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Amar Tumballi <amarts>
    CentOS-regression: Gluster Build System <jenkins.org>
Comment 1 Worker Ant 2017-06-05 07:20:43 UTC 
REVIEW: https://review.gluster.org/17463 (geo-rep: Fix meta data sync on symlink) posted (#1) for review on release-3.11 by Kotresh HR (khiremat)
Comment 2 Worker Ant 2017-06-06 12:58:47 UTC 
COMMIT: https://review.gluster.org/17463 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit 5d49ff1f8b41f5babb2f6d484b3f1e1e6bb51ec8
Author: Kotresh HR <khiremat>
Date:   Thu May 25 07:28:07 2017 -0400

    geo-rep: Fix meta data sync on symlink
    
    chmod doesn't support 'no dereference' option.
    It always deference the symlink. But 'chown'
    does support metadata changes on symlink itself,
    which was not taken care while syncing. This
    patch fixes the same.
    
    > Change-Id: Ic9985f4e39d15b5a9deb379841bcfb2c263d3e6c
    > BUG: 1455559
    > Signed-off-by: Kotresh HR <khiremat>
    > Reviewed-on: https://review.gluster.org/17389
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Aravinda VK <avishwan>
    > Smoke: Gluster Build System <jenkins.org>
    > Reviewed-by: Amar Tumballi <amarts>
    > CentOS-regression: Gluster Build System <jenkins.org>
    (cherry picked from commit 324e81d6fea324d512431a2604086326b8848e9b)
    
    
    Change-Id: Ic9985f4e39d15b5a9deb379841bcfb2c263d3e6c
    BUG: 1458664
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: https://review.gluster.org/17463
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
Comment 3 Shyamsundar 2017-06-28 18:32:26 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.11.1, please open a new bug report.

glusterfs-3.11.1 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/2017-June/000074.html
[2] https://www.gluster.org/pipermail/gluster-users/