Skip to content

Conversation

@stbenjam
Copy link
Member

The VolumeGroupSnapshot e2e test was running twice in CI, causing the second execution to fail with timeouts and crashes. The test suite initializer InitVolumeGroupSnapshottableTestSuite was incorrectly added to both BaseSuites and CSISuites. Since CSISuites is created by appending to BaseSuites, this caused the same test to be registered and executed twice. The second run would fail because it attempted to create volume group snapshot resources that were still cleaning up from the first successful run.

This removes the duplicate entry from CSISuites, ensuring the test only runs once.

Upstream already found this, but cherry-picking that entire change is a little more complex. kubernetes@d0a2a0d#diff-74a1bbe84c67d45f3d4e437f9dcfc98bcae740c9a88e05b803ef284f5a1f6ff0

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Oct 21, 2025
@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from deads2k and jerpeter1 October 21, 2025 20:24
@jsafrane
Copy link

/test e2e-aws-ovn-techpreview

@jsafrane
Copy link

/test e2e-aws-ovn-techpreview

failed to build coreos image

@jsafrane
Copy link

Only one VolumeGroupSnapshottable should create snapshots for multiple volumes in a pod ran.
/lgtm
/retest-required

@jsafrane
Copy link

Should the commit message be <drop>, since it's already fixed upstream?

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
…from CSISuites

The VolumeGroupSnapshot e2e test was running twice in CI, causing the second
execution to fail with timeouts and crashes. The test suite initializer
InitVolumeGroupSnapshottableTestSuite was incorrectly added to both BaseSuites
and CSISuites. Since CSISuites is created by appending to BaseSuites, this
caused the same test to be registered and executed twice. The second run would
fail because it attempted to create volume group snapshot resources that were
still cleaning up from the first successful run.

This removes the duplicate entry from CSISuites, ensuring the test only runs once.
@stbenjam stbenjam force-pushed the fix-duplicate-volumegroupsnapshot-test branch from 7bc7f23 to d3c4628 Compare October 24, 2025 11:15
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2025
@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@stbenjam stbenjam changed the title UPSTREAM: <carry>: Remove duplicate VolumeGroupSnapshottableTestSuite from CSISuites UPSTREAM: <drop>: Remove duplicate VolumeGroupSnapshottableTestSuite from CSISuites Oct 24, 2025
@jsafrane
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2025
@bertinatto
Copy link
Member

/approve

@openshift-ci
Copy link

openshift-ci bot commented Oct 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, jsafrane, stbenjam

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

The pull request process is described here

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 24, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 24, 2025

@stbenjam: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 7bc7f23 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-techpreview d3c4628 link false /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-techpreview-serial d3c4628 link false /test e2e-aws-ovn-techpreview-serial

Full PR test history. Your PR dashboard.

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.

@jsafrane
Copy link

/retest-required

@stbenjam stbenjam changed the title UPSTREAM: <drop>: Remove duplicate VolumeGroupSnapshottableTestSuite from CSISuites NO-JIRA: UPSTREAM: <drop>: Remove duplicate VolumeGroupSnapshottableTestSuite from CSISuites Oct 30, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 30, 2025
@openshift-ci-robot
Copy link

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

In response to this:

The VolumeGroupSnapshot e2e test was running twice in CI, causing the second execution to fail with timeouts and crashes. The test suite initializer InitVolumeGroupSnapshottableTestSuite was incorrectly added to both BaseSuites and CSISuites. Since CSISuites is created by appending to BaseSuites, this caused the same test to be registered and executed twice. The second run would fail because it attempted to create volume group snapshot resources that were still cleaning up from the first successful run.

This removes the duplicate entry from CSISuites, ensuring the test only runs once.

Upstream already found this, but cherry-picking that entire change is a little more complex. kubernetes@d0a2a0d#diff-74a1bbe84c67d45f3d4e437f9dcfc98bcae740c9a88e05b803ef284f5a1f6ff0

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.

@stbenjam
Copy link
Member Author

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 30, 2025
@openshift-ci-robot
Copy link

@stbenjam: The verified label has been added.

In response to this:

/verified bypass

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.

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. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants