Bug 1451887

Summary: Add tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t to bad tests
Product: [Community] GlusterFS Reporter: Shyamsundar <srangana>
Component: replicateAssignee: Ravishankar N <ravishankar>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11CC: bugs, ravishankar
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.11.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1450730 Environment:
Last Closed: 2017-05-30 18:52:40 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: 1450730    
Bug Blocks:    

Description Shyamsundar 2017-05-17 18:27:07 UTC
+++ This bug was initially created as a clone of Bug #1450730 +++

Description of problem:

gfid-mismatch-resolution-with-fav-child-policy.t  does a `TEST ls $M0/f3` (line #170) to trigger healing of a file in gfid split-brain in a rep-3 volume. But the code to trigger name heal of gfid split-brain file is not yet there. The test is passing due a lookup/ stat on $M0 which triggers a background entry self heal (which has the code to heal gfid-splitbrain files) which may or may not complete the heal before line 170. If it doesn't, lookup on f3 is failing with EIO.

Add the .t to bad tests until Karthik's patch for CLI based gfid split-brain resolution fixes name heal also.

Comment 1 Worker Ant 2017-05-17 18:28:33 UTC
REVIEW: https://review.gluster.org/17319 (afr: gfid-mismatch-resolution-with-fav-child-policy.t to bad tests) posted (#1) for review on release-3.11 by Shyamsundar Ranganathan (srangana)

Comment 2 Worker Ant 2017-05-17 18:29:58 UTC
REVIEW: https://review.gluster.org/17319 (afr: gfid-mismatch-resolution-with-fav-child-policy.t to bad tests) posted (#2) for review on release-3.11 by Shyamsundar Ranganathan (srangana)

Comment 3 Worker Ant 2017-05-17 23:32:38 UTC
COMMIT: https://review.gluster.org/17319 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit 7687ddbc6ace34226c826bbb3f29c11dcaf22112
Author: Ravishankar N <ravishankar>
Date:   Mon May 15 10:15:20 2017 +0530

    afr: gfid-mismatch-resolution-with-fav-child-policy.t to bad tests
    
    gfid-mismatch-resolution-with-fav-child-policy.t  does a `TEST ls
    $M0/f3` (line #170) to trigger healing of a file in gfid split-brain in
    a rep-3 volume. But the code to trigger name heal of gfid split-brain
    file is not yet there. The test is passing due a lookup/ stat on $M0
    which triggers a background entry self heal (which has the code to heal
    gfid split-brain files) which may or may not complete the heal before
    line 170. If it doesn't, lookup on f3 is failing with EIO.
    
    Add the .t to bad tests until Karthik's patch for CLI based gfid
    split-brain resolution fixes name heal also.
    
    
    > BUG: 1450730
    > Signed-off-by: Ravishankar N <ravishankar>
    > Reviewed-on: https://review.gluster.org/17290
    
    (cherry picked from commit ba0fc77947c9e873350b58a0e3e93ab51cc56b37)
    
    BUG: 1451887
    Change-Id: Iba6e9d81db386bc406aff1ecb6a18851f09bf7c0
    Reviewed-on: https://review.gluster.org/17319
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Tested-by: Shyamsundar Ranganathan <srangana>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>

Comment 4 Ravishankar N 2017-05-18 00:42:36 UTC
(In reply to Shyamsundar from comment #0)
> +++ This bug was initially created as a clone of Bug #1450730 +++
> 
Thanks for the back port!

Comment 5 Shyamsundar 2017-05-30 18:52:40 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.0, please open a new bug report.

glusterfs-3.11.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/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/