Skip to content

NO-ISSUE: [master] Bump OCP versions: 4.20, 4.18, 4.17#10372

Open
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-fced85c0-1d09-443b-8a0f-cbb65d977878
Open

NO-ISSUE: [master] Bump OCP versions: 4.20, 4.18, 4.17#10372
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-fced85c0-1d09-443b-8a0f-cbb65d977878

Conversation

@danmanor
Copy link
Copy Markdown
Contributor

@danmanor danmanor commented May 21, 2026

OpenShift updates: 4.17.53 -> 4.17.54, 4.17.53-multi -> 4.17.54-multi, 4.18.41-multi -> 4.18.42-multi, 4.20.22 -> 4.20.23, 4.20.22-multi -> 4.20.23-multi, 4.18.41 -> 4.18.42
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-18 edge-e2e-metal-assisted-4-17
/cc @rccrdpccl @gamli75

Summary by CodeRabbit

  • Chores
    • Updated OpenShift release images for versions 4.17, 4.18, and 4.20 across all supported architectures (x86_64, arm64, and multi-architecture builds).
    • Synchronized release image references across deployment configurations.

@openshift-ci openshift-ci Bot requested review from gamli75 and rccrdpccl May 21, 2026 04:12
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 21, 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.17.53 -> 4.17.54, 4.17.53-multi -> 4.17.54-multi, 4.18.41-multi -> 4.18.42-multi, 4.20.22 -> 4.20.23, 4.20.22-multi -> 4.20.23-multi, 4.18.41 -> 4.18.42
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-18 edge-e2e-metal-assisted-4-17
/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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 21, 2026

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: 7afd5141-2f66-4df8-8e0f-d9cd8dd3f903

📥 Commits

Reviewing files that changed from the base of the PR and between 21da507 and 8f75acd.

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

Walkthrough

This PR updates OpenShift release image metadata across three configuration sources. The primary source (data/default_release_images.json) contains version and URL bumps for OpenShift 4.17, 4.18, and 4.20 in x86_64, arm64, and multi-architecture variants. The same updates are propagated to the Podman ConfigMap and OpenShift template parameter.

Changes

Release image version bumps

Layer / File(s) Summary
Primary release image source updates
data/default_release_images.json
OpenShift 4.17, 4.18, and 4.20 entries for x86_64, arm64, and multi-arch are updated to newer url and matching version values.
Configuration propagation to deployment and template
deploy/podman/configmap.yml, openshift/template.yaml
Updated RELEASE_IMAGES in the Kubernetes ConfigMap and OpenShift template parameter with the same bumped release image entries.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • openshift/assisted-service#10348: Both PRs update the same release-image source-of-truth across data/default_release_images.json, deploy/podman/configmap.yml, and openshift/template.yaml by bumping OpenShift image tag/version entries for different OCP versions.
  • openshift/assisted-service#10342: Both PRs update release-image descriptor data and bump url/version in data/default_release_images.json and the corresponding RELEASE_IMAGES values in deployment and template configurations, with overlap for versions 4.18 and 4.20.

Suggested labels

approved, size/M, kind/dependency-change, lgtm

Suggested reviewers

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

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description provides specific version update details and test commands, but is missing several required template sections including issue type checkboxes, environment impact selection, and testing methodology checkboxes. Complete the PR description by filling out the required template sections: select relevant issue type, environment impact, testing methodology, and checklist items.
✅ Passed checks (11 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: bumping OpenShift versions 4.17, 4.18, and 4.20, which matches the file modifications in the changeset.
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/data file changes (JSON, YAML) with no Ginkgo test code or test names to evaluate against the stability check.
Test Structure And Quality ✅ Passed PR contains only data and configuration file updates (JSON and YAML); no Ginkgo test code is present, so the test structure check is not applicable.
Microshift Test Compatibility ✅ Passed PR contains only configuration/data updates (JSON and YAML files with version bumps). No new Ginkgo e2e tests are added, so MicroShift test compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only modifies configuration and release image metadata files (JSON/YAML); no new Ginkgo e2e tests are added, so SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates OCP release image versions and metadata in configuration files; no deployment manifests, scheduling constraints, or operator code are added or modified.
Ote Binary Stdout Contract ✅ Passed PR contains only data/config file updates (release image versions, ConfigMap, template params) with no source code changes to main binary or OTE test setup functions.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR contains only configuration/metadata updates (JSON, ConfigMap, template YAML) with no new Ginkgo e2e test code. Check is not applicable.

✏️ 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 added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 21, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 21, 2026

[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 May 21, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented May 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.32%. Comparing base (21da507) to head (8f75acd).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #10372   +/-   ##
=======================================
  Coverage   44.32%   44.32%           
=======================================
  Files         417      417           
  Lines       72766    72766           
=======================================
+ Hits        32256    32257    +1     
  Misses      37591    37591           
+ Partials     2919     2918    -1     

see 3 files 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
Copy link
Copy Markdown

openshift-ci Bot commented May 21, 2026

@danmanor: 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/edge-subsystem-kubeapi-aws 8f75acd link true /test edge-subsystem-kubeapi-aws

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.

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

3 participants