OCPBUGS-35462: shiftstack: add CPO rebase for 4.16 and update the master one #53206
Conversation
…ter one * master: bump CPO to upstream release-1.30, this is necessary to get the k8s 1.30 + deps, like we have in OCP 4.17 already. * 4.16: create the rebase and use upstream release-1.29 which is the release of k8s in OCP 4.16.
openshift-ci-robot
added
the
jira/valid-reference
|
@EmilienM: This pull request references Jira Issue OCPBUGS-35462, which is invalid:
Comment 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. |
openshift-ci-robot
added
the
jira/invalid-bug
|
/jira refresh |
|
@EmilienM: This pull request references Jira Issue OCPBUGS-35462, which is invalid:
Comment 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. |
|
/jira refresh |
|
@EmilienM: This pull request references Jira Issue OCPBUGS-35462, which is invalid:
Comment 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. |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse ack |
|
@EmilienM: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@EmilienM: This pull request references Jira Issue OCPBUGS-35462, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. 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. |
|
/cc mandre |
openshift-ci
bot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM, pierreprinetti 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 |
|
@EmilienM: 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. |
|
@EmilienM: Jira Issue OCPBUGS-35462: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-35462 has been moved to the MODIFIED state. 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. |
…ter one (openshift#53206) * master: bump CPO to upstream release-1.30, this is necessary to get the k8s 1.30 + deps, like we have in OCP 4.17 already. * 4.16: create the rebase and use upstream release-1.29 which is the release of k8s in OCP 4.16.
the k8s 1.30 + deps, like we have in OCP 4.17 already.
release of k8s in OCP 4.16.