Skip to content

Combining ROSA CLI and Terraform Provider periodic jobs#80256

Draft
jerichokeyne wants to merge 1 commit into
openshift:mainfrom
jerichokeyne:reduce_periodics
Draft

Combining ROSA CLI and Terraform Provider periodic jobs#80256
jerichokeyne wants to merge 1 commit into
openshift:mainfrom
jerichokeyne:reduce_periodics

Conversation

@jerichokeyne

@jerichokeyne jerichokeyne commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

ROSACLI:

  • Changing Slack message template to match TF provider jobs
  • All tests targeting production have been removed
    • rosa-sts-advanced-prod-critical-high-f3
    • rosa-hcp-advanced-prod-critical-high-f3
    • rosa-sts-upgrade-y-stream-prod-f3
  • rosa-sts-advanced-critical-high-f3 + rosa-sts-advanced-medium-low-f7 -> rosa-sts-advanced-f3
  • rosa-sts-shared-vpc-critical-high-f3 + rosa-sts-shared-vpc-medium-low-f7 -> rosa-sts-shared-vpc-f3
  • rosa-hcp-shared-vpc-critical-high-f3 + rosa-hcp-shared-vpc-medium-low-f7 -> rosa-hcp-shared-vpc-f3
  • rosa-hcp-external-auth-critical-high-f3 + rosa-hcp-external-auth-medium-low-f7 -> rosa-hcp-external-auth-f3
  • rosa-hcp-advanced-critical-high-f3 + rosa-hcp-advanced-medium-low-f7 -> rosa-hcp-advanced-f3
  • rosa-hcp-private-link-critical-high-f3 -> rosa-hcp-private-link-f3
  • rosa-ocm-resources-f3 + rosa-day1-negative-f7 + rosa-day1-supplemental-f3 -> rosa-extra-f3

Terraform Provider:

  • rosa-sts-advanced-critical-high-f3 + rosa-sts-advanced-medium-low-f7 -> rosa-sts-advanced-f3
  • rosa-sts-private-critical-high-f3 + rosa-sts-private-medium-low-f7 -> rosa-sts-private-f3
  • rosa-hcp-advanced-critical-high-f3 + rosa-hcp-advanced-medium-low-f7 -> rosa-hcp-advanced-f3
  • rosa-hcp-private-critical-high-f3 + rosa-hcp-private-medium-low-f7 -> rosa-hcp-private-f3

Summary by CodeRabbit

This PR consolidates and streamlines the OpenShift CI infrastructure for ROSA (Red Hat OpenShift on AWS) by reducing the number of periodic test jobs across the ROSA CLI and Terraform Provider components.

ROSA CLI Configuration Changes

The openshift-rosa-master__e2e.yaml file (437 lines) undergoes significant restructuring:

  • Removed production environments: Three production-targeted test jobs are removed entirely:

    • rosa-sts-advanced-prod-critical-high-f3
    • rosa-hcp-advanced-prod-critical-high-f3
    • rosa-sts-upgrade-y-stream-prod-f3
  • Merged test jobs: Multiple paired periodic jobs (split between "critical-high" and "medium-low" frequency variants) are consolidated into single jobs:

    • rosa-sts-advanced-critical-high-f3 + rosa-sts-advanced-medium-low-f7rosa-sts-advanced-f3
    • rosa-sts-shared-vpc-critical-high-f3 + rosa-sts-shared-vpc-medium-low-f7rosa-sts-shared-vpc-f3
    • rosa-hcp-shared-vpc-critical-high-f3 + rosa-hcp-shared-vpc-medium-low-f7rosa-hcp-shared-vpc-f3
    • rosa-hcp-external-auth-critical-high-f3 + rosa-hcp-external-auth-medium-low-f7rosa-hcp-external-auth-f3
    • rosa-hcp-advanced-critical-high-f3 + rosa-hcp-advanced-medium-low-f7rosa-hcp-advanced-f3
    • rosa-hcp-private-link-critical-high-f3rosa-hcp-private-link-f3
  • Combined test categories: Three previously separate test jobs are merged into one:

    • rosa-ocm-resources-f3 + rosa-day1-negative-f7 + rosa-day1-supplemental-f3rosa-extra-f3
  • Slack reporting alignment: The reporter configuration is updated to use a standardized Slack message template, aligning with the Terraform Provider's notification format.

Terraform Provider Configuration Changes

