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

[danmanor]

OpenShift updates: 4.20.24 -> 4.20.25, 4.22.0-multi -> 4.22.1-multi, 4.19.33-multi -> 4.19.34-multi, 4.21.19-multi -> 4.21.20-multi, 4.21.19 -> 4.21.20, 4.16.63 -> 4.16.64, 4.19.33 -> 4.19.34, 4.18.43-multi -> 4.18.44-multi, 4.18.43 -> 4.18.44, 4.22.0 -> 4.22.1, 4.20.24-multi -> 4.20.25-multi, 4.16.63-multi -> 4.16.64-multi
RHCOS updates: 4.22.0 -> 5.0.0-ec.3

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

Summary by CodeRabbit

• Updates
  • Added support for OpenShift 5.0 pre-release images (5.0.0-ec.3) across all CPU architectures (x86_64, arm64, ppc64le, s390x).
  • Updated OpenShift 4.x releases to newer patch versions: 4.16.64, 4.18.44, 4.19.34, 4.20.25, 4.21.20, and 4.22.1.

[openshift-ci-robot]

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

Details

In response to this:

OpenShift updates: 4.20.24 -> 4.20.25, 4.22.0-multi -> 4.22.1-multi, 4.19.33-multi -> 4.19.34-multi, 4.21.19-multi -> 4.21.20-multi, 4.21.19 -> 4.21.20, 4.16.63 -> 4.16.64, 4.19.33 -> 4.19.34, 4.18.43-multi -> 4.18.44-multi, 4.18.43 -> 4.18.44, 4.22.0 -> 4.22.1, 4.20.24-multi -> 4.20.25-multi, 4.16.63-multi -> 4.16.64-multi
RHCOS updates: 4.22.0 -> 5.0.0-ec.3

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-19 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-18 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.

[coderabbitai]

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: 912d8082-399a-4747-88d8-121f9423fbcc

📥 Commits

Reviewing files that changed from the base of the PR and between 0880ae6 and 5e92dd2.

📒 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

RHCOS OS image URLs for OpenShift 5.0 entries are updated from 4.22.0-based artifact paths to pre-release/5.0.0-ec.3 paths across all deployment manifests and data files. Separately, release image tags and versions for OpenShift 4.16 through 4.22 are bumped to the next micro release across the same set of files.

Changes

Image Catalog Updates

Layer / File(s)	Summary
RHCOS OS images: 5.0 pre-release URL update data/default_os_images.json, config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml, config/manager/manager.yaml, deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml, deploy/podman/configmap.yml, openshift/template.yaml	The url fields for OpenShift 5.0 RHCOS entries (x86_64, arm64, ppc64le, s390x) are changed from 4.22/4.22.0-based paths to rhcos/pre-release/5.0.0-ec.3 ISO artifact paths in every manifest that embeds the OS image catalog.
Release image micro version bumps (4.16–4.22) data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml	Release image url tags and version values are incremented for 4.16 (63→64), 4.18 (43→44), 4.19 (33→34), 4.20 (24→25), 4.21 (19→20), and 4.22 (0→1) across x86_64, aarch64, and multi architecture variants.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 13 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provides specific version updates and test triggers but lacks coverage of required template sections like issue links, type classification, environment impact, testing approach, and checklist items.	Fill in the structured template sections: classify as Enhancement, specify environment impact, mark testing approach (CI tests triggered), and complete the checklist items to ensure consistency with repository standards.
Topology-Aware Scheduling Compatibility	⚠️ Warning	New file internal/operators/odf/manifest.go introduces nodeAffinity with requiredDuringSchedulingIgnoredDuringExecution targeting only worker nodes, breaking SNO/Two-Node topologies with no dedicat...	ODF manifests must make worker node scheduling optional (preferred affinity) or dynamically check ControlPlaneTopology before applying worker-only constraints to support SNO, Two-Node, and arbiter topologies.

✅ Passed checks (13 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping multiple OCP versions (4.20, 4.19, 4.21, 4.16, 4.22, 4.18) and version 5.0, which directly matches the changeset's primary objective.
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 no Ginkgo test code. All modified files are configuration/data files (YAML, JSON, manifests). Check is not applicable.
Test Structure And Quality	✅ Passed	PR contains only configuration and data file changes (YAML manifests and JSON data). The custom check requires reviewing Ginkgo test code, which is not present in this PR. Check is not applicable.
Microshift Test Compatibility	✅ Passed	This PR only modifies configuration and data files (YAML, JSON) to update OpenShift release and RHCOS image versions. No new Ginkgo e2e tests are added, making the MicroShift test compatibility che...
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only modifies configuration/data files (YAML, JSON) updating OCP/RHCOS versions; no new Ginkgo e2e tests are added, so SNO compatibility check is not applicable.
Ote Binary Stdout Contract	✅ Passed	PR adds configuration/data file updates and service binaries, not OTE binaries that communicate via JSON stdout. No OTE Binary Stdout Contract violations detected.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR adds no Ginkgo e2e tests—only configuration files and data files updating OCP/RHCOS image versions and URLs. Check not applicable.
No-Weak-Crypto	✅ Passed	PR only modifies configuration and data files (YAML, JSON) with version updates; no weak cryptographic algorithms, custom crypto implementations, or insecure secret comparisons are introduced.
Container-Privileges	✅ Passed	PR adds only security-hardening settings (allowPrivilegeEscalation: false, readOnlyRootFilesystem: true), not dangerous privilege escalation settings. No privileged: true, hostPID, hostNetwork, hos...
No-Sensitive-Data-In-Logs	✅ Passed	PR contains only configuration and data file updates (image versions/URLs). No logging code is introduced or modified that could expose sensitive data like passwords, tokens, or API keys.

_{✏️ 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]

[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:

• OWNERS [danmanor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.34%. Comparing base (0880ae6) to head (5e92dd2).

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10484   +/-   ##
=======================================
  Coverage   44.34%   44.34%           
=======================================
  Files         423      423           
  Lines       73512    73512           
=======================================
+ Hits        32596    32599    +3     
+ Misses      37985    37983    -2     
+ Partials     2931     2930    -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.

[gamli75]

/retest-required

[openshift-ci]

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

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]

Closing as duplicate of #10494