Bug 1381421

Summary: afr fix shd log message error
Product: [Community] GlusterFS Reporter: Ravishankar N <ravishankar>
Component: replicateAssignee: Ravishankar N <ravishankar>
Status: CLOSED CURRENTRELEASE 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: glusterfs-3.10.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-06 17:29:11 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:

Description Ravishankar N 2016-10-04 04:46:29 UTC
Found while debugging 1381170.
    1. While looking at glustershd logs in DEBUG log-level, it was found that
    all bricks of the replica were printed as local bricks even though they
    were not. Fixed it.

    2. Print the name of the subvol from which the entry was got during
    index crawl.

Comment 1 Worker Ant 2016-10-04 04:47:12 UTC
REVIEW: http://review.gluster.org/15610 (afr: fix incorrect debug log in selfheal path) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Worker Ant 2016-10-04 18:32:10 UTC
COMMIT: http://review.gluster.org/15610 committed in master by Vijay Bellur (vbellur) 
------
commit a1bbbf35cb91e5132b8c46dff0681d24371295a4
Author: Ravishankar N <ravishankar>
Date:   Tue Oct 4 10:10:56 2016 +0530

    afr: fix incorrect debug log in selfheal path
    
    1. While looking at glustershd logs in DEBUG log-level, it was found that
    all bricks of the replica were printed as local bricks even though they
    were not. Fixed it.
    
    2. Print the name of the subvol from which the entry was got during
    index crawl.
    
    Change-Id: I08b32e38694c755715e9fe0c0e1dd9212abcfb16
    BUG: 1381421
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/15610
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Shyamsundar 2017-03-06 17:29:11 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.10.0, please open a new bug report.

glusterfs-3.10.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/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/