The terraform-redhat-terraform-provider-rhcs-main__e2e.yaml file (487 lines) applies similar consolidation:

  • Merged test jobs: Multiple test job pairs are consolidated into single variants:

    • rosa-sts-advanced-critical-high-f3 + rosa-sts-advanced-medium-low-f7rosa-sts-advanced-f3
    • rosa-sts-private-critical-high-f3 + rosa-sts-private-medium-low-f7rosa-sts-private-f3
    • rosa-hcp-advanced-critical-high-f3 + rosa-hcp-advanced-medium-low-f7rosa-hcp-advanced-f3
    • rosa-hcp-private-critical-high-f3 + rosa-hcp-private-medium-low-f7rosa-hcp-private-f3
  • Updated test filters: Case label filters are refined across various test configurations to ensure appropriate test scenarios are executed for each job variant.

Impact

This consolidation reduces operational overhead by reducing the number of periodic jobs that need to be maintained and monitored, while preserving test coverage through merged test configurations. The alignment of Slack message templates between ROSA CLI and Terraform Provider jobs improves consistency in CI/CD notifications.

ROSACLI:
- Changing Slack message template to match TF provider jobs
- All tests targeting production have been removed
    - `rosa-sts-advanced-prod-critical-high-f3`
    - `rosa-hcp-advanced-prod-critical-high-f3`
    - `rosa-sts-upgrade-y-stream-prod-f3`
- `rosa-sts-advanced-critical-high-f3` +
  `rosa-sts-advanced-medium-low-f7` -> `rosa-sts-advanced-f3`
- `rosa-sts-shared-vpc-critical-high-f3` +
  `rosa-sts-shared-vpc-medium-low-f7` -> `rosa-sts-shared-vpc-f3`
- `rosa-hcp-shared-vpc-critical-high-f3` +
  `rosa-hcp-shared-vpc-medium-low-f7` -> `rosa-hcp-shared-vpc-f3`
- `rosa-hcp-external-auth-critical-high-f3` +
  `rosa-hcp-external-auth-medium-low-f7` -> `rosa-hcp-external-auth-f3`
- `rosa-hcp-advanced-critical-high-f3` +
  `rosa-hcp-advanced-medium-low-f7` -> `rosa-hcp-advanced-f3`
- `rosa-hcp-private-link-critical-high-f3` -> `rosa-hcp-private-link-f3`
- `rosa-ocm-resources-f3` + `rosa-day1-negative-f7` +
  `rosa-day1-supplemental-f3` -> `rosa-extra-f3`

Terraform Provider:
- `rosa-sts-advanced-critical-high-f3` +
  `rosa-sts-advanced-medium-low-f7` -> `rosa-sts-advanced-f3`
- `rosa-sts-private-critical-high-f3` + `rosa-sts-private-medium-low-f7`
  -> `rosa-sts-private-f3`
- `rosa-hcp-advanced-critical-high-f3` +
  `rosa-hcp-advanced-medium-low-f7` -> `rosa-hcp-advanced-f3`
- `rosa-hcp-private-critical-high-f3` + `rosa-hcp-private-medium-low-f7`
  -> `rosa-hcp-private-f3`
@openshift-ci

openshift-ci Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 8, 2026
@openshift-ci

openshift-ci Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerichokeyne

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 8, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jerichokeyne: 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-rosa-master-e2e-rosa-sts-upgrade-y-stream-f3 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-upgrade-z-stream-f3 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-hibernation-f14 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-private-link-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-non-sts-advanced-critical-high-f3 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-shared-vpc-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-advanced-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-private-link-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-external-auth-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-shared-vpc-f3 N/A periodic Periodic changed
periodic-ci-terraform-redhat-terraform-provider-rhcs-main-e2e-rosa-hcp-advanced-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-non-sts-upgrade-y-stream-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-advanced-regional-f3 N/A periodic Ci-operator config changed
periodic-ci-terraform-redhat-terraform-provider-rhcs-main-e2e-rosa-hcp-private-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-upgrade-z-stream-f3 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-upgrade-y-stream-f3 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-advanced-f3 N/A periodic Periodic changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-arm-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-shared-vpc-upgrade-y-stream-f3 N/A periodic Ci-operator config changed
periodic-ci-terraform-redhat-terraform-provider-rhcs-main-e2e-rosa-sts-private-f3 N/A periodic Periodic changed
periodic-ci-terraform-redhat-terraform-provider-rhcs-main-e2e-rosa-sts-advanced-f3 N/A periodic Periodic 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 Jun 8, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

