Bug 861945

Summary: if replace-brick is running , it shouldn't allow geo-rep to start.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED ERRATA QA Contact: Vijaykumar Koppad <vkoppad>
Severity: low Docs Contact:
Priority: high    
Version: 2.0CC: aavati, bbandari, csaba, rhs-bugs, shaines, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.4rhs-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 872289 (view as bug list) Environment:
Last Closed: 2013-09-23 22:38:38 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: 872289    

Description Vijaykumar Koppad 2012-10-01 12:25:59 UTC
Description of problem: Currently, if there is a geo-rep session going on , we don't allow replace-brick to start or do any replace-brick operations. Similarly , we shouldn't allow geo-rep to start if there is a replace-brick going on. 


Version-Release number of selected component (if applicable):
3.3.0rhs-28.el6rhs.x86_64

How reproducible: Always 


Steps to Reproduce:
1.Create a volume, lets say distribute-volume, 
2.Create fair amount of data on the mount point.
3.Start replace-brick of one of the volume 
4.Before repace-brick commit, try to start geo-rep. 
  
Actual results: It allow geo-rep to start


Expected results: IT shouldn't allow replace-brick to start 


Additional info:

Comment 2 Vijay Bellur 2012-12-12 00:27:04 UTC
CHANGE: http://review.gluster.org/4289 (gsyncd / geo-rep: do not start geo-rep if replace brick is in progress) merged in master by Anand Avati (avati)

Comment 3 Vijaykumar Koppad 2013-07-31 09:27:36 UTC
Verified on 3.4.0.14rhs-1.el6rhs.x86_64

Comment 4 Scott Haines 2013-09-23 22:38:38 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html

Comment 5 Scott Haines 2013-09-23 22:41:27 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html