Skip to content

NO-ISSUE: [master] Bump OCP versions: 4.16, 4.19, 4.18, 4.22, 4.21, 4.20, 5.0#10517

Open
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-43565179-0dae-4c5b-9208-588dc54074b8
Open

NO-ISSUE: [master] Bump OCP versions: 4.16, 4.19, 4.18, 4.22, 4.21, 4.20, 5.0#10517
danmanor wants to merge 1 commit into
openshift:masterfrom
danmanor:bump/ocp-releases-43565179-0dae-4c5b-9208-588dc54074b8

Conversation

@danmanor

@danmanor danmanor commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

OpenShift updates: 4.22.0-multi -> 4.22.2-multi, 4.20.24-multi -> 4.20.26-multi, 4.19.33 -> 4.19.35, 4.21.19 -> 4.21.21, 4.22.0 -> 4.22.2, 4.16.63 -> 4.16.64, 4.20.24 -> 4.20.26, 4.16.63-multi -> 4.16.64-multi, 4.18.43 -> 4.18.45, 4.21.19-multi -> 4.21.21-multi, 4.18.43-multi -> 4.18.45-multi, 4.19.33-multi -> 4.19.35-multi
RHCOS updates: 4.22.0 -> 5.0.0-ec.3

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

Summary by CodeRabbit

  • Bug Fixes
    • Updated OS image references for OpenShift 5.0 so the correct pre-release images are used across all supported architectures.
    • Refreshed release image references for several OpenShift versions to newer patch releases, including multi-arch images.
    • Aligned sample and deployment metadata with the latest image locations.

@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

OpenShift updates: 4.22.0-multi -> 4.22.2-multi, 4.20.24-multi -> 4.20.26-multi, 4.19.33 -> 4.19.35, 4.21.19 -> 4.21.21, 4.22.0 -> 4.22.2, 4.16.63 -> 4.16.64, 4.20.24 -> 4.20.26, 4.16.63-multi -> 4.16.64-multi, 4.18.43 -> 4.18.45, 4.21.19-multi -> 4.21.21-multi, 4.18.43-multi -> 4.18.45-multi, 4.19.33-multi -> 4.19.35-multi
RHCOS updates: 4.22.0 -> 5.0.0-ec.3

/test edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-19 edge-e2e-metal-assisted-4-18 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-5-0
/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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 25, 2026
@openshift-ci openshift-ci Bot requested review from gamli75 and rccrdpccl June 25, 2026 04:09
@coderabbitai

coderabbitai Bot commented Jun 25, 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: 173e5acf-1ab0-4f4c-9f49-6e8b68afaf4d

📥 Commits

Reviewing files that changed from the base of the PR and between a9f9002 and 46e70f8.

📒 Files selected for processing (7)
  • config/manager/manager.yaml
  • config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml
  • data/default_os_images.json
  • data/default_release_images.json
  • deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml
  • deploy/podman/configmap.yml
  • openshift/template.yaml

Walkthrough

OpenShift 5.0 OS image URLs are corrected across manifests, samples, templates, and default OS image data. Several OpenShift release image references and version fields are also bumped for 4.16 through 4.22 in shared data and generated configuration.

Changes

Image metadata refresh

Layer / File(s) Summary
OS image URLs
config/manager/manager.yaml, config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml, data/default_os_images.json, deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml, deploy/podman/configmap.yml, openshift/template.yaml
OpenShift 5.0 OS image URLs are updated to the rhcos/pre-release/5.0.0-ec.3 paths across the shared data and mirrored manifests.
Release image tags
data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml
OpenShift release image URLs and version fields are bumped for 4.16 through 4.22 across the shared release data and generated config.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels

size/L

Suggested reviewers

  • jhernand
  • yoavsc0302
🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description lacks the required template sections, including issue list, impacted environments, testing details, and checklist items. Fill in the repo template: add summary/motivation, linked issues, impacted environments, testing notes, dependencies, and checklist/reviewer sections.
✅ Passed checks (14 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and accurately summarizes the main change: bumping supported OCP and RHCOS versions.
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 only changes config/data image references; no Ginkgo test titles or test files were added or modified, so no unstable names appear.
Test Structure And Quality ✅ Passed No Ginkgo test files or test logic were changed; the PR only updates config/template/image metadata, so this check is not applicable.
Microshift Test Compatibility ✅ Passed The PR only changes config/JSON/manifest data files; the diff contains no added Ginkgo specs or test files to audit for MicroShift incompatibility.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only updates YAML/JSON manifests; no new or changed Ginkgo e2e tests, and touched files contain no SNO-sensitive test logic.
Topology-Aware Scheduling Compatibility ✅ Passed Only image/version data changed; no nodeSelector, affinity, anti-affinity, topologySpreadConstraints, tolerations, or replica logic was added.
Ote Binary Stdout Contract ✅ Passed The PR only updates YAML/JSON image metadata; no process-level code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No Ginkgo e2e tests were added; the PR only changes config/JSON/YAML manifests, so the IPv6/disconnected test check is not applicable.
No-Weak-Crypto ✅ Passed Changed files only update OS/release image URLs and version tags; no MD5/SHA1/DES/RC4/3DES/ECB, custom crypto, or secret comparisons were introduced.
Container-Privileges ✅ Passed Touched manifests only update image data; the relevant pod specs keep allowPrivilegeEscalation:false and add no privileged/host* settings.
No-Sensitive-Data-In-Logs ✅ Passed PASS: The PR only updates OCP/RHCOS image metadata in YAML/JSON manifests; no new logging code or log output containing secrets/PII was added.

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

@openshift-ci openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 25, 2026
@openshift-ci

openshift-ci Bot commented Jun 25, 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 25, 2026
@codecov

codecov Bot commented Jun 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.34%. Comparing base (a9f9002) to head (46e70f8).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10517      +/-   ##
==========================================
- Coverage   44.34%   44.34%   -0.01%     
==========================================
  Files         423      423              
  Lines       73517    73517              
==========================================
- Hits        32602    32600       -2     
- Misses      37984    37985       +1     
- Partials     2931     2932       +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 25, 2026

Copy link
Copy Markdown

@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 46e70f8 link true /test edge-verify-generated-code
ci/prow/verify-generated-code 46e70f8 link true /test verify-generated-code
ci/prow/e2e-agent-compact-ipv4-iso-no-registry 46e70f8 link false /test e2e-agent-compact-ipv4-iso-no-registry

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/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants