[Bugs] [Bug 1333243] [AFR]: "volume heal info" command is failing during in-service upgrade to latest.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1333243



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14219 committed in release-3.8 by Niels de
Vos (ndevos at redhat.com) 
------
commit 2ceb471d369c7da89d14c755b759b9358e035ccb
Author: Anuradha Talur <atalur at redhat.com>
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.

            >BUG: 1332798
            >Signed-off-by: Anuradha Talur <atalur at redhat.com>
            >Reviewed-on: http://review.gluster.org/14199
            >Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
            >Tested-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
            >Smoke: Gluster Build System <jenkins at build.gluster.com>
            >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
            >CentOS-regression: Gluster Build System
<jenkins at build.gluster.com>
            >Signed-off-by: Anuradha Talur <atalur at redhat.com>

    Change-Id: I0d3541ed0594d67c3c3b8568a89a975a100bf6dd
    BUG: 1333243
    Signed-off-by: Anuradha Talur <atalur at redhat.com>
    Reviewed-on: http://review.gluster.org/14219
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.