Skip to content

Revert OTE Migration: release-4.18#299

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:release-4.18from
shiftstack:remove-ote-binary-4.18
Jul 23, 2026
Merged

Revert OTE Migration: release-4.18#299
openshift-merge-bot[bot] merged 3 commits into
openshift:release-4.18from
shiftstack:remove-ote-binary-4.18

Conversation

@danchild

@danchild danchild commented Jul 20, 2026

Copy link
Copy Markdown
Member

After further investigation, it was found that the OTE framework will not backport passed 4.19. So, it's necessary to revert all of the past commits related to the attempted OTE migration. The relevant commits are contained in the following PR:

#271

All of these reverts guarantee that all OTE related binary content is removed from the project.

@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 Jul 20, 2026
@openshift-ci

openshift-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@danchild danchild changed the title Revert the Addition of the OTE Framework: release-4.18 Revert OTE Migration: release-4.18 Jul 21, 2026
@danchild
danchild marked this pull request as ready for review July 21, 2026 13:08
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 21, 2026
@openshift-ci
openshift-ci Bot requested review from EmilienM and gryf July 21, 2026 13:09
@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

@danchild: all tests passed!

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.

@ekuris-redhat

Copy link
Copy Markdown

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2026
@danchild

Copy link
Copy Markdown
Member Author

/verified by @danchild

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 22, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@danchild: This PR has been marked as verified by @danchild.

Details

In response to this:

/verified by @danchild

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.

@eurijon

eurijon commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ekuris-redhat, eurijon

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 23, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 78da468 into openshift:release-4.18 Jul 23, 2026
5 checks passed
@openshift-merge-bot
openshift-merge-bot Bot deleted the remove-ote-binary-4.18 branch July 23, 2026 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants