-
Notifications
You must be signed in to change notification settings - Fork 4.7k
OCPBUGS-35855: Add dry-run server test for imagestreamtag #29834
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
base: main
Are you sure you want to change the base?
Conversation
@ardaguclu: This pull request references Jira Issue OCPBUGS-35855, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In 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. |
This test should fail without openshift/openshift-apiserver#511 |
Without the patch in openshift-apiserver, https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29834/pull-ci-openshift-origin-main-e2e-aws-ovn-image-registry/1925162064351858688 failed as expected. |
/lgtm |
/retest |
1 similar comment
/retest |
There is a failure in disconnected environment https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29834/pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6/1927574739656642560. It can not access quay.io. EDITED: Fixed by using internal tag instead of external access. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, posted a few questions
/lgtm |
How just creating an imagestreamtag is so impossible and difficult. |
/hold cancel |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, dgoodwin, flavianmissi, p0lyn0mial The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required |
1 similar comment
/retest-required |
2 similar comments
/retest-required |
/retest-required |
@ardaguclu: The following tests failed, say
Full PR test history. Your PR dashboard. 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Job Failure Risk Analysis for sha: 2bc880f
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 2bc880f
New tests seen in this PR at sha: 2bc880f
|
This PR adds a simple test to ensure that dry-run option is taken account by image api server.