-
Notifications
You must be signed in to change notification settings - Fork 152
[release-4.20] OCPBUGS-74132: test/e2e - do not use ambiguous container image short names #345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-4.20] OCPBUGS-74132: test/e2e - do not use ambiguous container image short names #345
Conversation
The e2e tests fail on OCP 4.22 because RHEL 9 enforces fully qualified
container image names ("short name mode"). The backend image
`nginxdemos/nginx-hello:plain-text` is rejected with ImageInspectError
since Podman cannot determine which registry to pull from.
Replace it with `registry.k8s.io/e2e-test-images/agnhost:2.53`, a fully
qualified image that is the standard e2e test image across OpenShift
repositories. The agnhost image requires running the `netexec` subcommand
to start its HTTP server.
Update test expectations from "URI: /" to "NOW:" to match agnhost's
response format.
Assisted-By: Claude Code
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-73848 has been cloned as Jira Issue OCPBUGS-74132. Will retitle bug to link to clone. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-74132, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/jira refresh |
|
@ibihim: This pull request references Jira Issue OCPBUGS-74132, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@ibihim: This pull request references Jira Issue OCPBUGS-74132, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@ibihim: This pull request references Jira Issue OCPBUGS-74132, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@ibihim: This pull request references Jira Issue OCPBUGS-74132, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/verified by the PR's "ci/prow/e2e-component - Job succeeded" CI job TestOAuthProxyE2E passed results |
|
@xingxingxia: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@xingxingxia: This pull request references Jira Issue OCPBUGS-74132, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/approve |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ibihim, liouk, openshift-cherrypick-robot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
baba7b5
into
openshift:release-4.20
|
@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-74132 Jira Issue OCPBUGS-74132 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in accepted release 4.20.0-0.nightly-2026-01-24-155111 |
This is an automated cherry-pick of #343
/assign ibihim