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

[danmanor]

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

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

Summary by CodeRabbit

• Chores
  • Updated OpenShift 5.0 pre-release OS images to point to correct pre-release mirror locations.
  • Bumped OpenShift release image versions for 4.16 through 4.22 to the latest available patches across all supported CPU architectures.

[openshift-ci-robot]

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

Details

In response to this:

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

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

[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: 94e547f5-9045-4fc7-89a0-985c9ffd5d5d

📥 Commits

Reviewing files that changed from the base of the PR and between a807766 and db9daa3.

📒 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

Two sets of image catalog data are updated across all deployment configurations: OpenShift 5.0 RHCOS OS image URLs are corrected from incorrect 4.22/4.22.0 paths to pre-release/5.0.0-ec.3 paths for all four CPU architectures, and OCP release image tags for versions 4.16 through 4.22 are bumped by one patch version each.

Changes

Image Catalog Updates

Layer / File(s)	Summary
OCP 5.0 OS image URL correction data/default_os_images.json, config/manager/manager.yaml, config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml, deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml, deploy/podman/configmap.yml, openshift/template.yaml	The url fields for openshift_version: "5.0" / openshiftVersion: '5.0' entries for x86_64, arm64, ppc64le, and s390x are changed from rhcos/4.22/4.22.0/... to rhcos/pre-release/5.0.0-ec.3/... in all config surfaces. The version fields remain unchanged.
OCP 4.16–4.22 release image version bumps data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml	Release image url and version fields are incremented by one patch for 4.16 (→4.16.64), 4.18 (→4.18.44), 4.19 (→4.19.34), 4.20 (→4.20.25), 4.21 (→4.21.20), and 4.22 (→4.22.1) across x86_64, arm64/aarch64, and multi architectures.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provides a detailed list of version updates but lacks structured responses to the template's required sections (issue type, testing approach, environment impact, and checklist confirmations).	Complete the description template by selecting appropriate checkboxes for issue type (Enhancement), environment impact, testing method, and checklist items. Add a summary explaining the purpose and impact of these version updates.

✅ Passed checks (14 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: bumping OpenShift versions (4.16-4.22) and 5.0, with specific version numbers listed. It accurately summarizes the primary change across multiple version updates.
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 configuration/data files (YAML, JSON), not test files. No Ginkgo test definitions with unstable/dynamic names were added or modified.
Test Structure And Quality	✅ Passed	PR contains no test code. All 7 modified files are configuration, data, sample, or manifest files (YAML/JSON), not Ginkgo tests. Check is not applicable.
Microshift Test Compatibility	✅ Passed	This PR contains no new Ginkgo e2e tests. It only modifies configuration, data, and manifest files to update OpenShift and RHCOS versions. The custom check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR contains only configuration and data file updates (YAML configs, JSON data, manifests). No Go test files or Ginkgo e2e tests (It(), Describe(), etc.) are added. SNO compatibility check is not ap...
Topology-Aware Scheduling Compatibility	✅ Passed	PR only updates image URLs and versions; no new scheduling constraints, deployment manifests, or topology-specific configuration is introduced.
Ote Binary Stdout Contract	✅ Passed	PR modifies only YAML configuration and JSON data files (7 files total). No Go code changes present; OTE Stdout Contract check applies only to process-level Go code, not configuration files.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR contains no new Ginkgo e2e tests; only configuration and data files are modified (YAML/JSON manifests and templates).
No-Weak-Crypto	✅ Passed	PR only updates OpenShift/RHCOS version numbers in config files. No weak crypto (MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB), custom crypto, or non-constant-time secret comparison code was added.
Container-Privileges	✅ Passed	PR contains only version/URL updates with no privileged container settings (privileged:true, hostPID/Network/IPC, SYS_ADMIN, allowPrivilegeEscalation:true, or root runAsUser) introduced or modified.
No-Sensitive-Data-In-Logs	✅ Passed	PR contains no new logging statements that could expose sensitive data. Changes are limited to version numbers and image URLs in configuration files.

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

[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 (a807766) to head (db9daa3).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10494      +/-   ##
==========================================
- Coverage   44.34%   44.34%   -0.01%     
==========================================
  Files         423      423              
  Lines       73512    73512              
==========================================
- Hits        32599    32597       -2     
- Misses      37983    37984       +1     
- Partials     2930     2931       +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]

@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	db9daa3	link	true	/test verify-generated-code
ci/prow/edge-verify-generated-code	db9daa3	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 #10506