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"}
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.
@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
(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?
@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.
This is duplicate of BZ 1632245. I'm closing this one. *** This bug has been marked as a duplicate of bug 1632245 ***