We are trying to update all of our Fedora 29 instances with the latest kernel package (kernel-5.0.16-200.fc29) that fixes a bunch of security issues. I opened up an AWS support ticket and they said that this Fedora Project runs this (d2lzkl7pfhq30w.cloudfront.net) mirror. It is the first mirror that gets chosen by running dnf update kernel-core across all of my AWS accounts and it isn't updating with the latest packages.
dnf update kernel-core
<url protocol="https" type="https" location="US" preference="100">https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/updates/29/Everything/x86_64/repodata/repomd.xml </url>
This URL doesn't have kernel-core-5.0.16-200.fc29.x86_64.rpm:
And another mirror does:
I have 200+ Fedora 29 VMs that are not updating to this latest kernel as a result.
Updates into Amazon have been extremely slow with updates taking 48 hours to sync out. We are trying to determine what is bottling our bandwidth into Amazon, and trying to sync out these important updates as quickly as possible.
Metadata Update from @smooge:
- Issue assigned to codeblock
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: downloads
Thanks @smooge. Not to scope creep this too much, but if work is being put into making this AWS mirror better, maybe some custom DNS could be setup on this cloudfront URL? That way it is easier for us end users to know that the Fedora Project is running this mirror. I had to contact AWS support and ask them to track down who owned this URL on cloudfront.
Setting a URL off of a Fedora domain name should be pretty straightforward: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html
That specific link is fixed now, and I'm working on some things to improve sync time in general.
Metadata Update from @codeblock:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
to comment on this ticket.