-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
Quay Enterprise
Description of problem:
Meet 500 error in UI when switch to an image repo contains manifest list
Version-Release number of selected component (if applicable):
quay.io/projectquay/quay:50ba6130
How reproducible:
Always
Steps to Reproduce:
1. Push a manifest list to Quay
$ sudo ./docker manifest push demo-quayecosystem-quay-quay-enterprise.apps.quay-283.qe.devcluster.openshift.com/quay/multi-arch:latest Pushed ref demo-quayecosystem-quay-quay-enterprise.apps.quay-283.qe.devcluster.openshift.com/quay/multi-arch@sha256:915f390a8912e16d4beb8689720a17348f3f6d1a7b659697df850ab625ea29d5 with digest: sha256:915f390a8912e16d4beb8689720a17348f3f6d1a7b659697df850ab625ea29d5 Pushed ref demo-quayecosystem-quay-quay-enterprise.apps.quay-283.qe.devcluster.openshift.com/quay/multi-arch@sha256:adeafb67bdeab6f8ab07a46bc7b789d9ae508aac3b0933fb165e3ceb1f36e3e2 with digest: sha256:adeafb67bdeab6f8ab07a46bc7b789d9ae508aac3b0933fb165e3ceb1f36e3e2 Pushed ref demo-quayecosystem-quay-quay-enterprise.apps.quay-283.qe.devcluster.openshift.com/quay/multi-arch@sha256:f7d5e9a7fa573052bbce9ad2d59b1c63b848f091a246a8c1e54ccc8178e1b794 with digest: sha256:f7d5e9a7fa573052bbce9ad2d59b1c63b848f091a246a8c1e54ccc8178e1b794 sha256:3c5d623c2c858283670bce4c0e24a2ff86a00158cfd1adf09caf3ffe052a80dc
2. Access the image repo in UI
Actual results:
Turn to 500 in UI
Expected results:
Show repo details in UI
Additional info:
It only occurs in local storage, cannot reproduce with GCS and AWS S3
