summaryrefslogtreecommitdiffstats
path: root/xlators/mgmt/glusterd/Makefile.am
diff options
context:
space:
mode:
authorAtin Mukherjee <amukherj@redhat.com>2016-02-25 14:42:48 +0530
committerJeff Darcy <jdarcy@redhat.com>2016-03-24 08:09:02 -0700
commit43652d54591e13234e1556e563866f7ecc2b56d6 (patch)
treecbdc1dfa3bcd3c6a7a778e21bbd5563bd8f3ec79 /xlators/mgmt/glusterd/Makefile.am
parent10d7b9d45a90d345f6ce4ec0e7192e0226602d80 (diff)
glusterd: reject peer probe from a reinstalled node
Backport of http://review.gluster.org/13519 In a cluster if a node (say N1) goes through a OS reinstallation then probing some other node in the cluster from N1 doesn't fail as in gd_validate_mgmt_hndsk_req () uuid & hostname checks are done separately but there should be one more check where both the conditions should meet. Steps to create the problem - N1 probes N2 - bring down glusterd instance on N2 - remove /var/lib/glusterd/* from N2 - restart glusterd instance on N2 - execute gluster peer probe N1 from N2 Validations in gd_validate_mgmt_hndsk_req () has been improved to handle this special case Change-Id: I3ba5d8e243bae07a7a6743d01b019e7014d39171 BUG: 1315147 Signed-off-by: Atin Mukherjee <amukherj@redhat.com> Reviewed-on: http://review.gluster.org/13519 Smoke: Gluster Build System <jenkins@build.gluster.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Jeff Darcy <jdarcy@redhat.com> Reviewed-on: http://review.gluster.org/13619
Diffstat (limited to 'xlators/mgmt/glusterd/Makefile.am')
0 files changed, 0 insertions, 0 deletions