Bug 767559 - glusterd responding to requests from outside the cluster
Summary: glusterd responding to requests from outside the cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact: shylesh
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2011-12-14 11:13 UTC by shylesh
Modified: 2015-11-03 23:04 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:12:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: 3.3.0qa42
Embargoed:


Attachments (Terms of Use)

Description shylesh 2011-12-14 11:13:39 UTC
Description of problem:
glusterd responding to requests from outside the cluster

Version-Release number of selected component (if applicable):
Mainline

How reproducible:
Always

Steps to Reproduce:
1.create a cluster of 2 machines
2.create some volumes .
3.wipe out /etc/glusterd manually from one of the machine and restart glusterd(now this machine is outside the cluster).
4.issue volume stop (say) from the other machine . 
   
Actual results:
volume stop command fails saying "volume doesn't exists". This is because the peer whose 'store' was wiped out responded to the "volume stop" request without checking if it was coming from a peer part of the cluster.

Expected results:
Volume stop command should fail because of broken cluster. The "wiped out" peer should not respond  (positively/negatively) to the "volume stop" request when coming from a peer not part of its cluster.

Additional info:

Comment 1 Anand Avati 2011-12-19 16:43:07 UTC
CHANGE: http://review.gluster.com/787 (glusterd: Fail 'requests' from non-peers.) merged in master by Vijay Bellur (vijay)

Comment 2 shylesh 2012-05-23 14:37:39 UTC
Now glusterd does not respond to peers outside the cluster


Note You need to log in before you can comment on or make changes to this bug.