New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix storage e2e snapshot test deletion order #99161
Conversation
@Jiawei0227: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
/assign @chrishenzie |
d3aa032
to
24773a0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than one comment this lgtm!
/lgtm
@@ -269,9 +269,17 @@ func (s *snapshottableTestSuite) DefineTests(driver storageframework.TestDriver, | |||
framework.ExpectNoError(err) | |||
|
|||
ginkgo.By("should delete the VolumeSnapshotContent according to its deletion policy") | |||
err = storageutils.DeleteAndWaitSnapshot(dc, vs.GetNamespace(), vs.GetName(), framework.Poll, f.Timeouts.SnapshotDelete) | |||
|
|||
// Delete both Snapshot and PVC at the same time because different storage systems |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can this comment be clarified? Does this mean the storage system expects the PVC to be deleted before the snapshot is deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
@@ -269,9 +269,17 @@ func (s *snapshottableTestSuite) DefineTests(driver storageframework.TestDriver, | |||
framework.ExpectNoError(err) | |||
|
|||
ginkgo.By("should delete the VolumeSnapshotContent according to its deletion policy") | |||
err = storageutils.DeleteAndWaitSnapshot(dc, vs.GetNamespace(), vs.GetName(), framework.Poll, f.Timeouts.SnapshotDelete) | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is DeleteAndWaitSnapshot used in any other tests? Will those other tests have the same issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's being used in the csi_mock_volume test and It seems the mock driver is okay with the ordering.
24773a0
to
c4dfee6
Compare
/approve |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrishenzie, Jiawei0227, msau42, xing-yang 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Some storage system has restrict ordering of snapshot deletion and PVC deletion. So we should delete both of them in parallel to let the CSI driver handle the deletion correctly.
Which issue(s) this PR fixes:
Fixes # #96719
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig storage
/cc @msau42 @xing-yang @chrishenzie