Block build02 related to sigstore issue

[deepsm007]

/cc @openshift/test-platform

https://redhat.enterprise.slack.com/archives/CHY2E1BL4/p1779268528961709

Blocks GCP Build Cluster build02 Due to Sigstore Issue

This PR blocks the build02 GCP build cluster from accepting new Prow jobs by setting its blocked status to true in the cluster configuration.

Changes

core-services/sanitize-prow-jobs/_clusters.yaml

• Sets gcp cluster build02 to blocked: true (was previously blocked: false)
• This prevents new jobs from being scheduled on this GCP-based build cluster
• build02 retains its capabilities (gcp, kvm, nested-podman) and capacity configuration (50 slots)

Context

The blocking is related to an ongoing sigstore verification issue. This follows a recent unblocking (PR #79418) that brought build02 back into rotation with 50% capacity. The cluster is a GCP-based build resource with KVM and nested container support capabilities used for OpenShift CI testing infrastructure.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@deepsm007: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 51862a45-70ac-44ec-8a8a-33bcbf3cfa06

📥 Commits

Reviewing files that changed from the base of the PR and between 70f74fc and 3c52b51.

📒 Files selected for processing (1)

• core-services/sanitize-prow-jobs/_clusters.yaml

---

Walkthrough

The PR updates the Prow job sanitization configuration to block the build02 cluster on gcp by changing its blocked flag from false to true, preventing that cluster's jobs from running.

Changes

Build Configuration Update

Layer / File(s)	Summary
Block build02 cluster core-services/sanitize-prow-jobs/_clusters.yaml	The blocked flag for the gcp cluster build02 is changed from false to true.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• openshift/release#79418: Also modifies the same blocked flag for gcp cluster build02, but sets it to false instead; these PRs directly conflict on the same configuration entry.

Suggested labels

lgtm, rehearsals-ack

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Block build02 related to sigstore issue' directly matches the changeset, which blocks the build02 cluster by setting blocked: true.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR modifies only a Prow job configuration YAML file, not Ginkgo test code. The check for stable test names is not applicable to configuration files.
Test Structure And Quality	✅ Passed	PR modifies only YAML configuration files (_clusters.yaml, _config.yaml, OWNERS, README.md) with no Ginkgo test code present; custom check is not applicable.
Microshift Test Compatibility	✅ Passed	PR does not add any Ginkgo e2e tests; it only modifies a Prow job cluster configuration file (_clusters.yaml). The custom check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only a Prow jobs YAML configuration file, not adding new Ginkgo e2e tests. SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR modifies a Prow build cluster configuration file, not deployment manifests, operator code, or controllers. No scheduling constraints or topology-aware code is introduced.
Ote Binary Stdout Contract	✅ Passed	PR contains only YAML configuration changes to cluster definitions, not OTE binary code. No code-level stdout violations possible.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR does not add any Ginkgo e2e tests; it only modifies a YAML configuration file to block the build02 cluster. Custom check is not applicable.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

@deepsm007: 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, droslean

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:

• core-services/sanitize-prow-jobs/OWNERS [deepsm007,droslean]

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