#10177 epel-release-latest-8.noarch.rpm 403 forbidden
Closed: Fixed 2 years ago by carlwgeorge. Opened 2 years ago by carlwgeorge.

  • Describe the issue
    https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm is returning a 403 forbidden error.

  • When do you need this? (YYYY/MM/DD)
    ASAP

  • When is this no longer needed or useful? (YYYY/MM/DD)
    2029-05-31 (RHEL8 EOL)

  • If we cannot complete your request, what is the impact?
    This is the documented URL for installing epel-release, so it's broken for users following instructions and automation that has been set up to use that URL.


I fixed the existing link, but the script is not right as it should have done so.

It was pointing to the old release.

lrwxrwxrwx. 1 ftpsync ftpsync 63 Jun 24 17:11 epel-release-latest-8.noarch.rpm -> 8/Everything/x86_64/Packages/e/epel-release-8-10.el8.noarch.rpm

% ls -la 8/Everything/x86_64/Packages/e/epel-release-8-11.el8.noarch.rpm
-rw-r--r--. 1 263 263 23452 Jun 8 00:46 8/Everything/x86_64/Packages/e/epel-release-8-11.el8.noarch.rpm

@mohanboddu can you take a look?

I am gonna take a look at this.

Metadata Update from @mohanboddu:
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

I'm currently experiencing this issue. I can't see the file/link (https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm) in that directory at all.

Metadata Update from @churchyard:
- Issue status updated to: Open (was: Closed)

2 years ago

I have the same problem as @qc :

# curl https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access this resource.</p>
</body></html>

so the symlinks were pointing to the old build. I have fixed it manually for now.

This has been working great for a little while now.

Metadata Update from @carlwgeorge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog