-
Notifications
You must be signed in to change notification settings - Fork 159
Fix resize test failure #379
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
Conversation
/assign @davidz627 |
test/run-k8s-integration.sh
Outdated
@@ -23,6 +23,7 @@ export GCE_PD_VERBOSITY=9 | |||
make -C ${PKGDIR} test-k8s-integration | |||
|
|||
base_cmd="${PKGDIR}/bin/k8s-integration-test \ | |||
--kube-feature-gates=\"ExpandCSIVolumes=true\" |
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.
can you add this to the local script too (or a comment saying to bring up your cluster with this feature gate or it wont work if the script doesn't bring up a cluster)
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.
I'm actually about to remove this, since we don't want resize test in latest yet
a21bbb0
to
b7ae1ef
Compare
/test pull-gcp-compute-persistent-disk-csi-driver-kubernetes-integration |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidz627, verult 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 |
Looks like this turned the tests green, thanks @verult!! |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes resize tests that was broken by #364
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Locally verified with k8s master, with
ExpandCSIVolumes
feature gate enabled. Also manually verified resize operation with dev deployment.Does this PR introduce a user-facing change?: