Bug 849303

Summary: Geo-rep ip based access control is broken.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vidya Sakar <vinaraya>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED DUPLICATE QA Contact: Sudhir D <sdharane>
Severity: high Docs Contact:
Priority: medium    
Version: 2.0CC: aavati, csaba, gluster-bugs, rfortier, vkoppad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 826021 Environment:
Last Closed: 2013-05-09 22:30:34 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: 826021    
Bug Blocks: 850514    

Description Vidya Sakar 2012-08-18 02:38:01 UTC 
+++ This bug was initially created as a clone of Bug #826021 +++

Description of problem:
If the slave is set up to restrict other machines from spawning the slave agent, it won't work the way it should. 

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


How reproducible:Always 


Steps to Reproduce:
1.On the slave machine, set up the restriction of file salve(i.e any directory as the slave) from any other machines except itself like this.

 - gluster volume geo-rep '/*' config allow-network  ::1, 127.0.0.1

2.Now start a geo-rep session from any machine as master and the /path/to/directory  as slave. 

  gluster volume geo-rep  <master> <slave-host>:/path/to/directory start 

3.This setup shouldn't succeed.
  
Actual results: The setup should go to faulty.


Expected results: It works fine.


Additional info:

--- Additional comment from vkoppad on 2012-05-29 07:52:43 EDT ---

Created attachment 587390 [details]
Slave gsyncd.conf file
Comment 3 Csaba Henk 2013-05-09 22:30:34 UTC 
Marking as duplicate of original.

Fix is the same -- documentation should be updated.

*** This bug has been marked as a duplicate of bug 826021 ***