Skip to content

oadp: Update image tag from ubi9-v1.25 to ubi9-v1.26 - #81949

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

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

Conversation

@kaovilai

@kaovilai kaovilai commented Jul 15, 2026

Copy link
Copy Markdown
Member

Merge this for now..
to discuss later, deferring to github actions unit tests which already passes on https://github.com/openshift/velero/actions/runs/29340442533/job/87232266013?pr=494

unblocks openshift/velero#494

Summary by CodeRabbit

  • Updates the OpenShift Velero OADP development CI build root from ubi9-v1.25 to ubi9-v1.26, helping unblock Velero PR #494.

@coderabbitai

coderabbitai Bot commented Jul 15, 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: a37f77ba-d8fd-433a-92b1-acc0cf1d083a

📥 Commits

Reviewing files that changed from the base of the PR and between 38b5968 and c1248e6.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/velero/openshift-velero-oadp-dev.yaml

Walkthrough

The Velero OADP development configuration updates its build root image stream tag from ubi9-v1.25 to ubi9-v1.26.

Changes

Velero build root configuration

Layer / File(s) Summary
Update build root image tag
ci-operator/config/openshift/velero/openshift-velero-oadp-dev.yaml
The build_root.image_stream_tag.tag value 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 summarizes the only change: bumping the OADP 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 bump changed; no Ginkgo test titles or test files were modified, so the check is not applicable.
Test Structure And Quality ✅ Passed Only a ci-operator YAML image-tag bump changed; no Ginkgo test code or assertions were modified.
Microshift Test Compatibility ✅ Passed Only a ci-operator config image tag changed; no Ginkgo e2e tests or MicroShift-sensitive APIs were added or modified.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Only a CI config YAML tag changed; no new Ginkgo e2e tests or SNO-sensitive logic were added.
Topology-Aware Scheduling Compatibility ✅ Passed Only a build_root image tag changed in a ci-operator YAML; no replicas, affinity, selectors, taints, or PDBs were added.
Ote Binary Stdout Contract ✅ Passed Only a ci-operator YAML tag changed; no Go/test startup code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only a ci-operator YAML image tag changed; no Ginkgo e2e tests or networking code were added or modified.
No-Weak-Crypto ✅ Passed Only a CI YAML tag bump changed; no crypto code, weak algorithms, or secret comparisons were added.
Container-Privileges ✅ Passed Only the build_root builder tag changed; no privileged, host*, SYS_ADMIN, or allowPrivilegeEscalation settings were added.
No-Sensitive-Data-In-Logs ✅ Passed The PR only bumps a CI build-root image tag in one YAML file; it adds no logging code or sensitive data exposure.
✨ 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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 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-openshift-velero-oadp-dev-images openshift/velero presubmit Ci-operator config changed
pull-ci-openshift-velero-oadp-dev-lint openshift/velero presubmit Ci-operator config changed
pull-ci-openshift-velero-oadp-dev-unit-test openshift/velero presubmit Ci-operator config changed
periodic-ci-openshift-velero-oadp-dev-periodics-rebasebot N/A periodic 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 15, 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-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2026
@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Joeavaikath, kaovilai

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 15, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 1e6ffee into openshift:main Jul 15, 2026
14 checks passed
SachinNinganure pushed a commit to SachinNinganure/release that referenced this pull request Jul 20, 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