Two CI job configuration files for OpenShift ROSA and Terraform provider RHCS are updated: test job variants are consolidated, reporting templates are reformatted to a simpler Slack style, test label filters are tightened, and cluster profiles are adjusted across f3/f7 configurations.

Changes

ROSA and RHCS CI Job Configuration Consolidation

Layer / File(s) Summary
ROSA e2e test job matrix consolidation and reporting update
ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml
ROSA test jobs rename critical/medium-low variants to simpler f3 variants, remove IMPORTANCE fields from most entries, consolidate separate extra/label-filter jobs into a single rosa-extra-f3, and update Slack reporter template formatting to use :slack-green:/:slack-yellow: and {{.Status.URL}} across the full test matrix including upgrade and hibernation jobs.
Terraform provider RHCS test job renaming and filter updates
ci-operator/config/terraform-redhat/terraform-provider-rhcs/terraform-redhat-terraform-provider-rhcs-main__e2e.yaml
RHCS test entries are renamed from critical-high variants to simpler names (rosa-sts-advanced-f3, rosa-hcp-advanced-f3), test blocks are added or adjusted with CASE_LABEL_FILTER tightened to day1-post/day2 combinations, cluster profiles are switched between ada and palomino variants, and QE_USAGE labels are updated across STS and HCP test configurations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • openshift/release#80086: Updates CI job reporter_config.report_template Slack formatting in COO 4.19 periodics, parallel reporting format changes to this PR's ROSA e2e configuration.

Suggested labels

ok-to-test, rehearsals-ack

Suggested reviewers

  • ravitri
  • marcolan018
  • tiwillia
🚥 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 directly and clearly describes the main change: consolidating ROSA CLI and Terraform Provider periodic jobs, which is the core objective of the PR.
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 modifies only Prow CI job configurations and unrelated tool tests, not Ginkgo test code. The check for stable test names is not applicable.
Test Structure And Quality ✅ Passed The PR modifies only Prow CI configuration YAML files, not Ginkgo test code. The custom check requires reviewing Ginkgo test code quality, which is not applicable to this PR.
Microshift Test Compatibility ✅ Passed PR modifies only CI configuration YAML files defining Prow jobs, not new Ginkgo e2e test code. The check applies to new tests, not CI configuration.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR contains only CI job configuration YAML files and utility tools; no new Ginkgo e2e tests are added, making SNO compatibility check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies CI job configuration files (Prow config), not deployment manifests, operator code, or controllers. The topology-aware scheduling check does not apply to CI infrastructure configuration.
Ote Binary Stdout Contract ✅ Passed PR contains only YAML Prow job configuration changes with no test code modifications. OTE Binary Stdout Contract check applies only to test binary code, not CI configuration.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies Prow CI job configuration files only, not Ginkgo test code. No new e2e tests with It(), Describe(), or Context() are added; therefore the check does not apply.
No-Weak-Crypto ✅ Passed PR contains only YAML Prow job configuration changes with no weak cryptography algorithms, custom crypto implementations, or insecure secret comparisons.
Container-Privileges ✅ Passed PR modifies Prow job config files (job scheduling, reporting). No privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings found in modified files.
No-Sensitive-Data-In-Logs ✅ Passed No sensitive data logging found. Modified files are CI job configs with only non-sensitive environment variables and Slack templates that report job status and logs URL.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ 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 and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
ci-operator/config/terraform-redhat/terraform-provider-rhcs/terraform-redhat-terraform-provider-rhcs-main__e2e.yaml (1)

48-74: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Update QE_USAGE to match the renamed job.

The job was renamed to rosa-sts-private-f3 (line 48), but the QE_USAGE label at line 67 still references the old name rosa-sts-private-critical-high-f3. This inconsistency could affect telemetry and usage tracking.

🔧 Proposed fix
       CLUSTER_PROFILE: rosa-sts-pl
