Skip to content

NO-ISSUE: [master] Bump OCP versions: 4.22, 4.14#9954

Closed
danmanor wants to merge 1 commit intoopenshift:masterfrom
danmanor:bump/ocp-releases-b7b87c93-ae15-4964-8e3d-66607ee8e846
Closed

NO-ISSUE: [master] Bump OCP versions: 4.22, 4.14#9954
danmanor wants to merge 1 commit intoopenshift:masterfrom
danmanor:bump/ocp-releases-b7b87c93-ae15-4964-8e3d-66607ee8e846

Conversation

@danmanor
Copy link
Contributor

@danmanor danmanor commented Mar 3, 2026

OpenShift updates: 4.22.0-ec.2-multi -> 4.22.0-ec.3-multi, 4.14.61 -> 4.14.62, 4.14.61-multi -> 4.14.62-multi, 4.22.0-ec.2 -> 4.22.0-ec.3
RHCOS updates: 4.22.0-ec.2 -> 4.22.0-ec.3

/test edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-14
/cc @rccrdpccl @gamli75

Summary by CodeRabbit

  • Chores
    • Updated RHCOS OS image references from 4.22.0-ec.2 to 4.22.0-ec.3 across all supported architectures (x86_64, arm64, ppc64le, s390x).
    • Updated release image references from 4.14.61 to 4.14.62 for the 4.14 release line, and 4.22.0-ec.2 to 4.22.0-ec.3 for the 4.22 pre-release entries.

@openshift-ci-robot
Copy link

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

Details

In response to this:

OpenShift updates: 4.22.0-ec.2-multi -> 4.22.0-ec.3-multi, 4.14.61 -> 4.14.62, 4.14.61-multi -> 4.14.62-multi, 4.22.0-ec.2 -> 4.22.0-ec.3
RHCOS updates: 4.22.0-ec.2 -> 4.22.0-ec.3

/test edge-e2e-metal-assisted-4-22 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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 3, 2026
@openshift-ci openshift-ci bot requested review from gamli75 and rccrdpccl March 3, 2026 05:31
@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2026

@danmanor: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-agent-compact-ipv4
/test edge-assisted-operator-catalog-publish-verify
/test edge-ci-index
/test edge-e2e-ai-operator-disconnected-capi
/test edge-e2e-ai-operator-ztp
/test edge-e2e-ai-operator-ztp-3masters
/test edge-e2e-ai-operator-ztp-capi
/test edge-e2e-ai-operator-ztp-disconnected
/test edge-e2e-metal-assisted-4-16
/test edge-e2e-metal-assisted-4-17
/test edge-e2e-metal-assisted-4-21
/test edge-e2e-metal-assisted-5-control-planes-4-21
/test edge-e2e-metal-assisted-external-4-21
/test edge-e2e-metal-assisted-lvm-4-21
/test edge-e2e-metal-assisted-none-4-21
/test edge-e2e-metal-assisted-openshift-ai-4-20
/test edge-e2e-metal-assisted-osc-4-21
/test edge-e2e-metal-assisted-virtualization-4-21
/test edge-e2e-metal-assisted-vlan-4-21
/test edge-e2e-vsphere-assisted-4-21
/test edge-images
/test edge-lint
/test edge-operator-publish-verify
/test edge-subsystem-aws
/test edge-subsystem-kubeapi-aws
/test edge-unit-test
/test edge-verify-generated-code
/test images
/test mce-images
/test okd-scos-images
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agent-4control-ipv4
/test e2e-agent-5control-ipv4
/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6
/test edge-e2e-ai-operator-ztp-4masters
/test edge-e2e-ai-operator-ztp-5masters
/test edge-e2e-ai-operator-ztp-compact-day2-masters
/test edge-e2e-ai-operator-ztp-compact-day2-workers
/test edge-e2e-ai-operator-ztp-multiarch-3masters-ocp
/test edge-e2e-ai-operator-ztp-multiarch-sno-ocp
/test edge-e2e-ai-operator-ztp-node-labels
/test edge-e2e-ai-operator-ztp-remove-node
/test edge-e2e-ai-operator-ztp-sno-day2-masters
/test edge-e2e-ai-operator-ztp-sno-day2-workers
/test edge-e2e-ai-operator-ztp-sno-day2-workers-ignitionoverride
/test edge-e2e-ai-operator-ztp-sno-day2-workers-late-binding
/test edge-e2e-metal-assisted-4-control-planes-4-21
/test edge-e2e-metal-assisted-4-masters-none-4-21
/test edge-e2e-metal-assisted-bond-4-21
/test edge-e2e-metal-assisted-day2-4-21
/test edge-e2e-metal-assisted-day2-arm-workers-4-21
/test edge-e2e-metal-assisted-day2-sno-4-21
/test edge-e2e-metal-assisted-dual-primary-v6-compact-4-21
/test edge-e2e-metal-assisted-dual-stack-primary-ipv6-4-21
/test edge-e2e-metal-assisted-ha-kube-api-ipv4-4-21
/test edge-e2e-metal-assisted-ha-kube-api-ipv6-4-21
/test edge-e2e-metal-assisted-ipv4v6-4-21
/test edge-e2e-metal-assisted-ipv6-4-21
/test edge-e2e-metal-assisted-kube-api-late-binding-sno-4-21
/test edge-e2e-metal-assisted-kube-api-late-unbinding-sno-4-21
/test edge-e2e-metal-assisted-kube-api-tna-4-21
/test edge-e2e-metal-assisted-kube-api-umlb-4-21
/test edge-e2e-metal-assisted-onprem-4-21
/test edge-e2e-metal-assisted-osc-sno-4-21
/test edge-e2e-metal-assisted-sno-4-21
/test edge-e2e-metal-assisted-static-ip-suite-4-21
/test edge-e2e-metal-assisted-tang-4-21
/test edge-e2e-metal-assisted-tna-4-21
/test edge-e2e-metal-assisted-tpmv2-4-21
/test edge-e2e-metal-assisted-umlb-4-21
/test edge-e2e-metal-assisted-upgrade-agent-4-21
/test edge-e2e-oci-assisted-4-21
/test edge-e2e-oci-assisted-bm-iscsi-4-21
/test edge-e2e-vsphere-assisted-umlb-4-21
/test edge-e2e-vsphere-assisted-umn-4-21
/test okd-scos-e2e-aws-ovn
/test push-pr-image

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-assisted-service-master-e2e-agent-compact-ipv4
pull-ci-openshift-assisted-service-master-edge-assisted-operator-catalog-publish-verify
pull-ci-openshift-assisted-service-master-edge-ci-index
pull-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-4-21
pull-ci-openshift-assisted-service-master-edge-images
pull-ci-openshift-assisted-service-master-edge-lint
pull-ci-openshift-assisted-service-master-edge-subsystem-aws
pull-ci-openshift-assisted-service-master-edge-subsystem-kubeapi-aws
pull-ci-openshift-assisted-service-master-edge-unit-test
pull-ci-openshift-assisted-service-master-edge-verify-generated-code
pull-ci-openshift-assisted-service-master-images
pull-ci-openshift-assisted-service-master-mce-images
pull-ci-openshift-assisted-service-master-okd-scos-images
pull-ci-openshift-assisted-service-master-verify-deps
Details

In response to this:

OpenShift updates: 4.22.0-ec.2-multi -> 4.22.0-ec.3-multi, 4.14.61 -> 4.14.62, 4.14.61-multi -> 4.14.62-multi, 4.22.0-ec.2 -> 4.22.0-ec.3
RHCOS updates: 4.22.0-ec.2 -> 4.22.0-ec.3

/test edge-e2e-metal-assisted-4-22 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 kubernetes-sigs/prow repository.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 3, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 3, 2026

Walkthrough

The PR updates OpenShift image references across multiple configuration files, bumping RHCOS 4.22 pre-release versions from ec.2 to ec.3 and updating 4.14 release versions from 4.14.61 to 4.14.62 across various architectures.

Changes

Cohort / File(s) Summary
Default Image and Release Data Files
data/default_os_images.json, data/default_release_images.json
Updates pre-release RHCOS 4.22 image URLs from ec.2 to ec.3 for all architectures (x86_64, arm64, ppc64le, s390x). Bumps 4.14 release versions from 4.14.61 to 4.14.62 and corresponding multi entries; version fields updated accordingly.
Configuration Samples
config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml
Updates RHCos image URLs for OpenShift 4.22 pre-release from 4.22.0-ec.2 to 4.22.0-ec.3 across multiple architectures in osImages entries.
Deployment Manifests
deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml, deploy/podman/configmap.yml
Updates RH COS OS image entries from 4.22 ec.2 to ec.3 across architectures; configmap values repositioned with identical content.
Configuration and Template Files
config/manager/manager.yaml, openshift/template.yaml
Formatting and line-level modifications with no semantic or functional changes to OS_IMAGES and RELEASE_IMAGES values.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is incomplete against the template, missing required checklist items, issue categorization, environment impact details, and testing methodology documentation. Complete the description template by selecting appropriate checkboxes (e.g., Enhancement, None for environment impact, No tests needed), marking required items as done, and clarifying testing approach.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically summarizes the main change: bumping OCP versions 4.22 and 4.14 across the codebase.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed PR modifies only configuration files, deployment manifests, and data files (YAML, JSON); no test code files are modified, making test name check not applicable.
Test Structure And Quality ✅ Passed PR contains no test code modifications, only configuration files and JSON data for OCP version bumping. 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
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 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 Mar 3, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
deploy/podman/configmap.yml (1)

25-30: Consider generating these embedded JSON values from a single source of truth.

Keeping large JSON blobs duplicated across manifests is drift-prone; an automated generation step from data/default_os_images.json and data/default_release_images.json would improve maintainability.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@deploy/podman/configmap.yml` around lines 25 - 30, The configmap includes
large embedded JSON blobs in the OS_IMAGES and RELEASE_IMAGES variables which
risk drift; refactor so the manifest is generated from single-source JSON files
(data/default_os_images.json and data/default_release_images.json) during your
build/CI step, update the generator script (or add a new build script referenced
by your Makefile/CI pipeline) to read those files and inject their content into
the ConfigMap template used to produce deploy/podman/configmap.yml, and replace
the hard-coded OS_IMAGES and RELEASE_IMAGES entries with template placeholders
that the generator fills (look for OS_IMAGES and RELEASE_IMAGES in
deploy/podman/configmap.yml and the build/Makefile or CI job that produces
manifests).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@deploy/podman/configmap.yml`:
- Around line 25-30: The configmap includes large embedded JSON blobs in the
OS_IMAGES and RELEASE_IMAGES variables which risk drift; refactor so the
manifest is generated from single-source JSON files (data/default_os_images.json
and data/default_release_images.json) during your build/CI step, update the
generator script (or add a new build script referenced by your Makefile/CI
pipeline) to read those files and inject their content into the ConfigMap
template used to produce deploy/podman/configmap.yml, and replace the hard-coded
OS_IMAGES and RELEASE_IMAGES entries with template placeholders that the
generator fills (look for OS_IMAGES and RELEASE_IMAGES in
deploy/podman/configmap.yml and the build/Makefile or CI job that produces
manifests).

ℹ️ Review info

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 5448b58 and a470ed6.

📒 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

@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 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-e2e-metal-assisted-4-21 a470ed6 link true /test edge-e2e-metal-assisted-4-21
ci/prow/images a470ed6 link true /test images
ci/prow/edge-verify-generated-code a470ed6 link true /test edge-verify-generated-code
ci/prow/edge-ci-index a470ed6 link true /test edge-ci-index
ci/prow/okd-scos-images a470ed6 link true /test okd-scos-images
ci/prow/edge-images a470ed6 link true /test edge-images
ci/prow/edge-unit-test a470ed6 link true /test edge-unit-test
ci/prow/edge-subsystem-kubeapi-aws a470ed6 link true /test edge-subsystem-kubeapi-aws
ci/prow/verify-deps a470ed6 link true /test verify-deps
ci/prow/mce-images a470ed6 link true /test mce-images
ci/prow/edge-assisted-operator-catalog-publish-verify a470ed6 link true /test edge-assisted-operator-catalog-publish-verify
ci/prow/edge-lint a470ed6 link true /test edge-lint
ci/prow/e2e-agent-compact-ipv4 a470ed6 link true /test e2e-agent-compact-ipv4
ci/prow/edge-subsystem-aws a470ed6 link true /test edge-subsystem-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.

@danmanor
Copy link
Contributor Author

danmanor commented Mar 4, 2026

Closing as duplicate of #9968

@danmanor danmanor closed this Mar 4, 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