Revert OTE Migration: release-4.14#296
Conversation
|
Skipping CI for Draft Pull Request. |
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
danchild
changed the title
danchild
changed the title
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
openshift-ci
Bot
added
the
needs-rebase
|
/verified by @danchild |
|
@danchild: This PR has been marked as verified by 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. |
openshift-ci-robot
added
the
verified
6b9d83a to
85043be
Compare
openshift-ci-robot
removed
the
verified
openshift-ci
Bot
removed
the
needs-rebase
This reverts commit 4354254.
85043be to
caeb37a
Compare
The revert was performed before the version bump from openshift#291, so the reverted modules and vendored dependencies became out of sync with the version bump. Module and vendored dependencies are now in sync with 9557a9f Signed-off-by: Dan Childers <dchilder@redhat.com>
|
/verified by @danchild |
openshift-ci-robot
added
the
verified
|
@danchild: This PR has been marked as verified by 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. |
|
@danchild: 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-sigs/prow repository. I understand the commands that are listed here. |
2 participants
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's:
#275
#279
#282
#293
All of these reverts guarantee that all OTE related binary content is removed from the project.