[Bugs] [Bug 1276423] glusterd: probing a new node(>=3.6) from 3.5 cluster is moving the peer to rejected state

[bugzilla at redhat.com]

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



--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12464 committed in master by Kaushal M
(kaushal at redhat.com) 
------
commit d29dd0747dbb2e7383867c97cbbaa8c41851db78
Author: anand <anekkunt at redhat.com>
Date:   Thu Oct 29 21:36:57 2015 +0530

    glusterd: fix info file checksum mismatch during upgrade

    issue: probing a new  node(>=3.6)  from 3.5 cluster is moving the peer to
rejected state.

    fix: Disperse vol support is added from 3.6 release, so write disperse
fields (disperse_count=0
    and redundancy_count=0) in vol info file  only if cluster version
supported.

    Change-Id: I11d5e2e337b9bbaddc8e52ca7295ba481beb1132
    BUG: 1276423
    Signed-off-by: anand <anekkunt at redhat.com>
    Reviewed-on: http://review.gluster.org/12464
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaushal M <kaushal at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=FFIwhZ0q3h&a=cc_unsubscribe