Skip to content

USHIFT-6438: Reorganize upstream bootc tests #6008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-bot merged 5 commits into from
Jan 5, 2026
Merged

USHIFT-6438: Reorganize upstream bootc tests #6008

openshift-merge-bot merged 5 commits into from
Jan 5, 2026

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Jan 2, 2026 •
edited
Loading

  • Add test-agent images to allow greenboot test execution
  • Sync the list of scenarios running on cos9 and cos10

Note that the greenboot tests are temporarily disabled until RHEL-138275 is resolved.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 2, 2026 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-6438 which is a valid jira issue.

Details

In response to this:

  • Add test-agent images to allow grenboot test execution
  • Move rhel96-bootc.image-bootc to layer1-base/group3 to optimize build time
  • Sync the list of scenarios run on cos9 and cos10

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 2, 2026
@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 Jan 2, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 2, 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 2, 2026
@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 2, 2026

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 2, 2026

@ggiguash: The following commands are available to trigger required jobs:

/test e2e-aws-ai-model-serving

/test e2e-aws-footprint-and-performance

/test e2e-aws-tests

/test e2e-aws-tests-arm

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc-arm

/test e2e-aws-tests-bootc-periodic

/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-release

/test e2e-aws-tests-bootc-release-arm

/test e2e-aws-tests-bootc-upstream

/test e2e-aws-tests-bootc-upstream-arm

/test e2e-aws-tests-cache

/test e2e-aws-tests-cache-arm

/test e2e-aws-tests-periodic

/test e2e-aws-tests-periodic-arm

/test e2e-aws-tests-release

/test e2e-aws-tests-release-arm

/test ocp-full-conformance-rhel-eus

/test ocp-full-conformance-serial-rhel-eus

/test test-rpm

/test test-unit

/test verify

/test verify-deps

The following commands are available to trigger optional jobs:

/test images

/test security

/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-main-e2e-aws-tests

pull-ci-openshift-microshift-main-e2e-aws-tests-arm

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-upstream

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-upstream-arm

pull-ci-openshift-microshift-main-images

pull-ci-openshift-microshift-main-security

pull-ci-openshift-microshift-main-test-unit

pull-ci-openshift-microshift-main-verify

pull-ci-openshift-microshift-main-verify-deps
Details

In response to this:

/test ?

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.

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 2, 2026

/test e2e-aws-tests-bootc-upstream
/test e2e-aws-tests-bootc-upstream-arm

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 2, 2026 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-6438 which is a valid jira issue.

Details

In response to this:

  • Add test-agent images to allow grenboot test execution
  • Move rhel96-bootc.image-bootc to layer1-base/group3 to optimize build time
  • Sync the list of scenarios running on cos9 and cos10

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
Copy link

openshift-ci-robot commented Jan 3, 2026 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-6438 which is a valid jira issue.

Details

In response to this:

  • Add test-agent images to allow greenboot test execution
  • Move rhel96-bootc.image-bootc to layer1-base/group3 to optimize build time
  • Sync the list of scenarios running on cos9 and cos10

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
Copy link

openshift-ci-robot commented Jan 5, 2026 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-6438 which is a valid jira issue.

Details

In response to this:

  • Add test-agent images to allow greenboot test execution
  • Move rhel96-bootc.image-bootc to layer1-base/group3 to optimize build time
  • Sync the list of scenarios running on cos9 and cos10

Note that the greenboot tests are temporarily disabled until RHEL-138275 is resolved.

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.

@ggiguash ggiguash marked this pull request as ready for review January 5, 2026 09:51
@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 Jan 5, 2026
@openshift-ci openshift-ci bot requested review from copejon and vanhalenar January 5, 2026 09:52
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 5, 2026 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-6438 which is a valid jira issue.

Details

In response to this:

  • Add test-agent images to allow greenboot test execution
  • Sync the list of scenarios running on cos9 and cos10

Note that the greenboot tests are temporarily disabled until RHEL-138275 is resolved.

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
Copy link
Contributor

openshift-ci bot commented Jan 5, 2026

@ggiguash: 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.

@agullon
Copy link
Contributor

agullon commented Jan 5, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

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

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 5, 2026

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 5, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 5, 2026

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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-merge-bot openshift-merge-bot bot merged commit 908fae4 into openshift:main Jan 5, 2026
12 checks passed
@ggiguash ggiguash deleted the upstream-greenboot-fix branch January 6, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@copejon copejon Awaiting requested review from copejon

@vanhalenar vanhalenar Awaiting requested review from vanhalenar

Assignees

@agullon agullon

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ggiguash @openshift-ci-robot @agullon