[Bugs] [Bug 1276541] New: glusterd: probing a new node(>=3.1) from 3.0.x cluster is moving the peer to rejected state

bugzilla at redhat.com bugzilla at redhat.com
Fri Oct 30 05:14:01 UTC 2015


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

            Bug ID: 1276541
           Summary: glusterd: probing a new  node(>=3.1)  from 3.0.x
                    cluster is moving the peer to rejected state
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs-server
          Assignee: rhs-bugs at redhat.com
          Reporter: anekkunt at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    nlevinki at redhat.com, vbellur at redhat.com
        Depends On: 1276423



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

Description of problem:

probing a new  node(>=3.1)  from 3.0.x cluster is moving the peer to rejected
state 



How reproducible:
Always

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


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
-- 
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=YyQz6q2aDa&a=cc_unsubscribe


More information about the Bugs mailing list