#6933 registry.stg.fedoraproject.org returns 503
Closed: Fixed Opened by cverna.

  • Describe what you need us to do:
    Trying to pull images from registry.stg.fedoraproject.org fails with image not found. When trying to check the registry catalog it returns a 503.
docker pull registry.stg.fedoraproject.org/fedora:latest
Trying to pull repository registry.stg.fedoraproject.org/fedora ... 
Pulling repository registry.stg.fedoraproject.org/fedora
Error: image fedora:latest not found
  • When do you need this? (YYYY/MM/DD)
    Whenever possible, it is blocking building containers on OSBS stg.

docker-registry02.stg is on virthost12, which is currently broken and waiting for replacement. The plan is to have all guests reinstalled on new hardware once it's set up, but if you can't wait we can reinstall docker-registry02.stg on another virthost. How urgent is this?

Metadata Update from @mizdebsk:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

Do we have an ETA for the new hardware installation ? It is not critical but I would like to be able to continue working on OSBS staging before the end of next week.

Metadata Update from @cverna:
- Issue priority set to: Needs Review (was: Waiting on Reporter)

There is no ETA. We are waiting in queue for onhands in PHX2.

Metadata Update from @kevin:
- Issue priority set to: Waiting on External (was: Needs Review)

Metadata Update from @codeblock:
- Issue assigned to codeblock

Metadata Update from @codeblock:
- Issue assigned to codeblock

Metadata Update from @codeblock:
- Issue assigned to codeblock

This is done and back online, but the gluster volume gave me trouble syncing between the two nodes. I think it's good now, but you might want to make sure everything is in place and okay before relying on it.

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

Metadata