Skip to content

Conversation

@dfajmon
Copy link
Contributor

@dfajmon dfajmon commented Dec 2, 2025

Removing the tests for techpreview and only keeping the GA version.
For GCP, we need a custom job because we need the n4 node type.

VAC tests are already running as part of the default CSI job.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 2, 2025
@openshift-ci-robot
Copy link
Contributor

@dfajmon: This pull request explicitly references no jira issue.

Details

In response to this:

Removing the tests for techpreview and only keeping the GA version.
For GCP, we need a custom job because we need the n4 node type.

VAC tests are already running as part of the default CSI job.

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 requested review from RomanBednar and gnufied December 2, 2025 21:38
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 2, 2025
@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 3, 2025
@radeore
Copy link
Contributor

radeore commented Dec 15, 2025

/retitle STOR-2543: Upgrade VolumeAttributesClass tests to GA

@openshift-ci openshift-ci bot changed the title NO-JIRA: upgrade VolumeAttributesClass tests to GA STOR-2543: Upgrade VolumeAttributesClass tests to GA Dec 15, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 15, 2025

@dfajmon: This pull request references STOR-2543 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 "4.22.0" version, but no target version was set.

Details

In response to this:

Removing the tests for techpreview and only keeping the GA version.
For GCP, we need a custom job because we need the n4 node type.

VAC tests are already running as part of the default CSI job.

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.

@jsafrane
Copy link
Contributor

/lgtm
/approve
I can see VAC tests in e2e-aws-csi in openshift/csi-operator#475 without any TP

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 17, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@dfajmon: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-gcp-pd-csi-driver-master-e2e-gcp-csi-volumeattributesclass openshift/gcp-pd-csi-driver presubmit Presubmit changed
pull-ci-openshift-gcp-pd-csi-driver-release-4.21-e2e-gcp-csi-volumeattributesclass openshift/gcp-pd-csi-driver presubmit Presubmit changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@jsafrane
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dfajmon, jsafrane

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:

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

@radeore
Copy link
Contributor

radeore commented Dec 18, 2025

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@radeore: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 18, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 8852d5d into openshift:master Dec 18, 2025
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants