Bug 1294083 - Wrong URL for CentOS VIrt SIG repository when using EL7 Server variant
Summary: Wrong URL for CentOS VIrt SIG repository when using EL7 Server variant
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-release
Classification: oVirt
Component: CentOS
Version: master-002
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ovirt-4.0.0-alpha
: master-002
Assignee: Sandro Bonazzola
QA Contact: Gonza
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-24 14:11 UTC by Yedidyah Bar David
Modified: 2016-03-24 07:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 10:57:45 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52575 0 master MERGED master: fix Virt SIG URL for EL7 Server 2016-01-21 16:19:25 UTC
oVirt gerrit 55176 0 ovirt-3.6 MERGED master: fix Virt SIG URL for EL7 Server 2016-03-24 07:40:14 UTC

Description Yedidyah Bar David 2015-12-24 14:11:04 UTC 
Description of problem:

We point at [1], but on RHEL, $releasever is 7Server, which does not exist.

Not sure if we try to support rhel. On centos it's '7' which works.

If we do, need to either fix the source (find some yum var that returns
'7' in such a case, or hard-code '7' during building the file) or ask
centos to add a link.

[1] http://mirror.centos.org/centos/$releasever/virt/$basearch/ovirt-3.6/
Comment 1 Sandro Bonazzola 2016-01-21 16:45:26 UTC 
ovirt-release-master has been updated with the fixing patch.
Comment 2 Gonza 2016-02-04 07:53:59 UTC 
Verified with:
ovirt-release-master-4.0.0-0.0.master.noarch
Red Hat Enterprise Linux Server release 7.2 (Maipo)

...
[centos-ovirt36]
name=CentOS-$releasever - oVirt 3.6
baseurl=http://mirror.centos.org/centos/7/virt/$basearch/ovirt-3.6/
gpgcheck=0
enabled=1
Note You need to log in before you can comment on or make changes to this bug.