Skip to content

[release-4.20] OCPBUGS-67359: RHOAI 2.25 bump #5901

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 7 commits into from
Dec 17, 2025
Merged

[release-4.20] OCPBUGS-67359: RHOAI 2.25 bump #5901

openshift-merge-bot merged 7 commits into from
Dec 17, 2025

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Dec 14, 2025

Manual cherry-pick of #5899 due to conflicts.
See this comment.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 14, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 14, 2025

@ggiguash: This pull request references Jira Issue OCPBUGS-67359, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-67358 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-67358 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @jogeo

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Manual cherry-pick of #5899 due to conflicts.
See this comment.

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 14, 2025
@ggiguash ggiguash marked this pull request as draft December 14, 2025 12:00
@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 Dec 14, 2025
@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 14, 2025

/test e2e-aws-ai-model-serving

@ggiguash ggiguash mentioned this pull request Dec 14, 2025
Merged
@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 15, 2025

/test e2e-aws-ai-model-serving

@ggiguash ggiguash marked this pull request as ready for review December 15, 2025 14:57
@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 Dec 15, 2025
@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 15, 2025

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 15, 2025

@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-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-release-4.20-e2e-aws-ai-model-serving

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-arm

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc-arm

pull-ci-openshift-microshift-release-4.20-images

pull-ci-openshift-microshift-release-4.20-ocp-full-conformance-rhel-eus

pull-ci-openshift-microshift-release-4.20-ocp-full-conformance-serial-rhel-eus

pull-ci-openshift-microshift-release-4.20-security

pull-ci-openshift-microshift-release-4.20-test-rebase

pull-ci-openshift-microshift-release-4.20-test-rpm

pull-ci-openshift-microshift-release-4.20-test-unit

pull-ci-openshift-microshift-release-4.20-verify

pull-ci-openshift-microshift-release-4.20-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 Dec 15, 2025

Also testing periodics because of the vendor dependency changes for kustomize packages.

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 15, 2025

@ggiguash: The following test 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/e2e-aws-tests-bootc-periodic d036893 link true /test e2e-aws-tests-bootc-periodic

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.

@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 16, 2025 •
edited
Loading

The bootc periodic tests failed on the el96-src@ai-model-serving-offline due to the following errors:
Need to check why this is not happening in 4.21 release and potentially increase the disc space in the VM.

Dec 15 17:33:03 el96-src-ai-model-serving-offline-bootc-host1 microshift-copy-images[28227]: time="2025-12-15T17:33:03Z" level=fatal msg="copying system image from manifest list: writing blob: storing blob to file \"/var/tmp/container_images_storage1974076239/1\": write /var/tmp/container_images_storage1974076239/1: no space left on device"

pacevedom
pacevedom approved these changes Dec 16, 2025
View reviewed changes
Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/label backport-risk-assessed
/verified by CI

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 16, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@copejon
Copy link
Contributor

copejon commented Dec 17, 2025

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 17, 2025

@copejon: 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 a111b97 into openshift:release-4.20 Dec 17, 2025
15 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 17, 2025

@ggiguash: Jira Issue OCPBUGS-67359: All pull requests linked via external trackers have merged:

All linked pull requests have the verified tag. Jira Issue OCPBUGS-67359 has been moved to the VERIFIED state.

Details

In response to this:

Manual cherry-pick of #5899 due to conflicts.
See this comment.

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 deleted the rhoai-225-bump-420 branch December 17, 2025 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jogeo jogeo Awaiting requested review from jogeo

@copejon copejon Awaiting requested review from copejon

@eslutsky eslutsky Awaiting requested review from eslutsky

@vanhalenar vanhalenar Awaiting requested review from vanhalenar

1 more reviewer

@pacevedom pacevedom pacevedom approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@pacevedom pacevedom

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.

5 participants

@ggiguash @openshift-ci-robot @copejon @pacevedom @pmtk