-      QE_USAGE: rosa-sts-private-critical-high-f3
+      QE_USAGE: rosa-sts-private-f3
       REGION: us-east-1
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/terraform-redhat/terraform-provider-rhcs/terraform-redhat-terraform-provider-rhcs-main__e2e.yaml`
around lines 48 - 74, Update the QE_USAGE environment variable to match the
renamed job; currently the job is named rosa-sts-private-f3 but QE_USAGE is set
to rosa-sts-private-critical-high-f3. Edit the env block and change QE_USAGE to
rosa-sts-private-f3 (the same value as the job name at the top) so
telemetry/usage tracking is consistent with the job rename; verify the variable
within the steps -> env section where QE_USAGE is defined.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml`:
- Around line 25-432: The PR renames job identifiers in
openshift-rosa-master__e2e.yaml (see changed as: values such as
rosa-sts-advanced-f3, rosa-sts-shared-vpc-f3, rosa-hcp-shared-vpc-f3, etc.), but
the generated CI job artifacts were not updated; run the repository job artifact
regeneration (e.g., invoke the project's update target like make update or the
canonical job generation command) to regenerate the generated jobs from
openshift-rosa-master__e2e.yaml and commit the resulting generated YAMLs so the
ci-operator/jobs output matches the new as: names.

---

Outside diff comments:
In
`@ci-operator/config/terraform-redhat/terraform-provider-rhcs/terraform-redhat-terraform-provider-rhcs-main__e2e.yaml`:
- Around line 48-74: Update the QE_USAGE environment variable to match the
renamed job; currently the job is named rosa-sts-private-f3 but QE_USAGE is set
to rosa-sts-private-critical-high-f3. Edit the env block and change QE_USAGE to
rosa-sts-private-f3 (the same value as the job name at the top) so
telemetry/usage tracking is consistent with the job rename; verify the variable
within the steps -> env section where QE_USAGE is defined.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 0b01ec46-bb5c-4771-bf44-611e30725898

📥 Commits

Reviewing files that changed from the base of the PR and between e1f542b and 5bf3e57.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/rosa/openshift-rosa-master-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/terraform-redhat/terraform-provider-rhcs/terraform-redhat-terraform-provider-rhcs-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml
  • ci-operator/config/terraform-redhat/terraform-provider-rhcs/terraform-redhat-terraform-provider-rhcs-main__e2e.yaml

