Skip to content

OCPBUGS-77475: Bump v1.34.5#2601

Open
jubittajohn wants to merge 6 commits intoopenshift:release-4.21from
jubittajohn:rebase-v1.34.5
Open

OCPBUGS-77475: Bump v1.34.5#2601
jubittajohn wants to merge 6 commits intoopenshift:release-4.21from
jubittajohn:rebase-v1.34.5

Conversation

@jubittajohn
Copy link

Bump release-4.21 to v1.34.5 from v1.34.4

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 27, 2026
@openshift-ci-robot
Copy link

@jubittajohn: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from deads2k and jerpeter1 February 27, 2026 16:29
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Feb 27, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jubittajohn
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jubittajohn jubittajohn changed the title Rebase v1.34.5 OCPBUGS-77475: Bump v1.34.5 Feb 27, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 27, 2026
@openshift-ci-robot
Copy link

@jubittajohn: This pull request references Jira Issue OCPBUGS-77475, 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.
  • expected Jira Issue OCPBUGS-77475 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

In response to this:

Bump release-4.21 to v1.34.5 from v1.34.4

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
Copy link

openshift-ci bot commented Feb 27, 2026

@jubittajohn: 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-metal-ipi-ovn-ipv6 dc33209 link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-fips dc33209 link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-techpreview-serial-1of2 dc33209 link false /test e2e-aws-ovn-techpreview-serial-1of2
ci/prow/unit dc33209 link true /test unit
ci/prow/e2e-aws-ovn-techpreview dc33209 link false /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-techpreview-serial-2of2 dc33209 link false /test e2e-aws-ovn-techpreview-serial-2of2

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants