Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: None
Affects Version/s: quay-v3.7.0
Component/s: quay
Labels:
- triaged

Blocked:
False
Ready:
False
Affects:

Compatibility/Configuration, User Experience
Backlogs:

Quay
Git Pull Request:
https://github.com/quay/quay/pull/1310
Steps to Reproduce:

Hide

Create a new cache organization and for the Remote Registry use registry.redhat.io with credentials from a RedHat registry service account.

or

Create a new cache organization and for the Remote Registry use registry.access.redhat.com and provide no credentials

Show
Create a new cache organization and for the Remote Registry use registry.redhat.io with credentials from a RedHat registry service account. or Create a new cache organization and for the Remote Registry use registry.access.redhat.com and provide no credentials

RICE Score:
0

Target Version:

quay-v3.7.0

SFDC Cases Links:
SFDC Cases Counter:

Description

Cache proxy pulls fail in Quay 3.7 when targeting the upstream registries "registry.access.redhat.com" and "registry.redhat.io".

During a pull using podman cli I receive the following error.

Error: determining manifest type MIME type for docker://.../redhat_images/ubi7:latest reading manifeset sha256:.. received unexpected status: 500 Internal Server Error.

The Quay pod logs have the following error.

ManifestAlreadyExists: duplicate key value violates unique constraint "manifest_repository_id_digest"