Skip to content

Add unmapped upstream image references for CSO bundle - #188

Merged
bcaton85 merged 1 commit into
quay:redhat-5.0from
redhat-chai-bot:fix-cso-image-references
Oct 9, 2026
Merged

bcaton85 merged 1 commit into
quay:redhat-5.0from
redhat-chai-bot:fix-cso-image-references

Conversation

@redhat-chai-bot

Copy link
Copy Markdown

The CSO bundle's image-references file only maps registry.redhat.io/quay/quay-container-security-rhel9-operator, but the upstream CSV uses two additional pullspec variants:

  • quay.io/quay/container-security-operator (containerImage annotation)
  • quay.io/projectquay/container-security-operator (deployment image)

Without these mappings, doozer's update-csv cannot replace the upstream pullspecs with the ART-built image during the FBC build. This causes olm.allowed_registries_related EC policy violations in the stage release pipeline (verify-conforma step).

This PR adds both upstream pullspec variants as additional entries in bundle/image-references, all pointing to the same ART image name (quay-container-security-rhel9-operator). This allows doozer to properly replace all upstream references with the delivery registry pullspec.

Violations fixed

  1. olm.allowed_registries_related — quay.io/quay/container-security-operator (upstream, unmapped)
  2. olm.allowed_registries_related — quay.io/redhat-user-workloads/ocp-art-tenant/art-images (Konflux build pullspec, not replaced because the upstream reference wasn't mapped)

AI-generated. Review for accuracy.

@bcaton85 requested from Slack

@bcaton85 bcaton85 reopened this Oct 9, 2026
@bcaton85
bcaton85 merged commit 65b82d2 into quay:redhat-5.0 Oct 9, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants