OCPBUGS-83515: use internal shell image for catalog FBC curl Job

[haklein]

This PR replaces the hardcoded image registry.redhat.io/rhel8/httpd-24:latest (445MB) in buildCurlJob() with image.ShellImage(), the node-cached openshift/tools image. A slow pull could exceed the 5-minute test timeout. All six FBC endpoint specs (/v1/api/all and /v1/api/metas for the three openshift catalogs) share buildCurlJob(), this change fixes all of them. No architectural changes.

Testing

• All six specs pass on OpenShift 4.20.17 with a binary from this branch
• Same Job with old image and new image, giving identical curl results.

Fixes OCPBUGS-83515 (https://issues.redhat.com/browse/OCPBUGS-83515)

Summary by CodeRabbit

• Bug Fixes
  • Updated the curl verification job to use the configured shell image, improving compatibility with the deployment environment.

[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: LGTM mode

[openshift-ci-robot]

@haklein: This pull request references Jira Issue OCPBUGS-83515, which is invalid:

• expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This PR replaces the hardcoded image registry.redhat.io/rhel8/httpd-24:latest (445MB) in buildCurlJob() with image.ShellImage(), the node-cached openshift/tools image. A slow pull could exceed the 5-minute test timeout. All six FBC endpoint specs (/v1/api/all and /v1/api/metas for the three openshift catalogs) share buildCurlJob(), this change fixes all of them. No architectural changes.

Testing

• All six specs pass on OpenShift 4.20.17 with a binary from this branch
• Same Job with old image and new image, giving identical curl results.

Fixes OCPBUGS-83515 (https://issues.redhat.com/browse/OCPBUGS-83515)

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: dec4d93d-5e4f-4c44-8ad8-dbe078345aef

📥 Commits

Reviewing files that changed from the base of the PR and between 19afc52 and a71e420.

📒 Files selected for processing (1)

• openshift/tests-extension/test/olmv1-catalog.go

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.

---

Walkthrough

The catalog verification Job changes its api-tester container image from the RHEL8 HTTPD image to the configured shell image.

Changes

Catalog verification Job

Layer / File(s)	Summary
Use configured shell image openshift/tests-extension/test/olmv1-catalog.go	The api-tester container now uses image.ShellImage() instead of registry.redhat.io/rhel8/httpd-24:latest.

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

Merge Risk:⚪ Minimal · up to a71e4

The catalog endpoint test Job now uses the node-cached internal shell image instead of a large external image, reducing pull-timeout risk while preserving curl behavior; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (14 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the catalog FBC curl Job change and the use of the internal shell image.
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 only PR change replaces the Job image; no Ginkgo test title changed. Existing Describe and It titles use static catalog and endpoint text, with dynamic values kept in test bodies.
Test Structure And Quality	✅ Passed	The PR changes only the Job image. Existing endpoint tests retain DeferCleanup, bounded Eventually waits, and diagnostic assertion messages; no stated quality issue is introduced.
Microshift Test Compatibility	✅ Passed	The diff changes only the curl Job image; it adds no Ginkgo tests, so the MicroShift test-compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The diff changes only the curl Job image; it adds no Ginkgo tests and introduces no multi-node or HA assumption.
Topology-Aware Scheduling Compatibility	✅ Passed	The diff changes only the curl Job container image from HTTPD to image.ShellImage(); it adds no scheduling constraints or topology assumptions.
Ote Binary Stdout Contract	✅ Passed	The diff only changes the Job image field. ShellImage() returns a pull spec without stdout output, and buildCurlJob is called from a test case, not process-level setup.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The diff changes only the curl Job image; it adds no Ginkgo tests, IPv4 literals, or external URLs. The curl target remains the ClusterCatalog cluster-internal base URL.
No-Weak-Crypto	✅ Passed	The diff only replaces the curl Job image; it introduces no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret comparison.
Container-Privileges	✅ Passed	The only PR change replaces the Job image; the PodSpec sets no privileged, host namespace, SYS_ADMIN, root-user, or allowPrivilegeEscalation option.
No-Sensitive-Data-In-Logs	✅ Passed	The diff changes only the Job image from a hardcoded HTTPD image to image.ShellImage(); it adds no logging or sensitive-data output. Existing URL logging is unchanged.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

Hi @haklein. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: haklein
Once this PR has been reviewed and has the lgtm label, please assign grokspawn for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[perdasilva]

/ok-to-test

[openshift-ci]

@haklein: 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/verify-commits	a71e420	link	true	/test verify-commits

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.