Description of problem: Create and start geo-rep session. Run status command twice. First time status shows fine, second time fails with error "No active geo-replication sessions between <MASTERVOL> and <SLAVEHOST>::<SLAVEVOL>" Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create and start geo-rep session 2. Run status command twice 3. Actual results: Fails with error Expected results: Show status output Additional info:
REVIEW: http://review.gluster.org/10694 (geo-rep: Fix corrupt gsyncd output) posted (#1) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/10694 committed in master by Vijay Bellur (vbellur) ------ commit 77edf5f7f78d5a551526b0d9bef8e0c0a8f22c1c Author: Aravinda VK <avishwan> Date: Sat May 9 00:26:14 2015 +0530 geo-rep: Fix corrupt gsyncd output When gsyncd fails with Python traceback, glusterd fails parsing gsyncd output and shows error. BUG: 1219937 Change-Id: Ic32fd897c49a5325294a6588351b539c6e124338 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/10694 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10698 (geo-rep: Update Not Started to Created in code and doc) posted (#1) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/10698 (geo-rep: Update Not Started to Created in code and doc) posted (#2) for review on master by Vijay Bellur (vbellur)
REVIEW: http://review.gluster.org/10698 (geo-rep: Update Not Started to Created in code and doc) posted (#3) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/10698 committed in master by Vijay Bellur (vbellur) ------ commit deb76ef2a97ea51c0cbe329a1fdb636071fda90f Author: Aravinda VK <avishwan> Date: Sat May 9 10:03:42 2015 +0530 geo-rep: Update Not Started to Created in code and doc "Not Started" status is now "Created", replaced "Not Started" string in code and doc. Change-Id: If7d606c2cc8156e41291e7eebe9d0da4ad7ac28d Signed-off-by: Aravinda VK <avishwan> BUG: 1219937 Reviewed-on: http://review.gluster.org/10698 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user