[release-4.19] OCPBUGS-67360: RHOAI 2.25 bump

[ggiguash]

Manual cherry-pick of #5901

[openshift-ci]

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

[ggiguash]

/test ?

[openshift-ci]

@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-cache

/test e2e-aws-tests-cache-arm

/test e2e-aws-tests-periodic

/test e2e-aws-tests-periodic-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.19-e2e-aws-ai-model-serving

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

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

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

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

pull-ci-openshift-microshift-release-4.19-images

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

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

pull-ci-openshift-microshift-release-4.19-security

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

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

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

pull-ci-openshift-microshift-release-4.19-verify

pull-ci-openshift-microshift-release-4.19-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]

/test e2e-aws-ai-model-serving

[openshift-ci-robot]

@ggiguash: This pull request references Jira Issue OCPBUGS-67360, which is invalid:

• expected dependent Jira Issue OCPBUGS-67359 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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 #5901

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]

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]

@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	1a2dc00	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]

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]

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

[openshift-ci]

[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:

• OWNERS [ggiguash,pacevedom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[copejon]

/verified by ci

[openshift-ci-robot]

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

[copejon]

/jira refresh

[openshift-ci-robot]

@copejon: This pull request references Jira Issue OCPBUGS-67360, which is invalid:

• expected dependent Jira Issue OCPBUGS-67359 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[copejon]

/jira refresh

[openshift-ci-robot]

@copejon: This pull request references Jira Issue OCPBUGS-67360, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[copejon]

/jira refresh

[openshift-ci-robot]

@copejon: This pull request references Jira Issue OCPBUGS-67360, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.z) matches configured target version for branch (4.19.z)
• bug is in the state POST, 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-67359 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-67359 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
• bug has dependents

Requesting review from QA contact:
/cc @jogeo

Details

In response to this:

/jira refresh

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]

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

• openshift/microshift#5902

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

Details

In response to this:

Manual cherry-pick of #5901

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.