prowgen: migrate slack_reporter from .config.prowgen to per-test reporter_config#78976
Merged
openshift-merge-bot[bot] merged 2 commits intoMay 13, 2026
Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughReplace many repo-level Prowgen ChangesReporter migration — remove global reporters
Reporter migration — add per-job reporter_config
Small unrelated CI edits bundled with reporter work
Estimated code review effort Suggested labels ✨ Finishing Touches🧪 Generate unit tests (beta)
|
Member
Author
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
openshift-ci
Bot
added
the
approved
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
ci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.20-lp-interop.yaml (1)
108-114:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAlign FIPS ODF version vars with the OCP 4.20 job target.
Line 108 now tags this as
4.20, but Line 113 and Line 114 still pin ODF tostable-4.19/"4.19". That mismatch can produce invalid 4.20 signal for this lane.Proposed fix
- ODF_OPERATOR_CHANNEL: stable-4.19 - ODF_VERSION_MAJOR_MINOR: "4.19" + ODF_OPERATOR_CHANNEL: stable-4.20 + ODF_VERSION_MAJOR_MINOR: "4.20"🤖 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/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.20-lp-interop.yaml` around lines 108 - 114, The ODF version variables are inconsistent with the OCP target: update ODF_OPERATOR_CHANNEL (currently ODF_OPERATOR_CHANNEL: stable-4.19) and ODF_VERSION_MAJOR_MINOR (currently ODF_VERSION_MAJOR_MINOR: "4.19") to match OCP_VERSION "4.20" by setting ODF_OPERATOR_CHANNEL to stable-4.20 and ODF_VERSION_MAJOR_MINOR to "4.20" so the FIREWATCH/OCP signals are consistent with the 4.20 job target.ci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-interop.yaml (1)
66-90:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win
camel-k-interop-ibmcloudis missing itsreporter_configblock.Every other analogous
camel-k-interop-ibmcloudtest in this PR (OCP 4.14, 4.15) receives areporter_configblock. This test will silently lose Slack notification coverage once.config.prowgenis removed.🐛 Proposed fix
workflow: firewatch-ipi-ibmcloud + reporter_config: + channel: '#camel-k-notifications' + job_states_to_report: + - success + - failure + - error + report_template: '{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}' zz_generated_metadata:🤖 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/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-interop.yaml` around lines 66 - 90, The job entry for camel-k-interop-ibmcloud is missing a reporter_config block, so add a reporter_config section to the camel-k-interop-ibmcloud job (the same place other OCP 4.14/4.15 camel-k-interop-ibmcloud jobs define it) to restore Slack notification coverage; mirror the reporter_config keys/values used by the analogous 4.14/4.15 entries (same reporter_config structure, channels and labels) and ensure it lives alongside the existing env/FIREWATCH_* settings so notifications continue after .config.prowgen removal.ci-operator/config/codeready-toolchain/toolchain-e2e/codeready-toolchain-toolchain-e2e-master.yaml (1)
66-69:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd
reporter_configtoci-daily-prodfor Slack notifications.The migration from
.config.prowgento per-testreporter_configleftci-daily-prodwithout notification configuration. Its siblingci-dailyhasreporter_configpointing to#sandbox-ci-reports, butci-daily-prod(the production daily job) has none. This inconsistency could cause production failures to go unreported.🤖 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/codeready-toolchain/toolchain-e2e/codeready-toolchain-toolchain-e2e-master.yaml` around lines 66 - 69, The job entry named ci-daily-prod is missing a reporter_config so it won't send Slack notifications; update the ci-daily-prod block to include reporter_config with the same value used by its sibling ci-daily (pointing to `#sandbox-ci-reports`) so production daily failures are reported to Slack. Locate the ci-daily-prod job definition and add reporter_config: "#sandbox-ci-reports" (matching the ci-daily configuration) under its top-level keys alongside cron and steps.ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yaml (1)
48-706:⚠️ Potential issue | 🟠 MajorAdd
reporter_configto all 16 remaining tests for consistent coverage.This file has partial reporter coverage: 33 of 49 tests include
reporter_configfor Slack notifications. The following 16 tests are missing reporter configuration and will not report job failures to#team-qe-agent-prow:
- vsphere-agent-sno-vcf9-f7
- vsphere-agent-ha-vcf9-f7
- vsphere-agent-compact-fips-vcf9-f7
- oci-agent-baremetal-ha-iscsi-f14
- oci-agent-baremetal-5cp-iscsi-f60
- oci-agent-baremetal-sno-iscsi-f14
- oci-agent-baremetal-compact-iscsi-f14
- oci-agent-vm-ha-f14
- oci-agent-vm-sno-f14
- oci-agent-vm-compact-f14
- nutanix-agent-sno-f28
- nutanix-agent-compact-fips-f28
- nutanix-agent-ha-f28
- nutanix-agent-disc-compact-f60
- baremetal-ove-compact-agent-ipv4-disc-f60
- baremetal-ove-compact-disc-konflux
This pattern is also present in other related files (4.18 amd64: 44/48, 4.20 amd64: 33/48), suggesting a systematic gap. Apply reporter configuration consistently across all test jobs.
🤖 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-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yaml` around lines 48 - 706, Multiple jobs are missing the reporter_config block so failures won't be posted to `#team-qe-agent-prow`; add the same reporter_config used elsewhere (channel: '#team-qe-agent-prow', job_states_to_report: [failure, error], report_template: "Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check") to each of the 16 jobs identified by their as: identifiers (e.g. vsphere-agent-sno-vcf9-f7, vsphere-agent-ha-vcf9-f7, vsphere-agent-compact-fips-vcf9-f7, oci-agent-baremetal-ha-iscsi-f14, oci-agent-baremetal-5cp-iscsi-f60, oci-agent-baremetal-sno-iscsi-f14, oci-agent-baremetal-compact-iscsi-f14, oci-agent-vm-ha-f14, oci-agent-vm-sno-f14, oci-agent-vm-compact-f14, nutanix-agent-sno-f28, nutanix-agent-compact-fips-f28, nutanix-agent-ha-f28, nutanix-agent-disc-compact-f60, baremetal-ove-compact-agent-ipv4-disc-f60, baremetal-ove-compact-disc-konflux) and ensure the same addition is applied to the equivalent 4.18 and 4.20 amd64 files to maintain consistency.
🤖 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/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.14-lp-interop.yaml`:
- Line 57: The Slack channel value for the YAML key `channel` is inconsistent:
change the current value `#camel-quarkus-qe` to `#team-camel-quarkus-qe` so the
`channel` key in this LP interop variant matches the other variants and routes
alerts to the same Slack channel.
In
`@ci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.17-lp-interop.yaml`:
- Around line 41-47: The report_template under reporter_config uses AWS-style
emojis (:slack-green:/:failed:) but this job's cluster_profile
(ibmcloud-cspi-qe) should use the IBM Cloud convention; update the
report_template in this file (reporter_config -> report_template) to use
:success: for the success branch and :dumpster-fire: for the non-success branch
so it matches the other ocp4.{14,15,16} IBM Cloud variants.
In
`@ci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yaml`:
- Around line 88-94: The IBM Cloud job variant mta-interop-ibmcloud is missing a
reporter_config block so Slack notifications will stop; add a reporter_config
for the mta-interop-ibmcloud job mirroring the mta-interop-aws settings (include
channel '#mta-interop', job_states_to_report entries success, failure, error,
and the same report_template) so that reporter_config, job_states_to_report and
report_template are present for the mta-interop-ibmcloud job.
In
`@ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml`:
- Around line 896-901: The report_template string in reporter_config contains a
stray "{{end}}" which causes a Go template parse error; open the
reporter_config.report_template value and remove the trailing "{{end}}" so the
template becomes ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs> `@cnv-hco`' (leave the other template fields
.Spec.Job, .Status.State, .Status.URL unchanged).
In
`@ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__amd64-stable.yaml`:
- Around line 100-105: The job "baremetal-ove-compact-agent-ipv4-disc-f60" is
missing the reporter_config block so it won't send failure/error Slack reports;
add a reporter_config section identical to the file's other tests (including
channel, job_states_to_report with failure and error, and the report_template
string) under the baremetal-ove-compact-agent-ipv4-disc-f60 job definition to
restore Slack reporting.
In
`@ci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.20__periodics.yaml`:
- Around line 28-29: The report_template block currently includes literal
leading and trailing apostrophes inside the block scalar which become part of
the Slack message; change the block scalar to use an unquoted literal form with
strip indicator (use report_template: |-) and remove the surrounding apostrophes
so the message body is unquoted (e.g. start the template text directly with
:red_jenkins_circle: Job ...) to avoid sending extraneous apostrophes and to
suppress the trailing newline.
In
`@ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.21-nightly-x86.yaml`:
- Around line 31-37: The Slack reporter configuration for channel
'#ocp-qe-scale-ci-results' lost the explicit job_names whitelist; update the
reporter_config block (the reporter_config object for channel
'#ocp-qe-scale-ci-results') to include a job_names list containing the missing
jobs: add aws-4.21: control-plane-fips-120nodes; aws-4.22:
control-plane-fips-120nodes; rosa-4.23: build-farm-114nodes,
control-plane-120nodes, control-plane-24nodes, data-path-9nodes,
node-density-heavy-24nodes so those tests receive notifications, preserving the
existing channel, job_states_to_report and report_template values.
---
Outside diff comments:
In
`@ci-operator/config/codeready-toolchain/toolchain-e2e/codeready-toolchain-toolchain-e2e-master.yaml`:
- Around line 66-69: The job entry named ci-daily-prod is missing a
reporter_config so it won't send Slack notifications; update the ci-daily-prod
block to include reporter_config with the same value used by its sibling
ci-daily (pointing to `#sandbox-ci-reports`) so production daily failures are
reported to Slack. Locate the ci-daily-prod job definition and add
reporter_config: "#sandbox-ci-reports" (matching the ci-daily configuration)
under its top-level keys alongside cron and steps.
In
`@ci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-interop.yaml`:
- Around line 66-90: The job entry for camel-k-interop-ibmcloud is missing a
reporter_config block, so add a reporter_config section to the
camel-k-interop-ibmcloud job (the same place other OCP 4.14/4.15
camel-k-interop-ibmcloud jobs define it) to restore Slack notification coverage;
mirror the reporter_config keys/values used by the analogous 4.14/4.15 entries
(same reporter_config structure, channels and labels) and ensure it lives
alongside the existing env/FIREWATCH_* settings so notifications continue after
.config.prowgen removal.
In
`@ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yaml`:
- Around line 48-706: Multiple jobs are missing the reporter_config block so
failures won't be posted to `#team-qe-agent-prow`; add the same reporter_config
used elsewhere (channel: '#team-qe-agent-prow', job_states_to_report: [failure,
error], report_template: "Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check") to each of the
16 jobs identified by their as: identifiers (e.g. vsphere-agent-sno-vcf9-f7,
vsphere-agent-ha-vcf9-f7, vsphere-agent-compact-fips-vcf9-f7,
oci-agent-baremetal-ha-iscsi-f14, oci-agent-baremetal-5cp-iscsi-f60,
oci-agent-baremetal-sno-iscsi-f14, oci-agent-baremetal-compact-iscsi-f14,
oci-agent-vm-ha-f14, oci-agent-vm-sno-f14, oci-agent-vm-compact-f14,
nutanix-agent-sno-f28, nutanix-agent-compact-fips-f28, nutanix-agent-ha-f28,
nutanix-agent-disc-compact-f60, baremetal-ove-compact-agent-ipv4-disc-f60,
baremetal-ove-compact-disc-konflux) and ensure the same addition is applied to
the equivalent 4.18 and 4.20 amd64 files to maintain consistency.
In
`@ci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.20-lp-interop.yaml`:
- Around line 108-114: The ODF version variables are inconsistent with the OCP
target: update ODF_OPERATOR_CHANNEL (currently ODF_OPERATOR_CHANNEL:
stable-4.19) and ODF_VERSION_MAJOR_MINOR (currently ODF_VERSION_MAJOR_MINOR:
"4.19") to match OCP_VERSION "4.20" by setting ODF_OPERATOR_CHANNEL to
stable-4.20 and ODF_VERSION_MAJOR_MINOR to "4.20" so the FIREWATCH/OCP signals
are consistent with the 4.20 job target.
🪄 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: 356d3cee-c583-4210-92c1-30ed5f327c26
📒 Files selected for processing (300)
ci-operator/config/3scale-qe/3scale-deploy/.config.prowgenci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.13-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.14-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.14-lp-rosa-classic.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.15-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.16-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.16-lp-rosa-classic.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.17-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.17-lp-rosa-classic.yamlci-operator/config/Apicurio/.config.prowgenci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.14-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.15-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.16-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.17-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.18-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.19-lp-interop.yamlci-operator/config/Azure/ARO-HCP/.config.prowgenci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__e2e.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__image-updater.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__periodic-cleanup.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__periodic.yamlci-operator/config/RedHatQE/interop-testing/.config.prowgenci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__acm-cnv-ocp-4.21-p2p.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__acm-cnv-ocp4.20-p2p-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.20-lp-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.21-lp-interop-cr.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp4.19-lp-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp4.20-konflux.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__gs-baremetal-localnet-ocp4.19-lp-gs.yamlci-operator/config/amq-streams-qe/strimzi-kafka-operator/.config.prowgenci-operator/config/amq-streams-qe/strimzi-kafka-operator/amq-streams-qe-strimzi-kafka-operator-main__amq-streams-ocp4.17-lp-interop.yamlci-operator/config/amq-streams-qe/strimzi-kafka-operator/amq-streams-qe-strimzi-kafka-operator-main__amq-streams-ocp4.18-lp-interop.yamlci-operator/config/amq-streams-qe/strimzi-kafka-operator/amq-streams-qe-strimzi-kafka-operator-main__amq-streams-ocp4.19-lp-interop.yamlci-operator/config/ansible/tower-qa/.config.prowgenci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.13-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.14-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.15-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.16-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.17-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.18-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.19-lp-interop.yamlci-operator/config/codeready-toolchain/toolchain-e2e/.config.prowgenci-operator/config/codeready-toolchain/toolchain-e2e/codeready-toolchain-toolchain-e2e-master.yamlci-operator/config/cri-o/cri-o/.config.prowgenci-operator/config/cri-o/cri-o/cri-o-cri-o-main__periodics.yamlci-operator/config/infinispan/infinispan-operator/.config.prowgenci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.13-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.14-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.15-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.16-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.17-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.18-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.19-lp-interop.yamlci-operator/config/insights-onprem/cost-onprem-chart/.config.prowgenci-operator/config/insights-onprem/cost-onprem-chart/insights-onprem-cost-onprem-chart-main__periodics.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/.config.prowgenci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.14-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.15-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.16-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.17-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.18-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.19-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.20-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/.config.prowgenci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.14-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.15-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.16-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.17-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.18-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/.config.prowgenci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.14-lp-rosa-classic.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-rosa-classic.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.17-lp-rosa-classic.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.18-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.20-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/.config.prowgenci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/.config.prowgenci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.18-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/.config.prowgenci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.18-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.19-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/.config.prowgenci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.14-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.15-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.16-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.17-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.18-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.19-lp-interop.yamlci-operator/config/kata-containers/kata-containers/.config.prowgenci-operator/config/kata-containers/kata-containers/kata-containers-kata-containers-main.yamlci-operator/config/kiegroup/kie-cloud-tests-container/.config.prowgenci-operator/config/kiegroup/kie-cloud-tests-container/kiegroup-kie-cloud-tests-container-main__rhba-ocp4.14-lp-interop.yamlci-operator/config/kiegroup/kie-cloud-tests-container/kiegroup-kie-cloud-tests-container-main__rhba-ocp4.15-lp-interop.yamlci-operator/config/kiegroup/kie-cloud-tests-container/kiegroup-kie-cloud-tests-container-main__rhba-ocp4.16-lp-interop.yamlci-operator/config/konflux-ci/konflux-ci/.config.prowgenci-operator/config/konflux-ci/konflux-ci/konflux-ci-konflux-ci-main__ocp420-arm64.yamlci-operator/config/konflux-ci/konflux-ci/konflux-ci-konflux-ci-main__ocp420.yamlci-operator/config/konveyor/tackle-ui-tests/.config.prowgenci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.16-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.18-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_8.0.0__mta-ocp-4.21-lp-interop-cr.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-release-0.6__mta-ocp4.19-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-release-0.7__mta-ocp4.20-lp-interop.yamlci-operator/config/konveyor/tackle2-ui/.config.prowgenci-operator/config/konveyor/tackle2-ui/konveyor-tackle2-ui-release-0.8__mta-ocp-4.21-lp-interop-cr.yamlci-operator/config/konveyor/tackle2-ui/konveyor-tackle2-ui-release-0.8__mta-ocp-4.21-lp-interop.yamlci-operator/config/kubevirt/hyperconverged-cluster-operator/.config.prowgenci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yamlci-operator/config/maistra/test-infra/.config.prowgenci-operator/config/maistra/test-infra/maistra-test-infra-main.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/.config.prowgenci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.14-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.14-lp-rosa-classic.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.14-lp-rosa-hypershift.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.15-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.15-lp-rosa-hypershift.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.16-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.16-lp-rosa-classic.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.16-lp-rosa-hypershift.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.17-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.17-lp-rosa-classic.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.18-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.19-lp-interop.yamlci-operator/config/oadp-qe/oadp-qe-automation/.config.prowgenci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-main__oadp1.4-ocp4.17-lp-interop.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-main__oadp1.4-ocp4.17-lp-rosa-classic.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-oadp-1.4__oadp1.4-ocp4.18-lp-interop.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-oadp-1.5__oadp1.5-ocp-4.21-lp-interop-cr.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-oadp-1.5__oadp1.5-ocp4.20-lp-interop.yamlci-operator/config/opendatahub-io/notebooks/.config.prowgenci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yamlci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023b.yamlci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2024a.yamlci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2024b.yamlci-operator/config/openshift-eng/agent-qe-infra/.config.prowgenci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-extended-support-4.12__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-extended-support-4.14__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__multi-nightly.yamlci-operator/config/openshift-eng/baremetal-qe-infra/.config.prowgenci-operator/config/openshift-eng/baremetal-qe-infra/openshift-eng-baremetal-qe-infra-monitoring.yamlci-operator/config/openshift-eng/edge-tooling/.config.prowgenci-operator/config/openshift-eng/edge-tooling/openshift-eng-edge-tooling-main.yamlci-operator/config/openshift-eng/ocp-build-data/.config.prowgenci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.12__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.13__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.14__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.15__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.16__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.17__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.18__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.19__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.20__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.21__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.22__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.23__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-5.0__periodics.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/.config.prowgenci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.23-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-5.0-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__cloud-governance.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__gcp-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__gcp-4.23-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__gcp-5.0-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.19-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.20-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-rhoso-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.23-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa_hcp-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa_hcp-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa_hcp-4.23-nightly-x86.yamlci-operator/config/openshift-hyperfleet/hyperfleet-e2e/.config.prowgenci-operator/config/openshift-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-main__e2e.yamlci-operator/config/openshift-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-release-0.2__e2e.yamlci-operator/config/openshift-knative/eventing-istio/.config.prowgenci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-next__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-next__420.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.15__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.15__420.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.16__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.16__420.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.17__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.21__416.yamlci-operator/config/openshift-knative/eventing-kafka-broker/.config.prowgenci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-next__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-next__420.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.15__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.15__420.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.16__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.16__420.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.17__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.21__416.yamlci-operator/config/openshift-knative/eventing/.config.prowgenci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-next__414.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-next__420.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.15__413.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.15__420.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.16__414.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.16__420.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.17__414.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.21__416.yamlci-operator/config/openshift-knative/kn-plugin-event/.config.prowgenci-operator/config/openshift-knative/kn-plugin-event/openshift-knative-kn-plugin-event-release-1.15__420.yamlci-operator/config/openshift-knative/kn-plugin-event/openshift-knative-kn-plugin-event-release-1.16__420.yamlci-operator/config/openshift-knative/serverless-operator/.config.prowgenci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.21-techpreview.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-aws-ovn.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-azure.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-gcp.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-hypershift.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-single-node.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-vsphere.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-release-1.37__ocp-4.22-lp-interop.yamlci-operator/config/openshift-knative/serving/.config.prowgenci-operator/config/openshift-knative/serving/openshift-knative-serving-release-next__414.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-next__420.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.15__413.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.15__420.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.16__414.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.16__420.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.17__414.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.21__416.yamlci-operator/config/openshift-kni/eco-ci-cd-private/.config.prowgenci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__performance-dell.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-container-tests-project1.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-container-tests-project2.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-gitlab-project2-site3.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-lab-oran-o2ims-compliance-tests.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-lab.yamlci-operator/config/openshift-kni/eco-ci-cd/.config.prowgenci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__ci-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-hcp-nrop-4.19.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-hcp-nrop-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-hcp-nrop-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.19.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.22.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.23.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-5.0.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__compute-nto.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.18.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.19.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.22.yaml
💤 Files with no reviewable changes (39)
- ci-operator/config/kiegroup/kie-cloud-tests-container/.config.prowgen
- ci-operator/config/openshift-eng/edge-tooling/.config.prowgen
- ci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/.config.prowgen
- ci-operator/config/3scale-qe/3scale-deploy/.config.prowgen
- ci-operator/config/infinispan/infinispan-operator/.config.prowgen
- ci-operator/config/kubevirt/hyperconverged-cluster-operator/.config.prowgen
- ci-operator/config/jws-qe/interop-ocp-ci/.config.prowgen
- ci-operator/config/amq-streams-qe/strimzi-kafka-operator/.config.prowgen
- ci-operator/config/konveyor/tackle2-ui/.config.prowgen
- ci-operator/config/cri-o/cri-o/.config.prowgen
- ci-operator/config/Apicurio/.config.prowgen
- ci-operator/config/openshift-eng/agent-qe-infra/.config.prowgen
- ci-operator/config/openshift-knative/eventing/.config.prowgen
- ci-operator/config/jboss-fuse/fuse-xpaas-qe-container/.config.prowgen
- ci-operator/config/openshift-knative/serving/.config.prowgen
- ci-operator/config/jboss-fuse/csb-tnb-tests-container/.config.prowgen
- ci-operator/config/codeready-toolchain/toolchain-e2e/.config.prowgen
- ci-operator/config/insights-onprem/cost-onprem-chart/.config.prowgen
- ci-operator/config/maistra/test-infra/.config.prowgen
- ci-operator/config/jboss-eap-qe/openshift-eap-tests/.config.prowgen
- ci-operator/config/konveyor/tackle-ui-tests/.config.prowgen
- ci-operator/config/insights-qe/iqe-cost-management-plugin/.config.prowgen
- ci-operator/config/openshift-knative/eventing-kafka-broker/.config.prowgen
- ci-operator/config/openshift-knative/kn-plugin-event/.config.prowgen
- ci-operator/config/openshift-eng/ocp-build-data/.config.prowgen
- ci-operator/config/openshift-eng/baremetal-qe-infra/.config.prowgen
- ci-operator/config/openshift-knative/serverless-operator/.config.prowgen
- ci-operator/config/openshift-hyperfleet/hyperfleet-e2e/.config.prowgen
- ci-operator/config/openshift-knative/eventing-istio/.config.prowgen
- ci-operator/config/opendatahub-io/notebooks/.config.prowgen
- ci-operator/config/jboss-fuse/camel-k-test-container/.config.prowgen
- ci-operator/config/mtc-qe/mtc-e2e-qev2/.config.prowgen
- ci-operator/config/konflux-ci/konflux-ci/.config.prowgen
- ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/.config.prowgen
- ci-operator/config/ansible/tower-qa/.config.prowgen
- ci-operator/config/Azure/ARO-HCP/.config.prowgen
- ci-operator/config/kata-containers/kata-containers/.config.prowgen
- ci-operator/config/oadp-qe/oadp-qe-automation/.config.prowgen
- ci-operator/config/RedHatQE/interop-testing/.config.prowgen
| - ref: camel-quarkus-execute-tests | ||
| workflow: firewatch-ipi-ibmcloud | ||
| reporter_config: | ||
| channel: '#camel-quarkus-qe' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify channel consistency across LP interop variants in this repo slice.
rg -n --type=yaml '^\s*channel:\s*' \
ci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/*camel-quarkus-ocp4.*-lp-interop.yamlRepository: openshift/release
Length of output: 1196
Align Slack channel with other LP interop variants.
Line 57 uses #camel-quarkus-qe, but all other LP interop variants (4.19, 4.17, 4.16, 4.15) use #team-camel-quarkus-qe. This inconsistency will route 4.14 alerts to a different channel. Update to #team-camel-quarkus-qe for consistency.
🤖 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/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.14-lp-interop.yaml`
at line 57, The Slack channel value for the YAML key `channel` is inconsistent:
change the current value `#camel-quarkus-qe` to `#team-camel-quarkus-qe` so the
`channel` key in this LP interop variant matches the other variants and routes
alerts to the same Slack channel.
Comment on lines
+41
to
+47
| reporter_config: | ||
| channel: '#csb-qe' | ||
| job_states_to_report: | ||
| - success | ||
| - failure | ||
| - error | ||
| report_template: '{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}' |
Contributor
There was a problem hiding this comment.
Emoji inconsistency with sibling IBM Cloud variants.
This file uses cluster_profile: ibmcloud-cspi-qe, matching the ocp4.14, 4.15, and 4.16 variants — all of which use :success:/:dumpster-fire: in their report_template. This file uses :slack-green:/:failed:, which matches the AWS (aws-cspi-qe) variants instead. This looks like the template was copied from an AWS variant rather than an IBM Cloud one.
🐛 Proposed fix to align with the IBM Cloud series convention
- report_template: '{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}'
+ report_template: '{{if eq .Status.State "success"}} :success: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :dumpster-fire: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}'🤖 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/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.17-lp-interop.yaml`
around lines 41 - 47, The report_template under reporter_config uses AWS-style
emojis (:slack-green:/:failed:) but this job's cluster_profile
(ibmcloud-cspi-qe) should use the IBM Cloud convention; update the
report_template in this file (reporter_config -> report_template) to use
:success: for the success branch and :dumpster-fire: for the non-success branch
so it matches the other ocp4.{14,15,16} IBM Cloud variants.
Comment on lines
+88
to
+94
| reporter_config: | ||
| channel: '#mta-interop' | ||
| job_states_to_report: | ||
| - success | ||
| - failure | ||
| - error | ||
| report_template: '{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}' |
Contributor
There was a problem hiding this comment.
Potential reporting gap: only AWS test got migrated.
Line 88 adds reporter_config for mta-interop-aws, but mta-interop-ibmcloud (Lines 30-57) has no equivalent block. That can drop Slack notifications for the IBM Cloud variant after removing shared prowgen config.
Proposed patch
- as: mta-interop-ibmcloud
cron: 0 23 31 2 *
steps:
@@
- ref: mta-tests-ui
workflow: firewatch-ipi-ibmcloud
+ reporter_config:
+ channel: '#mta-interop'
+ job_states_to_report:
+ - success
+ - failure
+ - error
+ report_template: '{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}'
- as: mta-interop-aws🤖 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/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yaml`
around lines 88 - 94, The IBM Cloud job variant mta-interop-ibmcloud is missing
a reporter_config block so Slack notifications will stop; add a reporter_config
for the mta-interop-ibmcloud job mirroring the mta-interop-aws settings (include
channel '#mta-interop', job_states_to_report entries success, failure, error,
and the same report_template) so that reporter_config, job_states_to_report and
report_template are present for the mta-interop-ibmcloud job.
Comment on lines
+896
to
+901
| reporter_config: | ||
| channel: '#forum-cnv-hyperconverged-cluster-operator' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}} @cnv-hco' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check if {{end}} appears in report_template values across reporter_config blocks
# in the kubevirt/hyperconverged-cluster-operator config files, and also sample other
# reporter_config additions in the broader release repo to assess if this is systematic.
echo "=== reporter_config blocks with {{end}} in kubevirt/hyperconverged-cluster-operator ==="
rg -n 'report_template.*\{\{end\}\}' ci-operator/config/kubevirt/
echo ""
echo "=== reporter_config blocks WITHOUT {{end}} in kubevirt/hyperconverged-cluster-operator ==="
rg -n 'report_template' ci-operator/config/kubevirt/ | grep -v '{{end}}'
echo ""
echo "=== All report_template occurrences across entire ci-operator/config tree (sample) ==="
rg -n 'report_template.*\{\{end\}\}' ci-operator/config/ | head -30
echo ""
echo "=== Check if .config.prowgen for this repo still exists and has report_template ==="
fd -e yaml 'kubevirt-hyperconverged-cluster-operator' ci-operator/config/kubevirt/ --exec grep -l 'reporter_config\|report_template'
echo ""
echo "=== Look for any remaining .config.prowgen files with slack_reporter/report_template ==="
fd '.config.prowgen' ci-operator/config/kubevirt/ --exec grep -l 'slack_reporter\|report_template'Repository: openshift/release
Length of output: 14087
Remove stray {{end}} from report_template — will cause Go template parse error
Line 901 contains a malformed Go template: a bare {{end}} with no matching {{if}}, {{range}}, {{with}}, or {{define}} opener in the same template string.
report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}} `@cnv-hco`'This will fail at parse time with "unexpected {{end}}" and prevent Slack notifications from rendering. The {{end}} should be removed:
Proposed fix
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}} `@cnv-hco`'
+ report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> `@cnv-hco`'Other report_template instances across the codebase follow proper Go template syntax (e.g., {{if}} ... {{else}} ... {{end}}), confirming this is an error specific to this file.
🤖 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/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml`
around lines 896 - 901, The report_template string in reporter_config contains a
stray "{{end}}" which causes a Go template parse error; open the
reporter_config.report_template value and remove the trailing "{{end}}" so the
template becomes ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs> `@cnv-hco`' (leave the other template fields
.Spec.Job, .Status.State, .Status.URL unchanged).
Comment on lines
+28
to
+29
| report_template: | | ||
| ':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify occurrences where block-scalar report_template lines are still wrapped in apostrophes.
rg -nP --type=yaml '^\s*report_template:\s*\|\-?\s*$' -A1 \
-g 'ci-operator/config/openshift-eng/ocp-build-data/*__periodics.yaml'
rg -nP --type=yaml "^\s*':red_jenkins_circle:.*'\s*$" \
-g 'ci-operator/config/openshift-eng/ocp-build-data/*__periodics.yaml'Repository: openshift/release
Length of output: 7556
Remove literal apostrophes from report_template block scalar.
Line 29 is inside a | block scalar, so the apostrophes become part of the literal message body sent to Slack. Use unquoted text and |- to suppress the trailing newline.
Suggested fix
- report_template: |
- ':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>'
+ report_template: |-
+ :red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>Note: This same issue exists in all version files (4.12–4.23, 5.0) in this directory.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| report_template: | | |
| ':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>' | |
| report_template: |- | |
| :red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> |
🤖 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-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.20__periodics.yaml`
around lines 28 - 29, The report_template block currently includes literal
leading and trailing apostrophes inside the block scalar which become part of
the Slack message; change the block scalar to use an unquoted literal form with
strip indicator (use report_template: |-) and remove the surrounding apostrophes
so the message body is unquoted (e.g. start the template text directly with
:red_jenkins_circle: Job ...) to avoid sending extraneous apostrophes and to
suppress the trailing newline.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
ci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yaml (1)
30-57:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win
mta-interop-ibmcloudis missing itsreporter_configblock.The prior
.config.prowgen-levelslack_reportercovered all tests in the repo, includingmta-interop-ibmcloud. After this migration onlymta-interop-aws(lines 88–94) gets the per-testreporter_config;mta-interop-ibmcloudsilently loses Slack notifications. The siblingkonveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.16-lp-interop.yamlappliesreporter_configto both its ibmcloud and aws entries — the same pattern should apply here.🐛 Proposed fix — add `reporter_config` after `workflow: firewatch-ipi-ibmcloud`
workflow: firewatch-ipi-ibmcloud + reporter_config: + channel: '#mta-interop' + job_states_to_report: + - success + - failure + - error + report_template: '{{if eq .Status.State "success"}} :slack-green: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{else}} :failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}}' - as: mta-interop-aws🤖 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/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yaml` around lines 30 - 57, The mta-interop-ibmcloud job (identifier "mta-interop-ibmcloud") is missing a reporter_config block so it no longer sends Slack notifications; add a reporter_config block immediately after the line "workflow: firewatch-ipi-ibmcloud" mirroring the reporter_config used by the sibling mta-interop-aws entry (use the same Slack reporter settings/labels used on lines ~88–94) so the IBM Cloud job regains the same Slack reporting behavior.ci-operator/config/maistra/test-infra/maistra-test-infra-main.yaml (1)
109-130:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd
reporter_configto theupdate-istio-builder-imageperiodic job.The
update-istio-builder-imagejob (line 109) is a cron periodic but lacks areporter_configfield, while other periodic jobs in the same file (sync-upstream-envoy-2.4,sync-upstream-istio-2.4) have it. This inconsistency should be resolved to ensure consistent failure notifications.🤖 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/maistra/test-infra/maistra-test-infra-main.yaml` around lines 109 - 130, The periodic job update-istio-builder-image is missing a reporter_config block; add a reporter_config entry to that job (the job beginning with "as: update-istio-builder-image") matching the reporter_config used by other periodic jobs like sync-upstream-envoy-2.4/sync-upstream-istio-2.4 so it sends failure notifications consistently (copy the same keys/values from those jobs into the update-istio-builder-image job).ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yaml (1)
557-584:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd
reporter_configto four tests or document why they are intentionally excluded.Four tests in this file are missing
reporter_config:
vsphere-agent-sno-vcf9-f7(Line 557)vsphere-agent-ha-vcf9-f7(Line 566)vsphere-agent-compact-fips-vcf9-f7(Line 575)oci-agent-baremetal-5cp-iscsi-f60(Line 639)The other OCI tests in this file (e.g.,
oci-agent-baremetal-ha-iscsi-f28,oci-agent-vm-ha-f28) and other vSphere tests (e.g.,vsphere-agent-compact-fips-f28,vsphere-agent-ha-f28) do havereporter_config. Since.config.prowgenwas deleted, these four will lose Slack notifications unless you add the reporter config or explicitly document the intent.🤖 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-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yaml` around lines 557 - 584, The four job entries vsphere-agent-sno-vcf9-f7, vsphere-agent-ha-vcf9-f7, vsphere-agent-compact-fips-vcf9-f7 and oci-agent-baremetal-5cp-iscsi-f60 are missing reporter_config and will lose Slack notifications; update each job block to include a reporter_config stanza matching the existing pattern used by other jobs (e.g., same reporter_config keys/channel/notify settings as oci-agent-baremetal-ha-iscsi-f28 or vsphere-agent-compact-fips-f28) or add an adjacent comment documenting why notifications are intentionally omitted; locate the job by the workflow names cucushift-agent-vsphere-install-sno / cucushift-agent-vsphere-install-ha / cucushift-agent-vsphere-install-compact and the OCI job name to apply the change.ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yaml (1)
707-890:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winOCI f14 tests missing
reporter_configdespite having it in 4.18 equivalents.16 tests lack
reporter_config:
vsphere-agent-{sno,ha,compact-fips}-vcf9-f7(Lines 707–734)oci-agent-baremetal-{ha,sno,compact}-iscsi-f14+5cp-iscsi-f60(Lines 735–761)oci-agent-vm-{ha,sno,compact}-f14(Lines 783–814)nutanix-agent-*(Lines 815–852)baremetal-ove-*(Lines 853–890)Notable regression: In
release-4.18__amd64-nightly.yaml, OCI f28 variants (oci-agent-baremetal-ha-iscsi-f28,oci-agent-vm-ha-f28, etc.) all havereporter_config. The 4.21 file replaces f28 with more-frequent f14 runs on the same platforms, but those f14 tests lackreporter_configentirely.The vcf9 tests were also missing in 4.18, so they are not a new gap. The nutanix and baremetal-ove tests are new to 4.21.
Clarify whether the OCI f14 tests should inherit the f28 variants'
reporter_config, or if alerts were intentionally dropped for this higher-frequency cadence.🤖 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-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yaml` around lines 707 - 890, Several job entries (vsphere-agent-sno/ha/compact-fips-vcf9-f7, oci-agent-baremetal-{ha,5cp,sno,compact}-iscsi-f14, oci-agent-vm-{ha,sno,compact}-f14, nutanix-agent-*, and baremetal-ove-* jobs) are missing reporter_config; restore the missing reporter_config by adding the same reporter_config stanza used by the equivalent release-4.18 f28 OCI jobs (or the existing f28 templates) into each job definition (refer to symbols like workflow: cucushift-agent-vsphere-install-sno, cucushift-agent-oci, agent-qe-nutanix, agent-qe-nutanix-disconnected, agent-qe-baremetal-install-ove-disconnected and agent-qe-baremetal-install-ove-disconnected-konflux) so alerts are enabled consistently—copy the reporter_config block from the 4.18 jobs and paste into these 4.21 job entries, or confirm intentionally omitted alerts and document that decision.
🧹 Nitpick comments (3)
ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.18-lp-interop.yaml (1)
45-47: ⚡ Quick winConsider adding
aborttojob_states_to_report.
abortis a valid Prow job state (e.g., jobs manually cancelled or pre-empted). Omitting it means aborted interop runs will silently produce no Slack notification. If parity with the original.config.prowgenslack_reporteris desired, verify whetherabortwas included there. This applies to all 7 OCP variant files in this PR.🔧 Proposed addition
job_states_to_report: - failure - error + - abortedAlso applies to: 75-77
🤖 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/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.18-lp-interop.yaml` around lines 45 - 47, Add the missing 'abort' job state to the job_states_to_report list so aborted Prow jobs generate Slack notifications; update the job_states_to_report entries (symbol: job_states_to_report) in this and the other six OCP variant YAMLs to include abort alongside failure and error, and confirm parity with the original .config.prowgen slack_reporter configuration (symbol: slack_reporter) to ensure all expected states are covered.ci-operator/config/openshift-eng/edge-tooling/openshift-eng-edge-tooling-main.yaml (2)
136-139: ⚡ Quick win
>folded scalar collapses multi-line template — consider|for intended line breaksWith
>(YAML folded scalar), the three lines in this block are joined with spaces into a single string::ai-intensifies: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <gcs-url|View report> <{{.Status.URL}}|View logs>Both Slack links end up on the same line. If the intent is to have "View report" and "View logs" on separate lines in the Slack message, use
|(literal block scalar) instead:✏️ Proposed fix
- report_template: > - :ai-intensifies: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. - <https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/{{.Spec.Job}}/{{.Status.BuildID}}/artifacts/microshift-ci-doctor/openshift-edge-tooling-microshift-ci-doctor/artifacts/microshift-ci-doctor-report.html|View report> - <{{.Status.URL}}|View logs> + report_template: | + :ai-intensifies: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. + <https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/{{.Spec.Job}}/{{.Status.BuildID}}/artifacts/microshift-ci-doctor/openshift-edge-tooling-microshift-ci-doctor/artifacts/microshift-ci-doctor-report.html|View report> + <{{.Status.URL}}|View logs>If both links on a single line is intentional (e.g., matching the format used across the 916 migrated files), this is fine as-is.
🤖 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-eng/edge-tooling/openshift-eng-edge-tooling-main.yaml` around lines 136 - 139, The report_template is using a folded scalar ('>') which collapses line breaks; change the scalar indicator to a literal block ('|') for report_template so the three template lines (the message plus the "View report" and "View logs" links) are preserved on separate lines in the resulting Slack message, i.e., replace the leading '>' on the report_template value with '|' so the lines remain distinct.
138-138: 💤 Low valueHardcoded workflow name and artifact sub-path in GCS URL
The URL at line 138 hardcodes both the workflow name (
openshift-edge-tooling-microshift-ci-doctor) and the artifact path structure. If the workflow is renamed or the artifact layout changes, this link will silently produce a 404 without any config-level indication of the breakage.There is no immediate fix without dynamic Go-template support for artifact paths, but this is worth a comment so the path is kept in sync with the actual workflow definition.
🤖 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-eng/edge-tooling/openshift-eng-edge-tooling-main.yaml` at line 138, The GCS URL hardcodes the workflow name "openshift-edge-tooling-microshift-ci-doctor" and artifact sub-path, which will break silently if the workflow or artifact layout changes; add a clear inline comment directly above this URL string noting that the path is brittle, must be kept in sync with the workflow/artifact layout, and should be replaced with a Go-template or job-derived variable when dynamic artifact path support is available so maintainers know to update it if they rename or restructure the workflow.
🤖 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/Azure/ARO-HCP/Azure-ARO-HCP-main.yaml`:
- Around line 233-238: The three integration jobs e2e-parallel-ocp-stable,
e2e-parallel-ocp-fast, and e2e-parallel-ocp-nightly are missing the
reporter_config block causing parity gaps; add a reporter_config to each
integration job matching the existing block (use reporter_config with channel:
'#aro-hcp-failures-int', job_states_to_report: [failure, error], and the same
report_template ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs>') so integration alerts mirror stage/prod, or
alternatively add an explicit comment/documentation next to those job
definitions explaining the intentional omission.
In
`@ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml`:
- Line 901: The report_template value contains a stray Go template terminator
"{{end}}" with no matching opening block; remove that dangling "{{end}}" from
the report_template string (the value assigned to report_template in the
kubevirt-hyperconverged-cluster-operator-main.yaml) so the template becomes a
valid Go template and Slack notifications can be rendered correctly.
In
`@ci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yaml`:
- Around line 284-307: The template's branch gating uses hardcoded
$active_release and $previous_release ("2024b"/"2024a") so .Spec.Refs.BaseRef
never matches for this 2023a postsubmit; update the two variables in the
report_template (the $active_release and $previous_release assignments) to the
actual release refs this config targets (e.g., replace "2024b"/"2024a" with
"2023a" and the appropriate sibling release) so the if-check against
.Spec.Refs.BaseRef follows the correct branch path and enables the subteam
mention/failure-specific logic.
In
`@ci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023b.yaml`:
- Around line 288-311: The branch gating constants in
reporter_config.report_template are wrong for this release: update the
$active_release and $previous_release variables (currently "2024b" and "2024a")
to the release branches this file is for (e.g., set $active_release to "2023b"
and $previous_release to "2023a") so the if condition that controls $emoji and
$group_tag (and thus the subteam mention and failure-vs-error formatting) will
match correctly; verify the variables near the top of the template where
$active_release and $previous_release are declared and keep the rest of the
template logic unchanged.
In
`@ci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.18__periodics.yaml`:
- Around line 28-29: The YAML block literal for report_template currently
includes literal single-quote characters around the Slack message; remove the
leading and trailing single quotes so the value of report_template is exactly
:red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs> (update all occurrences of the report_template key
in the 13 files), ensuring no extra quotes remain in the block scalar and
preserving the existing interpolation tokens {{.Spec.Job}}, {{.Status.State}},
and {{.Status.URL}}.
---
Outside diff comments:
In
`@ci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yaml`:
- Around line 30-57: The mta-interop-ibmcloud job (identifier
"mta-interop-ibmcloud") is missing a reporter_config block so it no longer sends
Slack notifications; add a reporter_config block immediately after the line
"workflow: firewatch-ipi-ibmcloud" mirroring the reporter_config used by the
sibling mta-interop-aws entry (use the same Slack reporter settings/labels used
on lines ~88–94) so the IBM Cloud job regains the same Slack reporting behavior.
In `@ci-operator/config/maistra/test-infra/maistra-test-infra-main.yaml`:
- Around line 109-130: The periodic job update-istio-builder-image is missing a
reporter_config block; add a reporter_config entry to that job (the job
beginning with "as: update-istio-builder-image") matching the reporter_config
used by other periodic jobs like sync-upstream-envoy-2.4/sync-upstream-istio-2.4
so it sends failure notifications consistently (copy the same keys/values from
those jobs into the update-istio-builder-image job).
In
`@ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yaml`:
- Around line 557-584: The four job entries vsphere-agent-sno-vcf9-f7,
vsphere-agent-ha-vcf9-f7, vsphere-agent-compact-fips-vcf9-f7 and
oci-agent-baremetal-5cp-iscsi-f60 are missing reporter_config and will lose
Slack notifications; update each job block to include a reporter_config stanza
matching the existing pattern used by other jobs (e.g., same reporter_config
keys/channel/notify settings as oci-agent-baremetal-ha-iscsi-f28 or
vsphere-agent-compact-fips-f28) or add an adjacent comment documenting why
notifications are intentionally omitted; locate the job by the workflow names
cucushift-agent-vsphere-install-sno / cucushift-agent-vsphere-install-ha /
cucushift-agent-vsphere-install-compact and the OCI job name to apply the
change.
In
`@ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yaml`:
- Around line 707-890: Several job entries
(vsphere-agent-sno/ha/compact-fips-vcf9-f7,
oci-agent-baremetal-{ha,5cp,sno,compact}-iscsi-f14,
oci-agent-vm-{ha,sno,compact}-f14, nutanix-agent-*, and baremetal-ove-* jobs)
are missing reporter_config; restore the missing reporter_config by adding the
same reporter_config stanza used by the equivalent release-4.18 f28 OCI jobs (or
the existing f28 templates) into each job definition (refer to symbols like
workflow: cucushift-agent-vsphere-install-sno, cucushift-agent-oci,
agent-qe-nutanix, agent-qe-nutanix-disconnected,
agent-qe-baremetal-install-ove-disconnected and
agent-qe-baremetal-install-ove-disconnected-konflux) so alerts are enabled
consistently—copy the reporter_config block from the 4.18 jobs and paste into
these 4.21 job entries, or confirm intentionally omitted alerts and document
that decision.
---
Nitpick comments:
In
`@ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.18-lp-interop.yaml`:
- Around line 45-47: Add the missing 'abort' job state to the
job_states_to_report list so aborted Prow jobs generate Slack notifications;
update the job_states_to_report entries (symbol: job_states_to_report) in this
and the other six OCP variant YAMLs to include abort alongside failure and
error, and confirm parity with the original .config.prowgen slack_reporter
configuration (symbol: slack_reporter) to ensure all expected states are
covered.
In
`@ci-operator/config/openshift-eng/edge-tooling/openshift-eng-edge-tooling-main.yaml`:
- Around line 136-139: The report_template is using a folded scalar ('>') which
collapses line breaks; change the scalar indicator to a literal block ('|') for
report_template so the three template lines (the message plus the "View report"
and "View logs" links) are preserved on separate lines in the resulting Slack
message, i.e., replace the leading '>' on the report_template value with '|' so
the lines remain distinct.
- Line 138: The GCS URL hardcodes the workflow name
"openshift-edge-tooling-microshift-ci-doctor" and artifact sub-path, which will
break silently if the workflow or artifact layout changes; add a clear inline
comment directly above this URL string noting that the path is brittle, must be
kept in sync with the workflow/artifact layout, and should be replaced with a
Go-template or job-derived variable when dynamic artifact path support is
available so maintainers know to update it if they rename or restructure the
workflow.
🪄 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: d15ca55d-5e97-40e3-867a-2493779c6e2b
📒 Files selected for processing (300)
ci-operator/config/3scale-qe/3scale-deploy/.config.prowgenci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.13-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.14-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.14-lp-rosa-classic.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.15-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.16-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.16-lp-rosa-classic.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.17-lp-interop.yamlci-operator/config/3scale-qe/3scale-deploy/3scale-qe-3scale-deploy-main__3scale-amp-ocp4.17-lp-rosa-classic.yamlci-operator/config/Apicurio/.config.prowgenci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.14-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.15-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.16-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.17-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.18-lp-interop.yamlci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.19-lp-interop.yamlci-operator/config/Azure/ARO-HCP/.config.prowgenci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__e2e.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__image-updater.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__periodic-cleanup.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__periodic.yamlci-operator/config/RedHatQE/interop-testing/.config.prowgenci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__acm-cnv-ocp-4.21-p2p.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__acm-cnv-ocp4.20-p2p-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.20-lp-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.21-lp-interop-cr.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp4.19-lp-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp4.20-konflux.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__gs-baremetal-localnet-ocp4.19-lp-gs.yamlci-operator/config/amq-streams-qe/strimzi-kafka-operator/.config.prowgenci-operator/config/amq-streams-qe/strimzi-kafka-operator/amq-streams-qe-strimzi-kafka-operator-main__amq-streams-ocp4.17-lp-interop.yamlci-operator/config/amq-streams-qe/strimzi-kafka-operator/amq-streams-qe-strimzi-kafka-operator-main__amq-streams-ocp4.18-lp-interop.yamlci-operator/config/amq-streams-qe/strimzi-kafka-operator/amq-streams-qe-strimzi-kafka-operator-main__amq-streams-ocp4.19-lp-interop.yamlci-operator/config/ansible/tower-qa/.config.prowgenci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.13-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.14-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.15-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.16-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.17-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.18-lp-interop.yamlci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.19-lp-interop.yamlci-operator/config/codeready-toolchain/toolchain-e2e/.config.prowgenci-operator/config/codeready-toolchain/toolchain-e2e/codeready-toolchain-toolchain-e2e-master.yamlci-operator/config/cri-o/cri-o/.config.prowgenci-operator/config/cri-o/cri-o/cri-o-cri-o-main__periodics.yamlci-operator/config/infinispan/infinispan-operator/.config.prowgenci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.13-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.14-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.15-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.16-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.17-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.18-lp-interop.yamlci-operator/config/infinispan/infinispan-operator/infinispan-infinispan-operator-stable__data-grid-ocp4.19-lp-interop.yamlci-operator/config/insights-onprem/cost-onprem-chart/.config.prowgenci-operator/config/insights-onprem/cost-onprem-chart/insights-onprem-cost-onprem-chart-main__periodics.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/.config.prowgenci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.14-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.15-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.16-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.17-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.18-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.19-lp-interop.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.20-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/.config.prowgenci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.14-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.15-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.16-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.17-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.18-lp-interop.yamlci-operator/config/jboss-eap-qe/openshift-eap-tests/jboss-eap-qe-openshift-eap-tests-pit-7.4.x__eap-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/.config.prowgenci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.14-lp-rosa-classic.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.16-lp-rosa-classic.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.17-lp-rosa-classic.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.18-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/camel-k-test-container/jboss-fuse-camel-k-test-container-main__camel-k-ocp4.20-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/.config.prowgenci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/jboss-fuse-camel-quarkus-openshift-interop-main__camel-quarkus-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/.config.prowgenci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.18-lp-interop.yamlci-operator/config/jboss-fuse/csb-tnb-tests-container/jboss-fuse-csb-tnb-tests-container-main__csb-ocp4.19-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/.config.prowgenci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.14-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.15-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.16-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.17-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.18-lp-interop.yamlci-operator/config/jboss-fuse/fuse-xpaas-qe-container/jboss-fuse-fuse-xpaas-qe-container-main__jboss-fuse-ocp4.19-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/.config.prowgenci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.14-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.15-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.16-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.17-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.18-lp-interop.yamlci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.19-lp-interop.yamlci-operator/config/kata-containers/kata-containers/.config.prowgenci-operator/config/kata-containers/kata-containers/kata-containers-kata-containers-main.yamlci-operator/config/kiegroup/kie-cloud-tests-container/.config.prowgenci-operator/config/kiegroup/kie-cloud-tests-container/kiegroup-kie-cloud-tests-container-main__rhba-ocp4.14-lp-interop.yamlci-operator/config/kiegroup/kie-cloud-tests-container/kiegroup-kie-cloud-tests-container-main__rhba-ocp4.15-lp-interop.yamlci-operator/config/kiegroup/kie-cloud-tests-container/kiegroup-kie-cloud-tests-container-main__rhba-ocp4.16-lp-interop.yamlci-operator/config/konflux-ci/konflux-ci/.config.prowgenci-operator/config/konflux-ci/konflux-ci/konflux-ci-konflux-ci-main__ocp420-arm64.yamlci-operator/config/konflux-ci/konflux-ci/konflux-ci-konflux-ci-main__ocp420.yamlci-operator/config/konveyor/tackle-ui-tests/.config.prowgenci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.16-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.17-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_7.2.0__mta-ocp4.18-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-mta_8.0.0__mta-ocp-4.21-lp-interop-cr.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-release-0.6__mta-ocp4.19-lp-interop.yamlci-operator/config/konveyor/tackle-ui-tests/konveyor-tackle-ui-tests-release-0.7__mta-ocp4.20-lp-interop.yamlci-operator/config/konveyor/tackle2-ui/.config.prowgenci-operator/config/konveyor/tackle2-ui/konveyor-tackle2-ui-release-0.8__mta-ocp-4.21-lp-interop-cr.yamlci-operator/config/konveyor/tackle2-ui/konveyor-tackle2-ui-release-0.8__mta-ocp-4.21-lp-interop.yamlci-operator/config/kubevirt/hyperconverged-cluster-operator/.config.prowgenci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yamlci-operator/config/maistra/test-infra/.config.prowgenci-operator/config/maistra/test-infra/maistra-test-infra-main.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/.config.prowgenci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.14-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.14-lp-rosa-classic.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.14-lp-rosa-hypershift.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.15-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.15-lp-rosa-hypershift.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.16-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.16-lp-rosa-classic.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.16-lp-rosa-hypershift.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.17-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.17-lp-rosa-classic.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.18-lp-interop.yamlci-operator/config/mtc-qe/mtc-e2e-qev2/mtc-qe-mtc-e2e-qev2-master__mtc1.8-ocp4.19-lp-interop.yamlci-operator/config/oadp-qe/oadp-qe-automation/.config.prowgenci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-main__oadp1.4-ocp4.17-lp-interop.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-main__oadp1.4-ocp4.17-lp-rosa-classic.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-oadp-1.4__oadp1.4-ocp4.18-lp-interop.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-oadp-1.5__oadp1.5-ocp-4.21-lp-interop-cr.yamlci-operator/config/oadp-qe/oadp-qe-automation/oadp-qe-oadp-qe-automation-oadp-1.5__oadp1.5-ocp4.20-lp-interop.yamlci-operator/config/opendatahub-io/notebooks/.config.prowgenci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yamlci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023b.yamlci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2024a.yamlci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2024b.yamlci-operator/config/openshift-eng/agent-qe-infra/.config.prowgenci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-extended-support-4.12__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-extended-support-4.14__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.16__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.17__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.19__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__amd64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__arm64-stable.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.20__multi-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__amd64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__arm64-nightly.yamlci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.21__multi-nightly.yamlci-operator/config/openshift-eng/baremetal-qe-infra/.config.prowgenci-operator/config/openshift-eng/baremetal-qe-infra/openshift-eng-baremetal-qe-infra-monitoring.yamlci-operator/config/openshift-eng/edge-tooling/.config.prowgenci-operator/config/openshift-eng/edge-tooling/openshift-eng-edge-tooling-main.yamlci-operator/config/openshift-eng/ocp-build-data/.config.prowgenci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.12__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.13__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.14__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.15__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.16__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.17__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.18__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.19__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.20__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.21__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.22__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.23__periodics.yamlci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-5.0__periodics.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/.config.prowgenci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-4.23-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__aws-5.0-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__cloud-governance.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__gcp-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__gcp-4.23-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__gcp-5.0-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.19-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.20-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-rhoso-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.23-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa_hcp-4.21-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa_hcp-4.22-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa_hcp-4.23-nightly-x86.yamlci-operator/config/openshift-hyperfleet/hyperfleet-e2e/.config.prowgenci-operator/config/openshift-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-main__e2e.yamlci-operator/config/openshift-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-release-0.2__e2e.yamlci-operator/config/openshift-knative/eventing-istio/.config.prowgenci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-next__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-next__420.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.15__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.15__420.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.16__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.16__420.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.17__414.yamlci-operator/config/openshift-knative/eventing-istio/openshift-knative-eventing-istio-release-v1.21__416.yamlci-operator/config/openshift-knative/eventing-kafka-broker/.config.prowgenci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-next__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-next__420.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.15__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.15__420.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.16__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.16__420.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.17__414.yamlci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.21__416.yamlci-operator/config/openshift-knative/eventing/.config.prowgenci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-next__414.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-next__420.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.15__413.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.15__420.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.16__414.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.16__420.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.17__414.yamlci-operator/config/openshift-knative/eventing/openshift-knative-eventing-release-v1.21__416.yamlci-operator/config/openshift-knative/kn-plugin-event/.config.prowgenci-operator/config/openshift-knative/kn-plugin-event/openshift-knative-kn-plugin-event-release-1.15__420.yamlci-operator/config/openshift-knative/kn-plugin-event/openshift-knative-kn-plugin-event-release-1.16__420.yamlci-operator/config/openshift-knative/serverless-operator/.config.prowgenci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.21-techpreview.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-aws-ovn.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-azure.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-gcp.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-hypershift.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-single-node.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__421-vsphere.yamlci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-release-1.37__ocp-4.22-lp-interop.yamlci-operator/config/openshift-knative/serving/.config.prowgenci-operator/config/openshift-knative/serving/openshift-knative-serving-release-next__414.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-next__420.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.15__413.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.15__420.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.16__414.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.16__420.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.17__414.yamlci-operator/config/openshift-knative/serving/openshift-knative-serving-release-v1.21__416.yamlci-operator/config/openshift-kni/eco-ci-cd-private/.config.prowgenci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__performance-dell.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-container-tests-project1.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-container-tests-project2.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-gitlab-project2-site3.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-lab-oran-o2ims-compliance-tests.yamlci-operator/config/openshift-kni/eco-ci-cd-private/openshift-kni-eco-ci-cd-private-main__slcm-lab.yamlci-operator/config/openshift-kni/eco-ci-cd/.config.prowgenci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__ci-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-hcp-nrop-4.19.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-hcp-nrop-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-hcp-nrop-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.19.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.22.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-4.23.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-compute-llc-5.0.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__compute-nto.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.18.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.19.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-4.22.yaml
💤 Files with no reviewable changes (39)
- ci-operator/config/codeready-toolchain/toolchain-e2e/.config.prowgen
- ci-operator/config/konflux-ci/konflux-ci/.config.prowgen
- ci-operator/config/Azure/ARO-HCP/.config.prowgen
- ci-operator/config/kiegroup/kie-cloud-tests-container/.config.prowgen
- ci-operator/config/Apicurio/.config.prowgen
- ci-operator/config/3scale-qe/3scale-deploy/.config.prowgen
- ci-operator/config/infinispan/infinispan-operator/.config.prowgen
- ci-operator/config/jboss-fuse/fuse-xpaas-qe-container/.config.prowgen
- ci-operator/config/ansible/tower-qa/.config.prowgen
- ci-operator/config/amq-streams-qe/strimzi-kafka-operator/.config.prowgen
- ci-operator/config/jws-qe/interop-ocp-ci/.config.prowgen
- ci-operator/config/RedHatQE/interop-testing/.config.prowgen
- ci-operator/config/cri-o/cri-o/.config.prowgen
- ci-operator/config/mtc-qe/mtc-e2e-qev2/.config.prowgen
- ci-operator/config/openshift-knative/eventing/.config.prowgen
- ci-operator/config/openshift-hyperfleet/hyperfleet-e2e/.config.prowgen
- ci-operator/config/openshift-eng/ocp-build-data/.config.prowgen
- ci-operator/config/jboss-fuse/csb-tnb-tests-container/.config.prowgen
- ci-operator/config/openshift-eng/agent-qe-infra/.config.prowgen
- ci-operator/config/oadp-qe/oadp-qe-automation/.config.prowgen
- ci-operator/config/jboss-fuse/camel-quarkus-openshift-interop/.config.prowgen
- ci-operator/config/opendatahub-io/notebooks/.config.prowgen
- ci-operator/config/konveyor/tackle2-ui/.config.prowgen
- ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/.config.prowgen
- ci-operator/config/kata-containers/kata-containers/.config.prowgen
- ci-operator/config/openshift-knative/serverless-operator/.config.prowgen
- ci-operator/config/openshift-knative/kn-plugin-event/.config.prowgen
- ci-operator/config/jboss-fuse/camel-k-test-container/.config.prowgen
- ci-operator/config/insights-onprem/cost-onprem-chart/.config.prowgen
- ci-operator/config/openshift-knative/eventing-kafka-broker/.config.prowgen
- ci-operator/config/jboss-eap-qe/openshift-eap-tests/.config.prowgen
- ci-operator/config/openshift-knative/eventing-istio/.config.prowgen
- ci-operator/config/insights-qe/iqe-cost-management-plugin/.config.prowgen
- ci-operator/config/kubevirt/hyperconverged-cluster-operator/.config.prowgen
- ci-operator/config/maistra/test-infra/.config.prowgen
- ci-operator/config/openshift-knative/serving/.config.prowgen
- ci-operator/config/konveyor/tackle-ui-tests/.config.prowgen
- ci-operator/config/openshift-eng/edge-tooling/.config.prowgen
- ci-operator/config/openshift-eng/baremetal-qe-infra/.config.prowgen
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}} @cnv-hco' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Read-only verification:
# 1) find report_template lines containing a closing `{{end}}`
# 2) check whether the same file has any corresponding `{{if` in report_template strings
rg -nP 'report_template:\s*.*\{\{end\}\}' ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml
rg -nP 'report_template:\s*.*\{\{if\b' ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yamlRepository: openshift/release
Length of output: 194
Remove the dangling template terminator in report_template.
Line 901 contains {{end}} with no corresponding opening block (no {{if, {{with}}, or {{range}}). This breaks Go template parsing and prevents Slack notifications for this job.
Proposed fix
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}} `@cnv-hco`'
+ report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> `@cnv-hco`'📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{end}} @cnv-hco' | |
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> `@cnv-hco`' |
🤖 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/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml`
at line 901, The report_template value contains a stray Go template terminator
"{{end}}" with no matching opening block; remove that dangling "{{end}}" from
the report_template string (the value assigned to report_template in the
kubevirt-hyperconverged-cluster-operator-main.yaml) so the template becomes a
valid Go template and Slack notifications can be rendered correctly.
Comment on lines
+284
to
+307
| reporter_config: | ||
| channel: '#pr-review-ai-ide-team' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: |- | ||
| ' | ||
| {{- $active_release := "2024b" -}} | ||
| {{- $previous_release := "2024a" -}} | ||
| {{- $emoji := "" -}} | ||
| {{- $group_tag := "" -}} | ||
| {{- if and (ne .Spec.Refs.BaseRef $active_release) (ne .Spec.Refs.BaseRef $previous_release) -}} | ||
| {{- $emoji = ":warning:" -}} | ||
| {{- else -}} | ||
| {{- $group_tag = "<!subteam^S05UB882TDF> " -}} | ||
| {{- if eq .Status.State "failure" -}} | ||
| {{- $emoji = ":failed:" -}} | ||
| {{- else -}} | ||
| {{- $emoji = ":bangbang:" -}} | ||
| {{- end -}} | ||
| {{- end -}} | ||
|
|
||
| {{- printf "%s" $emoji}} {{ printf "%s" $group_tag }}<{{.Spec.Refs.BaseLink}}|{{.Spec.Refs.Org}}/{{.Spec.Refs.Repo}} [{{.Spec.Refs.BaseRef}}]> Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{ printf "%s" $emoji -}} | ||
| ' |
Contributor
There was a problem hiding this comment.
Branch gating never matches this 2023a config.
This file generates postsubmits for 2023a, but the template only treats 2024b and 2024a as expected refs. As written, alerts from these jobs always fall back to :warning: and skip the subteam mention/failure-specific path. Please align the hardcoded release refs with the branches this config is supposed to report normally.
🤖 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/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yaml`
around lines 284 - 307, The template's branch gating uses hardcoded
$active_release and $previous_release ("2024b"/"2024a") so .Spec.Refs.BaseRef
never matches for this 2023a postsubmit; update the two variables in the
report_template (the $active_release and $previous_release assignments) to the
actual release refs this config targets (e.g., replace "2024b"/"2024a" with
"2023a" and the appropriate sibling release) so the if-check against
.Spec.Refs.BaseRef follows the correct branch path and enables the subteam
mention/failure-specific logic.
Comment on lines
+288
to
+311
| reporter_config: | ||
| channel: '#pr-review-ai-ide-team' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: |- | ||
| ' | ||
| {{- $active_release := "2024b" -}} | ||
| {{- $previous_release := "2024a" -}} | ||
| {{- $emoji := "" -}} | ||
| {{- $group_tag := "" -}} | ||
| {{- if and (ne .Spec.Refs.BaseRef $active_release) (ne .Spec.Refs.BaseRef $previous_release) -}} | ||
| {{- $emoji = ":warning:" -}} | ||
| {{- else -}} | ||
| {{- $group_tag = "<!subteam^S05UB882TDF> " -}} | ||
| {{- if eq .Status.State "failure" -}} | ||
| {{- $emoji = ":failed:" -}} | ||
| {{- else -}} | ||
| {{- $emoji = ":bangbang:" -}} | ||
| {{- end -}} | ||
| {{- end -}} | ||
|
|
||
| {{- printf "%s" $emoji}} {{ printf "%s" $group_tag }}<{{.Spec.Refs.BaseLink}}|{{.Spec.Refs.Org}}/{{.Spec.Refs.Repo}} [{{.Spec.Refs.BaseRef}}]> Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> {{ printf "%s" $emoji -}} | ||
| ' |
Contributor
There was a problem hiding this comment.
Branch gating never matches this 2023b config.
These postsubmits are defined for the 2023b branch, but the template hardcodes 2024b/2024a. That makes the condition always take the warning path here, so alerts from this file never set the subteam mention and never use the failure-vs-error formatting. Please switch these constants to the branches this release should treat as normal traffic.
🤖 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/opendatahub-io/notebooks/opendatahub-io-notebooks-2023b.yaml`
around lines 288 - 311, The branch gating constants in
reporter_config.report_template are wrong for this release: update the
$active_release and $previous_release variables (currently "2024b" and "2024a")
to the release branches this file is for (e.g., set $active_release to "2023b"
and $previous_release to "2023a") so the if condition that controls $emoji and
$group_tag (and thus the subteam mention and failure-vs-error formatting) will
match correctly; verify the variables near the top of the template where
$active_release and $previous_release are declared and keep the rest of the
template logic unchanged.
Comment on lines
+28
to
+29
| report_template: | | ||
| ':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# 1. Check if any .config.prowgen file still exists and contains report_template
echo "=== Remaining .config.prowgen files with report_template ==="
fd '.config.prowgen' --exec grep -l 'report_template' {}
# 2. Look at existing reporter_config blocks already in the repo (pre-PR examples)
echo "=== Existing reporter_config report_template values in ci-operator configs ==="
rg -n 'report_template' --type yaml -A 2 -g '!*openshift-eng-ocp-build-data*' | head -60
# 3. Check the flat vs nested reporter_config structure used elsewhere
echo "=== reporter_config structure (flat vs slack-nested) ==="
rg -n 'reporter_config' --type yaml -A 5 -g '!*openshift-eng-ocp-build-data*' | head -60Repository: openshift/release
Length of output: 12320
🏁 Script executed:
#!/bin/bash
# Check the PR file structure
echo "=== Examining the PR file (openshift-4.18__periodics.yaml) ==="
cat ci-operator/config/openshift-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.18__periodics.yaml | head -35
echo ""
echo "=== Other openshift-eng ocp-build-data files to check pattern ==="
fd 'openshift-eng.*__periodics' ci-operator/config/openshift-eng/ocp-build-data/ --exec head -35 {}
echo ""
echo "=== Check reporter_config structure in this directory ==="
rg -n 'reporter_config' ci-operator/config/openshift-eng/ocp-build-data/ -A 8 | head -100Repository: openshift/release
Length of output: 23674
Remove the literal single quotes from report_template — they will appear in Slack messages.
In YAML block literals (|), single quotes carry no syntactic meaning and become part of the string value. The current code includes these quotes as literal characters:
':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>'
Slack notifications will display the leading and trailing single quotes, which is unintended. Remove them:
🔧 Proposed fix
report_template: |
- ':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>'
+ :red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>This applies to all 13 files in ci-operator/config/openshift-eng/ocp-build-data/ that contain this report_template.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| report_template: | | |
| ':red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs>' | |
| report_template: | | |
| :red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> |
🤖 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-eng/ocp-build-data/openshift-eng-ocp-build-data-openshift-4.18__periodics.yaml`
around lines 28 - 29, The YAML block literal for report_template currently
includes literal single-quote characters around the Slack message; remove the
leading and trailing single quotes so the value of report_template is exactly
:red_jenkins_circle: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs> (update all occurrences of the report_template key
in the 13 files), ensuring no extra quotes remain in the block scalar and
preserving the existing interpolation tokens {{.Spec.Job}}, {{.Status.State}},
and {{.Status.URL}}.
Prucek
force-pushed
the
migrate-slack-reporter-inline
branch
2 times, most recently
from
d246da4 to
d4b805d
Compare
Member
Author
|
/retest-required |
1 similar comment
Member
Author
|
/retest-required |
Prucek
force-pushed
the
migrate-slack-reporter-inline
branch
from
d4b805d to
a4391d7
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
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/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yaml (1)
561-686:⚠️ Potential issue | 🟠 Major | ⚡ Quick winComplete the migration by adding
reporter_configto the remaining tests.
reporter_configis added to most jobs, but missing on Line 579, Line 588, Line 597, and Line 664. If this PR is the full move away from.config.prowgenslack_reporter, these jobs will stop sending failure/error Slack notifications.Suggested patch for the missing jobs
- as: vsphere-agent-sno-vcf9-f7 cron: 26 10 2,9,16,25 * * + reporter_config: + channel: '#team-qe-agent-prow' + job_states_to_report: + - failure + - error + report_template: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check steps: cluster_profile: vsphere-elastic - as: vsphere-agent-ha-vcf9-f7 cron: 46 11 6,15,22,29 * * + reporter_config: + channel: '#team-qe-agent-prow' + job_states_to_report: + - failure + - error + report_template: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check steps: cluster_profile: vsphere-elastic - as: vsphere-agent-compact-fips-vcf9-f7 cron: 29 15 5,12,21,28 * * + reporter_config: + channel: '#team-qe-agent-prow' + job_states_to_report: + - failure + - error + report_template: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check steps: cluster_profile: vsphere-elastic - as: oci-agent-baremetal-5cp-iscsi-f60 cron: 2 6 16 */2 * + reporter_config: + channel: '#team-qe-agent-prow' + job_states_to_report: + - failure + - error + report_template: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check steps: cluster_profile: oci-agent-qe🤖 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-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yaml` around lines 561 - 686, Several jobs are missing the reporter_config block (so Slack failure/error notifications will stop); add the same reporter_config used elsewhere to the jobs with "as: vsphere-agent-sno-vcf9-f7", "as: vsphere-agent-ha-vcf9-f7", "as: vsphere-agent-compact-fips-vcf9-f7", and "as: oci-agent-baremetal-5cp-iscsi-f60". Insert a reporter_config that sets channel: '#team-qe-agent-prow', job_states_to_report: [failure, error], and the existing report_template: "Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check" so these jobs match the others and continue sending Slack alerts.
♻️ Duplicate comments (2)
ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml (1)
883-884:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove dangling
{{end}}inreport_template.Line 884 includes
{{end}}without a matching opener in this template string, which can make the Go template invalid and break Slack notification rendering.Proposed fix
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. - <{{.Status.URL}}|View logs> {{end}} `@cnv-hco`' + report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. + <{{.Status.URL}}|View logs> `@cnv-hco`'#!/bin/bash # Read-only verification for unmatched Go template terminator in this file rg -nP 'report_template:\s*.*\{\{end\}\}' ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml rg -nP 'report_template:\s*.*\{\{(if|with|range|define)\b' ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml🤖 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/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml` around lines 883 - 884, The Slack report_template contains a dangling Go template terminator "{{end}}" with no matching opener; edit the report_template value (the YAML key named report_template) to remove the stray "{{end}}" token from the template string so the template becomes a valid Go template, and re-run your template/CI checks to confirm there are no unmatched template openers/closers (ensure any remaining "{{if|with|range|define}}" have matching "{{end}}").ci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yaml (1)
281-290:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAlign the release gates with the
2023aconfig.Every added template hardcodes
2024b/2024a, but this file generates jobs for branch2023a. That makes theBaseRefcheck miss the normal-release path for these postsubmits, so alerts always fall back to:warning:and skip the subteam/failure-specific formatting.Also applies to: 306-315, 331-340, 366-375, 391-400, 416-425, 441-450, 466-475, 491-500, 516-525, 541-550, 586-595, 621-630, 640-640
🤖 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/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yaml` around lines 281 - 290, The report_template blocks hardcode $active_release = "2024b" and $previous_release = "2024a", which don't match this file's branch; update the two variables in each report_template (the $active_release and $previous_release assignments) to use the releases for this config (set $active_release to "2023a" and set $previous_release to the appropriate prior release for this branch), so the BaseRef check (the "if and (ne .Spec.Refs.BaseRef $active_release) (ne .Spec.Refs.BaseRef $previous_release)" condition) correctly detects the normal-release path; apply the same replacement to every report_template occurrence mentioned (including the other ranges called out).
🤖 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-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.21-nightly-x86.yaml`:
- Around line 51-60: Several jobs (cluster-density-v2-249nodes,
node-density-cni-24nodes, conc-builds-3nodes, control-plane-3nodes) are missing
the Slack reporter settings so they will stop posting notifications; for each of
those job entries add the reporter_config block matching the existing pattern
(channel, job_states_to_report, report_template) used elsewhere in this file
(e.g., the block starting with reporter_config: channel:
'#ocp-qe-scale-ci-results') or re-enable the .config.prowgen slack_reporter
generation; update the reporter_config for each job name
(cluster-density-v2-249nodes, node-density-cni-24nodes, conc-builds-3nodes,
control-plane-3nodes) to ensure notifications are sent on success/failure/error
with the same report_template and channel.
In
`@ci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.20-lp-interop.yaml`:
- Around line 91-100: The cnv-component-readiness-aws-ipi-ocp420 test block is
missing a reporter_config, so add a reporter_config entry to that test (the
block under the list item with "as: cnv-component-readiness-aws-ipi-ocp420")
mirroring the reporter_config used earlier (include channel,
job_states_to_report: [success, failure, error], and the same report_template
string) so Slack notifications are enabled for this job; ensure YAML indentation
matches the surrounding steps block.
---
Outside diff comments:
In
`@ci-operator/config/openshift-eng/agent-qe-infra/openshift-eng-agent-qe-infra-release-4.18__amd64-nightly.yaml`:
- Around line 561-686: Several jobs are missing the reporter_config block (so
Slack failure/error notifications will stop); add the same reporter_config used
elsewhere to the jobs with "as: vsphere-agent-sno-vcf9-f7", "as:
vsphere-agent-ha-vcf9-f7", "as: vsphere-agent-compact-fips-vcf9-f7", and "as:
oci-agent-baremetal-5cp-iscsi-f60". Insert a reporter_config that sets channel:
'#team-qe-agent-prow', job_states_to_report: [failure, error], and the existing
report_template: "Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs> <!subteam^S09H79P1UMA> Please check" so these jobs
match the others and continue sending Slack alerts.
---
Duplicate comments:
In
`@ci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yaml`:
- Around line 883-884: The Slack report_template contains a dangling Go template
terminator "{{end}}" with no matching opener; edit the report_template value
(the YAML key named report_template) to remove the stray "{{end}}" token from
the template string so the template becomes a valid Go template, and re-run your
template/CI checks to confirm there are no unmatched template openers/closers
(ensure any remaining "{{if|with|range|define}}" have matching "{{end}}").
In
`@ci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-2023a.yaml`:
- Around line 281-290: The report_template blocks hardcode $active_release =
"2024b" and $previous_release = "2024a", which don't match this file's branch;
update the two variables in each report_template (the $active_release and
$previous_release assignments) to use the releases for this config (set
$active_release to "2023a" and set $previous_release to the appropriate prior
release for this branch), so the BaseRef check (the "if and (ne
.Spec.Refs.BaseRef $active_release) (ne .Spec.Refs.BaseRef $previous_release)"
condition) correctly detects the normal-release path; apply the same replacement
to every report_template occurrence mentioned (including the other ranges called
out).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
Comment on lines
+51
to
+60
| reporter_config: | ||
| channel: '#ocp-qe-scale-ci-results' | ||
| job_states_to_report: | ||
| - success | ||
| - failure | ||
| - error | ||
| report_template: '{{if eq .Status.State "success"}} :white_check_mark: Job *{{.Spec.Job}}* | ||
| ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :white_check_mark: | ||
| {{else}} :warning: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View | ||
| logs> :warning: {{end}}' |
Contributor
There was a problem hiding this comment.
Migration is incomplete: several tests still lack reporter_config
Given the PR goal, this file still has tests without Slack reporter settings (Line 27 cluster-density-v2-249nodes, Line 168 node-density-cni-24nodes, Line 186 conc-builds-3nodes, Line 208 control-plane-3nodes). If .config.prowgen slack_reporter is removed, those jobs will stop posting notifications.
Suggested patch pattern (apply same block to each missing test)
- always_run: false
as: cluster-density-v2-249nodes
+ reporter_config:
+ channel: '#ocp-qe-scale-ci-results'
+ job_states_to_report:
+ - success
+ - failure
+ - error
+ report_template: '{{if eq .Status.State "success"}} :white_check_mark: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :white_check_mark: {{else}} :warning: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :warning: {{end}}'
steps:🤖 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-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__rosa-4.21-nightly-x86.yaml`
around lines 51 - 60, Several jobs (cluster-density-v2-249nodes,
node-density-cni-24nodes, conc-builds-3nodes, control-plane-3nodes) are missing
the Slack reporter settings so they will stop posting notifications; for each of
those job entries add the reporter_config block matching the existing pattern
(channel, job_states_to_report, report_template) used elsewhere in this file
(e.g., the block starting with reporter_config: channel:
'#ocp-qe-scale-ci-results') or re-enable the .config.prowgen slack_reporter
generation; update the reporter_config for each job name
(cluster-density-v2-249nodes, node-density-cni-24nodes, conc-builds-3nodes,
control-plane-3nodes) to ensure notifications are sent on success/failure/error
with the same report_template and channel.
Member
Author
|
/test generated-config |
1 similar comment
Member
Author
|
/test generated-config |
Prucek
force-pushed
the
migrate-slack-reporter-inline
branch
2 times, most recently
from
9c33c9b to
ae5cd9d
Compare
Member
Author
|
/hold cancel |
openshift-ci
Bot
removed
the
do-not-merge/hold
Contributor
|
/lgtm |
Member
Author
|
/retest-required |
5 similar comments
Member
Author
|
/retest-required |
Member
Author
|
/retest-required |
Member
Author
|
/retest-required |
Member
Author
|
/retest-required |
Member
Author
|
/retest-required |
Member
Author
|
/pj-rehearse ack |
Contributor
|
@Prucek: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
openshift-ci
Bot
added
the
needs-rebase
…rter_config Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prucek
force-pushed
the
migrate-slack-reporter-inline
branch
from
ae5cd9d to
3cd0f03
Compare
openshift-ci
Bot
removed
lgtm
openshift-merge-bot
Bot
removed
the
rehearsals-ack
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
Author
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
Contributor
|
[REHEARSALNOTIFIER]
A total of 3674 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Contributor
|
/lgtm |
Contributor
Contributor
|
/unhold |
openshift-ci
Bot
removed
the
do-not-merge/hold
Member
Author
|
/pj-rehearse ack |
Contributor
|
@Prucek: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
Contributor
|
@Prucek: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
openshift-merge-bot Bot
pushed a commit
that referenced
this pull request
May 13, 2026
Route release branch Prow Slack reporter notifications to dedicated per-release channels (#rhdh-e2e-alerts-1-8, #rhdh-e2e-alerts-1-9) instead of the shared #rhdh-e2e-alerts channel. The main branch continues to use #rhdh-e2e-alerts. This was previously not possible when using the centralized .config.prowgen slack_reporter (see PR #76593). The migration to per-test reporter_config in PR #78976 removed that limitation. Also updates CLAUDE.md new release branch checklist to document the reporter_config channel naming convention. Assisted-by: OpenCode
tbuskey
pushed a commit
to tbuskey/release
that referenced
this pull request
May 13, 2026
…rter_config (openshift#78976) * prowgen: migrate slack_reporter from .config.prowgen to per-test reporter_config Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * prowgen: regenerate jobs after slack_reporter migration Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
tbuskey
pushed a commit
to tbuskey/release
that referenced
this pull request
May 13, 2026
…hift#79228) Route release branch Prow Slack reporter notifications to dedicated per-release channels (#rhdh-e2e-alerts-1-8, #rhdh-e2e-alerts-1-9) instead of the shared #rhdh-e2e-alerts channel. The main branch continues to use #rhdh-e2e-alerts. This was previously not possible when using the centralized .config.prowgen slack_reporter (see PR openshift#76593). The migration to per-test reporter_config in PR openshift#78976 removed that limitation. Also updates CLAUDE.md new release branch checklist to document the reporter_config channel naming convention. Assisted-by: OpenCode
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move slack_reporter configs from .config.prowgen files into per-test reporter_config fields in ci-operator config YAML files. This is part of the incremental .config.prowgen deprecation.
This PR migrates Slack notification configuration from centralized prowgen .config.prowgen files into per-test reporter_config blocks inside individual ci-operator job YAMLs across the OpenShift CI configuration repository.
What changed (practical terms)
Scope / components affected
Reviewer guidance / recommended checks
Bottom line