Bug 1909581 - 403 fetching EPEL 8 release RPM
Summary: 403 fetching EPEL 8 release RPM
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: epel-release
Version: epel8
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michael Stahnke
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-21 03:49 UTC by Peter Portante
Modified: 2020-12-21 04:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-21 04:43:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Portante 2020-12-21 03:49:19 UTC 
403 received fetching https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm using "dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm".
Comment 1 Peter Portante 2020-12-21 03:50:43 UTC 
# dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
[sudo] password for pportant:
Last metadata expiration check: 3:24:20 ago on Sun 20 Dec 2020 07:25:35 PM EST.
[MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
[MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
[MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
[MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
[FAILED] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
Comment 2 Kevin Fenzi 2020-12-21 04:43:10 UTC 
This actually has nothing to do with the epel-release rpm package itself. This is a courtsey link setup in fedora infrastructure. 

I've filed a releng ticket to look into it: https://pagure.io/releng/issue/9915

This is very likely fallout from adding some handling to the sync script to automatically update the link when the epel-release package is updated. 

I've manually fixed the link for now... we will sort out what went wrong on the update script.
Note You need to log in before you can comment on or make changes to this bug.