Skip to content

Update image tag from ubi9-v1.25 to ubi9-v1.26 - #82434

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
kaovilai:patch-22
Jul 24, 2026
Merged

Update image tag from ubi9-v1.25 to ubi9-v1.26#82434
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
kaovilai:patch-22

Conversation

@kaovilai

@kaovilai kaovilai commented Jul 24, 2026

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • Updates the MIGTools KubeVirt DataMover Controller CI build environment to use the ubi9-v1.26 builder image instead of ubi9-v1.25.

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 778efd4c-0ef1-4965-857f-56ae9ff55764

📥 Commits

Reviewing files that changed from the base of the PR and between a912569 and 7e75b45.

📒 Files selected for processing (1)
  • ci-operator/config/migtools/kubevirt-datamover-controller/migtools-kubevirt-datamover-controller-oadp-dev.yaml

Walkthrough

The CI configuration updates the kubevirt datamover controller builder image stream tag from ubi9-v1.25 to ubi9-v1.26.

Changes

Builder Image Update

Layer / File(s) Summary
Update build root image
ci-operator/config/migtools/kubevirt-datamover-controller/migtools-kubevirt-datamover-controller-oadp-dev.yaml
The build_root builder image stream tag changes from ubi9-v1.25 to ubi9-v1.26.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the only substantive change: updating the builder image tag from ubi9-v1.25 to ubi9-v1.26.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Only a CI YAML tag changed; no test files or Ginkgo titles were modified, so no unstable test names were introduced.
Test Structure And Quality ✅ Passed Only a ci-operator YAML tag changed; no Ginkgo or test files were modified, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only a ci-operator YAML image-tag change is present; no Ginkgo tests or MicroShift-relevant APIs/features were added or modified.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only updates a ci-operator YAML image tag; no test files or Ginkgo specs were added or changed, so there are no SNO assumptions to review.
Topology-Aware Scheduling Compatibility ✅ Passed Only the build_root builder tag changed; the YAML has no scheduling, replicas, affinity, nodeSelector, or topology fields, so this check is not applicable.
Ote Binary Stdout Contract ✅ Passed PR only changes a ci-operator YAML builder tag; no process-level Go/test code or stdout writes were touched.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only a ci-operator YAML build_root tag changed; no new Ginkgo tests or network-using code were added.
No-Weak-Crypto ✅ Passed Diff only updates a builder image tag in YAML; no crypto code or weak algorithms appear in the changed file.
Container-Privileges ✅ Passed Only the build_root image tag changed; the touched YAML contains no privileged flags, host namespaces, or SYS_ADMIN settings.
No-Sensitive-Data-In-Logs ✅ Passed The only change is a builder image tag bump in a ci-operator YAML; no log statements or sensitive fields were added.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci
openshift-ci Bot requested review from sseago and weshayutin July 24, 2026 20:53
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@kaovilai: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-migtools-kubevirt-datamover-controller-oadp-dev-images migtools/kubevirt-datamover-controller presubmit Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaovilai, shubham-pampattiwar

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

@kaovilai

Copy link
Copy Markdown
Member Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@kaovilai: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 24, 2026
@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit 6b1aa27 into openshift:main Jul 24, 2026
14 checks passed
mrniranjan pushed a commit to mrniranjan/release that referenced this pull request Jul 28, 2026
amogh-redhat pushed a commit to amogh-redhat/release that referenced this pull request Aug 5, 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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants