Skip to content

OSASINFRA-4375: Drop Legacy openshift-test entry point: release-4.20 - #308

Open
danchild wants to merge 1 commit into
openshift:release-4.20from
shiftstack:drop-legacy-openstack-test-4.20
Open

OSASINFRA-4375: Drop Legacy openshift-test entry point: release-4.20#308
danchild wants to merge 1 commit into
openshift:release-4.20from
shiftstack:drop-legacy-openstack-test-4.20

Conversation

@danchild

@danchild danchild commented Jul 29, 2026

Copy link
Copy Markdown
Member

Following the migration of openstack-test to the
OTE framework, the entry point is no longer needed.

Changes:

  • Remove openstack-test binary and related libs
    in pkg
  • Remove openshift-tests builder and entry point in
    the Containerfile
  • Remove stale openshift-tests references for make tooling
  • Update README.md with new instructions on how to manually
    invoke the new OTE binary
  • update module and vendored dependencies

Dependencies:
openshift/release/pull/82506
openshift/release/pull/82674

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

openshift-ci Bot commented Jul 29, 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 marked this pull request as ready for review July 29, 2026 14:26
@danchild
danchild marked this pull request as draft July 29, 2026 14:26
@openshift-ci openshift-ci Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jul 29, 2026
@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

[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 gryf 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
openshift-ci Bot requested review from mandre and rlobillo July 29, 2026 14:33
@danchild
danchild force-pushed the drop-legacy-openstack-test-4.20 branch 3 times, most recently from 0d5540d to 322e766 Compare July 29, 2026 14:43
Following the migration of openstack-test to the
OTE framework, the entry point is no longer needed.

Changes:
- Remove `openstack-test` binary and related libs
  in `pkg`
- Remove openshift-tests builder and entry point in
  the Containerfile
- Remove stale openshift-tests references for make tooling
- Update README.md with new instructions on how to manually
  invoke the new OTE binary
- update module and vendored dependencies

Signed-off-by: Dan Childers <[email protected]>
@danchild
danchild force-pushed the drop-legacy-openstack-test-4.20 branch from 322e766 to c1725d5 Compare July 29, 2026 14:48
@danchild
danchild marked this pull request as ready for review July 29, 2026 14:49
@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 29, 2026
@openshift-ci
openshift-ci Bot requested review from eurijon and itzikb-redhat July 29, 2026 14:57
@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

@danchild: 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 c1725d5 link true /test build
ci/prow/test c1725d5 link true /test test
ci/prow/images c1725d5 link true /test images

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.

@danchild danchild changed the title Drop Legacy openshift-test entry point: 4.20 OSASINFRA-4375: Drop Legacy openshift-test entry point: 4.20 Jul 30, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 30, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 30, 2026

Copy link
Copy Markdown

@danchild: This pull request references OSASINFRA-4375 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.20.z" version, but no target version was set.

Details

In response to this:

Following the migration of openstack-test to the
OTE framework, the entry point is no longer needed.

Changes:

  • Remove openstack-test binary and related libs
    in pkg
  • Remove openshift-tests builder and entry point in
    the Containerfile
  • Remove stale openshift-tests references for make tooling
  • Update README.md with new instructions on how to manually
    invoke the new OTE binary
  • update module and vendored dependencies

NOTE: depends on openshift/release#82506; 4.20 release jobs need to drop callers of the legacy openstack-tests binary before this can be merged.

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 danchild changed the title OSASINFRA-4375: Drop Legacy openshift-test entry point: 4.20 OSASINFRA-4375: Drop Legacy openshift-test entry point: release-4.20 Jul 30, 2026
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