-
Notifications
You must be signed in to change notification settings - Fork 217
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
relax volume lifecycle checks by default #293
relax volume lifecycle checks by default #293
Conversation
The recently introduced "still in use" check revealed a bug in Kubernetes (kubernetes/kubernetes#101911). While the check itself is correct, enabling it would cause a lot of test flakes. Therefore the check has to be disabled until all Kubernetes versions that we test against are fixed.
75554c0
to
30b4e6a
Compare
6aac6a1
to
30b4e6a
Compare
@pohly: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly, 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 failing-test
What this PR does / why we need it:
The recently introduced "still in use" check revealed a bug in
Kubernetes (kubernetes/kubernetes#101911). While
the check itself is correct, enabling it would cause a lot of test
flakes. Therefore the check has to be disabled until all Kubernetes
versions that we test against are fixed.
Which issue(s) this PR fixes:
Related-to kubernetes/kubernetes#101911
Does this PR introduce a user-facing change?: