Add upi-installer base image to COO periodic 4.20 job

[simonpasquier]

Summary by CodeRabbit

This change adds the upi-installer base image reference to the CI configuration for the rhobs/observability-operator's OpenShift 4.20 Azure-based test job.

What changed:

• Added upi-installer base image to the ci-operator configuration file for the observability-operator's periodic "coo-stage" test job
• The image references OCP 4.20's upi-installer component from the ocp namespace
• This addition supports the existing periodic test that runs every Thursday on Azure infrastructure to validate the cluster observability operator (COO) setup

Impact:
The upi-installer base image is now available for use in the test workflow's build and execution steps, making it a dependency for the COO periodic 4.20 job. This is part of the OpenShift release repository's CI infrastructure configuration, which orchestrates testing across various OpenShift component repositories.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: a06a3c60-d130-481b-b711-f79651aa49cf

📥 Commits

Reviewing files that changed from the base of the PR and between f8d5c5b and 45f48c2.

📒 Files selected for processing (1)

• ci-operator/config/rhobs/observability-operator/rhobs-observability-operator-main__amd64-ocp-4.20-azure.yaml

---

Walkthrough

This change adds a new upi-installer base image configuration entry to the observability-operator CI operator YAML file. The entry references OCP version 4.20 and enables the ci-operator workflow to use the upi-installer container image from the ocp image namespace.

Changes

CI operator base image configuration

Layer / File(s)	Summary
UPI installer base image registration ci-operator/config/rhobs/observability-operator/rhobs-observability-operator-main__amd64-ocp-4.20-azure.yaml	A new upi-installer base image entry is added to reference OCP 4.20, enabling the ci-operator to use the upi-installer image from the ocp namespace.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding a upi-installer base image to a CI configuration for OCP 4.20.
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	The PR modifies a YAML CI operator configuration file, not Ginkgo test code. There are no test names or test titles in the modified file to assess against the stability and determinism requirement.
Test Structure And Quality	✅ Passed	This PR modifies only YAML configuration files and does not contain any Ginkgo test code changes. The custom check for test structure and quality is not applicable.
Microshift Test Compatibility	✅ Passed	PR only modifies CI/CD YAML configuration, not adding any Ginkgo e2e tests; MicroShift test compatibility check is inapplicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies CI configuration (YAML base image reference) and does not add any Ginkgo e2e tests, so the SNO test compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies CI configuration file only, adding a base image reference. Check applies only to deployment manifests, operator code, or controllers; this is neither—no scheduling constraints introduced.
Ote Binary Stdout Contract	✅ Passed	This PR modifies only CI configuration YAML files and documentation. No test code or executable code that could violate the OTE Binary Stdout Contract was changed.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only modifies CI operator YAML configuration to add upi-installer base image reference; no Ginkgo e2e tests are added, making the IPv6/disconnected network compatibility 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

---

_{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: simonpasquier

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:

• ci-operator/config/rhobs/observability-operator/OWNERS [simonpasquier]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@simonpasquier: 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
periodic-ci-rhobs-observability-operator-main-amd64-ocp-4.20-azure-coo-stage	N/A	periodic	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.

[danielmellado]

/pj-rehearse auto-ack

[openshift-merge-bot]

@danielmellado: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@simonpasquier: The following test 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/rehearse/periodic-ci-rhobs-observability-operator-main-amd64-ocp-4.20-azure-coo-stage	45f48c2	link	unknown	/pj-rehearse periodic-ci-rhobs-observability-operator-main-amd64-ocp-4.20-azure-coo-stage

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.