[Bugs] [Bug 1277822] New: 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=1277822

            Bug ID: 1277822
           Summary: glusterd: probing a new  node(>=3.6)  from 3.5 cluster
                    is moving the peer to rejected state
           Product: GlusterFS
           Version: 3.6.0
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: anekkunt at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    pkarampu at redhat.com
        Depends On: 1276423
            Blocks: 1276541, 1276905



+++ This bug was initially created as a clone of Bug #1276423 +++

Description of problem:

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



How reproducible:
Always

Steps to Reproduce:
probe the 3.7 node from 3.5 cluster, then 3.7 node moves to rejected state due
to check sum mismatch

--- Additional comment from Vijay Bellur on 2015-10-29 12:24:27 EDT ---

REVIEW: http://review.gluster.org/12464 (glusterd: fixing vol info checksum
mismatch) posted (#1) for review on master by Anand Nekkunti
(anekkunt at redhat.com)

--- Additional comment from Vijay Bellur on 2015-10-30 07:22:46 EDT ---

REVIEW: http://review.gluster.org/12464 (glusterd: fix info file checksum
mismatch during upgrade) posted (#2) for review on master by Anand Nekkunti
(anekkunt at redhat.com)

--- Additional comment from Vijay Bellur on 2015-10-30 09:46:00 EDT ---

REVIEW: http://review.gluster.org/12464 (glusterd: fix info file checksum
mismatch during upgrade) posted (#3) for review on master by Anand Nekkunti
(anekkunt at redhat.com)

--- Additional comment from Vijay Bellur on 2015-11-01 01:52:45 EST ---

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>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1276423
[Bug 1276423] glusterd: probing a new  node(>=3.6)  from 3.5 cluster is
moving the peer to rejected state
https://bugzilla.redhat.com/show_bug.cgi?id=1276541
[Bug 1276541] glusterd: probing a new  node(>=3.1)  from 3.0.x cluster is
moving the peer to rejected state
https://bugzilla.redhat.com/show_bug.cgi?id=1276905
[Bug 1276905] glusterd: probing a new  node(>=3.6)  from 3.5 cluster is
moving the peer to rejected state
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.