-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
CI jobs are failing because podman cannot find the microshift-ci-brew image, or a supported arch within the manifests of that image. This is a regular reason for failing CI jobs.
Actual results:
* 2025-03-19T00:08:41Z 1x multiarch-tuning-operator: Failed to retrieve the supported architectures: reading manifest microshift-ci-brew in image-registry.openshift-image-registry.svc:5000/ci-op-0yg5iytv/pipeline: manifest unknown
Additional info:
See jobs:
Job periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-tests-cache-nightly-arm ended with failure. View logs
Job periodic-ci-openshift-microshift-main-e2e-aws-tests-cache-nightly ended with failure. View logs
Job periodic-ci-openshift-microshift-release-4.17-microshift-metal-cache-nightly-arm ended with failure. View logs
Job periodic-ci-openshift-microshift-release-4.18-e2e-aws-tests-cache-nightly ended with failure. View logs
- duplicates
-
USHIFT-5475 MicroShift cache CI jobs fail due to container pull errors from CI registry
-
- Closed
-