-
Notifications
You must be signed in to change notification settings - Fork 4.8k
OCPBUGS-63040: Add imagestream update dryrun test #30357
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
OCPBUGS-63040: Add imagestream update dryrun test #30357
Conversation
fd65143 to
738b811
Compare
|
/cc @ardaguclu |
|
/verified by e2e ci/prow/e2e-vsphere-ovn |
|
@wangke19: This PR has been marked as verified by 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. |
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 738b811
|
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.
This bug https://issues.redhat.com/browse/OCPBUGS-62875 is about 4.15. But I'm not sure that we backported the fix in this branch (I couldn't see the fix in here https://github.com/openshift/openshift-apiserver/commits/release-4.15/)?. So in my opinion, it is expected to not working on 4.15.
Additionally, creation and update are almost equal. If one of them works, it is likely that other one should work too.
738b811 to
d5f9f96
Compare
The bug https://issues.redhat.com/browse/OCPBUGS-62875 was found on 4.21, not 4.15, it was not fixed in openshift/openshift-apiserver#511, it should not be fixed on all versions。 |
6c359a4 to
98dd33d
Compare
|
/retest |
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 98dd33d
|
test/extended/images/dryrun.go
Outdated
| }() | ||
|
|
||
| g.By("verifying the imagestream was actually created") | ||
| _, err = oc.Run("get").Args("imagestream", "dryrun-test", "-o", "jsonpath={.metadata.name}").Output() |
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.
I think this needs to be wrapped with PollUntilContextTimeout. Otherwise, it is possible that imagestream hasn't been created yet which causes flaky behavior.
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.
Sure, Updated.
98dd33d to
6aa3223
Compare
|
Thanks |
|
/retest |
|
/test verify |
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 6aa3223
|
|
/test verify |
|
/cherry-pick release-4.20 |
|
@wangke19: once the present PR merges, I will cherry-pick it on top of 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 kubernetes-sigs/prow repository. |
|
@wangke19: This pull request references Jira Issue OCPBUGS-63040, which is valid. The bug has been moved to the POST state. 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. |
|
/test e2e-metal-ipi-ovn-ipv6 |
|
/jira refresh |
|
@wangke19: This pull request references Jira Issue OCPBUGS-63040, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
/cherry-pick release-4.19 |
|
@wangke19: once the present PR merges, I will cherry-pick it on top of 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 kubernetes-sigs/prow repository. |
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 5dc8051
|
|
/test e2e-aws-ovn-serial-2of2 |
|
@wangke19: all tests passed! 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. |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 5dc8051
New tests seen in this PR at sha: 5dc8051
|
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 5dc8051
|
1 similar comment
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 5dc8051
|
|
@wangke19: Jira Issue Verification Checks: Jira Issue OCPBUGS-63040 Jira Issue OCPBUGS-63040 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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. |
|
@wangke19: new pull request created: #30387 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 kubernetes-sigs/prow repository. |
|
@wangke19: #30357 failed to apply on top of branch "release-4.19": 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 kubernetes-sigs/prow repository. |
|
Fix included in accepted release 4.21.0-0.nightly-2025-10-17-012128 |
What does this do?
But newly discovered that, creation of imagestream with
--dry-run=serverdoesn't work as expected, filed one bug https://issues.redhat.com/browse/OCPBUGS-62875 for this.so only add update of imagestream with
--dry-run=servertest.sippy, use an existing internal image stream tagopenshift/cli:latestinstead.