TRT-2243: Revert "OCPBUGS-56202: DownStream Merge [07-25-2025]"#2706
Conversation
openshift-ci-robot
added
jira/severity-critical
|
@xueqzhan: This pull request references Jira Issue OCPBUGS-56202, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade 3 |
|
@xueqzhan: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/80df21d0-76f4-11f0-967d-4b5739387f61-0 |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-upgrade 3 |
|
@xueqzhan: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a62dc2c0-76f4-11f0-8f78-b7b524af5f47-0 |
|
/retest-required |
sdodson
removed
the
jira/invalid-bug
|
/retitle TRT-2243: Revert "OCPBUGS-56202: DownStream Merge [07-25-2025]" |
openshift-ci
bot
changed the title
openshift-ci-robot
removed
the
jira/severity-critical
|
@xueqzhan: This pull request references TRT-2243 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/override ci/prow/e2e-gcp-ovn ci/prow/qe-perfscale-payload-control-plane-6nodes ci/prow/e2e-aws-ovn-upgrade-local-gateway ci/prow/4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade |
|
@sdodson: Overrode contexts on behalf of sdodson: ci/prow/4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade, ci/prow/e2e-aws-ovn-upgrade-local-gateway, ci/prow/e2e-gcp-ovn, ci/prow/qe-perfscale-payload-control-plane-6nodes 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-sigs/prow repository. |
|
/label approved |
openshift-ci
bot
added
the
approved
openshift-ci
bot
added
lgtm
sdodson
added
the
approved
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: sdodson, xueqzhan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/override /override ci/prow/e2e-aws-ovn-edge-zones ci/prow/lint |
|
/override ci/prow/e2e-aws-ovn-edge-zones ci/prow/lint |
|
@sdodson: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. 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-sigs/prow repository. |
|
@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-ovn-edge-zones, ci/prow/lint 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-sigs/prow repository. |
|
@xueqzhan: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] Distgit: ovn-kubernetes-base |
|
[ART PR BUILD NOTIFIER] Distgit: ovn-kubernetes-microshift |
|
[ART PR BUILD NOTIFIER] Distgit: ose-ovn-kubernetes |
|
Fix included in accepted release 4.20.0-0.nightly-2025-09-08-182033 |
|
Fix included in accepted release 4.20.0-0.nightly-2026-03-14-030631 |
5 participants
Reverts #2693; tracked by
Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.
This PR has caused disruptions with ingress that are affecting massive number of GCP upgrade jobs. You can see the above jira case for examples. This is also blocking payloads.
Slack thread: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1754918087727769
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:
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-upgrade 10
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade 10
Please make sure there is no ingress related disruptions with the test jobs.
CC: @jcaamano @jluhrsen