-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Revert "k8s 1.25.0" #27489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "k8s 1.25.0" #27489
Conversation
|
/label approved |
|
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-agnostic-ovn-cmd, ci/prow/e2e-aws-csi, ci/prow/e2e-aws-image-registry, ci/prow/e2e-aws-ovn-cgroupsv2, ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-aws-ovn-single-node, ci/prow/e2e-aws-ovn-single-node-serial, ci/prow/e2e-aws-ovn-single-node-upgrade, ci/prow/e2e-gcp-builds, ci/prow/e2e-gcp-csi, ci/prow/e2e-gcp-image-ecosystem, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-rt-upgrade, ci/prow/e2e-gcp-ovn-upgrade, ci/prow/e2e-metal-ipi-ovn-ipv6, ci/prow/e2e-metal-ipi-sdn, ci/prow/e2e-openstack-ovn DetailsIn 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 kubernetes/test-infra repository. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dgoodwin, stbenjam The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label approved |
|
@stbenjam: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
Reverts #27416 ; tracked by TRT-635
Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.
Since this merged, CI payloads have been failing on 4.11 -> 4.12 upgrades, exceeding time outs and reaching 4+ hours for some runs. It's not hitting every run, but it is hitting most. There was only one minor ovn aws upgrade on that PR, which unfortunately succeeded, but the aggregated ones failed due to timeouts.
To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of
/payload 4.12 ci blocking. The/payloadcommands on the originlal PR timed out after 3h, we may need to investigate the timeout configured for those.CC: @soltysh