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

Bug 1806499

Summary: afr-lock-heal-basic.t and /afr-lock-heal-advanced.t fails when brick mux is enabled
Product: [Community] GlusterFS Reporter: Ravishankar N <ravishankar>
Component: testsAssignee: Ravishankar N <ravishankar>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-12 14:24:38 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:

Description Ravishankar N 2020-02-24 11:32:08 UTC 
Description of problem:
There seems to be some problems with the statedump code when brick mux is enabled - it dumpsthe ACTIVE locks held by each inode multiple times on the statedump file. Because of that the .t fails due to mismatching of the actual and expected counts. While that needs to be fixed, I am currently filtering out the duplicates in the .t
Comment 1 Worker Ant 2020-02-24 11:36:52 UTC 
REVIEW: https://review.gluster.org/24160 (tests: fix afr-lock-heal-* failure) posted (#2) for review on master by Ravishankar N
Comment 2 Worker Ant 2020-03-12 14:24:38 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1042, and will be tracked there from now on. Visit GitHub issues URL for further details