Bug 985833

Summary:	Dist-geo-rep : Geo-rep commands won't work if the state_file is changed using config between create and start of geo-rep session.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	geo-replication	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED ERRATA	QA Contact:	Vijaykumar Koppad <vkoppad>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.1	CC:	aavati, amarts, asengupt, bbandari, csaba, rhs-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.15rhs-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 22:38:45 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:

Description Vijaykumar Koppad 2013-07-18 10:54:25 UTC

Description of problem: None of the geo-rep commands work, if the state_file is changes using the geo-rep config to some nonexistent file, in between create and start of geo-rep.


Version-Release number of selected component (if applicable):3.4.0.12rhs.beta4-1.el6rhs.x86_64


How reproducible:Happens everytime.


Steps to Reproduce:
1.Create a geo-rep relationship between master and slave.
2.Change the state_file using geo-rep config command to some non existent file 
3.try geo-rep start command 

Actual results: After the state_file change none of the geo-rep commands work.


Expected results: Config change at any stage shouldn't affect any of the geo-rep commands.


Additional info:

Comment 2 Avra Sengupta 2013-07-22 08:46:22 UTC

Resolved in https://code.engineering.redhat.com/gerrit/#/c/10452/

Comment 3 Vijaykumar Koppad 2013-08-12 09:19:43 UTC

verified on glusterfs-3.4.0.18rhs-1.el6rhs.x86_64

Comment 4 Scott Haines 2013-09-23 22:38:45 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:29 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