-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
quay-v3.7.0
When an image is pulled via proxying, storage replication does not kick in. The storage replication job is issued on manifest push and is done manually when manifest is written. This does not happen when an image is proxied from an upstream registry, no replication jobs are created.
Example of storage replication job that is created when a manifest is normally pushed to the registry:
gunicorn-registry stdout | 2022-06-08 10:58:34,904 [372] [DEBUG] [peewee] ('INSERT INTO "queueitem" ("queue_name", "body", "available_after", "available", "retries_remaining", "state_id") VALUES (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s), (%s, %s, %s, %s, %s, %s) RETURNING "queueitem"."id"', ['imagestoragereplication/7fc712ac-0227-4975-919e-b7d82f620019/', '{"namespace_user_id": 7, "storage_id": "7fc712ac-0227-4975-919e-b7d82f620019"}', datetime.datetime(2022, 6, 8, 10, 58, 34, 904167), True, 5, '3d7a2767-e102-4612-822b-83d1cc6499a1', 'imagestoragereplication/985a40e1-a185-4c15-a6ac-b413d50f7b73/', ...
