Add Platform:metal variant for agent baremetal jobs

[redhat-chai-bot]

Agent baremetal jobs (e.g. e2e-agent-compact-*, e2e-agent-ha-dualstack-*, e2e-agent-sno-*) deploy on bare metal but don't have -metal in their job names. This causes setPlatform() in the variant registry to skip them entirely, leaving them with no Platform variant dimension in BigQuery's job_variants table.

This blocks the new Installer / Agent based installation component from appearing in Component Readiness — because CR filters on Platform via an intersect query, jobs without any Platform row are invisible regardless of which Platform filter value you select.

Changes

• Added {"-e2e-agent-", "metal"} pattern to setPlatform() in pkg/variantregistry/ocp.go, placed above the generic {"-metal", "metal"} entry (first-match-wins semantics)
• Regenerated pkg/variantregistry/snapshot.yaml via make update-variants

Impact

106 agent jobs across all tracked releases now gain Platform:metal. No other variant dimensions are affected.

Context

Discussion thread: https://redhat-internal.slack.com/archives/C01CQA76KMX (forum-ocp-release-oversight)

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[coderabbitai]

Warning

Review limit reached

@redhat-chai-bot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 6553f344-6746-4652-bc40-4fa0c4e26f3e

📥 Commits

Reviewing files that changed from the base of the PR and between 6ab2e82 and 186bb6f.

📒 Files selected for processing (2)

• pkg/variantregistry/ocp.go
• pkg/variantregistry/snapshot.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[andfasano]

/lgtm

[stbenjam]

/approve

[openshift-merge-bot]

Scheduling required tests:
/test e2e

[stbenjam]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, redhat-chai-bot, stbenjam

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [stbenjam]

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

[openshift-ci]

@redhat-chai-bot: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.