Bug 1415705

Summary: Repository virtio-win-stable is listed more than once in the configuration
Product: [oVirt] ovirt-release Reporter: Evgheni Dereveanchin <ederevea>
Component: GeneralAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: low Docs Contact:
Priority: low    
Version: 4.0.1CC: bugs, lsvaty
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
jbelka: testing_plan_complete-
lsvaty: testing_ack+
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:02:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Evgheni Dereveanchin 2017-01-23 13:27:22 UTC 
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):
ovirt-release40-4.0.6.1-1.noarch

How reproducible:
always

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

Actual results:

 ...
 Failed to set locale, defaulting to C
 Loaded plugins: fastestmirror
 Repository virtio-win-stable is listed more than once in the configuration
 ...

 # echo $?
 100

Expected results:

No warning displayed and yum returns exit code 0
 # echo $?
 100

Additional info:
this seems to be caused by virtio-win-stable defined in two *dependencies repo files:

# grep -r virtio-win-stable /etc/yum.repos.d/
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:[virtio-win-stable]
/etc/yum.repos.d/ovirt-3.6-dependencies.repo:[virtio-win-stable]

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.
Comment 1 Jiri Belka 2017-10-04 12:14:49 UTC 
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/
Comment 2 Sandro Bonazzola 2017-12-20 11:02:20 UTC 
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.