+++ 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) --- 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) --- 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) --- 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) ------ commit d29dd0747dbb2e7383867c97cbbaa8c41851db78 Author: anand <anekkunt> 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> Reviewed-on: http://review.gluster.org/12464 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> Tested-by: NetBSD Build System <jenkins.org>
REVIEW: http://review.gluster.org/12477 (glusterd: fix info file checksum mismatch during upgrade) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/12477 (glusterd: fix info file checksum mismatch during upgrade) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/12477 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 6d4c63f12f2d87b4ed45ddd7c81825d013a9b43f Author: anand <anekkunt> 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> >Reviewed-on: http://review.gluster.org/12464 >Reviewed-by: Pranith Kumar Karampuri <pkarampu> >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Kaushal M <kaushal> >Tested-by: NetBSD Build System <jenkins.org> BUG: 1276905 Change-Id: Ia601c068706a96621203132429d4417fa1c96f76 Signed-off-by: anand <anekkunt> Reviewed-on: http://review.gluster.org/12477 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.