Skip to content

Conversation

@stbenjam
Copy link
Member

Reverts #542 ; tracked by TRT-XXXX

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

webhook-related tests are failing payloads

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 these jobs to confirm the fix has corrected the problem:

Verify tests pass 10x on something like periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-techpreview

CC: @camilamacedo86

PR created by Revertomatic™️

…new-test"

This reverts commit 5706dc9, reversing
changes made to 99e740d.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 11, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 11, 2025

@stbenjam: This pull request references OPRUN-4212 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 story to target the "4.21.0" version, but no target version was set.

In response to this:

Reverts #542 ; tracked by TRT-XXXX

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

webhook-related tests are failing payloads

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 these jobs to confirm the fix has corrected the problem:

Verify tests pass 10x on something like periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-techpreview

CC: @camilamacedo86

PR created by Revertomatic™️

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.

@stbenjam
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-techpreview 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/147f2690-bf0e-11f0-8175-0e5207260eaa-0

@stbenjam stbenjam changed the title TRT-XXXX: Revert #542 "OPRUN-4212: [OTE]: Add webhook cleanup validation on extension uninstall" [WIP] TRT-XXXX: Revert #542 "OPRUN-4212: [OTE]: Add webhook cleanup validation on extension uninstall" Nov 11, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 11, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stbenjam
Once this PR has been reviewed and has the lgtm label, please assign jianzhangbjz 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

@camilamacedo86
Copy link
Contributor

/hold

As we discussed, all the issues we’re seeing are in other tests (which have been running for a while) and are mainly timeouts.
It seems they’re caused by another issue: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1762874649650379?thread_ts=1762872659.571929&cid=C01CQA76KMX

So, I understand that we agree in hold for know that does not seems the root cause of the problems faced.

@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 Nov 11, 2025
@camilamacedo86
Copy link
Contributor

I am closing it out based on: #553 (comment)

If we need to revert we will need to create a new pr with the commit msg in the right format.

/close

@openshift-ci openshift-ci bot closed this Nov 11, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2025

@camilamacedo86: Closed this PR.

In response to this:

I am closing it out based on: #553 (comment)

If we need to revert we will need to create a new pr with the commit msg in the right format.

/close

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.

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

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants