#12584 Fedora mirrormanager answering 503 for metalink
Closed: Invalid by arrfab. Opened by arrfab.

Related to #12571 ?

Errors during downloading metadata for repository 'baseos':
  - Status code: 503 for https://mirrors.centos.org/metalink?repo=centos-baseos-10-stream&arch=ppc64le&protocol=https,http
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.centos.org/metalink?repo=centos-baseos-10-stream&arch=ppc64le&protocol=https,http 

@adrian , @abompard ^ ?


Can you curl -v and get the actual proxy you are hitting there?

@kevin : oh .. it's not even going to outside, but it's in new RDU3 dc

mirrors.centos.org is an alias for mirrors.fedoraproject.org.
mirrors.fedoraproject.org is an alias for wildcard.fedoraproject.org.
wildcard.fedoraproject.org has address 10.16.163.75
wildcard.fedoraproject.org has address 10.16.163.74
wildcard.fedoraproject.org has address 10.16.163.77
wildcard.fedoraproject.org has address 10.16.163.76

and I guess it's not deployed yet , and that would explain the 503 - service unavailable ...

I guess we can close this one but that's a kind of problem to solve anyway for Fedora bootstrap in rdu3 too, except if you don't rely on mirrormanager at all :D

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

Ah yes, I bulk changed that in dns.

I can set those back to the external address ? or you don't need me to?

that's fine, for the time being I'm just forcing baseurl= for new deployments in rdu3 but something just to verify later (and also have a "local" mirror that mirrormanager would redirect to, hosted in rdu3)

Yes, we almost do already... but data is pushed to mirrorlists from the backend and I need to get that working before the rdu3 ones work. Soon!

Metadata