TRT-2907: Add gcd platform to 5.1-main and 4.23-main views

[openshift-trt-agent]

Summary

• Add gcd (Google Dedicated Cloud) platform to the 5.1-main and 4.23-main Component Readiness views in config/views.yaml
• PR Gcd capability mapping #3899 added the GCD platform variant to the registry and to the 5.0-main and 4.22-main views, but missed the 5.1-main and 4.23-main views
• This caused the warning "Unknown variant value: gcd (for variant Platform from view)" since GCD jobs exist for 5.0/5.1 releases but the views did not include the platform

Test plan

• make lint passes
• make test passes (all unit tests green)
• make e2e passes (153/154 pass; 1 pre-existing failure in TestRegressionCacheLoader due to BigQuery credentials, unrelated to this change)
• Verify warning no longer appears on the 5.0-main and 5.1-main Component Readiness views after deployment

Always review AI generated responses prior to use.
Generated with Claude Code via openshift-developer plugin

[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

[openshift-ci-robot]

@openshift-trt-agent[bot]: This pull request references TRT-2907 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 story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary

• Add gcd (Google Dedicated Cloud) platform to the 5.1-main and 4.23-main Component Readiness views in config/views.yaml
• PR Gcd capability mapping #3899 added the GCD platform variant to the registry and to the 5.0-main and 4.22-main views, but missed the 5.1-main and 4.23-main views
• This caused the warning "Unknown variant value: gcd (for variant Platform from view)" since GCD jobs exist for 5.0/5.1 releases but the views did not include the platform

Test plan

• make lint passes
• make test passes (all unit tests green)
• make e2e passes (153/154 pass; 1 pre-existing failure in TestRegressionCacheLoader due to BigQuery credentials, unrelated to this change)
• Verify warning no longer appears on the 5.0-main and 5.1-main Component Readiness views after deployment

Always review AI generated responses prior to use.
Generated with Claude Code via openshift-developer plugin

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.

[openshift-ci]

Hi @openshift-trt-agent[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[neisw]

add a unit test for the periodic-ci-openshift-release-main-ci-5.0-e2e-gcd-ovn in https://github.com/openshift-trt/sippy/blob/4d84967ac50db09ae6ebf7451e2c9cbcf41e17fe/pkg/variantregistry/ocp_test.go#L23 the platform should be gcd and the release 5.0

[openshift-trt-agent]

Done. Added test case for periodic-ci-openshift-release-main-ci-5.0-e2e-gcd-ovn verifying platform=gcd and release=5.0, along with the component/capability variants (Installer/GCPSovereignCloudInstall). Also updated the variant snapshot to fix a pre-existing gcd JobTier mismatch (candidate -> standard).

---

AI-assisted response via Claude Code

[neisw]

I believe we need to add a case for gcd platform to skip using the value from the cluster

[neisw]

convert this from draft to a pr

[openshift-trt-agent]

Done. Added gcd to the platform skip list in CalculateVariantsForJob so cluster data doesn't override the job-name-derived gcd platform with gcp, matching the existing pattern for rosa and osd-gcp.

---

AI-assisted response via Claude Code

[openshift-trt-agent]

Done. Converted from draft to ready for review.

---

AI-assisted response via Claude Code

[neisw]

/ok-to-test

[neisw]

update the new test to pass in a variants file the specified the gcp platform similar to https://github.com/openshift-trt/sippy/blob/f82b6591bea13949cc7618fcb3c2459fff3b56dd/pkg/variantregistry/ocp_test.go#L156

[openshift-trt-agent]

Done. Added variantsFile with "Platform": "gcp" to the GCD test case, verifying that cluster data reporting gcp does not override the gcd platform derived from the job name.

---

AI-assisted response via Claude Code

[openshift-merge-bot]

Scheduling required tests:
/test e2e

[openshift-trt-agent]

CI failure (not fixing): ci/prow/e2e

Classification: pre_existing

Evidence: The e2e job (link) fails with 4 test failures in test/e2e/componentreadiness/triage: Test_TriageAPI/get_with_expanded_regressions and Test_TriagePotentialMatchingRegressions/find_potential_matching_regressions. This PR changes only config/views.yaml, pkg/variantregistry/ocp.go, pkg/variantregistry/ocp_test.go, and pkg/variantregistry/snapshot.yaml, none of which affect the failing triage e2e tests (which use config/seed-views.yaml). The identical 4 failures appear on unrelated open PRs #3942 and #3944, confirming this is a fleet-wide pre-existing issue.

Action needed: Human or infra follow-up required — not addressed in this PR.

---

AI-assisted response via Claude Code

[neisw]

/test e2e

[neisw]

/test e2e

[neisw]

/test e2e

[neisw]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, openshift-trt-agent[bot]

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 [neisw]

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

[openshift-ci]

@openshift-trt-agent: 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.