Bug 1593033

Summary: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates- released-f28&arch=aarch64
Product: [Fedora] Fedora Reporter: Ed Gasiorowski <egasiorowski>
Component: mirrormanagerAssignee: Adrian Reber <adrian>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 28CC: adrian, ctatman, jonstanley, kdreyer, pingou, puiterwijk
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-15 17:46:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Beaker logs none

Description Ed Gasiorowski 2018-06-19 22:30:20 UTC 
Created attachment 1453044 [details]
Beaker logs

Description of problem: Beaker provision Fedora 28, Failed to download the following packages: Status code: 503 for
   https://mirrors.fedoraproject.org/metalink?repo=updates-
   released-f28&arch=aarch64


Version-Release number of selected component (if applicable):


How reproducible: Run INventory job in BEaker 


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Adrian Reber 2018-06-20 12:03:24 UTC 
Closing as a duplicate.

Once every hour (around 15 minutes after the full hour) the mirrorlist servers are reloaded. In the logs you attached it is indeed 15 minutes after the hour so this fits pretty good. During that time there is a small chance that the mirrorlist server will answer with a 503.

One workaround implemented in DNF (see https://bugzilla.redhat.com/show_bug.cgi?id=1591225) is to retry a few times if it failed. So DNF will have a workaround soon.

*** This bug has been marked as a duplicate of bug 1591225 ***
Comment 2 Ken Dreyer (Red Hat) 2018-11-15 15:05:29 UTC 
Adrian, is there any way to resolve this (with mod_cache or something similar) so that there is no point at which we answer with a 503?

We hit this quite often with EPEL 7 when continuously testing Ceph.
Comment 3 Adrian Reber 2018-11-15 17:46:23 UTC 
I cannot really answer that as that is more fedora infrastructure related on how it is proxied to the outside. There are many layers involved in the proxying but I am not familiar enough to make useful comments about this.

If there are problems they should be rather reported at the fedora-infrastructure bug tracker than here. This is more about the package than its usage in Fedora.

*** This bug has been marked as a duplicate of bug 1591225 ***