test/e2e: unpin optional-operators fixture from EOL ocp/4.6 integrated stream

[kaovilai]

Note

Responses generated with Claude

Summary

The e2e-oo job has failed on every run since at least February 2026 (job history): the fixture pins tag_specification: ocp/4.6, an EOL integrated stream that configresolver no longer serves, so all four TestOptionalOperators subtests die at ci-operator startup (Ran for 0s):

failed to generate integrated streams: failed to get integrated stream ocp/4.6: got unexpected http 400 status code from configresolver: not a valid integrated stream: ocp/4.6

This means the optional-operators (bundle/index build) path currently has no working e2e coverage.

Changes

• tag_specification bumped ocp/4.6 → ocp/4.20 (verified: https://config.ci.openshift.org/integratedStream?namespace=ocp&name=4.20 returns 200 with 384 tags; 4.6 returns 400).
• The two substitutions whose with: targets were metering components (gone from modern release streams) now point at components present in every current stream — cli and machine-config-operator (both verified present in the ocp/4.20 integrated stream; oauth-proxy already was). Unprefixed names resolve via DependencyParts/ImageStreamFor to stable:<name>, same as before.
• The substitution pullspec: strings are unchanged so they keep matching the CSV under test/manifests/4.6 — the manifest-replacement behavior the suite exercises is preserved.
• base_index (ci/redhat-operator-index:v4.6) and the CSV names asserted by the verify-db-* steps are left untouched: they describe the test's own bundle and base-index content, not the release stream.

Test plan

• YAML-only change; the e2e-oo job triggered on this PR is the real verification (first run able to get past config resolution since the breakage).

Fixes #5333

/cc @droslean

Updates the e2e-oo optional-operators fixture to use the currently served ocp/4.20 stream instead of the obsolete ocp/4.6 (switching tag_specification to name: "4.20"), unblocking ci-operator startup so the optional-operators end-to-end tests can execute. It refreshes the fixture’s substitution mappings in test/e2e/optional-operators/optional-operators.yaml by changing the metering-related origin pullspecs to resolve to with: cli and introducing a substitution that resolves to with: machine-config-operator, while keeping the existing oauth-proxy mapping, the v4.6 base index, and the CSV assertions unchanged.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[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: c059849a-e1c0-4098-86c3-cd776dec9306

📥 Commits

Reviewing files that changed from the base of the PR and between 0239d59 and cdf95e7.

📒 Files selected for processing (1)

• test/e2e/optional-operators/optional-operators.yaml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• openshift/release (manual)
• openshift/ci-docs (manual)
• openshift/release-controller (manual)
• openshift/ci-chat-bot (manual)

---

📝 Walkthrough

Walkthrough

The optional-operators end-to-end fixture updates bundle substitution targets and changes its integrated stream from OpenShift 4.6 to 4.20.

Changes

Optional operators fixture

Layer / File(s)	Summary
Update substitutions and release stream test/e2e/optional-operators/optional-operators.yaml	Updates substitution targets, preserves the oauth-proxy mapping, and changes tag_specification.name from 4.6 to 4.20.

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

Suggested reviewers: copilot

🚥 Pre-merge checks | ✅ 17

✅ Passed checks (17 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: moving the optional-operators fixture off the EOL ocp/4.6 integrated stream.
Linked Issues check	✅ Passed	The change addresses #5333 by updating the fixture from ocp/4.6 to a served stream and adjusting related substitutions for compatibility.
Out of Scope Changes check	✅ Passed	The modified YAML stays within the optional-operators fixture scope and does not introduce unrelated code changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Go Error Handling	✅ Passed	PR only changes a YAML fixture; no Go code or error-handling paths are touched, so the check is not applicable.
Test Coverage For New Features	✅ Passed	Config-only YAML change; no new Go code or pure functions were added, so the test-coverage requirement doesn’t apply.
Stable And Deterministic Test Names	✅ Passed	PR only changes a YAML fixture; no Ginkgo It/Describe/Context/When titles were added or edited, so there are no unstable test names.
Test Structure And Quality	✅ Passed	PR only updates a YAML ci-operator fixture; it does not add/modify any Ginkgo It blocks, Eventually calls, or test setup/cleanup code to assess.
Microshift Test Compatibility	✅ Passed	Only a YAML fixture changed; no new Ginkgo tests, labels, or API-using test logic were added, so the MicroShift check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The PR only updates a YAML fixture; no new It/Describe tests or SNO-sensitive topology assumptions were added.
Topology-Aware Scheduling Compatibility	✅ Passed	Only an e2e fixture YAML changed; it updates image-stream tags/substitutions and adds no pod specs, affinity, nodeSelectors, or topology-sensitive scheduling rules.
Ote Binary Stdout Contract	✅ Passed	Only a YAML fixture changed; no binary code, init/main, or suite setup stdout paths were modified.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Fixture-only change; no new Ginkgo tests or IPv4/public-internet assumptions were added. Existing github.com/grpcurl download predates this PR.
No-Weak-Crypto	✅ Passed	YAML-only fixture update; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons were introduced.
Container-Privileges	✅ Passed	The changed YAML only updates stream/substitution values; no privileged, host*, SYS_ADMIN, or allowPrivilegeEscalation settings are present.
No-Sensitive-Data-In-Logs	✅ Passed	No added logs or sensitive literals found; the fixture only updates test inputs and shell commands with public component names and URLs.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[Copilot]

Pull request overview

Updates the optional-operators e2e fixture to use a currently-served OCP integrated stream so the e2e-oo job can resolve tag_specification again and actually exercise the bundle/index build flow.

Changes:

• Bumps tag_specification from ocp/4.6 (EOL/unserved) to ocp/4.20.
• Repoints operator manifest pullspec substitutions away from removed metering components to images expected to exist in modern streams (cli, machine-config-operator), while keeping the substituted pullspec strings the same.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: droslean, kaovilai

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 [droslean]

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

[droslean]

Thanks for the fix Tiger!

[openshift-ci]

New changes are detected. LGTM label has been removed.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[kaovilai]

/retest

[openshift-ci]

@kaovilai: 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/prow/integration	cdf95e7	link	true	/test integration

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.