Bug 1311874
Summary: | Peer probe from a reinstalled node should fail | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Atin Mukherjee <amukherj> | |
Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1315147 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:58:25 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1315147 |
Description
Atin Mukherjee
2016-02-25 09:11:11 UTC
REVIEW: http://review.gluster.org/13519 (glusterd: reject peer probe from a reinstalled node) posted (#1) for review on master by Atin Mukherjee (amukherj) REVIEW: http://review.gluster.org/13519 (glusterd: reject peer probe from a reinstalled node) posted (#2) for review on master by Atin Mukherjee (amukherj) REVIEW: http://review.gluster.org/13519 (glusterd: reject peer probe from a reinstalled node) posted (#3) for review on master by Atin Mukherjee (amukherj) COMMIT: http://review.gluster.org/13519 committed in master by Jeff Darcy (jdarcy) ------ commit 85b9e8ebb89ecadd30a364853e1e7c706dcce968 Author: Atin Mukherjee <amukherj> Date: Thu Feb 25 14:42:48 2016 +0530 glusterd: reject peer probe from a reinstalled node 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: 1311874 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/13519 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy> 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.8.0, please open a new bug report. glusterfs-3.8.0 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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |