Bug 1175566

Summary: Can not use mirrorlist with RHEL $releasever
Product: [Fedora] Fedora Reporter: Ian Wienand <iwienand>
Component: mirrormanagerAssignee: Pierre-YvesChibon <pingou>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: jonstanley, matt_domsch, puiterwijk
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-28 12:18:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ian Wienand 2014-12-18 03:32:38 UTC 
I'm trying to install the latest EPEL automatically with the following repo

---
[epel]
name=Setup EPEL
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-$releasever&arch=$basearch
---

After than I can then "yum install epel-release" to know I'm getting the latest version

The issue is that on RHEL "$releasever" expands to "6Server", which is an invalid path

---
$ urlgrabber 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6Server&arch=x86_64'
$ head -2 mirrorlist 
# repo = epel-6Server arch = x86_64 error: invalid repo or arch
# following repositories are available:
---

As far as I can tell, there is no variable for yum that provides just the major version.  I think the solution is to have the mirrorlist recognise 6Server (and 7Server) and just point them at epel-X
Comment 1 Matt Domsch 2015-07-23 04:05:40 UTC 
This fails in production today using mirrormanager v2.  There is supposed to be a RepositoryRedirect entry that maps repo=epel-6Server to repo=epel-6.  That may have gotten lost somewhere. Reassigning to pingou.
Comment 2 Pierre-YvesChibon 2015-07-28 12:18:33 UTC 
I have added the repository redirect that was indeed missing.

So this should be fixed now :)