Major Description of problem:
Sometimes when pulling images from quay oc-mirror receives 502 Bad Gateway back
Version-Release number of selected component (if applicable):
How reproducible:
It is not always reproducible, it happens intermittently
Steps to Reproduce:
1.
2.
3.
Actual results:
2025/04/03 15:50:20 [ERROR] : [Worker] error mirroring image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:242b3d66438c42745f4ef318bdeaf3d793426f12962a42ea83e18d06c08aaf09 error: initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:242b3d66438c42745f4ef318bdeaf3d793426f12962a42ea83e18d06c08aaf09: reading manifest sha256:242b3d66438c42745f4ef318bdeaf3d793426f12962a42ea83e18d06c08aaf09 in quay.io/openshift-release-dev/ocp-v4.0-art-dev: received unexpected HTTP status: 502 Bad Gateway
Expected results:
No 502 Bad Gateway
Additional info:
There is one fix in the containers/common that could also be applied in oc-mirror: https://github.com/containers/common/pull/2378
- duplicates
-
OCPBUGS-54587 [v2] oc-mirror v2 retry-times parameter does not work when mirroring release images
-
- Verified
-