Bug 1332798 - [AFR]: "volume heal info" command is failing during in-service upgrade to latest.
Summary: [AFR]: "volume heal info" command is failing during in-service upgrade to lat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On: 1311362
Blocks: 1268895 1333239 1333243
TreeView+ depends on / blocked
 
Reported: 2016-05-04 06:23 UTC by Anuradha
Modified: 2017-03-27 18:27 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.9.0
Clone Of: 1311362
: 1333239 1333243 (view as bug list)
Environment:
Last Closed: 2017-03-27 18:27:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-05-04 06:32:47 UTC
REVIEW: http://review.gluster.org/14199 (heal: Fix incorrect heal info output) posted (#1) for review on master by Anuradha Talur (atalur)

Comment 2 Vijay Bellur 2016-05-05 01:46:27 UTC
COMMIT: http://review.gluster.org/14199 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 2326f8c2a775f6536d95e2e4676866f1b5dfc368
Author: Anuradha Talur <atalur>
Date:   Wed May 4 11:55:43 2016 +0530

    heal: Fix incorrect heal info output
    
    Problem:
    In heterogenous clusters, heal info gives incorrect
    outout as "Failed to process entries completely.
    Number of entries so far: 0".
    
    This happens when the getxattr on virtual xattr
    for <brickpath>/.glusterfs/indices/dirty fails
    on older bricks as they do not recognize the xattr.
    
    Fix:
    Ignore that error so that heal info doesn't
    incorrectly report failure.
    
    Change-Id: I0d3541ed0594d67c3c3b8568a89a975a100bf6dd
    BUG: 1332798
    Signed-off-by: Anuradha Talur <atalur>
    Reviewed-on: http://review.gluster.org/14199
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 5 Shyamsundar 2017-03-27 18:27:08 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.9.0, please open a new bug report.

glusterfs-3.9.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/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.