#9230 Container registry has no content
Closed: Fixed 3 years ago by mizdebsk. Opened 3 years ago by mizdebsk.

Fedora container registry at https://registry.fedoraproject.org/ seems to have no content.
podman pull fails too:

# podman pull registry.fedoraproject.org/fedora:32
Trying to pull registry.fedoraproject.org/fedora:32...
  manifest unknown: manifest unknown
Error: unable to pull registry.fedoraproject.org/fedora:32: Error initializing source docker://registry.fedoraproject.org/fedora:32: Error reading manifest 32 in registry.fedoraproject.org/fedora: manifest unknown: manifest unknown
# podman pull registry.fedoraproject.org/fedora:latest
Trying to pull registry.fedoraproject.org/fedora:latest...
  manifest unknown: manifest unknown
Error: unable to pull registry.fedoraproject.org/fedora:latest: Error determining manifest MIME type for docker://registry.fedoraproject.org/fedora:latest: Error reading manifest sha256:34839f71041671f22e505c640008f3089c9ba291e2601651d38d1bac606d221b in registry.fedoraproject.org/fedora: manifest unknown: manifest unknown

There was a failed mount on oci-registry02:

Aug 12 22:58:13 oci-registry02.iad2.fedoraproject.org systemd[1]: Mounting /srv/registry...
Aug 12 22:58:19 oci-registry02.iad2.fedoraproject.org mount[732]: mount.nfs: Failed to resolve server ntap-iad2-c02-fedora01-nfs01a: Name or service not known
Aug 12 22:58:19 oci-registry02.iad2.fedoraproject.org systemd[1]: srv-registry.mount: Mount process exited, code=exited, status=32/n/a
Aug 12 22:58:19 oci-registry02.iad2.fedoraproject.org systemd[1]: srv-registry.mount: Failed with result 'exit-code'.
Aug 12 22:58:19 oci-registry02.iad2.fedoraproject.org systemd[1]: Failed to mount /srv/registry.

I fixed it with systemctl restart srv-registry.mount.

Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk

3 years ago

The issue seems to be fixed, but it would be good to add monitoring for srv-registry.mount unit -- the mount was down for 11 hours and we didn't get any alert about the issue.

Metadata Update from @mizdebsk:
- Issue close_status updated to: Fixed
- Issue priority set to: None (was: Needs Review)
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata