-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
e2e: restore volume lifecycle check for most tests #104863
e2e: restore volume lifecycle check for most tests #104863
Conversation
kubernetes@f1e1f3a disable the check to work around an issue in one test. It's better to keep the check enabled by default and only disable it for that test.
@pohly: 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. |
This PR fixes two distruptive subpath test failures. 1. disable --check-volume-lifecycle check 2. skip hostpath driver tests on graceful pod deletion test too. See details in #103651 (comment) Change-Id: Ibecd051be865feea5f2a92d22ade848367400939
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jingxu97, pohly 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 cleanup
What this PR does / why we need it:
f1e1f3a
disabled the check to work around an issue in one test. It's better to keep the
check enabled by default and only disable it for that test.
Special notes for your reviewer:
I've tested locally that it changes the parameters, but the test itself doesn't run in a
local-up-cluster.sh
. Is there a pre-submit check where we can see the effect?Does this PR introduce a user-facing change?
/cc @jingxu97