+++ 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>
patch : http://review.gluster.org/#/c/12501/1
COMMIT: http://review.gluster.org/12501 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit 50cde2853bd144ff19ac8b6ac06e993cfb734f63 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. Backport of: >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> >(cherry picked from commit d29dd0747dbb2e7383867c97cbbaa8c41851db78) Change-Id: I8351457d15e76936851128eb8609746ae87d5aa8 BUG: 1277822 Signed-off-by: anand <anekkunt> Reviewed-on: http://review.gluster.org/12501 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Raghavendra Bhat <raghavendra>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.7, please open a new bug report. glusterfs-3.6.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/gluster-devel/2015-December/047260.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user