Description of problem:
When upgrading from 3.6 to 4.0, both release files contain definitions for the same repo name. It is expected that users remove the older release RPM, however due to bz#1415700 repo files are left over causing yum warning causing automation issues since yum returns a non-zero exit code due to duplicate repos.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install 3.6 and 4.0 release RPMs on a CentOS 7 machine:
# yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
# yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
2. remove 3.6 RPM (this imitates a successful update to 4.0)
# yum remove ovirt-release36
3. check for updates
# yum check-update
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Repository virtio-win-stable is listed more than once in the configuration
# echo $?
No warning displayed and yum returns exit code 0
# echo $?
this seems to be caused by virtio-win-stable defined in two *dependencies repo files:
# grep -r virtio-win-stable /etc/yum.repos.d/
A workaround to bz#1415700 would be to remove 3.6 repo files manually. A proper fix is to give unique names to virtio-win-stable in each release or supply this dependency in a separate RPM so that it can be shared by several release files.
ok, based on steps on #0
# yum repolist -v | egrep '^Repo-(id|baseurl).*virtio'
Repo-id : ovirt-master-virtio-win-latest
Repo-baseurl : http://fedorapeople.org/groups/virt/virtio-win/repo/latest/
Repo-id : virtio-win-stable
Repo-baseurl : http://fedorapeople.org/groups/virt/virtio-win/repo/stable/
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.