Bug 1500466

Summary:	EPEL 404 Errors
Product:	[Fedora] Fedora EPEL	Reporter:	dD.d <it+rhelbugzilla>
Component:	epel-release	Assignee:	Michael Stahnke <mastahnke>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	dennis, extras-orphan, kevin, mastahnke
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-10 17:39:23 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 dD.d 2017-10-10 16:03:20 UTC

Description of problem:

Copied from https://bugs.centos.org/view.php?id=12597

I am not the original poster of the bug above, but I am experiencing the same issue. I did not see the bug opened here, so I'm posting it now.

Running yum install epel-release is successful. Installation of epel-release breaks yum. On investigation, it appears that the requested FQDN on client side for two of the destination files does not match what is in the repository.

http://ucmirror.canterbury.ac.nz/linux/fedora/fedora-epel/7/x86_64/repodata/273d91af54359e55a0d6f254466eec1297a5c41af7574a3ba5937e20cbefbc5c-primary.sqlite.xz: [Errno 14] HTTP Error 404 - Not Found

epel/x86_64/updateinfo FAILED
http://ucmirror.canterbury.ac.nz/linux/fedora/fedora-epel/7/x86_64/repodata/30835c6dcc431734bfe90516122028230508df49312aa0f29456016c40a2226a-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found

Yum attempts other mirrors which are accessible through curl, HTTP Error 404 - Not found also returned from upstream repositories for all other attempts.

Browsing directly to the repo (http://ucmirror.canterbury.ac.nz/linux/fedora/fedora-epel/7/x86_64/repodata/repomd.xml) and reviewing both primary.sqllite.yz and updateinfo indicates different file names exist upstream to what the client is expecting to access.

On review of repomd.xml file on the upstream repo server, the file a href location appears to illustrate the same path in which the client is trying to access but the actual directory doesn't contain this file.

How reproducible:

yum remove epel-release
rm -rf /var/lib/rpm/__db*
yum clean all
yum update (without epel-release) successful
yum install epel-release
yum update

Additional info:

Unsure what the issue is here but it appears to be upstream across a wide variety of mirrors.

yum install epel-release installs noarch 7-6 yet another server that is completely up to date and working perfectly is using epel-release 7-8. Forcefully remove epel-release and installing epel-release 7-8 using rpm -i epel-release-7-8.noarch.rpm and manually restoring the key in /etc/pki/rpm-gpg/ does not help. Same issue.

Curious to know whether this issue is wider spread or if this is a local server issue. Out of ideas on what else to check.

Comment 1 dD.d 2017-10-10 17:11:26 UTC

After further testing, the issue is caused by:

repo_gpgcheck=1

in yum.conf

Is this expected behavior?

Comment 2 dD.d 2017-10-10 17:39:23 UTC

RHEL Products do not currently support repo_gpgcheck

https://access.redhat.com/solutions/2850911

Comment 3 Kevin Fenzi 2017-10-10 17:48:57 UTC

Additionally to note here: epel-release does not ship with any repos that have this enabled. Check and make sure it wasn't added manually or by a CM locally.

Comment 4 dD.d 2017-10-10 18:07:28 UTC

I added it manually. I just never ran into this issue before.

I hope epel repo gets gpgcheck functionality in the future...