Bug 1543975

Summary: Gdeploy fails to set up a geo-replication session.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Devyani Kota <dkota>
Component: gdeployAssignee: Devyani Kota <dkota>
Status: CLOSED DUPLICATE QA Contact: Manisha Saini <msaini>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: amukherj, dkota, rcyriac, rhinduja, rhs-bugs, rreddy, sheggodu, smohan, storage-qa-internal, surs
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-08 12:53:58 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:

Description Devyani Kota 2018-02-09 17:19:31 UTC
Description of problem:
Gdeploy fails while setting up a geo-replication session.

Gdeploy should be able to create/delete, start/stop geo-replication sessions.
But, the config file fails to create a geo-rep session, complaining about missing master volume.

TASK [Create the geo-rep session] *******************************************************************************************************************************************
fatal: [10.70.42.156]: FAILED! => {"changed": false, "failed": true, "msg": "Volume mastervol does not exist\n"}

Comment 2 Sachidananda Urs 2018-02-09 17:39:52 UTC
This should be a documentation bug. Master volume and slave volume are pre-requisites for creating geo-rep session.

Master/Slave volumes can be created by separate config files.

Comment 3 Devyani Kota 2018-02-10 15:24:11 UTC
@sachi, when trying to create a georep session, gdeploy was trying to find master volume on the slave node.(Both master and slave volumes exist)
Checked the group_vars/all file, master node is being reassigned.
I think that this[1] commit fixed the same.

[1]https://github.com/gluster/gdeploy/pull/480/commits/84e3494c86319940a3fc0a52467692d16828f4dc

Comment 11 Yaniv Kaul 2018-09-20 10:42:55 UTC
(In reply to Devyani Kota from comment #3)
> @sachi, when trying to create a georep session, gdeploy was trying to find
> master volume on the slave node.(Both master and slave volumes exist)
> Checked the group_vars/all file, master node is being reassigned.
> I think that this[1] commit fixed the same.
> 
> [1]https://github.com/gluster/gdeploy/pull/480/commits/
> 84e3494c86319940a3fc0a52467692d16828f4dc

That's merged now. What's the latest status?

Comment 12 Devyani Kota 2018-10-18 08:13:43 UTC
@yaniv hello,
The pull request is merged and available.
Since this issue was scoped out of 3.4, it is not tested by QE.
We can document the same and help if the QE plan on testing the same for the upcoming release.

Comment 13 Atin Mukherjee 2018-11-08 12:53:58 UTC
This is duplicate of BZ 1632245. I'm closing this one.

*** This bug has been marked as a duplicate of bug 1632245 ***