#9282 Pulling f30 image on registry.fedoraproject.org returns 503s
Closed: Fixed 4 years ago by mohanboddu. Opened 4 years ago by jlebon.

Our CI is hitting this a lot:

Trying to pull registry.fedoraproject.org/fedora:30...
received unexpected HTTP status: 503 Service Temporarily Unavailable
Error: unable to pull registry.fedoraproject.org/fedora:30: unable to pull image: Error initializing source docker://registry.fedoraproject.org/fedora:30: Error reading manifest 30 in registry.fedoraproject.org/fedora: received unexpected HTTP status: 503 Service Temporarily Unavailable

I can also reproduce this locally:

skopeo inspect docker://registry.fedoraproject.org/fedora:30
FATA[0003] Error determining repository tags: error pinging docker registry registry.fedoraproject.org: invalid status code from registry 503 (Service Unavailable)

@mohanboddu mentioned there were known issues and that this will be worked on soon.

Interestingly, f31 doesn't hit this.


Nope, f31 also hits 503s occasionally.

There was new containers published this week I believe (another rel-eng ticket) I wonder if there's a caching/CDN issue somewhere

This may somehow be specific to CentOS CI, or at least more frequent there. I know there have always been weird networking issues between Fedora/CentOS infra and RHT infra.

I've been seeing 503s a lot when pulling on my home network and from the RHT office in raleigh. It's been causing a lot of intermittent problems for me.

Can you all try again now and let me know here if you see any more 503s?

Also, quay.io is fixed now. You can use them as well.

@kevin made some changes and seems to be working for me. I am not sure how random it is, so, I am gonna close this ticket for now and if you find any issues again, please re-open the ticket.

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

4 years ago

Login to comment on this ticket.

Metadata