Skip to content

openshift/os: update release-4.22 ci-operator config for build-args changes#81971

Open
aaradhak wants to merge 1 commit into
openshift:mainfrom
aaradhak:acs-ar
Open

openshift/os: update release-4.22 ci-operator config for build-args changes#81971
aaradhak wants to merge 1 commit into
openshift:mainfrom
aaradhak:acs-ar

Conversation

@aaradhak

Copy link
Copy Markdown

Backport of #78212 for the release-4.22 branch.

In openshift/os#1946, we're backporting the labels.json and OCI security labels changes which require the Containerfile to use ARG IMAGE_FROM=overridden instead of a hardcoded FROM and to require IMAGE_NAME/IMAGE_CPE build args for RHCOS builds.

Since ci-operator doesn't support build-args files, we need to:

  1. Add ${IMAGE_FROM} to the as list so ci-operator knows to
    replace FROM ${IMAGE_FROM} with the rhel-coreos-base image.

  2. Pass IMAGE_NAME and IMAGE_CPE as explicit build args.

…hanges

Backport of openshift#78212 for the release-4.22 branch.

In openshift/os#1946, the Containerfile changes
from a hardcoded FROM image to using `ARG IMAGE_FROM`. It also adds a
`generate-labels` script that needs IMAGE_NAME and IMAGE_CPE to produce
labels.json and OCI security labels for Clair scanning.

Since ci-operator doesn't support build-args files, we need to:
1. Add `${IMAGE_FROM}` to the `as` list so ci-operator knows to
   replace `FROM ${IMAGE_FROM}` with the rhel-coreos-base image.
2. Pass IMAGE_NAME and IMAGE_CPE as explicit build args.

Both the old FROM value and `${IMAGE_FROM}` are in the `as` list so
that CI works regardless of which PR merges first (this one or openshift#1946).
@openshift-ci
openshift-ci Bot requested review from Rolv-Apneseth and cverna July 15, 2026 19:38
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@aaradhak: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-os-release-4.22-e2e-aws openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-release-4.22-images openshift/os presubmit Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: c1e2612f-23ae-4027-8671-49883030b719

📥 Commits

Reviewing files that changed from the base of the PR and between 028b330 and 2b363af.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/os/openshift-os-release-4.22.yaml

Walkthrough

The OpenShift 4.22 OS release configuration adds image metadata build arguments and expands the rhel-coreos-base input sources with a parameterized image reference.

Changes

OpenShift 4.22 OS release

Layer / File(s) Summary
Image build inputs and metadata
ci-operator/config/openshift/os/openshift-os-release-4.22.yaml
Adds IMAGE_NAME and IMAGE_CPE build arguments and includes ${IMAGE_FROM} alongside the existing fixed rhel-coreos-base source.

Estimated code review effort: 1 (Trivial) | ~2 minutes

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@aaradhak: 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.

@Rolv-Apneseth Rolv-Apneseth left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2026
@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak, Rolv-Apneseth

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

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants