[
https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jir...
]
eyal edri commented on OVIRT-1893:
----------------------------------
The best way to solve it is to release a newer version than 1.1 with the fix, removing
deployed versions from yum repos is not recommended and can cause issues to users/qe who
is already using that repo.
Also, master repo is pointing on nightly compose, not official release, you might want to
use the 4.2 release rpm which
includes only official releases ( and might also include the 0.1 version you're
looking for ).
[~sbonazzo@redhat.com][~bkorren(a)redhat.com]
Remove ovirt-ansible-disaster-recovery-1.1 upstream version to
install version 0.1 instead
------------------------------------------------------------------------------------------
Key: OVIRT-1893
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1893
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Maor Lipchuk
Assignee: infra
Hi all,
It seems that ovirt-ansible-disaster-recovery repo installed from upstream
[1] is installed with version 1.1 [2]:
ovirt-ansible-disaster-recovery-1.1 is broken, because of a bug which was
already fixed [3] in ovirt-ansible-disaster-recovery 0.1.
The thing is that the release which automatically installed is 1.1 although
the fix is available in ovirt-ansible-disaster-recovery 0.1.
Is there a way to do something about it, could we remove the 1.1 versions,
so 0.1 will be installed instead?
[1]
http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
[2]
ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch
[3]
https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4
Regards,
Maor
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)