Bug 1224934

Summary: [New] - Removing a geo replication session and re creating it gives error saying "geo replication session is already present"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED WORKSFORME QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.1CC: asrivast, knarra, nlevinki, rhs-bugs, sabose
Target Milestone: ---   
Target Release: RHGS 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-12 02:17: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:
Bug Depends On:    
Bug Blocks: 1224288    
Attachments:
Description Flags
Attaching the screenshot for the error of geo replication none

Description RamaKasturi 2015-05-26 09:12:41 UTC 
Description of problem:
Removing geo replication session from UI and trying to create it again from UI displays an error saying "Geo Rep session Creation failed error: Session between <mastervol> and root@<hostname::<vol_slave> is already created_ return code:-1.

But the same succeeds from cli.

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.0.scratch.master.el6.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Create a geo-rep session from UI and delete it.
2. Now try creating the same session again.
3.

Actual results:
UI fails to create a geo rep session and displays an error which says geo replication session is already created.

Expected results:
Geo-rep session should be successful.

Additional info:
Comment 2 RamaKasturi 2015-05-26 09:18:27 UTC 
Engine and vdsm logs can be found at the link below.

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1224934/
Comment 3 RamaKasturi 2015-05-26 09:19:34 UTC 
Created attachment 1029827 [details]
Attaching the screenshot for the error of geo replication
Comment 4 Sahina Bose 2015-06-01 09:05:03 UTC 
Check the vdsm verb output - may require a change in gluster cli option
Comment 6 Sahina Bose 2015-06-11 11:06:59 UTC 
Could not reproduce this issue. Tried with
1. single node volumes
2. 3 node volumes replicating to another 3 node volume

Could you provide steps to reproduce?
Comment 7 RamaKasturi 2015-06-11 13:13:03 UTC 
Hi sahina,

     I am not able to reproduce the issue. You can close this bug saying this is not reproducible. I will re open again if seen again.

Thanks
kasturi
Comment 8 Sahina Bose 2015-06-12 02:17:45 UTC 
Closing this as per comment 7