Skip to content

[release-5.0] TRT-2930: skip regional-PD e2e on GCP families without pd-standard - #31575

Open
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-31572-to-release-5.0
Open

[release-5.0] TRT-2930: skip regional-PD e2e on GCP families without pd-standard#31575
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-31572-to-release-5.0

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #31572

/assign stbenjam

[sig-storage][Jira:"Storage"][Driver: pd.csi.storage.gke.io] "regional PD
should store data and sync across zones" provisions a regional pd-standard
PersistentDisk and attaches it to the worker that runs the test pod. Several
GCP families cannot attach pd-standard - C4/C4A/C4D and N4 are Hyperdisk-only,
and C3/C3D support only pd-ssd/pd-balanced - so the attach fails
deterministically:

  AttachVolume.Attach failed: googleapi: Error 400:
  Regional disks is not supported for n4-standard-8 machine type

The test already guarded the cross-zone reattach against such a control
plane, but not the primary pod's worker, so it still failed hard on N4
workers. Skip the whole test in BeforeEach when the workers use a family
without pd-standard; on pd-standard-capable workers (e.g. N2) it runs
unchanged.

The machine-family check is consolidated into a single anyNodeLacksPDStandard
helper (shared by the worker and control-plane guards) backed by
familyLacksPDStandard / nodeInstanceType, and the family list now includes
c4d. Adds table-driven and fake-clientset unit tests for the new helpers.

This lets the GCP jobs that run openshift/conformance/parallel move to N4
without the temporary per-job TEST_SKIPS added in openshift/release. It
should be backported to release-5.1, release-5.0 and release-4.23 (the
branches that carry this test). Lineage: test added in STOR-3063.

Assisted-By: Claude Opus 4.8
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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-ci-robot commented Aug 28, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: TRT-2930

Details

In response to this:

This is an automated cherry-pick of #31572

/assign stbenjam

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 openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Aug 28, 2026
@coderabbitai

coderabbitai Bot commented Aug 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: cbfa7f68-152f-4761-8d34-ccb3dc20ead7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@openshift-ci
openshift-ci Bot requested review from bertinatto and tsmetana August 28, 2026 00:46
@openshift-ci

openshift-ci Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign gnufied for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-ci

openshift-ci Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants