Bug 985833 - 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.
Dist-geo-rep : Geo-rep commands won't work if the state_file is changed using...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: geo-replication (Show other bugs)
2.1
x86_64 Linux
high Severity medium
: ---
: ---
Assigned To: Avra Sengupta
Vijaykumar Koppad
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-18 06:54 EDT by Vijaykumar Koppad
Modified: 2014-08-24 20:50 EDT (History)
6 users (show)

See Also:
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 18:38:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vijaykumar Koppad 2013-07-18 06:54:25 EDT
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 04:46:22 EDT
Resolved in https://code.engineering.redhat.com/gerrit/#/c/10452/
Comment 3 Vijaykumar Koppad 2013-08-12 05:19:43 EDT
verified on glusterfs-3.4.0.18rhs-1.el6rhs.x86_64
Comment 4 Scott Haines 2013-09-23 18:38:45 EDT
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 18:41:29 EDT
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

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