Skip to content

Conversation

kevinrizza
Copy link
Member

This reverts commit 05a24c5.

@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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 Aug 27, 2025
@openshift-ci-robot
Copy link

@kevinrizza: This pull request references Jira Issue OCPBUGS-60507, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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 reverts commit 05a24c5.

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

@kevinrizza: 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 bertinatto and tkashem August 27, 2025 19:41
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Aug 27, 2025
Copy link

openshift-ci bot commented Aug 27, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@kevinrizza kevinrizza changed the title Revert "UPSTREAM: <carry>: Revert "OCPBUGS-60507: Bump 1.33.4"" OCPBUGS-60507: Revert "UPSTREAM: <carry>: Revert "OCPBUGS-60507: Bump 1.33.4"" Aug 27, 2025
@kevinrizza kevinrizza force-pushed the unrevert-1.33.4-revert branch from e5d4eef to 589943d Compare August 27, 2025 19:56
@openshift-ci-robot
Copy link

@kevinrizza: 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.

@kevinrizza
Copy link
Member Author

/hold

looks like the metal job we need signal on isn't included in the presumbits

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 27, 2025
@bertinatto
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

@bertinatto
Copy link
Member

/retest

1 similar comment
@wangke19
Copy link

/retest

Copy link

openshift-ci bot commented Aug 28, 2025

@kevinrizza: The following test 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 589943d link true /test e2e-metal-ipi-ovn-ipv6

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.

@wangke19
Copy link

wangke19 commented Aug 28, 2025

Most failed jobs of e2e-metal-ipi-ovn-ipv6 are due to timeout 4 hours, Can we consider sharding it? Just like we have done for job e2e-aws-ovn-serial @kevinrizza @bertinatto

@openshift-merge-bot openshift-merge-bot bot merged commit 589943d into openshift:master Sep 6, 2025
27 of 29 checks passed
@openshift-ci-robot
Copy link

@kevinrizza: An error was encountered updating to the MODIFIED state for bug OCPBUGS-60507 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. Error marking step #37037402 finished: root cause: Tried to update an entity that does not exist.: request failed. Please analyze the request body for more details. Status code: 400:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This reverts commit 05a24c5.

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

4 participants