Skip to content
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

Sanity: "pagination should detect volumes added between pages" removes volumes it didn't create & other issues #223

Open
davidz627 opened this issue Oct 2, 2019 · 8 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects

Comments

@davidz627
Copy link
Contributor

This test specifically checks for "existing volumes" by doing a ListVolumes call then afterwards does removing all listed volumes

This means that this test could removes all volumes listed even if the volume was not created by this test. This could cause data loss depending on how a consumer is using CSI sanity.

This brings up a larger problem I have with this test too - either

  1. You are consuming csi-sanity and mocking out the back-end (this is what I do) -> this test is way too complicated and depends on the workings of pagination and doesn't feel like a simple "sanity test" like the rest of the package
  2. You are not mocking out the backend -> this test has potential for data loss
@davidz627
Copy link
Contributor Author

/cc @msau42 @lpabon @pohly @darkowlzz

@msau42
Copy link
Collaborator

msau42 commented Oct 2, 2019

I agree that the test should only remove volumes created by the test.
/kind bug
/help

@k8s-ci-robot
Copy link
Contributor

@msau42:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

I agree that the test should only remove volumes created by the test.
/kind bug
/help

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.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Oct 2, 2019
@msau42 msau42 added this to To do in K8s 1.17 Oct 2, 2019
@msau42 msau42 added this to Backlog in K8s 1.18 Dec 4, 2019
@msau42 msau42 removed this from To do in K8s 1.17 Dec 4, 2019
@timoreimann
Copy link
Contributor

I'd be happy to take a stab at this one.

@timoreimann
Copy link
Contributor

/assign @timoreimann

@pohly
Copy link
Contributor

pohly commented Dec 9, 2019

Note that the test is currently disabled (#226) because it was so problematic.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 8, 2020
@msau42
Copy link
Collaborator

msau42 commented Mar 9, 2020

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 9, 2020
@jsafrane jsafrane added this to Backlog in K8s 1.19 Apr 9, 2020
@jsafrane jsafrane moved this from Backlog to To do in K8s 1.19 Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
No open projects
K8s 1.18
  
Backlog
Development

No branches or pull requests

6 participants