Bug 1219938 - Running status second time shows no active sessions
Summary: Running status second time shows no active sessions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On: 1219937
Blocks: glusterfs-3.7.1
TreeView+ depends on / blocked
 
Reported: 2015-05-08 18:59 UTC by Aravinda VK
Modified: 2015-05-14 17:35 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.7.0beta2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1219937
Environment:
Last Closed: 2015-05-14 17:27:36 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Aravinda VK 2015-05-08 18:59:16 UTC
+++ This bug was initially created as a clone of Bug #1219937 +++

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:

Comment 1 Anand Avati 2015-05-08 19:04:08 UTC
REVIEW: http://review.gluster.org/10695 (geo-rep: Fix corrupt gsyncd output) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)

Comment 2 Anand Avati 2015-05-09 04:46:55 UTC
REVIEW: http://review.gluster.org/10699 (geo-rep: Update Not Started to Created in code and doc) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)

Comment 3 Anand Avati 2015-05-09 09:18:18 UTC
COMMIT: http://review.gluster.org/10695 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 7fb2437f17e1fabf184a5ea5f9fcad5f11615c55
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: 1219938
    Change-Id: Ic32fd897c49a5325294a6588351b539c6e124338
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/10694
    Reviewed-on: http://review.gluster.org/10695
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Aravinda VK 2015-05-10 03:52:57 UTC
One more patch http://review.gluster.org/#/c/10699/(merged)

Comment 5 Niels de Vos 2015-05-14 17:27:36 UTC
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.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:28:59 UTC
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.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:35:22 UTC
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.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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