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:
Resolved in https://code.engineering.redhat.com/gerrit/#/c/10452/
verified on glusterfs-3.4.0.18rhs-1.el6rhs.x86_64
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