Set OCM_URL=stage for rosa-gap-analysis periodic jobs

[dustman9000]

The gap analysis OCM version gate check (CHECK #7) queries version gates via ocm login which defaults to production. Version gates for pre-GA versions like 5.0 are created in staging first, so CHECK #7 always fails for those versions.

This adds export OCM_URL=stage to all 5 gap analysis periodic jobs so the version gate check queries the correct OCM environment.

Depends on openshift-online/rosa-gap-analysis#68 (adds OCM_URL support to ocm_authenticate()).

Jira: https://redhat.atlassian.net/browse/ROSAENG-62569

Summary by CodeRabbit

Updates all five ROSA gap analysis periodic jobs to export OCM_URL=stage, ensuring version gate checks use the staging OCM environment where pre-GA gates are created.

[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: 956c0b23-8706-46d9-9221-230d2ddbea3c

📥 Commits

Reviewing files that changed from the base of the PR and between 59bcae9 and c3ca776.

📒 Files selected for processing (1)

• ci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main__periodics.yaml

---

Walkthrough

The nightly ROSA gap-analysis periodic commands for OpenShift 4.19 through 5.0 now export OCM_URL=stage after setting the OCM client secret.

Changes

ROSA gap-analysis configuration

Layer / File(s)	Summary
Configure staging OCM endpoint ci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main__periodics.yaml	Adds export OCM_URL=stage to the nightly gap-analysis commands for OpenShift 4.19, 4.20, 4.21, 4.22, and 5.0.

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

Suggested reviewers: chamalabey

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 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: setting OCM_URL=stage for the ROSA gap-analysis periodic jobs.
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	PR only adds OCM_URL exports in a periodic YAML; no Ginkgo test titles or dynamic test names were introduced.
Test Structure And Quality	✅ Passed	Only a ci-operator YAML changed; no Ginkgo test code was touched, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	Only a CI periodic YAML was changed; no Ginkgo tests or OpenShift API/resource references were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo tests were added; the PR only inserts OCM_URL=stage into periodic YAML job commands, so SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Change only exports OCM_URL in periodic test scripts; no deployments, operators, or scheduling constraints were added or modified.
Ote Binary Stdout Contract	✅ Passed	Only ci-operator YAML changed; no process-level OTE binary code or stdout writes were modified.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo tests were added; the PR only updates periodic YAML job commands to export OCM_URL=stage.
No-Weak-Crypto	✅ Passed	Diff only adds OCM_URL=stage to periodic job commands; no weak-crypto, custom crypto, or secret-comparison code was introduced.
Container-Privileges	✅ Passed	The changed YAML only adds OCM_URL=stage in test commands; no privileged:true, hostPID/network/IPC, root, or allowPrivilegeEscalation fields are present.
No-Sensitive-Data-In-Logs	✅ Passed	The PR only adds OCM_URL=stage env exports; it does not add or alter any logging that could expose sensitive data.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@dustman9000: 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-openshift-online-rosa-gap-analysis-main-periodics-nightly-4-22	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-5-0	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-4-19	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-4-20	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-4-21	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.

[dustman9000]

/pj-rehearse periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-5-0

[openshift-merge-bot]

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

[dustman9000]

/pj-rehearse periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-5-0

[openshift-merge-bot]

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

[openshift-ci]

@dustman9000: 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-openshift-online-rosa-gap-analysis-main-periodics-nightly-5-0	c3ca776	link	unknown	/pj-rehearse periodic-ci-openshift-online-rosa-gap-analysis-main-periodics-nightly-5-0

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.

[dustman9000]

/pj-rehearse ack

[openshift-merge-bot]

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

[jfrazierRedHat]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustman9000, jfrazierRedHat

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/openshift-online/rosa-gap-analysis/OWNERS [dustman9000]

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