-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.20.0
Description of problem
Current production Cincinnati occasionally confuses arch-specific shards of multi-arch images as single-arch releases:
$ while sleep 30; do PAYLOAD="$(curl -s 'https://api.openshift.com/api/upgrades_info/v1/graph?arch=amd64&channel=fast-4.15' | jq -r '.nodes[] | select(.version == "4.15.5 ").payload')"; DATE="$(date --iso=s --utc)"; printf '%s\t%s\n' "${DATE}" "${PAYLOAD}"; done 2025-05-12T18:47:03+00:00 quay.io/openshift-release-dev/ocp-release@sha256:b17bc935bfb0fb250e738733af5d3d4ea1f27065de8e2622890782780b36320c 2025-05-12T18:47:33+00:00 quay.io/openshift-release-dev/ocp-release@sha256:b17bc935bfb0fb250e738733af5d3d4ea1f27065de8e2622890782780b36320c 2025-05-12T18:48:04+00:00 quay.io/openshift-release-dev/ocp-release@sha256:c07f82ae6a59893a4a3c5f2780fbe931382a737f23fe580fb3d2a07b7fd011f5 2025-05-12T18:48:35+00:00 quay.io/openshift-release-dev/ocp-release@sha256:b17bc935bfb0fb250e738733af5d3d4ea1f27065de8e2622890782780b36320c ^C
Possibly triggered by a race or other buggy handling of Quay 502s while scraping releases.
Version-Release number of selected component
https://github.com/openshift/cincinnati/commit/ec72ca150f8537a3cfe292b8299570d86f4ffd15
How reproducible
Unclear.
Steps to Reproduce
Unclear. Possibly related to Quay 502s while scraping releases.
Actual results
Occasional Cincinanti shards claim the c07f... amd64 shard of the 4.15.5 multi-arch image in arch=amd64 results.
Expected results
Cincinnati consistently and correctly distinguishes between multi-arch images, the per-arch shards of those multi-arch images, and single-arch images.
Additional info
Possibly a gap since this commit that gave us the ability to handle multi-arch images?
- is cloned by
-
OCPBUGS-56269 Cincinnati should remove registry-cache placeholders on release scrape failures
-
- POST
-
- links to