Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1450730

Summary:	Add tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t to bad tests
Product:	[Community] GlusterFS	Reporter:	Ravishankar N <ravishankar>
Component:	replicate	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, ksubrahm
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1451887 (view as bug list)		Environment:
Last Closed:	2017-08-23 07:15:17 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:	1451887

Description Ravishankar N 2017-05-15 04:44:53 UTC

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-15 04:47:13 UTC

REVIEW: https://review.gluster.org/17290 (afr: gfid-mismatch-resolution-with-fav-child-policy.t to bad tests) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Worker Ant 2017-05-15 12:17:25 UTC

COMMIT: https://review.gluster.org/17290 committed in master by Jeff Darcy (jeff.us) 
------
commit ba0fc77947c9e873350b58a0e3e93ab51cc56b37
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.
    
    Change-Id: Iba6e9d81db386bc406aff1ecb6a18851f09bf7c0
    BUG: 1450730
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: https://review.gluster.org/17290
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Raghavendra G <rgowdapp>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Shyamsundar 2017-09-05 17:30:07 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.12.0, please open a new bug report.

glusterfs-3.12.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-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/