WINC-1456: adds windows-exporter jobs for 4.22#79273
Open
wgahnagl wants to merge 216 commits into
Open
Conversation
openshift-ci-robot
added
the
jira/valid-reference
Contributor
|
@wgahnagl: This pull request references WINC-1456 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "5.0." or "openshift-5.0.", but it targets "WMCO 10.19.0" instead. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Contributor
|
Caution Review failedFailed to post review comments WalkthroughThis PR removes multiple retired CI configs, adds new CI variants and jobs, updates job reporting and gating, adjusts workflow scripts and resources, updates several build images and paths, and changes assorted OWNERS and alias entries. ChangesCI configuration updates
Estimated code review effort🎯 5 (Critical) | ⏱️ ~100 minutes Possibly related PRs
Suggested labels
✨ Finishing Touches🧪 Generate unit tests (beta)
|
wgahnagl
changed the title
![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: 1
🤖 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/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml`:
- Around line 28-32: The job currently clones openshift/promu using "git clone
--branch master" which is non-reproducible; change the git clone command to pin
a specific immutable revision (a tag or commit SHA) instead of master (replace
the "git clone --branch master https://github.com/openshift/promu.git
openshift-promu" line), then continue to install and run promu as before (the
subsequent commands
GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go
install . and GOOS=windows ./promu build -v remain unchanged) so the build uses
a known stable promu version.
🪄 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: cd3c9a38-7563-4f44-89d6-5bd9b886d001
📒 Files selected for processing (1)
ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml
Comment on lines
+28
to
+32
| git clone --branch master --single-branch https://github.com/openshift/promu.git openshift-promu | ||
| cd openshift-promu/ | ||
| GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go install . | ||
| cd /go/src/github.com/openshift/prometheus-community-windows_exporter | ||
| GOOS=windows ./promu build -v |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Default branch ref:"
git ls-remote --symref https://github.com/openshift/promu.git HEAD
echo
echo "Existing branch refs (master/main):"
git ls-remote --heads https://github.com/openshift/promu.git master main || true
echo
echo "Recent tags to choose a pinned version from:"
git ls-remote --tags https://github.com/openshift/promu.git | tail -n 20Repository: openshift/release
Length of output: 1069
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check if the file exists
FILE="ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml"
if [ -f "$FILE" ]; then
echo "File exists. Extracting lines 25-35 for context:"
sed -n '25,35p' "$FILE" | cat -n
echo
echo "Full file for complete context:"
cat -n "$FILE"
else
echo "File does not exist at: $FILE"
echo "Listing available CI configs in the directory:"
find ci-operator/config/openshift -name "*prometheus*windows*" -o -name "*windows_exporter*" 2>/dev/null | head -20
fiRepository: openshift/release
Length of output: 1941
Pin openshift/promu to an immutable revision.
Line 28 clones master, which makes this job non-reproducible and can break when upstream changes. Pin to a tag or commit SHA (stable versions v0.1.0 through v0.6.1 are available).
Suggested change
- git clone --branch master --single-branch https://github.com/openshift/promu.git openshift-promu
- cd openshift-promu/
- GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go install .
- cd /go/src/github.com/openshift/prometheus-community-windows_exporter
+ GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter \
+ go install github.com/openshift/promu@<tag-or-commit-sha>
+ cd /go/src/github.com/openshift/prometheus-community-windows_exporter
GOOS=windows ./promu build -v🤖 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/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml`
around lines 28 - 32, The job currently clones openshift/promu using "git clone
--branch master" which is non-reproducible; change the git clone command to pin
a specific immutable revision (a tag or commit SHA) instead of master (replace
the "git clone --branch master https://github.com/openshift/promu.git
openshift-promu" line), then continue to install and run promu as before (the
subsequent commands
GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go
install . and GOOS=windows ./promu build -v remain unchanged) so the build uses
a known stable promu version.
openshift-merge-bot
Bot
added
the
rehearsals-ack
openshift-ci
Bot
added
lgtm
Contributor
Member
|
/lgtm |
Contributor
Contributor
Contributor
|
/hold Revision 258d744 was retested 3 times: holding |
openshift-ci
Bot
added
the
do-not-merge/hold
Contributor
|
@wgahnagl please rebase to pickup the latest |
…build05 (openshift#79269) * DPTP-4410: Argo ignore GCP MachineSet boot disk image on build02, AWS AMI on build05 * DPTP-4410: drop common/assets _machine-configuration.yaml from GitOps
Signed-off-by: grokspawn <jordan@nimblewidget.com>
Updated baseurl in 14 ocp-4.13-*.repo files under core-services/release-controller/_repos/ to use the Cloudflare Workers R2 endpoint instead of mirror2.openshift.com. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…ift#79272) Co-authored-by: openshift-bot <openshift-bot@users.noreply.github.com>
…ift#79256) Promotes ci/vcf-migration-operator:latest as base_image for as base_images for other repositories to reference in their CI configurations.
* Add karpenter-operator verify check Signed-off-by: Max Cao <macao@redhat.com> * Promote karpenter-operator image Signed-off-by: Max Cao <macao@redhat.com> * DevPreview karpenter-operator e2e-aws test Signed-off-by: Max Cao <macao@redhat.com> --------- Signed-off-by: Max Cao <macao@redhat.com>
* MCE multicloud-operators-foundation e2e fix for 2.17 - e2e is using latest/main versions of images rather than ones that go with the specific release branch Signed-off-by: Tesshu Flower <tflower@redhat.com> * MCE multicloud-operators-foundation e2e fix all branches - run e2e using appropriate images for branch Signed-off-by: Tesshu Flower <tflower@redhat.com> * update backplane-5.0 to use proper br Signed-off-by: Tesshu Flower <tflower@redhat.com> --------- Signed-off-by: Tesshu Flower <tflower@redhat.com>
…ic STS) (openshift#79246) * Remove STS conformance jobs for 4.23 and 5.0 ROSA Classic STS is not available on 4.23 (not a ROSA version) or 5.0 (HCP-only). Remove e2e-rosa-sts-ovn from both nightly configs. * Remove rosa-classic-sts-conformance from 5.0 release-controller config The Prow job was removed but the release-controller entry still referenced it, causing CI validation failures.
Add CI configuration for multicluster-mesh-addon with verify, unit, integration, linting, and SonarCloud tests. Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
…lease-0.2 variant (openshift#79420) Switch the three nightly tier tests to pull api/sentinel/adapter images from quay.io/redhat-services-prod/hyperfleet-tenant/hyperfleet/ (Konflux builds, public, no pull secret) instead of registry.ci.openshift.org. Update the e2e step-registry defaults to match, and remove the release-0.2 variant configs and generated jobs — per-release-branch Prow pipelines are being replaced by a single reusable definition. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…shift#79498) * Update Quay SDL scan step to use single Konflux service account Replace per-component, per-version credentials with a single service account that can pull all Quay images from the Konflux registry. This removes ~100 lines of repetitive credential handling and simplifies adding new versions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Wrap credential reads with set +x to prevent secret leakage Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Add quay v3.18 and v3.17 SDL scan jobs, update v3.16 with full Konflux image paths Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Upgrade trivy from v0.54.1 to v0.70.0 in security testing provisioning Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Update all SDL scan jobs to use full Konflux image paths with latest digests Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jakub Guzik <jguzik@redhat.com>
…penshift#79504) Co-authored-by: openshift-ci[bot] <75433959+openshift-ci[bot]@users.noreply.github.com>
…enshift#79505) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: pastequo <infrastructure-operator@redhat.com>
openshift#79510) * multicluster-mesh-addon: Mark pre submit sonar job as optional for now TODO: stolostron/multicluster-mesh-addon#78 * Run make ci-operator-config
…ift#79524) Co-authored-by: openshift-bot <openshift-bot@users.noreply.github.com>
…nshift#79469) IMAGE_NAME was constructed as "${QUAY_REPO}:${TAG_NAME}" in the PR Branch Handling block, but QUAY_REPO is initialized empty and only gets set from IMAGE_REPO after Image Tag Resolution. This produced broken image names like ":pr-123-abcdef12" (missing repo prefix). Fix by using IMAGE_REPO (the primary variable since PR openshift#76964) with a fallback default: "${IMAGE_REPO:-rhdh-community/rhdh}:${TAG_NAME}". This respects Gangway API overrides (MULTISTAGE_PARAM_OVERRIDE_IMAGE_REPO) when set, and falls back to the default for standard presubmit runs. Also set IMAGE_NAME in the else branch of Image Tag Resolution right after IMAGE_REPO is assigned, so the wait loop echo statements display the correct image name instead of the stale empty value. Default IMAGE_REGISTRY to "quay.io" at initialization instead of empty string, since that is always the intended default. Remove the now redundant ${IMAGE_REGISTRY:-quay.io} fallbacks and duplicate export statements that followed Image Tag Resolution. Align osd-gcp/helm/nightly with the other scripts: add Gangway API override logic, TAG_NAME override guard in PR Branch Handling, override-first check in Image Tag Resolution, IMAGE_REGISTRY conditional for the wait loop, and declare all MULTISTAGE_PARAM_OVERRIDE env vars in the ref YAML. Affected scripts: - ocp/helm (presubmit) - ocp/helm/nightly - ocp/helm/upgrade/nightly - eks/helm/nightly - gke/helm/nightly - aks/helm/nightly - osd-gcp/helm/nightly Assisted-by: OpenCode
…nshift#79530) Signed-off-by: Nikolaos Moraitis <nmoraiti@redhat.com>
….0 --skip-periodics --future-release 4.23 --future-release 5.1 --confirm
…openshift-priv --only-org openshift --whitelist-file ./core-services/openshift-priv/_whitelist.yaml
…865 --github-app-private-key-path /etc/github/cert --github-endpoint http://ghproxy --dry-run=false --whitelist-file ./core-services/openshift-priv/_whitelist.yaml
…/core-services/sanitize-prow-jobs/_config.yaml
…magesets ./clusters/hosted-mgmt/hive/pools
Contributor
|
New changes are detected. LGTM label has been removed. |
Contributor
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jrvaldes, mansikulkarni96, wgahnagl The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
Bot
removed
the
approved
Contributor
|
@wgahnagl: The following tests failed, say
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. |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 17
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
ci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main__periodics.yaml (1)
1-72:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd required inherited sections for this
__periodicsconfig.This variant file is missing required inherited sections (
base_images,promotion, andreleases). Please copy those from the corresponding main config and keep only periodic (cron/interval) tests in this variant.As per coding guidelines: "Variant periodic configuration files should include
base_images,build_root,images,promotion, andreleasessections copied from main config, then add onlytests:entries withinterval:orcron:scheduling."🤖 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-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main__periodics.yaml` around lines 1 - 72, The variant __periodics config is missing required inherited sections (base_images, promotion, and releases); copy the corresponding sections from the main config into this file and keep the existing build_root, images and tests blocks unchanged, ensuring you include base_images, promotion, and releases blocks before zz_generated_metadata and only add periodic tests (the current tests: entries with cron scheduling such as nightly-4-19, nightly-4-20, etc. should remain). Locate the sections by their names (base_images, build_root, images, promotion, releases, tests) and merge the missing base_images/promotion/releases from the main config so the variant contains base_images, build_root, images, promotion, releases and then the tests entries only.ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-5.0-nightly-x86.yaml (1)
1-136:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRegenerate downstream artifacts after adding this CI configuration.
As per coding guidelines, after adding CI configuration files in
ci-operator/config/, regenerate downstream artifacts by runningmake updatefrom the repository root.As per coding guidelines: After modifying CI configuration files in
ci-operator/config/, regenerate downstream artifacts by runningmake update.🤖 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__metal-5.0-nightly-x86.yaml` around lines 1 - 136, You added a new CI config (contains tests like "as: daily-virt-6nodes", "as: udn-bgp", "as: weekly-eip" and the zz_generated_metadata block) but did not regenerate downstream artifacts; run the repository-level make target to update generated files by executing "make update" from the repo root and commit the resulting changes so the downstream artifacts reflect this new ci-operator config.
🧹 Nitpick comments (2)
ci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-release-4.23.yaml (1)
122-134: 💤 Low valueConsider using
pipeline_skip_if_only_changedfor consistency.The new job uses
skip_if_only_changedwhile most other test jobs in this file (lines 76, 82, 89, 97, 105, 138, etc.) usepipeline_skip_if_only_changed. Consider usingpipeline_skip_if_only_changedfor consistency unless there's a specific reason to use the simpler form.♻️ Align with existing pattern
- as: e2e-aws-capi-techpreview-post-install - skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$ + pipeline_skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$ 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-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-release-4.23.yaml` around lines 122 - 134, The job with as: e2e-aws-capi-techpreview-post-install (cluster_profile: openshift-org-aws, workflow: openshift-e2e-aws-techpreview-post-install) uses skip_if_only_changed; replace that key with pipeline_skip_if_only_changed to match the existing pattern used by other test jobs in this file for consistent CI behavior.ci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-release-5.1.yaml (1)
474-475: 💤 Low valueConsider parameterizing or documenting hardcoded AMI IDs.
The AMI IDs (
ami-0b78302f83217d149) are hardcoded for both compute and control plane nodes. These AMIs are region-specific and may become outdated over time, requiring manual updates to this configuration file.Consider either:
- Moving these to a centralized configuration or environment variable if multiple jobs need the same AMIs
- Adding a comment explaining why these specific AMIs are required and how to update them
🤖 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-priv/csi-operator/openshift-priv-csi-operator-release-5.1.yaml` around lines 474 - 475, The CI config currently hardcodes AMI IDs for COMPUTE_AMI and CONTROL_PLANE_AMI which are region-specific and brittle; replace these literals with parameterized values (e.g., environment variables or a shared config reference) and/or add a clear comment explaining why these AMIs were chosen and how to update them; specifically update the COMPUTE_AMI and CONTROL_PLANE_AMI entries to read from a centralized variable (or reference a variables map) and add a one-line comment above them documenting region, selection criteria, and update process so future maintainers know where to change the AMI.
🤖 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-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-staging.yaml`:
- Around line 29-34: Several jobs (notably
ocm-fvt-periodic-cs-rosa-hcp-autonode-staging-main,
ocm-fvt-periodic-cs-rosa-hcp-arm-staging-main,
ocm-fvt-periodic-cs-rosa-hcp-amd64-staging-main and the other jobs referenced)
set umask 077 for temp file creation but do not restore the original umask;
update each job to follow the saved-and-restore pattern used elsewhere: capture
old_umask=$(umask) before setting umask 077, create the podman_env_file with
mktemp, add trap 'rm -f "${podman_env_file}"' EXIT, and then restore the
original umask with umask "$old_umask" after the temp file creation so the
pattern is consistent across all jobs.
In
`@ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__periodics.yaml`:
- Around line 6-9: The variant periodic config includes a base image entry named
"ocm-cli" that is not present in the main base_images list; either remove the
"ocm-cli" block from this variant file or add a matching "ocm-cli" entry to the
main config's base_images so the variant only copies from main. Locate the
"ocm-cli" block in the variant periodic file and either delete those four lines
or add an identical "ocm-cli: name: ocm-cli namespace: ci tag: latest" entry
into the main configuration's base_images section so the variant remains a copy
of main.
In
`@ci-operator/config/openshift-priv/apiserver-network-proxy/openshift-priv-apiserver-network-proxy-release-5.1.yaml`:
- Around line 41-45: The verify-commits job uses commitchecker with a fallback
of ${PULL_BASE_SHA:-main}, which validates against main instead of the release
branch; update the commitchecker invocation in the verify-commits job (the
commands block that runs "commitchecker --start ...") to use a
release-branch-aware baseline such as ${PULL_BASE_REF:-release-5.1} (or ensure
PULL_BASE_REF is injected) so commit validation runs against the correct release
base instead of main.
In
`@ci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-main.yaml`:
- Around line 122-134: The new post-install e2e job
"e2e-aws-capi-techpreview-post-install" is missing an explicit always_run
setting and thus defaults to running for all presubmits; add the key always_run:
false to that job's top-level config (the same level as
skip_if_only_changed/steps/workflow) so it matches the adjacent e2e jobs and
does not run unconditionally in presubmits.
In
`@ci-operator/config/openshift-priv/console-plugin-template/openshift-priv-console-plugin-template-release-4.22.yaml`:
- Line 46: You need to ensure the env var rename is applied or documented
consistently: search all CI job configs for the old variable name
CYPRESS_PLUGIN_TEMPLATE_PULL_SPEC and replace it with PLUGIN_TEMPLATE_PULL_SPEC
(or vice‑versa if the rename was reversed) across all related job definitions
for networking-console-plugin and console-plugin-template in both openshift and
openshift-priv orgs and across affected release branches; if any files must
intentionally keep the old name, add a short comment in those job configs
explaining the exception and update any central docs or a changelog entry to
list which repos/branches were updated and which were intentionally excluded.
In
`@ci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-main.yaml`:
- Line 543: The current pipeline_skip_if_only_changed uses the markdown token
'(^[A-Z]+\.md$)' which only matches uppercase filenames; update that token to
match all markdown filenames like the other jobs by replacing '(^[A-Z]+\.md$)'
with '(^.*\.md$)' in the pipeline_skip_if_only_changed value so lowercase-only
.md PRs are also skipped.
In
`@ci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-4.23.yaml`:
- Line 528: The pipeline_skip_if_only_changed entry currently uses the
restrictive regex '(^[A-Z]+\.md$)' which only matches uppercase markdown
filenames; update that pattern in the pipeline_skip_if_only_changed value to
match all markdown files (consistent with other jobs that use '(\.md$)') so any
.md file triggers the skip logic; modify the regex fragment for markdown from
'(^[A-Z]+\.md$)' to '(\.md$)' within the pipeline_skip_if_only_changed string.
In
`@ci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-5.0.yaml`:
- Line 529: Update the pipeline_skip_if_only_changed regex to match any markdown
filename (not only uppercase names) by replacing the current '(^[A-Z]+\.md$)'
fragment with a broader '(\.md$)' fragment in the pipeline_skip_if_only_changed
value; locate the pipeline_skip_if_only_changed key and adjust the regex string
so it aligns with the other e2e jobs' pattern and prevents triggering e2e-v2-gke
on lowercase markdown-only changes.
In
`@ci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-5.1.yaml`:
- Line 528: The pipeline_skip_if_only_changed regex currently uses
'(^[A-Z]+\.md$)' which misses lowercase markdown filenames; update that token in
the pipeline_skip_if_only_changed value to '(^[A-Za-z]+\.md$)' so markdown-only
changes with lowercase names are skipped (locate the
pipeline_skip_if_only_changed entry and replace the '(^[A-Z]+\.md$)' segment
with '(^[A-Za-z]+\.md$)').
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-main.yaml`:
- Around line 704-710: Remove the unmatched template terminators "{{end}}" from
the reporter templates so they no longer contain orphaned closing tags;
specifically edit reporter_config.report_template to strip the trailing
"{{end}}" (and apply the same removal to the other reporter template instance in
this file that also ends with "{{end}}"). Ensure any remaining template syntax
is balanced (only use "{{end}}" when paired with an opening {{if|with|range}}
block).
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.20.yaml`:
- Around line 674-680: The report_template values in the reporter_config blocks
contain a stray closing template action "{{end}}" with no matching "{{if ...}}"
which breaks template parsing; edit the reporter_config.report_template entries
(the report_template field under reporter_config) and remove the trailing
"{{end}}" from each template so the templates end after the URL link (e.g.,
change ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
<{{.Status.URL}}|View logs>' ), ensuring both occurrences are updated.
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.21.yaml`:
- Around line 689-695: The reporter_config.report_template for the
e2e-agent-compact-ipv4 and e2e-gcp-mco-disruptive jobs contains a dangling
"{{end}}" with no matching "{{if ...}}"; remove the trailing "{{end}}" from the
report_template string in both job blocks (look for reporter_config and
report_template entries within the e2e-agent-compact-ipv4 and
e2e-gcp-mco-disruptive job definitions) so the Go template is valid, then run
make update to regenerate downstream CI artifacts.
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yaml`:
- Around line 719-725: The reporter_config.report_template values include a
dangling "{{end}}" with no matching "{{if}}", which makes the templates invalid;
locate the report_template entries (e.g., under reporter_config with channel
'`#trt-alert-mco`' and the other test job config referenced in the review) and
remove the trailing "{{end}}" token from each template so they contain only the
intended text and link markup.
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yaml`:
- Around line 704-710: The reporter_config report templates contain an unmatched
trailing "{{end}}" that makes the Go template invalid; remove the stray
"{{end}}" from the report_template (and the other reporter template under
reporter_config) so each template no longer ends with an unmatched "{{end}}",
leaving the rest of the template text intact and ensuring any conditional blocks
use a proper {{if ...}}{{else}}{{end}} pair if needed.
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yaml`:
- Around line 705-711: The reporter config's report_template strings contain a
stray closing template action "{{end}}" with no matching opening control; remove
the trailing "{{end}}" from the report_template entries under reporter_config
(both occurrences of report_template) so the templates are valid for Go's
text/template parser while preserving the existing message and URL placeholder
content.
In
`@ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yaml`:
- Around line 704-710: The reporter_config's report_template strings contain
stray closing template tags "{{end}}" with no matching opening block; remove the
trailing "{{end}}" from the report_template values so the Go templates are valid
(update the two report_template occurrences under reporter_config to delete the
"{{end}}" token).
In
`@ci-operator/config/openshift-priv/machine-os-images/openshift-priv-machine-os-images-release-5.0.yaml`:
- Around line 59-65: The CI config change (the workflow: agent-e2e-compact-ipv4
entry under cluster_profile: equinix-ocp-metal) requires regenerating downstream
artifacts; run "make update" in the repository to regenerate files under
ci-operator/config and related generated outputs so the change is propagated
into the CI pipeline.
---
Outside diff comments:
In
`@ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-5.0-nightly-x86.yaml`:
- Around line 1-136: You added a new CI config (contains tests like "as:
daily-virt-6nodes", "as: udn-bgp", "as: weekly-eip" and the
zz_generated_metadata block) but did not regenerate downstream artifacts; run
the repository-level make target to update generated files by executing "make
update" from the repo root and commit the resulting changes so the downstream
artifacts reflect this new ci-operator config.
In
`@ci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main__periodics.yaml`:
- Around line 1-72: The variant __periodics config is missing required inherited
sections (base_images, promotion, and releases); copy the corresponding sections
from the main config into this file and keep the existing build_root, images and
tests blocks unchanged, ensuring you include base_images, promotion, and
releases blocks before zz_generated_metadata and only add periodic tests (the
current tests: entries with cron scheduling such as nightly-4-19, nightly-4-20,
etc. should remain). Locate the sections by their names (base_images,
build_root, images, promotion, releases, tests) and merge the missing
base_images/promotion/releases from the main config so the variant contains
base_images, build_root, images, promotion, releases and then the tests entries
only.
---
Nitpick comments:
In
`@ci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-release-4.23.yaml`:
- Around line 122-134: The job with as: e2e-aws-capi-techpreview-post-install
(cluster_profile: openshift-org-aws, workflow:
openshift-e2e-aws-techpreview-post-install) uses skip_if_only_changed; replace
that key with pipeline_skip_if_only_changed to match the existing pattern used
by other test jobs in this file for consistent CI behavior.
In
`@ci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-release-5.1.yaml`:
- Around line 474-475: The CI config currently hardcodes AMI IDs for COMPUTE_AMI
and CONTROL_PLANE_AMI which are region-specific and brittle; replace these
literals with parameterized values (e.g., environment variables or a shared
config reference) and/or add a clear comment explaining why these AMIs were
chosen and how to update them; specifically update the COMPUTE_AMI and
CONTROL_PLANE_AMI entries to read from a centralized variable (or reference a
variables map) and add a one-line comment above them documenting region,
selection criteria, and update process so future maintainers know where to
change the AMI.
🪄 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: 0f1cba32-ff0d-423e-8d63-56b6c1b12a3e
📒 Files selected for processing (300)
MakefileOWNERS_ALIASESci-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/Apicurio/apicurio-registry-system-tests/OWNERSci-operator/config/Apicurio/apicurio-registry-system-tests/README.mdci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main.yamlci-operator/config/Azure/ARO-HCP/Azure-ARO-HCP-main__baseimage-generator.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.22-lp-interop.yamlci-operator/config/RedHatQE/interop-testing/RedHatQE-interop-testing-master__cnv-odf-ocp-4.23-lp-interop.yamlci-operator/config/ansible/tower-qa/OWNERSci-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/cloud-bulldozer/e2e-benchmarking/OWNERSci-operator/config/cloud-bulldozer/orion/OWNERSci-operator/config/codeready-toolchain/toolchain-e2e/codeready-toolchain-toolchain-e2e-master.yamlci-operator/config/codeready-toolchain/workload-analyzer/OWNERSci-operator/config/fleetshift/fleetshift-user-interface/fleetshift-fleetshift-user-interface-main.yamlci-operator/config/fleetshift/fleetshift-user-interface/fleetshift-fleetshift-user-interface-main__multiarch.yamlci-operator/config/ibmz-eco/isv-operator/OWNERSci-operator/config/ibmz-eco/isv-operator/ibmz-eco-isv-operator-openshift-4.6.yamlci-operator/config/ibmz-eco/isv-operator/ibmz-eco-isv-operator-openshift-4.7.yamlci-operator/config/insights-qe/iqe-cost-management-plugin/OWNERSci-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/jws-qe/interop-ocp-ci/OWNERSci-operator/config/jws-qe/interop-ocp-ci/README.mdci-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/kubev2v/migration-planner/OWNERSci-operator/config/kubevirt/hyperconverged-cluster-operator/kubevirt-hyperconverged-cluster-operator-main.yamlci-operator/config/kubevirt/ssp-operator/kubevirt-ssp-operator-release-v0.26.yamlci-operator/config/lightspeed-core/lightspeed-stack/lightspeed-core-lightspeed-stack-main.yamlci-operator/config/maistra/test-infra/maistra-test-infra-main.yamlci-operator/config/medik8s/node-remediation-console/medik8s-node-remediation-console-main.yamlci-operator/config/medik8s/system-tests/OWNERSci-operator/config/medik8s/system-tests/medik8s-system-tests-main.yamlci-operator/config/netobserv/netobserv-perf-tests/netobserv-netobserv-perf-tests-main__netobserv-aws-4.22-nightly-x86.yamlci-operator/config/opendatahub-io/data-science-pipelines-operator/OWNERSci-operator/config/opendatahub-io/kubeflow-sdk/OWNERSci-operator/config/opendatahub-io/kubeflow/opendatahub-io-kubeflow-main.yamlci-operator/config/openshift-eng/aos-cd-jobs/OWNERSci-operator/config/openshift-eng/art-tools/OWNERSci-operator/config/openshift-eng/edge-tooling/openshift-eng-edge-tooling-main.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-5.0-nightly-x86.yamlci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-x86.yamlci-operator/config/openshift-eng/rebasebot/openshift-eng-rebasebot-main.yamlci-operator/config/openshift-eng/ship-hook/openshift-eng-ship-hook-main.yamlci-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-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-release-0.2__images.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-ran-two-sno-4.14.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-ran-two-sno-4.16.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-ran-two-sno-4.18.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-ran-two-sno-4.20.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-ran-two-sno-4.21.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__cnf-ran-two-sno-4.22.yamlci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-compute-nrop.yamlci-operator/config/openshift-kni/oran-o2ims/openshift-kni-oran-o2ims-main.yamlci-operator/config/openshift-kni/oran-o2ims/openshift-kni-oran-o2ims-release-4.20.yamlci-operator/config/openshift-kni/oran-o2ims/openshift-kni-oran-o2ims-release-4.21.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/OWNERSci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__cluster-logging-ocp4.15-lp-rosa-classic.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__cluster-logging-ocp4.16-lp-rosa-classic.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__cluster-logging-ocp4.17-lp-rosa-classic.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.14-lp-rosa-hypershift.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.15-lp-rosa-hypershift.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.16-lp-rosa-hypershift.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.17-lp-rosa-hypershift.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.19-lp-rosa-hypershift.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.20-lp-rosa-hypershift.yamlci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.21-lp-rosa-hypershift.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-osd-gcp-staging.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-classic-integration.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-classic-staging.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-integration.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-staging.yamlci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__periodics.yamlci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main.yamlci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main__periodics.yamlci-operator/config/openshift-online/rosa-regional-platform/openshift-online-rosa-regional-platform-main.yamlci-operator/config/openshift-pipelines/performance/openshift-pipelines-performance-main.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.11__openshift-pipelines-ocp4.14-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.13__openshift-pipelines-ocp4.15-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.14__openshift-pipelines-ocp4.14-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.14__openshift-pipelines-ocp4.15-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.14__openshift-pipelines-ocp4.15-lp-rosa-hypershift.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.14__openshift-pipelines-ocp4.16-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.15__openshift-pipelines-ocp4.15-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.15__openshift-pipelines-ocp4.16-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.15__openshift-pipelines-ocp4.16-lp-rosa-hypershift.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.15__openshift-pipelines-ocp4.17-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.15__openshift-pipelines-ocp4.18-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.16__openshift-pipelines-ocp4.17-lp-rosa-classic.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.17__openshift-pipelines-ocp4.17-lp-rosa-classic.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.17__openshift-pipelines-ocp4.17-lp-rosa-hypershift.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.17__openshift-pipelines-ocp4.18-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.18__openshift-pipelines-ocp4.19-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.19__openshift-pipelines-ocp4.20-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.20__openshift-pipelines-ocp-4.21-lp-interop-cr.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.20__openshift-pipelines-ocp4.20-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.21__ocp-4.22-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.21__openshift-pipelines-ocp-4.21-lp-interop-cr.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.21__openshift-pipelines-ocp-4.21-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.21__openshift-pipelines-ocp4.21-e2e-osp.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.22__ocp-4.22-lp-interop.yamlci-operator/config/openshift-pipelines/release-tests/openshift-pipelines-release-tests-release-v1.22__openshift-pipelines-ocp4.21-lp-rosa-hypershift.yamlci-operator/config/openshift-priv/apiserver-network-proxy/openshift-priv-apiserver-network-proxy-main.yamlci-operator/config/openshift-priv/apiserver-network-proxy/openshift-priv-apiserver-network-proxy-release-4.23.yamlci-operator/config/openshift-priv/apiserver-network-proxy/openshift-priv-apiserver-network-proxy-release-5.0.yamlci-operator/config/openshift-priv/apiserver-network-proxy/openshift-priv-apiserver-network-proxy-release-5.1.yamlci-operator/config/openshift-priv/assisted-image-service/openshift-priv-assisted-image-service-v2.53.yamlci-operator/config/openshift-priv/cluster-authentication-operator/openshift-priv-cluster-authentication-operator-master.yamlci-operator/config/openshift-priv/cluster-authentication-operator/openshift-priv-cluster-authentication-operator-release-4.22.yamlci-operator/config/openshift-priv/cluster-authentication-operator/openshift-priv-cluster-authentication-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-authentication-operator/openshift-priv-cluster-authentication-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-authentication-operator/openshift-priv-cluster-authentication-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-main.yamlci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-image-registry-operator/openshift-priv-cluster-image-registry-operator-main.yamlci-operator/config/openshift-priv/cluster-image-registry-operator/openshift-priv-cluster-image-registry-operator-release-4.22.yamlci-operator/config/openshift-priv/cluster-image-registry-operator/openshift-priv-cluster-image-registry-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-image-registry-operator/openshift-priv-cluster-image-registry-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-image-registry-operator/openshift-priv-cluster-image-registry-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-kube-apiserver-operator/openshift-priv-cluster-kube-apiserver-operator-main.yamlci-operator/config/openshift-priv/cluster-kube-apiserver-operator/openshift-priv-cluster-kube-apiserver-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-kube-apiserver-operator/openshift-priv-cluster-kube-apiserver-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-kube-apiserver-operator/openshift-priv-cluster-kube-apiserver-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-kube-controller-manager-operator/openshift-priv-cluster-kube-controller-manager-operator-main.yamlci-operator/config/openshift-priv/cluster-kube-controller-manager-operator/openshift-priv-cluster-kube-controller-manager-operator-release-4.22.yamlci-operator/config/openshift-priv/cluster-kube-controller-manager-operator/openshift-priv-cluster-kube-controller-manager-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-kube-controller-manager-operator/openshift-priv-cluster-kube-controller-manager-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-kube-controller-manager-operator/openshift-priv-cluster-kube-controller-manager-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-logging-operator/openshift-priv-cluster-logging-operator-master.yamlci-operator/config/openshift-priv/cluster-logging-operator/openshift-priv-cluster-logging-operator-release-6.5.yamlci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-master.yamlci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-4.21.yamlci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-4.22.yamlci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-node-tuning-operator/openshift-priv-cluster-node-tuning-operator-main.yamlci-operator/config/openshift-priv/cluster-node-tuning-operator/openshift-priv-cluster-node-tuning-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-node-tuning-operator/openshift-priv-cluster-node-tuning-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-node-tuning-operator/openshift-priv-cluster-node-tuning-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-openshift-apiserver-operator/openshift-priv-cluster-openshift-apiserver-operator-main.yamlci-operator/config/openshift-priv/cluster-openshift-apiserver-operator/openshift-priv-cluster-openshift-apiserver-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-openshift-apiserver-operator/openshift-priv-cluster-openshift-apiserver-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-openshift-apiserver-operator/openshift-priv-cluster-openshift-apiserver-operator-release-5.1.yamlci-operator/config/openshift-priv/cluster-version-operator/openshift-priv-cluster-version-operator-main.yamlci-operator/config/openshift-priv/cluster-version-operator/openshift-priv-cluster-version-operator-release-4.23.yamlci-operator/config/openshift-priv/cluster-version-operator/openshift-priv-cluster-version-operator-release-5.0.yamlci-operator/config/openshift-priv/cluster-version-operator/openshift-priv-cluster-version-operator-release-5.1.yamlci-operator/config/openshift-priv/console-plugin-template/openshift-priv-console-plugin-template-main.yamlci-operator/config/openshift-priv/console-plugin-template/openshift-priv-console-plugin-template-release-4.22.yamlci-operator/config/openshift-priv/console-plugin-template/openshift-priv-console-plugin-template-release-4.23.yamlci-operator/config/openshift-priv/console-plugin-template/openshift-priv-console-plugin-template-release-5.0.yamlci-operator/config/openshift-priv/console-plugin-template/openshift-priv-console-plugin-template-release-5.1.yamlci-operator/config/openshift-priv/console/openshift-priv-console-main.yamlci-operator/config/openshift-priv/console/openshift-priv-console-release-4.23.yamlci-operator/config/openshift-priv/console/openshift-priv-console-release-5.0.yamlci-operator/config/openshift-priv/console/openshift-priv-console-release-5.1.yamlci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-main.yamlci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-release-4.22.yamlci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-release-4.23.yamlci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-release-5.0.yamlci-operator/config/openshift-priv/csi-operator/openshift-priv-csi-operator-release-5.1.yamlci-operator/config/openshift-priv/eventrouter/openshift-priv-eventrouter-master.yamlci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-main.yamlci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-4.22.yamlci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-4.23.yamlci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-5.0.yamlci-operator/config/openshift-priv/hypershift/openshift-priv-hypershift-release-5.1.yamlci-operator/config/openshift-priv/insights-operator/openshift-priv-insights-operator-release-4.22.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-main.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.12.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.13.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.14.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.15.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.15__altinfra.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.16.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.17.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.18.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.19.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.20.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.21.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.22.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-4.23.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-5.0.yamlci-operator/config/openshift-priv/installer/openshift-priv-installer-release-5.1.yamlci-operator/config/openshift-priv/karpenter-operator/openshift-priv-karpenter-operator-main.yamlci-operator/config/openshift-priv/karpenter-operator/openshift-priv-karpenter-operator-release-4.23.yamlci-operator/config/openshift-priv/karpenter-operator/openshift-priv-karpenter-operator-release-5.0.yamlci-operator/config/openshift-priv/karpenter-operator/openshift-priv-karpenter-operator-release-5.1.yamlci-operator/config/openshift-priv/kubevirt-csi-driver/openshift-priv-kubevirt-csi-driver-main.yamlci-operator/config/openshift-priv/kubevirt-csi-driver/openshift-priv-kubevirt-csi-driver-release-4.23.yamlci-operator/config/openshift-priv/kubevirt-csi-driver/openshift-priv-kubevirt-csi-driver-release-5.0.yamlci-operator/config/openshift-priv/kubevirt-csi-driver/openshift-priv-kubevirt-csi-driver-release-5.1.yamlci-operator/config/openshift-priv/log-file-metric-exporter/openshift-priv-log-file-metric-exporter-main.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-main.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.19.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.20.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.21.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yamlci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yamlci-operator/config/openshift-priv/machine-os-images/openshift-priv-machine-os-images-main.yamlci-operator/config/openshift-priv/machine-os-images/openshift-priv-machine-os-images-release-4.23.yamlci-operator/config/openshift-priv/machine-os-images/openshift-priv-machine-os-images-release-5.0.yamlci-operator/config/openshift-priv/machine-os-images/openshift-priv-machine-os-images-release-5.1.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-main.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-4.18.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-4.19.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-4.20.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-4.21.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-4.22.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-4.23.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-5.0.yamlci-operator/config/openshift-priv/monitoring-plugin/openshift-priv-monitoring-plugin-release-5.1.yamlci-operator/config/openshift-priv/must-gather-operator/openshift-priv-must-gather-operator-master.yamlci-operator/config/openshift-priv/must-gather-operator/openshift-priv-must-gather-operator-release-4.21.yamlci-operator/config/openshift-priv/must-gather-operator/openshift-priv-must-gather-operator-release-4.22.yamlci-operator/config/openshift-priv/must-gather-operator/openshift-priv-must-gather-operator-release-4.23.yamlci-operator/config/openshift-priv/must-gather-operator/openshift-priv-must-gather-operator-release-5.0.yamlci-operator/config/openshift-priv/must-gather-operator/openshift-priv-must-gather-operator-release-5.1.yamlci-operator/config/openshift-priv/networking-console-plugin/openshift-priv-networking-console-plugin-release-4.16.yamlci-operator/config/openshift-priv/networking-console-plugin/openshift-priv-networking-console-plugin-release-4.17.yamlci-operator/config/openshift-priv/oadp-operator/openshift-priv-oadp-operator-oadp-1.6__4.22.yamlci-operator/config/openshift-priv/oadp-operator/openshift-priv-oadp-operator-oadp-dev__4.22.yamlci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-main.yamlci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-release-4.20.yamlci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-release-4.21.yamlci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-release-4.22.yamlci-operator/config/openshift-priv/openstack-networking-generic-switch/openshift-priv-openstack-networking-generic-switch-main.yamlci-operator/config/openshift-priv/openstack-networking-generic-switch/openshift-priv-openstack-networking-generic-switch-release-4.23.yamlci-operator/config/openshift-priv/openstack-networking-generic-switch/openshift-priv-openstack-networking-generic-switch-release-5.0.yamlci-operator/config/openshift-priv/openstack-networking-generic-switch/openshift-priv-openstack-networking-generic-switch-release-5.1.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-main.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.12.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.13.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.14.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.15.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.16.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.17.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.18.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.19.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.20.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.21.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.22.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.23.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-5.0.yamlci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-5.1.yamlci-operator/config/openshift-priv/operator-framework-operator-controller/openshift-priv-operator-framework-operator-controller-main.yamlci-operator/config/openshift-priv/operator-framework-operator-controller/openshift-priv-operator-framework-operator-controller-release-4.23.yamlci-operator/config/openshift-priv/operator-framework-operator-controller/openshift-priv-operator-framework-operator-controller-release-5.0.yamlci-operator/config/openshift-priv/operator-framework-operator-controller/openshift-priv-operator-framework-operator-controller-release-5.1.yamlci-operator/config/openshift-priv/origin/openshift-priv-origin-main.yamlci-operator/config/openshift-priv/origin/openshift-priv-origin-release-4.23.yamlci-operator/config/openshift-priv/origin/openshift-priv-origin-release-5.0.yamlci-operator/config/openshift-priv/origin/openshift-priv-origin-release-5.1.yamlci-operator/config/openshift-priv/os/openshift-priv-os-master.yamlci-operator/config/openshift-priv/os/openshift-priv-os-release-4.23.yamlci-operator/config/openshift-priv/os/openshift-priv-os-release-5.0.yamlci-operator/config/openshift-priv/os/openshift-priv-os-release-5.1.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-master.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.16.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.17.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.18.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.19.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.20.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.21.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.22.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-4.23.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-5.0.yamlci-operator/config/openshift-priv/ovn-kubernetes/openshift-priv-ovn-kubernetes-release-5.1.yaml
💤 Files with no reviewable changes (66)
- ci-operator/config/openshift-online/rosa-gap-analysis/openshift-online-rosa-gap-analysis-main.yaml
- ci-operator/config/opendatahub-io/data-science-pipelines-operator/OWNERS
- ci-operator/config/opendatahub-io/kubeflow/opendatahub-io-kubeflow-main.yaml
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.15-lp-interop.yaml
- ci-operator/config/Apicurio/apicurio-registry-system-tests/README.md
- ci-operator/config/cloud-bulldozer/e2e-benchmarking/OWNERS
- ci-operator/config/openshift-logging/extended-logging-tests-interop/OWNERS
- ci-operator/config/insights-qe/iqe-cost-management-plugin/OWNERS
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.16-lp-interop.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/README.md
- ci-operator/config/jws-qe/interop-ocp-ci/OWNERS
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.17-lp-interop.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.15-lp-rosa-hypershift.yaml
- ci-operator/config/ansible/tower-qa/OWNERS
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.15-lp-interop.yaml
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.18-lp-interop.yaml
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.18-lp-interop.yaml
- ci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.14-lp-interop.yaml
- ci-operator/config/cloud-bulldozer/orion/OWNERS
- ci-operator/config/Apicurio/apicurio-registry-system-tests/OWNERS
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.14-lp-rosa-hypershift.yaml
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.17-lp-interop.yaml
- ci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-release-4.21.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__cluster-logging-ocp4.15-lp-rosa-classic.yaml
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.14-lp-interop.yaml
- ci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.18-lp-interop.yaml
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.19-lp-interop.yaml
- ci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.19-lp-interop.yaml
- ci-operator/config/openshift-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-release-0.2__images.yaml
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.19-lp-interop.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.17-lp-interop.yaml
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.20-lp-interop.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.18-lp-interop.yaml
- ci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-main.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.17-lp-rosa-hypershift.yaml
- ci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.16-lp-interop.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.19-lp-interop.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__cluster-logging-ocp4.16-lp-rosa-classic.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.16-lp-interop.yaml
- ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.21-nightly-x86.yaml
- ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.20-nightly-x86.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.15-lp-interop.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.21-lp-rosa-hypershift.yaml
- ci-operator/config/ibmz-eco/isv-operator/ibmz-eco-isv-operator-openshift-4.7.yaml
- ci-operator/config/openshift-hyperfleet/hyperfleet-e2e/openshift-hyperfleet-hyperfleet-e2e-release-0.2__e2e.yaml
- ci-operator/config/ibmz-eco/isv-operator/ibmz-eco-isv-operator-openshift-4.6.yaml
- ci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-master.yaml
- ci-operator/config/ibmz-eco/isv-operator/OWNERS
- ci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.15-lp-interop.yaml
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.13-lp-interop.yaml
- ci-operator/config/insights-qe/iqe-cost-management-plugin/insights-qe-iqe-cost-management-plugin-master__ocp4.16-lp-interop.yaml
- ci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-release-4.22.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.19-lp-rosa-hypershift.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.20-lp-rosa-hypershift.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__openshift-logging-hypershift-4.16-lp-rosa-hypershift.yaml
- ci-operator/config/openshift-priv/operator-framework-operator-controller/openshift-priv-operator-framework-operator-controller-release-5.0.yaml
- ci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-4.23.yaml
- ci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-4.22.yaml
- ci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-5.0.yaml
- ci-operator/config/openshift-logging/extended-logging-tests-interop/openshift-logging-extended-logging-tests-interop-main__cluster-logging-ocp4.17-lp-rosa-classic.yaml
- ci-operator/config/ansible/tower-qa/ansible-tower-qa-devel__ocp4.14-lp-interop.yaml
- ci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-5.1.yaml
- ci-operator/config/jws-qe/interop-ocp-ci/jws-qe-interop-ocp-ci-main__ocp-4.14-lp-interop.yaml
- ci-operator/config/openshift-priv/openshift-tests-private/openshift-priv-openshift-tests-private-release-4.20.yaml
- ci-operator/config/Apicurio/apicurio-registry-system-tests/Apicurio-apicurio-registry-system-tests-main__service-registry-ocp4.17-lp-interop.yaml
- ci-operator/config/openshift-priv/cluster-network-operator/openshift-priv-cluster-network-operator-release-4.21.yaml
✅ Files skipped from review due to trivial changes (20)
- ci-operator/config/openshift-eng/aos-cd-jobs/OWNERS
- ci-operator/config/opendatahub-io/kubeflow-sdk/OWNERS
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.13.yaml
- ci-operator/config/codeready-toolchain/workload-analyzer/OWNERS
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.21.yaml
- ci-operator/config/openshift-priv/kubevirt-csi-driver/openshift-priv-kubevirt-csi-driver-release-4.23.yaml
- OWNERS_ALIASES
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-5.1.yaml
- ci-operator/config/openshift-kni/eco-ci-cd/openshift-kni-eco-ci-cd-main__nightly-compute-nrop.yaml
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.16.yaml
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.19.yaml
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.12.yaml
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.18.yaml
- ci-operator/config/kubev2v/migration-planner/OWNERS
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-5.0.yaml
- ci-operator/config/medik8s/system-tests/OWNERS
- ci-operator/config/openshift-eng/ocp-qe-perfscale-ci/openshift-eng-ocp-qe-perfscale-ci-main__metal-4.22-nightly-x86.yaml
- ci-operator/config/openshift-priv/kubevirt-csi-driver/openshift-priv-kubevirt-csi-driver-main.yaml
- ci-operator/config/openshift-eng/art-tools/OWNERS
- ci-operator/config/openshift-priv/openstack-test/openshift-priv-openstack-test-release-4.14.yaml
Comment on lines
+29
to
+34
| old_umask=$(umask) | ||
| umask 077 | ||
| podman_env_file="$(mktemp /tmp/podman.env.XXXXXX)" | ||
| trap 'rm -f "${podman_env_file}"' EXIT | ||
| umask "$old_umask" | ||
|
|
Contributor
There was a problem hiding this comment.
Apply the umask save/restore pattern consistently across all jobs.
Six jobs in this file were updated to save the original umask, apply restrictive permissions for temp file creation, then restore the original umask. However, several other jobs (including the newly added ocm-fvt-periodic-cs-rosa-hcp-autonode-staging-main at lines 363-402, and existing jobs ocm-fvt-periodic-cs-rosa-hcp-arm-staging-main, ocm-fvt-periodic-cs-rosa-hcp-amd64-staging-main, and others) still use the old pattern where umask 077 is set without restoration.
For consistency and maintainability, apply the umask save/restore pattern to all jobs in this file.
🔐 Recommended pattern for remaining jobs
+ old_umask=$(umask)
+ umask 077
podman_env_file="$(mktemp /tmp/podman.env.XXXXXX)"
trap 'rm -f "${podman_env_file}"' EXIT
- umask 077
+ umask "$old_umask"
+
env -i bash --norc --noprofile << EOF > "${podman_env_file}"Also applies to: 72-77, 115-120, 158-163, 201-206, 244-249
🤖 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-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-staging.yaml`
around lines 29 - 34, Several jobs (notably
ocm-fvt-periodic-cs-rosa-hcp-autonode-staging-main,
ocm-fvt-periodic-cs-rosa-hcp-arm-staging-main,
ocm-fvt-periodic-cs-rosa-hcp-amd64-staging-main and the other jobs referenced)
set umask 077 for temp file creation but do not restore the original umask;
update each job to follow the saved-and-restore pattern used elsewhere: capture
old_umask=$(umask) before setting umask 077, create the podman_env_file with
mktemp, add trap 'rm -f "${podman_env_file}"' EXIT, and then restore the
original umask with umask "$old_umask" after the temp file creation so the
pattern is consistent across all jobs.
Comment on lines
+6
to
+9
| ocm-cli: | ||
| name: ocm-cli | ||
| namespace: ci | ||
| tag: latest |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check if ocm-cli base_image exists in main config
fd -t f 'openshift-online-rosa-e2e-main.yaml' ci-operator/config/openshift-online/rosa-e2e/ --exec cat {} \; | rg -nP 'ocm-cli:' -A3Repository: openshift/release
Length of output: 43
🏁 Script executed:
# First, let's confirm both files exist and examine their structure
cd ci-operator/config/openshift-online/rosa-e2e/
# Check what files exist
ls -la openshift-online-rosa-e2e-main*.yaml
# Get line counts to understand file sizes
wc -l openshift-online-rosa-e2e-main.yaml openshift-online-rosa-e2e-main__periodics.yaml
# Search for base_images sections in both files
echo "=== Main config base_images section ==="
rg -n 'base_images:' openshift-online-rosa-e2e-main.yaml -A 20
echo -e "\n=== Periodics variant base_images section ==="
rg -n 'base_images:' openshift-online-rosa-e2e-main__periodics.yaml -A 20Repository: openshift/release
Length of output: 1883
Remove ocm-cli from base_images or add it to the main config first.
The ocm-cli base image in lines 6-9 should not be added to this variant file. According to the coding guidelines, variant periodic configuration files should include sections copied from the main config. Since ocm-cli does not exist in openshift-online-rosa-e2e-main.yaml, it must be added to the main config before being included in the variant periodic 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/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__periodics.yaml`
around lines 6 - 9, The variant periodic config includes a base image entry
named "ocm-cli" that is not present in the main base_images list; either remove
the "ocm-cli" block from this variant file or add a matching "ocm-cli" entry to
the main config's base_images so the variant only copies from main. Locate the
"ocm-cli" block in the variant periodic file and either delete those four lines
or add an identical "ocm-cli: name: ocm-cli namespace: ci tag: latest" entry
into the main configuration's base_images section so the variant remains a copy
of main.
Comment on lines
+41
to
+45
| - as: verify-commits | ||
| commands: | | ||
| commitchecker --start ${PULL_BASE_SHA:-main} | ||
| container: | ||
| from: commitchecker |
Contributor
There was a problem hiding this comment.
❓ Verification inconclusive
Script executed:
#!/bin/bash
# Verify existing patterns for commitchecker start args in ci-operator configs.
# Expected: release-branch jobs avoid hardcoded `main` fallback, or consistently use PULL_BASE_REF/SHA.
rg -n -C2 'commitchecker\s+--start' ci-operator/config
echo "----"
rg -n -C2 '\$\{PULL_BASE_SHA:-main\}' ci-operator/configRepository: openshift/release
Repository: openshift/release
Exit code: 0
stdout:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.1.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.1.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.1.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.1.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.1.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.0.yaml-57-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.0.yaml-58- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.0.yaml:59: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.0.yaml-60- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-5.0.yaml-61- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.23.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.23.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.23.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.23.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.23.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.21.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.21.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.21.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.21.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.21.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.22.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.22.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.22.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.22.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.22.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.20.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.20.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.20.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.20.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.20.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.19.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.19.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.19.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.19.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.19.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.18.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.18.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.18.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.18.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.18.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.17.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.17.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.17.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.17.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.17.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.16.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.16.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.16.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.16.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-release-4.16.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-master.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-master.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-master.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-master.yaml-59- container:
ci-operator/config/openshift-priv/csi-driver-smb/openshift-priv-csi-driver-smb-master.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.21.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.21.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.21.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.21.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.21.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.0.yaml-59-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.0.yaml-60- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.0.yaml:61: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.0.yaml-62- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.0.yaml-63- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.23.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.23.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.23.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.23.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.23.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.22.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.22.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.22.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.22.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.22.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.1.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.1.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.1.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.1.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.1.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.0.yaml-52-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.0.yaml-53- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.0.yaml:54: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.0.yaml-55- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-5.0.yaml-56- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.1.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.1.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.1.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.1.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-5.1.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.19.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.19.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.19.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.19.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.19.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.18.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.18.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.18.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.18.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.18.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.17.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.17.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.17.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.17.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.17.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.23.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.23.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.23.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.23.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.23.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.16.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.16.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.16.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.16.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.16.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.21.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.21.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.21.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.21.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.21.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.20.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.20.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.20.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.20.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.20.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.14.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.14.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.14.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.14.yaml-59- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.14.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.19.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.19.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.19.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.19.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.19.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.18.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.18.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.18.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.18.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.18.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.17.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.17.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.17.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.17.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.17.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.16.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.16.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.16.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.16.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.16.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.14.yaml-56-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.14.yaml-57- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.14.yaml:58: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.14.yaml-59- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.14.yaml-60- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-master.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-master.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-master.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-master.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-master.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.15.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.15.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.15.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.15.yaml-54- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.15.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-master.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-master.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-master.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-master.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-master.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.16.yaml-55-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.16.yaml-56- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.16.yaml:57: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.16.yaml-58- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.16.yaml-59- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.0.yaml-54-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.0.yaml-55- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.0.yaml:56: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.0.yaml-57- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.0.yaml-58- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.1.yaml-53-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.1.yaml-54- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.1.yaml:55: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.1.yaml-56- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-5.1.yaml-57- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.22.yaml-53-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.22.yaml-54- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.22.yaml:55: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.22.yaml-56- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.22.yaml-57- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.21.yaml-53-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.21.yaml-54- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.21.yaml:55: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.21.yaml-56- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.21.yaml-57- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.20.yaml-53-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.20.yaml-54- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.20.yaml:55: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.20.yaml-56- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.20.yaml-57- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.19.yaml-53-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.19.yaml-54- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.19.yaml:55: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.19.yaml-56- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.19.yaml-57- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.18.yaml-55-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.18.yaml-56- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.18.yaml:57: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.18.yaml-58- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.18.yaml-59- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.17.yaml-55-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.17.yaml-56- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.17.yaml:57: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.17.yaml-58- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.17.yaml-59- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.22.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.22.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.22.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.22.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.22.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.21.yaml-41-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.21.yaml-42- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.21.yaml:43: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.21.yaml-44- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.21.yaml-45- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.20.yaml-41-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.20.yaml-42- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.20.yaml:43: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.20.yaml-44- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.20.yaml-45- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-master.yaml-41-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-master.yaml-42- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-master.yaml:43: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-master.yaml-44- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-master.yaml-45- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.22.yaml-41-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.22.yaml-42- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.22.yaml:43: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.22.yaml-44- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.22.yaml-45- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.16.yaml-89-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.16.yaml-90- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.16.yaml:91: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.16.yaml-92- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.16.yaml-93- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.1.yaml-90-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.1.yaml-91- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.1.yaml:92: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.1.yaml-93- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.1.yaml-94- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.0.yaml-91-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.0.yaml-92- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.0.yaml:93: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.0.yaml-94- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-5.0.yaml-95- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.22.yaml-90-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.22.yaml-91- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.22.yaml:92: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.22.yaml-93- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.22.yaml-94- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.23.yaml-90-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.23.yaml-91- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.23.yaml:92: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.23.yaml-93- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.23.yaml-94- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.21.yaml-98-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.21.yaml-99- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.21.yaml:100: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.21.yaml-101- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.21.yaml-102- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.20.yaml-98-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.20.yaml-99- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.20.yaml:100: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.20.yaml-101- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.20.yaml-102- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.19.yaml-98-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.19.yaml-99- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.19.yaml:100: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.19.yaml-101- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.19.yaml-102- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.18.yaml-98-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.18.yaml-99- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.18.yaml:100: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.18.yaml-101- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.18.yaml-102- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.17.yaml-97-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.17.yaml-98- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.17.yaml:99: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.17.yaml-100- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.17.yaml-101- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.15.yaml-83-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.15.yaml-84- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.15.yaml:85: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.15.yaml-86- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.15.yaml-87- from: commitchecker
--
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.20.yaml-58-- as: verify-commits
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.20.yaml-59- commands: |
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.20.yaml:60: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.20.yaml-61- container:
ci-operator/config/openshift-priv/csi-node-driver-registrar/openshift-priv-csi-node-driver-registrar-release-4.20.yaml-62- from: commitchecker
--
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.15.yaml-51-- as: verify-commits
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.15.yaml-52- commands: |
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.15.yaml:53: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.15.yaml-54- container:
ci-operator/config/openshift-priv/csi-livenessprobe/openshift-priv-csi-livenessprobe-release-4.15.yaml-55- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-master.yaml-90-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-master.yaml-91- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-master.yaml:92: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-master.yaml-93- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-master.yaml-94- from: commitchecker
--
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.23.yaml-53-- as: verify-commits
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.23.yaml-54- commands: |
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.23.yaml:55: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.23.yaml-56- container:
ci-operator/config/openshift-priv/csi-external-snapshotter/openshift-priv-csi-external-snapshotter-release-4.23.yaml-57- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.0.yaml-42-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.0.yaml-43- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.0.yaml:44: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.0.yaml-45- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.0.yaml-46- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.23.yaml-41-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.23.yaml-42- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.23.yaml:43: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.23.yaml-44- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-4.23.yaml-45- from: commitchecker
--
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.14.yaml-83-- as: verify-commits
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.14.yaml-84- commands: |
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.14.yaml:85: commitchecker --start ${PULL_BASE_SHA:-master}
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.14.yaml-86- container:
ci-operator/config/openshift-priv/vmware-vsphere-csi-driver/openshift-priv-vmware-vsphere-csi-driver-release-4.14.yaml-87- from: commitchecker
--
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.1.yaml-41-- as: verify-commits
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.1.yaml-42- commands: |
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.1.yaml:43: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.1.yaml-44- container:
ci-operator/config/openshift-priv/volume-data-source-validator/openshift-priv-volume-data-source-validator-release-5.1.yaml-45- from: commitchecker
--
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.1.yaml-97-- as: verify-commits
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.1.yaml-98- commands: |
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.1.yaml:99: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.1.yaml-100- container:
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.1.yaml-101- from: commitchecker
--
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.0.yaml-98-- as: verify-commits
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.0.yaml-99- commands: |
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.0.yaml:100: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.0.yaml-101- container:
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-5.0.yaml-102- from: commitchecker
--
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.22.yaml-97-- as: verify-commits
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.22.yaml-98- commands: |
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.22.yaml:99: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.22.yaml-100- container:
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.22.yaml-101- from: commitchecker
--
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.23.yaml-97-- as: verify-commits
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.23.yaml-98- commands: |
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.23.yaml:99: commitchecker --start ${PULL_BASE_SHA:-main}
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.23.yaml-100- container:
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.23.yaml-101- from: commitchecker
--
ci-operator/config/openshift-priv/secrets-store-csi-driver/openshift-priv-secrets-store-csi-driver-release-4.21.yaml-97-- as: verify-commits
ci
... [stdout truncated: output exceeded 50000 characters (858924 total). Please modify your command to reduce output size, for example by:
- Using grep/rg to filter results
- Using head/tail to limit lines
- Using --max-count flag with grep/rg
- Processing output with awk/sed to extract only needed information]
Use a release-branch-aware baseline for the verify-commits job.
The fallback ${PULL_BASE_SHA:-main} will validate against main instead of the release-5.1 base when PULL_BASE_SHA is unset, causing mismatched commit checks. This pattern appears elsewhere in the codebase (volume-data-source-validator, secrets-store-csi-driver), but those projects should align too.
Prefer ${PULL_BASE_REF} (or inject the correct branch name) to keep validation branch-correct on release builds.
🤖 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-priv/apiserver-network-proxy/openshift-priv-apiserver-network-proxy-release-5.1.yaml`
around lines 41 - 45, The verify-commits job uses commitchecker with a fallback
of ${PULL_BASE_SHA:-main}, which validates against main instead of the release
branch; update the commitchecker invocation in the verify-commits job (the
commands block that runs "commitchecker --start ...") to use a
release-branch-aware baseline such as ${PULL_BASE_REF:-release-5.1} (or ensure
PULL_BASE_REF is injected) so commit validation runs against the correct release
base instead of main.
Comment on lines
+122
to
+134
| - as: e2e-aws-capi-techpreview-post-install | ||
| skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$ | ||
| steps: | ||
| cluster_profile: openshift-org-aws | ||
| test: | ||
| - as: test | ||
| commands: make e2e | ||
| from: src | ||
| resources: | ||
| requests: | ||
| cpu: 100m | ||
| timeout: 3h0m0s | ||
| workflow: openshift-e2e-aws-techpreview-post-install |
Contributor
There was a problem hiding this comment.
Set always_run: false on the new post-install e2e job.
This new job currently defaults to always running, unlike the adjacent e2e jobs in this file. That can unintentionally increase presubmit load/cost.
Suggested patch
- as: e2e-aws-capi-techpreview-post-install
+ always_run: false
skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$
steps:
cluster_profile: openshift-org-aws📝 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
| - as: e2e-aws-capi-techpreview-post-install | |
| skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$ | |
| steps: | |
| cluster_profile: openshift-org-aws | |
| test: | |
| - as: test | |
| commands: make e2e | |
| from: src | |
| resources: | |
| requests: | |
| cpu: 100m | |
| timeout: 3h0m0s | |
| workflow: openshift-e2e-aws-techpreview-post-install | |
| - as: e2e-aws-capi-techpreview-post-install | |
| always_run: false | |
| skip_if_only_changed: ^docs/|\.md$|^(?:.*/)?(?:\.gitignore|OWNERS|PROJECT|LICENSE)$ | |
| steps: | |
| cluster_profile: openshift-org-aws | |
| test: | |
| - as: test | |
| commands: make e2e | |
| from: src | |
| resources: | |
| requests: | |
| cpu: 100m | |
| timeout: 3h0m0s | |
| workflow: openshift-e2e-aws-techpreview-post-install |
🤖 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-priv/cluster-capi-operator/openshift-priv-cluster-capi-operator-main.yaml`
around lines 122 - 134, The new post-install e2e job
"e2e-aws-capi-techpreview-post-install" is missing an explicit always_run
setting and thus defaults to running for all presubmits; add the key always_run:
false to that job's top-level config (the same level as
skip_if_only_changed/steps/workflow) so it matches the adjacent e2e jobs and
does not run unconditionally in presubmits.
| commands: ./test-prow-e2e.sh | ||
| dependencies: | ||
| - env: CYPRESS_PLUGIN_TEMPLATE_PULL_SPEC | ||
| - env: PLUGIN_TEMPLATE_PULL_SPEC |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for references to the old environment variable name
rg -nP '\bCYPRESS_PLUGIN_TEMPLATE_PULL_SPEC\b' -C3Repository: openshift/release
Length of output: 38350
Verify environment variable rename is coordinated across all related CI configuration files.
The old environment variable name CYPRESS_PLUGIN_TEMPLATE_PULL_SPEC still appears in multiple CI configuration files across both openshift and openshift-priv organizations, including:
- networking-console-plugin (multiple release branches and main)
- console-plugin-template (multiple release branches)
Confirm that this rename is coordinated across all affected repositories and release branches, or document why certain files are intentionally excluded from this change.
🤖 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-priv/console-plugin-template/openshift-priv-console-plugin-template-release-4.22.yaml`
at line 46, You need to ensure the env var rename is applied or documented
consistently: search all CI job configs for the old variable name
CYPRESS_PLUGIN_TEMPLATE_PULL_SPEC and replace it with PLUGIN_TEMPLATE_PULL_SPEC
(or vice‑versa if the rename was reversed) across all related job definitions
for networking-console-plugin and console-plugin-template in both openshift and
openshift-priv orgs and across affected release branches; if any files must
intentionally keep the old name, add a short comment in those job configs
explaining the exception and update any central docs or a changelog entry to
list which repos/branches were updated and which were intentionally excluded.
Comment on lines
+719
to
+725
| reporter_config: | ||
| channel: '#trt-alert-mco' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | ||
| <{{.Status.URL}}|View logs> {{end}}' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yaml"
python - <<'PY'
import re, pathlib
p = pathlib.Path("ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yaml")
t = p.read_text()
for i, m in enumerate(re.finditer(r"report_template:\s*'([^']*)'", t), 1):
tpl = m.group(1)
has_if = "{{if" in tpl
has_end = "{{end}}" in tpl
print(f"template#{i}: has_if={has_if} has_end={has_end}")
if has_end and not has_if:
print(" -> dangling {{end}} detected")
PYRepository: openshift/release
Length of output: 199
🏁 Script executed:
cd /tmp && cat -n ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yaml | sed -n '715,745p'Repository: openshift/release
Length of output: 208
🏁 Script executed:
cat -n ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yaml | sed -n '715,745p'Repository: openshift/release
Length of output: 1201
Remove dangling {{end}} from report_template in two test job configurations.
Lines 724-725 and 739-740 contain {{end}} without a matching {{if}}, making the templates invalid. Both affected templates should remove the trailing {{end}}.
Proposed fix
report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
- <{{.Status.URL}}|View logs> {{end}}'
+ <{{.Status.URL}}|View logs>'📝 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
| reporter_config: | |
| channel: '#trt-alert-mco' | |
| job_states_to_report: | |
| - failure | |
| - error | |
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | |
| <{{.Status.URL}}|View logs> {{end}}' | |
| reporter_config: | |
| channel: '`#trt-alert-mco`' | |
| job_states_to_report: | |
| - failure | |
| - error | |
| report_template: ':failed: 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-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.22.yaml`
around lines 719 - 725, The reporter_config.report_template values include a
dangling "{{end}}" with no matching "{{if}}", which makes the templates invalid;
locate the report_template entries (e.g., under reporter_config with channel
'`#trt-alert-mco`' and the other test job config referenced in the review) and
remove the trailing "{{end}}" token from each template so they contain only the
intended text and link markup.
Comment on lines
+704
to
+710
| reporter_config: | ||
| channel: '#trt-alert-mco' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | ||
| <{{.Status.URL}}|View logs> {{end}}' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yaml"
rg -n "report_template:.*\{\{end\}\}" "$FILE"
rg -n -C2 "as: e2e-(aws|gcp)-mco-disruptive|report_template:" "$FILE"Repository: openshift/release
Length of output: 43
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yaml"
# Check if file exists
if [ -f "$FILE" ]; then
echo "=== File exists ==="
echo "File size: $(wc -l < "$FILE") lines"
echo ""
# Read lines 704-710
echo "=== Lines 704-710 ==="
sed -n '704,710p' "$FILE"
echo ""
# Read lines 719-725
echo "=== Lines 719-725 ==="
sed -n '719,725p' "$FILE"
echo ""
# Search for all report_template occurrences
echo "=== All report_template occurrences ==="
rg -n "report_template:" "$FILE" || echo "No matches found"
else
echo "File does not exist: $FILE"
fiRepository: openshift/release
Length of output: 817
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Search for other report_template examples in ci-operator config
echo "=== Searching for other report_template examples ==="
rg -n "report_template:" ci-operator/config/ | head -20
echo ""
echo "=== Checking for patterns with {{if}} or {{range}} paired with {{end}} ==="
rg -B5 -A2 "report_template:" ci-operator/config/ | grep -E "(report_template:|if|range|end)" | head -40Repository: openshift/release
Length of output: 11902
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Get a complete report_template from windup example
echo "=== Complete report_template from windup example ==="
rg -A5 "report_template: '\{\{if" ci-operator/config/windup/windup-ui-tests/windup-windup-ui-tests-v1.2__mtr-ocp4.19-lp-interop.yaml | head -20
echo ""
echo "=== Complete report_template from MCO file ==="
sed -n '709,710p' ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yaml
echo ""
echo "=== Check for {{end}} in MCO file around the templates ==="
sed -n '704,726p' ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yamlRepository: openshift/release
Length of output: 1666
Remove the unmatched {{end}} in both reporter templates.
Lines 709-710 and 724-725 include {{end}} without a corresponding opening block, making the template invalid. Proper templates like those in other configs use {{if ... {{else}} ... {{end}}' structure; the MCO template lacks this conditional structure and should not end with {{end}}'.
Suggested fix
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
- <{{.Status.URL}}|View logs> {{end}}'
+ report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
+ <{{.Status.URL}}|View logs>'
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
- <{{.Status.URL}}|View logs> {{end}}'
+ report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
+ <{{.Status.URL}}|View logs>'Also applies to: 719-725
🤖 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-priv/machine-config-operator/openshift-priv-machine-config-operator-release-4.23.yaml`
around lines 704 - 710, The reporter_config report templates contain an
unmatched trailing "{{end}}" that makes the Go template invalid; remove the
stray "{{end}}" from the report_template (and the other reporter template under
reporter_config) so each template no longer ends with an unmatched "{{end}}",
leaving the rest of the template text intact and ensuring any conditional blocks
use a proper {{if ...}}{{else}}{{end}} pair if needed.
Comment on lines
+705
to
+711
| reporter_config: | ||
| channel: '#trt-alert-mco' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | ||
| <{{.Status.URL}}|View logs> {{end}}' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yaml"
nl -ba "$FILE" | sed -n '705,712p;720,727p'Repository: openshift/release
Length of output: 104
🏁 Script executed:
cat -n ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yaml | sed -n '700,730p'Repository: openshift/release
Length of output: 1206
🏁 Script executed:
# Search for reporter_config usage and documentation
rg "reporter_config" ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yaml -A 5 | head -40Repository: openshift/release
Length of output: 432
🏁 Script executed:
# Check if there are other reporter templates in the same file for comparison
rg "report_template:" ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yamlRepository: openshift/release
Length of output: 227
🏁 Script executed:
# Search for documentation about reporter_config format
find . -name "*.md" -o -name "*.txt" | xargs grep -l "reporter_config" 2>/dev/null | head -5Repository: openshift/release
Length of output: 233
🏁 Script executed:
# Find CI operator code that might define or use reporter_config
find . -name "*.go" | xargs grep -l "reporter_config\|report_template" 2>/dev/null | head -10Repository: openshift/release
Length of output: 102
🏁 Script executed:
# Look for documentation about reporter format in the release repo
find . -path ./vendor -prune -o -name "*.md" -exec grep -l "report_template\|reporter" {} \; 2>/dev/null | head -10Repository: openshift/release
Length of output: 345
🏁 Script executed:
cat -n ./hack/validate_slack_report_template.goRepository: openshift/release
Length of output: 8245
🏁 Script executed:
# Check broader context around both templates to ensure no wrapping
cat -n ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yaml | sed -n '705,712p;720,727p'Repository: openshift/release
Length of output: 645
Remove unmatched {{end}} from reporter templates at lines 710-711 and 725-726.
Both report_template values in the reporter config end with {{end}} without a matching opening control structure (such as {{if}} or {{range}}). This will cause Go's text/template parser to fail, breaking failure notifications.
Suggested fix
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
- <{{.Status.URL}}|View logs> {{end}}'
+ report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
+ <{{.Status.URL}}|View logs>'Apply the same change to both occurrences (lines 710-711 and 725-726).
📝 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
| reporter_config: | |
| channel: '#trt-alert-mco' | |
| job_states_to_report: | |
| - failure | |
| - error | |
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | |
| <{{.Status.URL}}|View logs> {{end}}' | |
| reporter_config: | |
| channel: '`#trt-alert-mco`' | |
| job_states_to_report: | |
| - failure | |
| - error | |
| report_template: ':failed: 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-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.0.yaml`
around lines 705 - 711, The reporter config's report_template strings contain a
stray closing template action "{{end}}" with no matching opening control; remove
the trailing "{{end}}" from the report_template entries under reporter_config
(both occurrences of report_template) so the templates are valid for Go's
text/template parser while preserving the existing message and URL placeholder
content.
Comment on lines
+704
to
+710
| reporter_config: | ||
| channel: '#trt-alert-mco' | ||
| job_states_to_report: | ||
| - failure | ||
| - error | ||
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | ||
| <{{.Status.URL}}|View logs> {{end}}' |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yaml"
# Show changed area for quick inspection
nl -ba "$file" | sed -n '700,730p'
# Verify unmatched Go-template block terminators in single-quoted report_template values.
python - <<'PY'
import re
from pathlib import Path
p = Path("ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yaml")
txt = p.read_text()
for i, m in enumerate(re.finditer(r"report_template:\s*'([^']*)'", txt, re.S), 1):
t = m.group(1)
opens = len(re.findall(r'{{-?\s*(if|range|with)\b', t))
ends = len(re.findall(r'{{-?\s*end\s*}}', t))
print(f"template#{i}: opens={opens}, ends={ends}")
PYRepository: openshift/release
Length of output: 104
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yaml"
# Show lines 700-730 with line numbers using sed
echo "=== File content (lines 700-730) ==="
sed -n '700,730p' "$file" | sed -n 'l;=' | sed 'N;s/\n/ /'
echo ""
echo "=== Analyzing all report_template values ==="
# Verify unmatched Go-template block terminators in all report_template values
python3 - <<'PY'
import re
from pathlib import Path
p = Path("ci-operator/config/openshift-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yaml")
txt = p.read_text()
lines = txt.split('\n')
# Find all report_template lines
print("All report_template entries found:")
for line_num, line in enumerate(lines, 1):
if 'report_template:' in line:
print(f" Line {line_num}: {line[:80]}")
print("\nAnalyzing report_template Go template syntax:")
# Look for report_template with multiline values (using quotes)
pattern = r"report_template:\s*['\"]([^'\"]*)['\"]"
for i, m in enumerate(re.finditer(pattern, txt, re.MULTILINE), 1):
t = m.group(1)
# Count opening and closing blocks
opens = len(re.findall(r'{{-?\s*(if|range|with)\b', t))
closes = len(re.findall(r'{{-?\s*end\s*}}', t))
print(f"Template #{i}:")
print(f" Content: {t[:100]}")
print(f" Opens: {opens}, Closes: {closes}")
if opens != closes:
print(f" ⚠️ MISMATCH: {closes - opens} extra closing tags" if closes > opens else f" ⚠️ MISMATCH: {opens - closes} missing closing tags")
PYRepository: openshift/release
Length of output: 1820
Remove stray {{end}} from reporter templates.
Both report_template values on lines 709 and 724 contain {{end}} without a matching opening block (no if, range, or with statement), making the Go templates invalid.
Proposed fix
- report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
- <{{.Status.URL}}|View logs> {{end}}'
+ report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*.
+ <{{.Status.URL}}|View logs>'(Same fix applies to both lines 709 and 724)
📝 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
| reporter_config: | |
| channel: '#trt-alert-mco' | |
| job_states_to_report: | |
| - failure | |
| - error | |
| report_template: ':failed: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. | |
| <{{.Status.URL}}|View logs> {{end}}' | |
| reporter_config: | |
| channel: '`#trt-alert-mco`' | |
| job_states_to_report: | |
| - failure | |
| - error | |
| report_template: ':failed: 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-priv/machine-config-operator/openshift-priv-machine-config-operator-release-5.1.yaml`
around lines 704 - 710, The reporter_config's report_template strings contain
stray closing template tags "{{end}}" with no matching opening block; remove the
trailing "{{end}}" from the report_template values so the Go templates are valid
(update the two report_template occurrences under reporter_config to delete the
"{{end}}" token).
Comment on lines
+59
to
+65
| - as: e2e-agent-compact-ipv4 | ||
| capabilities: | ||
| - intranet | ||
| skip_if_only_changed: (^[A-Z]+\.md$)|((^|/)OWNERS$) | ||
| steps: | ||
| cluster_profile: equinix-ocp-metal | ||
| workflow: agent-e2e-compact-ipv4 |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the agent-e2e-compact-ipv4 workflow definition
fd -t f -e yaml 'agent-e2e-compact-ipv4' ci-operator/step-registry | head -5 | xargs -I {} sh -c 'echo "=== {} ===" && cat {}'Repository: openshift/release
Length of output: 2226
Run make update to regenerate CI artifacts.
When modifying CI configuration files in ci-operator/config/, you must regenerate downstream artifacts after making changes. The agent-e2e-compact-ipv4 workflow is properly designed for compact cluster topology testing and does not introduce scheduling constraints that would be problematic.
🤖 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-priv/machine-os-images/openshift-priv-machine-os-images-release-5.0.yaml`
around lines 59 - 65, The CI config change (the workflow: agent-e2e-compact-ipv4
entry under cluster_profile: equinix-ocp-metal) requires regenerating downstream
artifacts; run "make update" in the repository to regenerate files under
ci-operator/config and related generated outputs so the change is propagated
into the CI pipeline.
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
20 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.
This is needed so this
openshift/prometheus-community-windows_exporter#131
PR can merge
This PR adds Windows Exporter CI job configuration for OpenShift 4.22. The primary change is the addition of
openshift-prometheus-community-windows_exporter-release-4.22.yamlunderci-operator/config/openshift/prometheus-community-windows_exporter/, which defines a build job that compiles the Windows Exporter for Windows against OCP 4.22 base images. The job uses therhel-9-golang-1.25-openshift-4.22builder image and executes a test stage that clones the promu build tool and builds the Windows binary withGOOS=windows.The PR also includes various unrelated CI configuration updates across multiple component repositories (Apicurio, ARO-HCP, RedHatQE, Ansible Tower QA, CloudBulldozer, CodeReady Toolchain, FleetShift, IBMZ ISV Operator, Insights QE, JWS QE, KubeVirt, and OpenShift private operator repositories), including reporter configuration additions for Slack notifications, test step updates, and resource limit adjustments. Additionally, the
Makefilecheckconfig container version was updated andkrisnababuwas added to theieng-chaosalias inOWNERS_ALIASES.The changes enable the prometheus-community-windows_exporter upstream project to merge a corresponding PR by establishing the necessary CI infrastructure for testing Windows Exporter builds against OCP 4.22.