Comment on lines +25 to +432
- as: rosa-sts-advanced-f3
cron: 34 13 3,6,9,12,15,18,21,24,27,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-sts-f3
TEST_PROFILE: rosa-advanced
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-sts-shared-vpc-f3
cron: 59 0 1,4,7,10,13,16,19,22,25,28 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-sv-f3
TEST_PROFILE: rosa-shared-vpc
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-hcp-shared-vpc-f3
cron: 0 0 1,4,7,10,13,16,19,22,25,28 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
NAME_PREFIX: hcp-sv-f3
TEST_PROFILE: rosa-hcp-shared-vpc-advanced
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-sts-private-link-f3
cron: 27 23 3,6,9,12,15,18,21,24,27,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-pl-f3
TEST_PROFILE: rosa-private-link
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-non-sts-advanced-critical-high-f3
cron: 6 6 3,6,9,12,15,18,21,24,27,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "100"
IMPORTANCE: (Critical,High)
NAME_PREFIX: rosa-nsts-f3
TEST_PROFILE: rosa-non-sts-advanced
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-hcp-external-auth-f3
cron: 31 15 1,4,7,10,13,16,19,22,25,28 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
NAME_PREFIX: rosa-auth-f3
TEST_PROFILE: rosa-hcp-external-auth
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-hcp-advanced-f3
cron: 29 17 1,4,7,10,13,16,19,22,25,28 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
NAME_PREFIX: rosa-hcp-f3
TEST_PROFILE: rosa-hcp-advanced
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-hcp-advanced-regional-f3
cron: 53 17 3,6,8,12,15,18,21,24,27,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
IMPORTANCE: (Critical,High)
NAME_PREFIX: rosa-reghcp-f3
OCM_LOGIN_ENV: https://api.aws.ap-southeast-1.stage.openshift.com
REGION: ap-southeast-1
TEST_PROFILE: rosa-hcp-advanced
VERSION: "4.14"
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-hcp-private-link-f3
cron: 27 19 2,5,8,11,14,17,20,23,26,29 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
NAME_PREFIX: rosa-hcppl-f3
TEST_PROFILE: rosa-hcp-pl
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-hcp-arm-f7
cron: 12 0 9,16,23,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
COMPUTE_MACHINE_TYPE: m6g.xlarge
NAME_PREFIX: rosa-hcparm-f3
TEST_PROFILE: rosa-hcp-advanced
test:
- chain: rosa-tests-e2e-fullcycle
workflow: rosa-lifecycle
- as: rosa-extra-f3
cron: 24 19 2,5,8,11,14,17,20,23,26,29 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
TEST_LABEL_FILTERS: (day1-negative,day1-supplemental,ocm-resources)&&!Exclude
TEST_PROFILE: "null"
test:
- ref: rosa-tests
- ref: rosa-tests-report
- as: rosa-sts-upgrade-z-stream-f3
cron: 32 18 3,6,9,12,15,18,21,24,27,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-upgz-f3
TEST_LABEL_FILTERS: (upgrade)&&!Exclude
TEST_PROFILE: rosa-upgrade-z-stream
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle
- as: rosa-non-sts-upgrade-y-stream-f7
cron: 21 12 6,13,20,29 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "100"
NAME_PREFIX: rosa-upgy-f3
TEST_LABEL_FILTERS: (upgrade)&&!Exclude
TEST_PROFILE: rosa-non-sts-upgrade-y-stream
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle
- as: rosa-sts-shared-vpc-upgrade-y-stream-f3
cron: 0 0 1,4,7,10,13,16,19,22,25,28 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-upgy-f3
TEST_LABEL_FILTERS: (upgrade)&&!Exclude
TEST_PROFILE: rosa-shared-vpc
VERSION: y-1
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle
- as: rosa-sts-upgrade-y-stream-f3
cron: 26 16 2,5,8,11,14,17,20,23,26,29 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-upgy-f3
TEST_LABEL_FILTERS: (upgrade)&&!Exclude
TEST_PROFILE: rosa-upgrade-y-stream
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle
- as: rosa-hcp-upgrade-z-stream-f3
cron: 53 12 3,6,9,12,15,18,21,24,27,30 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
NAME_PREFIX: rosa-hcpz-f3
TEST_LABEL_FILTERS: (upgrade)&&!Exclude
TEST_PROFILE: rosa-hcp-upgrade-z-stream
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle
- as: rosa-hcp-upgrade-y-stream-f3
cron: 42 1 1,4,7,10,13,16,19,22,25,28 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
NAME_PREFIX: rosa-hcpy-f3
TEST_LABEL_FILTERS: (upgrade)&&!Exclude
TEST_PROFILE: rosa-hcp-upgrade-y-stream
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle
- as: rosa-sts-hibernation-f14
cron: 3 18 13,29 * *
reporter_config:
channel: "#ocm-qe-prow-ci-jobs"
job_states_to_report:
- error
- failure
- success
report_template:
'{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}*
ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :slack-yellow:
Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>
{{end}}'
steps:
cluster_profile: oex-aws-qe
env:
CLUSTER_TIMEOUT: "120"
NAME_PREFIX: rosa-hib-f14
TEST_LABEL_FILTERS: (hibernate)&&!Exclude
TEST_PROFILE: rosa-advanced
test:
- ref: rosa-tests
- ref: rosa-tests-report
workflow: rosa-lifecycle

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check if generated ProwJob files exist and were modified for renamed jobs

# Check for generated job files in ci-operator/jobs/ for openshift/rosa
fd -t f -e yaml . ci-operator/jobs/openshift/rosa/ | head -20

# Check git status to see if generated files are staged
git diff --name-only HEAD | rg 'ci-operator/jobs/openshift/rosa'

Repository: openshift/release

Length of output: 271


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Modified generated files (should be non-empty if make update was run):"
git diff --name-only HEAD -- ci-operator/jobs/openshift/rosa/ || true

echo
echo "Diff stat for generated jobs directory:"
git diff --stat HEAD -- ci-operator/jobs/openshift/rosa/ || true

echo
echo "Git status (for context):"
git status --porcelain || true

Repository: openshift/release

Length of output: 200


Regenerate and commit Prow job artifacts after job as: renames

The changes in ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml alter job identifiers (as:), so the generated YAMLs under ci-operator/jobs/openshift/rosa/ must be regenerated with make update and committed. The generated jobs directory has no corresponding updates.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml` around
lines 25 - 432, The PR renames job identifiers in
openshift-rosa-master__e2e.yaml (see changed as: values such as
rosa-sts-advanced-f3, rosa-sts-shared-vpc-f3, rosa-hcp-shared-vpc-f3, etc.), but
the generated CI job artifacts were not updated; run the repository job artifact
regeneration (e.g., invoke the project's update target like make update or the
canonical job generation command) to regenerate the generated jobs from
openshift-rosa-master__e2e.yaml and commit the resulting generated YAMLs so the
ci-operator/jobs output matches the new as: names.

Source: Coding guidelines

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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant