Details
-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
quay-v3.6.6
-
False
-
None
-
False
-
Quay Enterprise
-
0
Description
We have a client where Quay for a majority of images shows they are in queued status. Specifically, for {{sha256:9fbf583a47785172bd36d1e60da19b1f1736f654e741aaaab6292a517bf165fe
}}. This SHA, for some reason, appears twice in their manifest table:
=> select id from manifest where digest='sha256:9fbf583a47785172bd36d1e60da19b1f1736f654e741aaaab6292a517bf165fe'; id ------- 75328 75327 (2 rows)
However, even though the UI shows this image as being in queued state, niether of these two manifest ids are in the manifestsecuritystatus table:
SELECT * FROM manifestsecuritystatus WHERE manifest_id=75327; id | manifest_id | repository_id | index_status | error_json | last_indexed | indexer_hash | indexer_version | metadata_json ----+-------------+---------------+--------------+------------+--------------+--------------+-----------------+--------------- (0 rows) SELECT * FROM manifestsecuritystatus WHERE manifest_id=75328; id | manifest_id | repository_id | index_status | error_json | last_indexed | indexer_hash | indexer_version | metadata_json ----+-------------+---------------+--------------+------------+--------------+--------------+-----------------+--------------- (0 rows)
This is an upgrade from Quay 3.3.0 to 3.6.6. I have requested the latest config.yaml files for both Quay and Clair and will add them to the case as soon as I get them.
Can you please check why Quay is locked and cannot scan images?
