Describe the issue When attempting to install epel release on RedHat 7, receiving forbidden 403 to https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
When do you need this? (YYYY/MM/DD) ASAP as it is impacting production, server deployments.
When is this no longer needed or useful? (YYYY/MM/DD) Ongoing access is required.
If we cannot complete your request, what is the impact? Production build, and deployment pipeline.
Strange same goes for epel9-release. Epel8 works.
I checked the permissions and they are the same on all 3 of them.
Agreed, we're getting this only on EPEL7. Others (REHL8) are working correctly
The current failure rate is about one in two requests, based on our current testing.
This is already reported/tracked at https://pagure.io/fedora-infrastructure/issue/11564
Please watch that ticket for more information.
The problem is the script that is supposed to update that link when epel-release updates is updating it everytime it runs and if httpd tries to get it right at that point it's replacing it it sometimes caches a 401.
Metadata Update from @kevin: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)