Hello,
who could help in resolving an issue with an AWS S3 mirror ? I'd like to download the epel release package using this URL: 'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm'. On my PC (proxy) I can download the file however if I run wget on EC2 instances (tried different accounts) in region eu-west-1 this ends up in 404.
[ec2-user@ip ~]$ wget 'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm' --2018-03-10 03:30:12-- http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm Resolving download.fedoraproject.org (download.fedoraproject.org)... 185.141.165.254, 8.43.85.67, 152.19.134.142, ... Connecting to download.fedoraproject.org (download.fedoraproject.org)|185.141.165.254|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... [following] --2018-03-10 03:30:12-- http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... Resolving s3-mirror-eu-west-1.fedoraproject.org (s3-mirror-eu-west-1.fedoraproject.org)... 52.218.64.194 Connecting to s3-mirror-eu-west-1.fedoraproject.org (s3-mirror-eu-west-1.fedoraproject.org)|52.218.64.194|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-03-10 03:30:12 ERROR 404: Not Found. [ec2-user@ip ~]$ The link http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... isn't also valid on my PC.
Please help/fix.
Eg. Bo.
PS: I did send this to epel-devel but noticed that there's a proper infrastructure mailing list.
On 03/10/2018 02:35 PM, Eg. Bo. wrote:
Hello,
who could help in resolving an issue with an AWS S3 mirror ? I'd like to download the epel release package using this URL:
'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm'.
On my PC (proxy) I can download the file however if I run wget on EC2
instances (tried different accounts) in region eu-west-1 this ends up in 404.
[ec2-user@ip ~]$ wget
'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm'
--2018-03-10 03:30:12--
http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Resolving download.fedoraproject.org (download.fedoraproject.org)...
185.141.165.254, 8.43.85.67, 152.19.134.142, ...
Connecting to download.fedoraproject.org
(download.fedoraproject.org)|185.141.165.254|:80... connected.
HTTP request sent, awaiting response... 302 Found Location:
http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... [following]
--2018-03-10 03:30:12--
http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7....
Resolving s3-mirror-eu-west-1.fedoraproject.org
(s3-mirror-eu-west-1.fedoraproject.org)... 52.218.64.194
Connecting to s3-mirror-eu-west-1.fedoraproject.org
(s3-mirror-eu-west-1.fedoraproject.org)|52.218.64.194|:80... connected.
HTTP request sent, awaiting response... 404 Not Found 2018-03-10 03:30:12 ERROR 404: Not Found. [ec2-user@ip ~]$
The link
http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... isn't also valid on my PC.
Please help/fix.
Yeah, this is because that url points to just a link on our master mirrors to help folks install the latest version of that package.
Where did you get the download.fedoraproject.org url for it?
You can use:
https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
which will use the master mirrors for it.
As for fixing it on AWS, I suppose we could add some logic to our mirroring to also copy up the latest epel-release version as that 'latest' link. We should make sure it auto updates though so we aren't publishing a stale package.
Ricky: can you look into adding that to the existing sync script?
kevin
Von: Kevin Fenzi
Gesendet: Montag, 12. März, 20:49
Betreff: Re: check mirror s3-mirror-eu-west-1.fedoraproject.org
An: Fedora Infrastructure
On 03/10/2018 02:35 PM, Eg. Bo. wrote: > > Hello, > > who could help in resolving an issue with an AWS S3 mirror ? > I'd like to download the epel release package using this URL: 'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm'. > On my PC (proxy) I can download the file however if I run wget on EC2 instances (tried different accounts) in region eu-west-1 this ends up in 404. > > > [ec2-user@ip ~]$ wget 'http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm' > --2018-03-10 03:30:12-- http://download.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm > Resolving download.fedoraproject.org (download.fedoraproject.org)... 185.141.165.254, 8.43.85.67, 152.19.134.142, ... > Connecting to download.fedoraproject.org (download.fedoraproject.org)|185.141.165.254|:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... [following] > --2018-03-10 03:30:12-- http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... > Resolving s3-mirror-eu-west-1.fedoraproject.org (s3-mirror-eu-west-1.fedoraproject.org)... 52.218.64.194 > Connecting to s3-mirror-eu-west-1.fedoraproject.org (s3-mirror-eu-west-1.fedoraproject.org)|52.218.64.194|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-03-10 03:30:12 ERROR 404: Not Found. > [ec2-user@ip ~]$ > > The link http://s3-mirror-eu-west-1.fedoraproject.org/pub/epel/epel-release-latest-7.... isn't also valid on my PC. > > > Please help/fix. Yeah, this is because that url points to just a link on our master mirrors to help folks install the latest version of that package. Where did you get the download.fedoraproject.org url for it? You can use: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm which will use the master mirrors for it. As for fixing it on AWS, I suppose we could add some logic to our mirroring to also copy up the latest epel-release version as that 'latest' link. We should make sure it auto updates though so we aren't publishing a stale package. Ricky: can you look into adding that to the existing sync script? kevin
I think the URL was built based on e.g. the iso download URL for fedora server (https://download.fedoraproject.org/pub/fedora/linux/releases/27/Server/x86_6... )
Should we use dl instead of download in general ?
As I mentioned "outside" of AWS region the link is valid.
Thanks
On 03/12/2018 01:53 PM, egonle@aim.com wrote:
I think the URL was built based on e.g. the iso download URL for fedora server (https://download.fedoraproject.org/pub/fedora/linux/releases/27/Server/x86_6... )
No, it was specifially setup so RHEL users had a static link to the latest epel-release package for automated installs. You wouldn't know what the version-release is unless you looked in the repo.
Should we use dl instead of download in general ?
Nope. Use dl to just install that one epel-release package if you need to enable epel on a rhel machine. Then you should use the default repo settings, which use a metalink from our mirrors.fedoraproject.org.
This is vastly better than using a static url (even download.fedoraproject.org), because:
* Metalinks not only contain a list of mirrors that have the thing you are looking for, but also checksums of all the repodata. * querying mirrors allows us to do things also like if you query from AWS, we can point you at our AWS S3 storage that has a synced copy of epel and avoid having to go outside to get things. Or if your company or school has a epel mirror we can direct all users there to the local mirror.
As I mentioned "outside" of AWS region the link is valid.
download.fedoraproject.org is a somewhat dumb redirect. It tries to redirect you to a mirror, but it isn't sure that exact content is there. In AWS it redirects you likely to our S3 storage... however, currently we are only storing rpms in there, so we need to add this link or a copy to the latest epel-release file before it will work there.
So, sorry to go on, but to summarize:
* For now, please use dl.fedoraproject.org for the epel-latest link. Hopefully we will fix things soon so download.fedoraproject.org will work too, but not sure when. * Please use the default repo metalinks for all other installs/updates/etc for epel repos.
Hope that helps,
kevin
infrastructure@lists.fedoraproject.org
-
Eg. Bo. -
egonle＠aim.com
-
Kevin Fenzi