origin
origin copied to clipboard
openshift
[release-4.17] OCPBUGS-43569: feat: update to use pullspec image
This is an automated cherry-pick of #29205
/assign eggfoobar
/retitle [release-4.17] OCPBUGS-43569: feat: update to use pullspec image
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-43569, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
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 #29205
/assign eggfoobar
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.
@eggfoobar: This pull request references Jira Issue OCPBUGS-43569, 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.17.z) matches configured target version for branch (4.17.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-43568 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-43568 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
- bug has dependents
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.
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.
/unhold
Looking at sippy we now see success for 4.18 but failures for 4.17. We should be good to backport this
@xueqzhan: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]
In response to this:
/label backport-risk-assessed
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.
![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 APPROVED
This pull-request has been approved by: deads2k, openshift-cherrypick-robot, xueqzhan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [deads2k,xueqzhan]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@xueqzhan: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]
In response to this:
/label cherry-pick-approved
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.
/retest-required
Remaining retests: 0 against base HEAD aa11468238bef5704aaf7eaadf0f9fbf8b777b0e and 2 for PR HEAD c17f1e9b2961193975118b737cf3c4e8b56b1700 in total
@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-ovn-single-node-upgrade | c17f1e9b2961193975118b737cf3c4e8b56b1700 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-openstack-ovn | c17f1e9b2961193975118b737cf3c4e8b56b1700 | link | false | /test e2e-openstack-ovn |
| ci/prow/e2e-azure-ovn-upgrade | c17f1e9b2961193975118b737cf3c4e8b56b1700 | link | false | /test e2e-azure-ovn-upgrade |
| ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 | c17f1e9b2961193975118b737cf3c4e8b56b1700 | link | false | /test e2e-vsphere-ovn-dualstack-primaryv6 |
| ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout | c17f1e9b2961193975118b737cf3c4e8b56b1700 | link | false | /test e2e-metal-ipi-ovn-kube-apiserver-rollout |
| ci/prow/e2e-aws-ovn-single-node | c17f1e9b2961193975118b737cf3c4e8b56b1700 | link | false | /test e2e-aws-ovn-single-node |
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.
/retest-required
Remaining retests: 0 against base HEAD aa11468238bef5704aaf7eaadf0f9fbf8b777b0e and 2 for PR HEAD c17f1e9b2961193975118b737cf3c4e8b56b1700 in total
@openshift-cherrypick-robot: Jira Issue OCPBUGS-43569: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-43569 has been moved to the MODIFIED state.
In response to this:
This is an automated cherry-pick of #29205
/assign eggfoobar
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.
[ART PR BUILD NOTIFIER]
Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202410220737.p0.g13862c1.assembly.stream.el9. All builds following this will include this PR.
