Skip to content

OSASINFRA-4209: Migrate to openshift-tests-extension (OTE)#260

Open
mandre wants to merge 3 commits into
openshift:mainfrom
shiftstack:migrate-ote
Open

OSASINFRA-4209: Migrate to openshift-tests-extension (OTE)#260
mandre wants to merge 3 commits into
openshift:mainfrom
shiftstack:migrate-ote

Conversation

@mandre
Copy link
Copy Markdown
Member

@mandre mandre commented May 19, 2026

Migrate to OTE using the ote-migration skill [1].

[1] https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ote-migration

mandre added 3 commits May 19, 2026 15:25
Add cmd/extension/main.go as a new OTE-based test extension binary
alongside the existing openshift-tests entry point. This registers
all openstack tests with the OTE framework, adds [OTP] annotations
to all Describe blocks, and integrates the extension build into the
Makefile and Containerfile.

The OTE binary discovers 51 tests and does not pull in origin's
monitor test framework, avoiding the duplicate test results seen
with the old entry point.
The old cmd/openshift-tests/ entry point used origin's test runner
framework which unconditionally loaded 40+ monitor tests (disruption
analyzers, termination message policy checks, etc.), producing
duplicate/unwanted JUnit results in CI alongside the actual openstack
tests.

Remove the old entry point and all its supporting code:
- cmd/openshift-tests/
- pkg/cmd/openshift-tests/ and pkg/testsuites/
- test/extended/util/annotate/ (annotation generator)
- test/extended/include.go

This shrinks the vendored origin footprint from 29MB/796 files to
2.5MB/58 files, as only test/extended/util (CLI helpers) is still
needed.
Bump openshift/origin from 140c6726a606 (Jun 2025) to
4486518a1248 (May 2026), upgrading k8s.io/kubernetes from
v1.32.5 to v1.35.1 and all related dependencies.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 19, 2026

@mandre: This pull request references OSASINFRA-4209 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 "5.0.0" version, but no target version was set.

Details

In response to this:

Migrate to OTE using the ote-migration skill [1].

[1] https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ote-migration

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 openshift-ci Bot requested review from eurijon and gryf May 19, 2026 13:32
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign eurijon for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

@mandre: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/build 47c80ba link true /test build
ci/prow/images 47c80ba link true /test images
ci/prow/test 47c80ba link true /test test
ci/prow/verify 47c80ba link true /test verify

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.

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

Labels

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.

2 participants