openshift
[release-4.16] OCPBUGS-65709: Add imagestream update dryrun test
This is an automated cherry-pick of #30479
/assign wangke19
Pipeline controller notification
This repository is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.
For optional jobs, comment /test ? to see a list of all defined jobs. Review these jobs and use /test <job> to manually trigger optional jobs most likely to be impacted by the proposed changes.
@openshift-cherrypick-robot: Jira Issue OCPBUGS-65492 has been cloned as Jira Issue OCPBUGS-65709. Will retitle bug to link to clone. /retitle [release-4.16] OCPBUGS-65709: Add imagestream update dryrun test
In response to this:
This is an automated cherry-pick of #30479
/assign wangke19
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-65709, which is invalid:
- expected dependent Jira Issue OCPBUGS-65492 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #30479
/assign wangke19
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: This pull request references Jira Issue OCPBUGS-65709, which is valid. The bug has been moved to the POST state.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.16.z) matches configured target version for branch (4.16.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-65492 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-65492 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
- bug has dependents
Requesting review from QA contact: /cc @gangwgr
In response to this:
/jira refresh
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.
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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: flavianmissi, openshift-cherrypick-robot Once this PR has been reviewed and has the lgtm label, please assign rphillips for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
- ~~test/extended/images/OWNERS~~ [flavianmissi]
- test/extended/util/annotate/generated/OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment