Skip to content

CORS-4324: Update default release image to 4.22#10429

Open
sadasu wants to merge 1 commit intoopenshift:mainfrom
sadasu:update-release-image
Open

CORS-4324: Update default release image to 4.22#10429
sadasu wants to merge 1 commit intoopenshift:mainfrom
sadasu:update-release-image

Conversation

@sadasu
Copy link
Contributor

@sadasu sadasu commented Mar 24, 2026

No description provided.

@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 24, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 24, 2026

@sadasu: This pull request references CORS-4324 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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
Copy link

coderabbitai bot commented Mar 24, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9b1acc53-f04c-4782-8d6d-6ded45ca06d6

📥 Commits

Reviewing files that changed from the base of the PR and between 883a6d8 and c4c98e6.

📒 Files selected for processing (1)
  • pkg/asset/releaseimage/default.go

Walkthrough

Updated the default embedded release image pullspec constant to reference version 4.22 instead of 4.21. No modifications to control flow, parsing behavior, or error handling.

Changes

Cohort / File(s) Summary
Release Image Version
pkg/asset/releaseimage/default.go
Updated defaultReleaseImageOriginal constant from registry.ci.openshift.org/origin/release:4.21 to registry.ci.openshift.org/origin/release:4.22.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.3)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions


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

@openshift-ci openshift-ci bot requested review from patrickdillon and tthvo March 24, 2026 15:11
Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2026
@patrickdillon
Copy link
Contributor

/approve
for some reason, thuan's didn't take.

This can be verified from the build log from the aws install log. The job hasn't stopped running, but looking at the equivalent here: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_installer/10380/pull-ci-openshift-installer-main-e2e-aws-ovn/2036248697376870400/artifacts/e2e-aws-ovn/ipi-install-install/build-log.txt

that same output in this pr should show 4.22 (shows 4.21 in this run)

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon, tthvo

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 [patrickdillon,tthvo]

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 24, 2026
@tthvo
Copy link
Member

tthvo commented Mar 24, 2026

that same output in this pr should show 4.22 (shows 4.21 in this run)

This run shows the correct 4.22 image 👍

openshift-install v1.4.21-pre-356-gf679218da8c6065cf46bd49287e6e4945971d46b-dirty
built from commit f679218da8c6065cf46bd49287e6e4945971d46b
release image registry.ci.openshift.org/origin/release:4.22

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 24, 2026
@openshift-ci-robot
Copy link
Contributor

@tthvo: This PR has been marked as verified by CI.

Details

In response to this:

that same output in this pr should show 4.22 (shows 4.21 in this run)

This run shows the correct 4.22 image 👍

openshift-install v1.4.21-pre-356-gf679218da8c6065cf46bd49287e6e4945971d46b-dirty
built from commit f679218da8c6065cf46bd49287e6e4945971d46b
release image registry.ci.openshift.org/origin/release:4.22

/verified by CI

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.

@tthvo
Copy link
Member

tthvo commented Mar 24, 2026

/test artifacts-images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

@sadasu: all tests passed!

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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants