Skip to content

NO-ISSUE: [master] Bump OCP versions: 4.20, 4.22, 4.21#10475

Closed
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-b47f2caa-3a6b-4d41-80ba-aaf5243e69b2
Closed

NO-ISSUE: [master] Bump OCP versions: 4.20, 4.22, 4.21#10475
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-b47f2caa-3a6b-4d41-80ba-aaf5243e69b2

Conversation

@danmanor

@danmanor danmanor commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

OpenShift updates: 4.21.19-multi -> 4.21.20-multi, 4.20.24 -> 4.20.25, 4.21.19 -> 4.21.20, 4.22.0-multi -> 4.22.1-multi, 4.20.24-multi -> 4.20.25-multi, 4.22.0 -> 4.22.1
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-21
/cc @rccrdpccl @gamli75

Summary by CodeRabbit

  • Chores
    • Updated supported OpenShift release image versions to include 4.20.25, 4.21.20, and 4.22.1 across multiple architectures.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 17, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@danmanor: This pull request explicitly references no jira issue.

Details

In response to this:

OpenShift updates: 4.21.19-multi -> 4.21.20-multi, 4.20.24 -> 4.20.25, 4.21.19 -> 4.21.20, 4.22.0-multi -> 4.22.1-multi, 4.20.24-multi -> 4.20.25-multi, 4.22.0 -> 4.22.1
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-21
/cc @rccrdpccl @gamli75

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 requested review from gamli75 and rccrdpccl June 17, 2026 04:06
@coderabbitai

coderabbitai Bot commented Jun 17, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5dc5fcf7-982d-4fd6-946f-bebf72028671

📥 Commits

Reviewing files that changed from the base of the PR and between 61a9f3c and 6156ef4.

📒 Files selected for processing (3)
  • data/default_release_images.json
  • deploy/podman/configmap.yml
  • openshift/template.yaml

Walkthrough

Updates OpenShift release image url and version fields in data/default_release_images.json for versions 4.20 (→4.20.25), 4.21 (→4.21.20), and 4.22 (→4.22.1) across x86_64, arm64, and multi architectures, then propagates the same changes to the derived deploy/podman/configmap.yml and openshift/template.yaml manifests.

Changes

Release Image Version Bump

Layer / File(s) Summary
Source release image data updates
data/default_release_images.json
url and version fields updated for 4.20 (4.20.24→4.20.25), 4.21 (4.21.19→4.21.20), and 4.22 (4.22.0→4.22.1) across all three architectures (x86_64, arm64, multi).
Derived deployment manifest updates
deploy/podman/configmap.yml, openshift/template.yaml
The RELEASE_IMAGES value in the Podman ConfigMap and the OpenShift template parameter are regenerated to reflect the same version bumps; all other metadata fields (support_level, default) are preserved.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • openshift/assisted-service#10449: Applies the same pattern of bumping release image tag/version entries across the same three files (data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml), targeting OCP 4.19.
  • openshift/assisted-service#10472: Also regenerates release-image JSON in the same three files with overlapping OCP 4.21 version bumps (4.21.18→4.21.19).

Suggested labels

approved, size/S, lgtm

Suggested reviewers

  • gamli75
  • rccrdpccl
🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description lists the specific version updates and references test commands, but does not follow the repository's PR template structure with required sections and checkboxes. Add the complete PR template structure including issue type checkboxes, environment impact, testing methodology checkboxes, and the full checklist items.
✅ Passed checks (14 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically summarizes the main change: bumping OpenShift versions 4.20, 4.21, and 4.22 across the repository.
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 PR contains only configuration file changes (JSON, YAML) with no modifications to Ginkgo test code or test files, making the test names check not applicable.
Test Structure And Quality ✅ Passed This PR only modifies configuration data files (data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml) with updated OpenShift version tags. It does not include any...
Microshift Test Compatibility ✅ Passed PR contains only configuration/data updates (JSON and YAML files) for OpenShift release image versions. No new Ginkgo e2e tests are added, so the MicroShift compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR only updates OpenShift release image metadata in three configuration files (JSON/YAML). No new Ginkgo e2e tests are added, so SNO compatibility assessment is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates OpenShift release image version numbers in data files and configuration; no deployment manifests, operator code, or scheduling constraints are introduced.
Ote Binary Stdout Contract ✅ Passed PR contains only data/configuration updates (JSON and YAML files). No Go code, test code, or executable binaries modified. OTE Binary Stdout Contract check not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No new Ginkgo e2e tests added in this PR. Changes are limited to configuration and data files (default_release_images.json, configmap.yml, template.yaml) that update OpenShift version metadata only.
No-Weak-Crypto ✅ Passed PR contains only configuration/data file updates (OpenShift release image metadata). No code changes, no cryptographic implementations, no weak crypto patterns.
Container-Privileges ✅ Passed PR updates only image URLs/versions in three data-only files; no container privilege configurations (privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation) are present or m...
No-Sensitive-Data-In-Logs ✅ Passed PR contains only data-only configuration updates (image URLs and version numbers) with no new logging statements and no sensitive data exposure risks.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci

openshift-ci Bot commented Jun 17, 2026

Copy link
Copy Markdown

@danmanor: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-agent-compact-ipv4
/test edge-assisted-operator-catalog-publish-verify
/test edge-ci-index
/test edge-e2e-ai-operator-disconnected-capi
/test edge-e2e-ai-operator-ztp
/test edge-e2e-ai-operator-ztp-3masters
/test edge-e2e-ai-operator-ztp-capi
/test edge-e2e-ai-operator-ztp-disconnected
/test edge-e2e-metal-assisted-4-16
/test edge-e2e-metal-assisted-4-17
/test edge-e2e-metal-assisted-5-0
/test edge-e2e-metal-assisted-5-control-planes-5-0
/test edge-e2e-metal-assisted-external-5-0
/test edge-e2e-metal-assisted-lvm-5-0
/test edge-e2e-metal-assisted-none-5-0
/test edge-e2e-metal-assisted-openshift-ai-4-21
/test edge-e2e-metal-assisted-osc-5-0
/test edge-e2e-metal-assisted-virtualization-4-22
/test edge-e2e-metal-assisted-vlan-5-0
/test edge-e2e-vsphere-assisted-5-0
/test edge-images
/test edge-lint
/test edge-operator-publish-verify
/test edge-subsystem-aws
/test edge-subsystem-kubeapi-aws
/test edge-unit-test
/test edge-verify-generated-code
/test images
/test mce-images
/test okd-scos-images
/test verify-deps
/test verify-generated-code

The following commands are available to trigger optional jobs:

/test e2e-agent-4control-ipv4
/test e2e-agent-5control-ipv4
/test e2e-agent-compact-ipv4-iso-no-registry
/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6
/test edge-e2e-ai-operator-ztp-4masters
/test edge-e2e-ai-operator-ztp-5masters
/test edge-e2e-ai-operator-ztp-compact-day2-masters
/test edge-e2e-ai-operator-ztp-compact-day2-workers
/test edge-e2e-ai-operator-ztp-multiarch-3masters-ocp
/test edge-e2e-ai-operator-ztp-multiarch-sno-ocp
/test edge-e2e-ai-operator-ztp-node-labels
/test edge-e2e-ai-operator-ztp-remove-node
/test edge-e2e-ai-operator-ztp-sno-day2-masters
/test edge-e2e-ai-operator-ztp-sno-day2-workers
/test edge-e2e-ai-operator-ztp-sno-day2-workers-ignitionoverride
/test edge-e2e-ai-operator-ztp-sno-day2-workers-late-binding
/test edge-e2e-metal-assisted-4-control-planes-5-0
/test edge-e2e-metal-assisted-4-masters-none-5-0
/test edge-e2e-metal-assisted-bond-5-0
/test edge-e2e-metal-assisted-day2-5-0
/test edge-e2e-metal-assisted-day2-arm-workers-5-0
/test edge-e2e-metal-assisted-day2-sno-5-0
/test edge-e2e-metal-assisted-dual-primary-v6-compact-5-0
/test edge-e2e-metal-assisted-dual-stack-primary-ipv6-5-0
/test edge-e2e-metal-assisted-ha-kube-api-ipv4-5-0
/test edge-e2e-metal-assisted-ha-kube-api-ipv6-5-0
/test edge-e2e-metal-assisted-ipv4v6-5-0
/test edge-e2e-metal-assisted-ipv6-5-0
/test edge-e2e-metal-assisted-kube-api-late-binding-sno-5-0
/test edge-e2e-metal-assisted-kube-api-late-unbinding-sno-5-0
/test edge-e2e-metal-assisted-kube-api-tna-5-0
/test edge-e2e-metal-assisted-kube-api-umlb-5-0
/test edge-e2e-metal-assisted-onprem-5-0
/test edge-e2e-metal-assisted-osc-sno-5-0
/test edge-e2e-metal-assisted-sno-5-0
/test edge-e2e-metal-assisted-static-ip-suite-5-0
/test edge-e2e-metal-assisted-tang-5-0
/test edge-e2e-metal-assisted-tna-5-0
/test edge-e2e-metal-assisted-tpmv2-5-0
/test edge-e2e-metal-assisted-umlb-5-0
/test edge-e2e-metal-assisted-upgrade-agent-5-0
/test edge-e2e-oci-assisted-5-0
/test edge-e2e-oci-assisted-bm-4cp-5-0
/test edge-e2e-oci-assisted-bm-iscsi-5-0
/test edge-e2e-vsphere-assisted-umlb-5-0
/test edge-e2e-vsphere-assisted-umn-5-0
/test okd-scos-e2e-aws-ovn
/test push-pr-image

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

pull-ci-openshift-assisted-service-master-e2e-agent-compact-ipv4
pull-ci-openshift-assisted-service-master-e2e-agent-compact-ipv4-iso-no-registry
pull-ci-openshift-assisted-service-master-edge-ci-index
pull-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-5-0
pull-ci-openshift-assisted-service-master-edge-images
pull-ci-openshift-assisted-service-master-edge-lint
pull-ci-openshift-assisted-service-master-edge-subsystem-aws
pull-ci-openshift-assisted-service-master-edge-subsystem-kubeapi-aws
pull-ci-openshift-assisted-service-master-edge-unit-test
pull-ci-openshift-assisted-service-master-edge-verify-generated-code
pull-ci-openshift-assisted-service-master-images
pull-ci-openshift-assisted-service-master-mce-images
pull-ci-openshift-assisted-service-master-okd-scos-images
pull-ci-openshift-assisted-service-master-verify-deps
pull-ci-openshift-assisted-service-master-verify-generated-code
Details

In response to this:

OpenShift updates: 4.21.19-multi -> 4.21.20-multi, 4.20.24 -> 4.20.25, 4.21.19 -> 4.21.20, 4.22.0-multi -> 4.22.1-multi, 4.20.24-multi -> 4.20.25-multi, 4.22.0 -> 4.22.1
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-21
/cc @rccrdpccl @gamli75

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.

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 17, 2026
@openshift-ci

openshift-ci Bot commented Jun 17, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danmanor

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 17, 2026
@codecov

codecov Bot commented Jun 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.36%. Comparing base (61a9f3c) to head (6156ef4).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10475      +/-   ##
==========================================
- Coverage   44.36%   44.36%   -0.01%     
==========================================
  Files         420      420              
  Lines       73107    73107              
==========================================
- Hits        32433    32431       -2     
- Misses      37740    37741       +1     
- Partials     2934     2935       +1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-ci

openshift-ci Bot commented Jun 17, 2026

Copy link
Copy Markdown

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

@gamli75

gamli75 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2026
@danmanor

Copy link
Copy Markdown
Contributor Author

Closing as duplicate of #10476

@danmanor danmanor closed this Jun 18, 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. 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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants