Skip to content

fix(e2e): use tag-based image references instead of nested repo paths#2208

Open
avinal wants to merge 1 commit into
shipwright-io:mainfrom
avinal:avinal/e2e-fix
Open

fix(e2e): use tag-based image references instead of nested repo paths#2208
avinal wants to merge 1 commit into
shipwright-io:mainfrom
avinal:avinal/e2e-fix

Conversation

@avinal

@avinal avinal commented May 21, 2026

Copy link
Copy Markdown
Member

Changes

Several e2e tests construct output image references as
TEST_IMAGE_REPO/:latest, creating nested repository paths. This only
works with registries that support arbitrary nested repos (e.g. ttl.sh).
Registries like Quay.io and the OpenShift internal registry expect
/: and reject nested paths with 401/400 errors.

Change to TEST_IMAGE_REPO: to match the pattern used by
amendOutputImage in common_test.go, making TEST_IMAGE_REPO work consistently
regardless of the registry backend

Related Issue

Fixes #

Type of PR

/kind bug

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Kind label has been set
  • Release notes block has been filled in, or marked NONE

Several e2e tests construct output image references as
TEST_IMAGE_REPO/<testID>:latest, creating nested repository paths. This only
works with registries that support arbitrary nested repos (e.g. ttl.sh).
Registries like Quay.io and the OpenShift internal registry expect
<namespace>/<repo>:<tag> and reject nested paths with 401/400 errors.

Change to TEST_IMAGE_REPO:<testID> to match the pattern used by
amendOutputImage in common_test.go, making TEST_IMAGE_REPO work consistently
regardless of the registry backend

Signed-off-by: Avinal Kumar <avinal@redhat.com>
@openshift-ci openshift-ci Bot added release-note-none Label for when a PR does not need a release note kind/bug Categorizes issue or PR as related to a bug. labels May 21, 2026
@pull-request-size pull-request-size Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 21, 2026
@openshift-ci openshift-ci Bot requested review from qu1queee and rxinui May 21, 2026 07:05
@openshift-ci

openshift-ci Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign apoorvajagtap for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bug Categorizes issue or PR as related to a bug. release-note-none Label for when a PR does not need a release note size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants