Skip to content

MCO-2171: Migrate boot image tests to MCO's disruptive suites#5800

Draft
djoshy wants to merge 3 commits intoopenshift:mainfrom
djoshy:migrate-origin-bootimage
Draft

MCO-2171: Migrate boot image tests to MCO's disruptive suites#5800
djoshy wants to merge 3 commits intoopenshift:mainfrom
djoshy:migrate-origin-bootimage

Conversation

@djoshy
Copy link
Contributor

@djoshy djoshy commented Mar 24, 2026

- What I did
This PR migrates the AWS, GCP and vsphere bootimage test from origin, reusing existing helpers wherever possible. It refactors a few of the helpers so they are accessible via the exutil package.

- How to verify it
The migrated tests added to the disruptive suite should pass; this should not affect functionality so does not need additional QE.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 24, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 24, 2026

@djoshy: This pull request references MCO-2171 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.22.0" version, but no target version was set.

Details

In response to this:

- What I did
This PR migrates the AWS, GCP and vsphere bootimage test from origin, reusing existing helpers wherever possible. It refactors a few of the helpers so they are accessible via the exutil package.

- How to verify it
The migrated tests added to the disruptive suite should pass; this should not affect functionality so does not need additional QE.

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 added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 24, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

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

@coderabbitai
Copy link

coderabbitai bot commented Mar 24, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5ef81d81-1acc-4fc9-8de2-5bac8e3db6c5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy

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 Mar 24, 2026
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. 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.

2 participants