Once CentOS 1708 will be released, gdeploy will become available from GlusterFS repositories from CentOS Storage SIG.
Packages for gdeploy are currently in the testing repositories that are provided through centos-release-gluster310 and centos-release-gluster312 (not released yet). Because Ansible is not available in standard CentOS yet (coming soon!), the gdeploy packages are not tagged for release. You could already consume the packages from the SIG, as long as you take care of enabling a repository that contains the ansible dependencies. There are at least two options that can be considered: a. Create a repository definition that only includes the gdeploy packages from testing, and exclude all others. This can replace the COPR repository definition. Once the next minor release of CentOS is available, this repository definition can be removed. b. Tag gdeploy in the ovirt tags in the CBS. Once the package lands in the release tags of the Storage SIG, the ovirt tags do not need to track it anymore. HTH, Niels gdeploy in the CBS: http://cbs.centos.org/koji/packageinfo?packageID=6557 Repositories: - https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.10/ - https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.12/
Niels, no rush for this. We'll wait for 7.4 to go GA and gdeploy to be tagged for release.
Tested with ovirt-4.2.2, gdeploy 2.0.6 is consumed from centos SIG
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.