Skip to content

NO-ISSUE: [master] Bump OCP versions: 4.18, 4.16, 4.20, 4.21, 4.19, 4.14#10326

Closed
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-1bdd7c5b-ebd5-4c52-9c14-c4251af39557
Closed

NO-ISSUE: [master] Bump OCP versions: 4.18, 4.16, 4.20, 4.21, 4.19, 4.14#10326
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-1bdd7c5b-ebd5-4c52-9c14-c4251af39557

Conversation

@danmanor
Copy link
Copy Markdown
Contributor

@danmanor danmanor commented May 14, 2026

OpenShift updates: 4.16.61 -> 4.16.62, 4.21.14 -> 4.21.15, 4.14.63 -> 4.14.65, 4.14.63-multi -> 4.14.65-multi, 4.20.21 -> 4.20.22, 4.21.14-multi -> 4.21.15-multi, 4.20.21-multi -> 4.20.22-multi, 4.18.40 -> 4.18.41, 4.18.40-multi -> 4.18.41-multi, 4.16.61-multi -> 4.16.62-multi, 4.19.30-multi -> 4.19.31-multi, 4.19.30 -> 4.19.31
RHCOS updates:

/test edge-e2e-metal-assisted-4-18 edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-19 edge-e2e-metal-assisted-4-14
/cc @rccrdpccl @gamli75

Summary by CodeRabbit

  • Updates
    • Updated OpenShift release container image versions and tags across all supported releases (versions 4.14, 4.16, 4.18, 4.19, 4.20, and 4.21) and CPU architectures (x86_64, arm64, and multi-architecture variants). Updated release image references in deployment and platform configuration templates to ensure users have access to the latest available OpenShift release images.

@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 14, 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.16.61 -> 4.16.62, 4.21.14 -> 4.21.15, 4.14.63 -> 4.14.65, 4.14.63-multi -> 4.14.65-multi, 4.20.21 -> 4.20.22, 4.21.14-multi -> 4.21.15-multi, 4.20.21-multi -> 4.20.22-multi, 4.18.40 -> 4.18.41, 4.18.40-multi -> 4.18.41-multi, 4.16.61-multi -> 4.16.62-multi, 4.19.30-multi -> 4.19.31-multi, 4.19.30 -> 4.19.31
RHCOS updates:

/test edge-e2e-metal-assisted-4-18 edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-19 edge-e2e-metal-assisted-4-14
/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 May 14, 2026 04:06
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 14, 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: cabc590f-852f-4a7b-b12c-b582d23df2fe

📥 Commits

Reviewing files that changed from the base of the PR and between d8b5726 and 3385b15.

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

Walkthrough

This PR updates OpenShift release image versions and corresponding container image URLs across three configuration files for versions 4.14 through 4.21, applying patch-level bumps consistently across x86\_64, arm64, and multi-architecture variants.

Changes

OpenShift Release Image Version Bumps

Layer / File(s) Summary
Default release images data source
data/default_release_images.json
OpenShift release versions updated for 4.14 (4.14.63→4.14.65), 4.16 (4.16.61→4.16.62), 4.18 (4.18.40→4.18.41), 4.19 (4.19.30→4.19.31), 4.20 (4.20.21→4.20.22), and 4.21 (4.21.14→4.21.15) across x86\_64, arm64, and multi architectures, with corresponding quay.io image URLs updated to match.
Deployment configuration propagation
deploy/podman/configmap.yml, openshift/template.yaml
RELEASE_IMAGES ConfigMap and template parameter values updated to reference the bumped OpenShift release image tags and versions, synchronized with the source data file.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

  • openshift/assisted-service#9752: Updates the same release-image data/templating files by bumping OpenShift release image tags and versions (4.16–4.22 patch-level changes).
  • openshift/assisted-service#8267: Updates data/default_release_images.json and propagates to ConfigMap/template for OpenShift release image version bumps with synchronized URL/version changes.
  • openshift/assisted-service#8831: Updates data/default_release_images.json release image metadata for OpenShift 4.21 with url/version value changes.

Suggested labels

lgtm, size/M

Suggested reviewers

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

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description lists version updates but lacks clear structure following the repository template; it omits issue type categorization, environment impact, testing methodology, and commit message clarity. Organize the description using the template structure: select issue type (likely Enhancement), confirm environment impact, specify testing method, and add a meaningful summary statement.
✅ Passed checks (11 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: bumping OpenShift release versions across multiple versions (4.14-4.21) and CPU architectures.
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 modifies only config/data files (JSON/YAML) with version bumps. No Go code or Ginkgo tests present. Custom check not applicable.
Test Structure And Quality ✅ Passed Custom check requires Ginkgo test code review. This PR modifies only configuration/data files (JSON and YAML), not test code. Check is not applicable.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests added. PR only updates OpenShift version data in configuration files (JSON, YAML manifests). Check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR does not add new Ginkgo e2e tests. It only modifies configuration files to bump OpenShift release versions. The SNO test compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only data configuration files with release image versions. No deployment manifests, controllers, operator code, or scheduling constraints are introduced or modified.
Ote Binary Stdout Contract ✅ Passed This PR modifies only configuration files (JSON/YAML) with no Go code changes. The OTE Binary Stdout Contract check applies only to Go source code and is not applicable here.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No new Ginkgo e2e tests added. PR only updates configuration/data files (release images metadata in JSON and YAML). Custom check 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

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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 14, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 14, 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 14, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented May 14, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.32%. Comparing base (d8b5726) to head (3385b15).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10326      +/-   ##
==========================================
- Coverage   44.33%   44.32%   -0.01%     
==========================================
  Files         417      417              
  Lines       72762    72762              
==========================================
- Hits        32257    32253       -4     
- Misses      37587    37589       +2     
- Partials     2918     2920       +2     

see 2 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 14, 2026

@danmanor: The following tests 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-verify-generated-code 3385b15 link true /test edge-verify-generated-code
ci/prow/verify-generated-code 3385b15 link true /test verify-generated-code
ci/prow/edge-e2e-metal-assisted-4-22 3385b15 link true /test edge-e2e-metal-assisted-4-22

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.

@danmanor
Copy link
Copy Markdown
Contributor Author

Closing as duplicate of #10335

@danmanor danmanor closed this May 17, 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. 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