-
Notifications
You must be signed in to change notification settings - Fork 151
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
Raw volumes coverage improvements #269
Raw volumes coverage improvements #269
Conversation
Hi @taaraora. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
af9d6fb
to
e3f6925
Compare
pkg/sanity/sanity.go
Outdated
@@ -190,7 +190,7 @@ func NewTestConfig() TestConfig { | |||
StagingPath: os.TempDir() + "/csi-staging", | |||
CreatePathCmdTimeout: 10 * time.Second, | |||
RemovePathCmdTimeout: 10 * time.Second, | |||
TestVolumeSize: 10 * 1024 * 1024 * 1024, // 10 GiB | |||
TestVolumeSize: 1 * 1024 * 1024 * 1024, // 10 GiB |
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.
Comment also needs to be updated.
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 had not enough space on my k8s cluster and didn't find flag to set test volume size at that time, that's why I changed it. But this change is not intended to be in final patch and I finally found --csi.testvolumesize
flag.
It is rolled back now.
/ok-to-test Please add some short release note text to the PR description. |
- ExpandVolume [Controller Server] - CreateSnapshot [Controller Server] - DeleteSnapshot [Controller Server] - ListSnapshots [Controller Server] - ControllerPublishVolume - CreateVolume - from snapshot - from source volume Signed-off-by: Dmytro Tsapko <dmytro.tsapko@gmail.com>
e3f6925
to
6f6334d
Compare
/retest |
@pohly release note text was added. |
/assign @jsafrane |
@@ -416,7 +416,8 @@ var _ = DescribeSanity("Controller Service [Controller Server]", func(sc *TestCo | |||
Expect(serverError.Code()).To(Equal(codes.InvalidArgument)) | |||
}) | |||
|
|||
It("should return appropriate values SingleNodeWriter NoCapacity Type:Mount", func() { | |||
// TODO: whether CreateVolume request with no capacity should fail or not depends on driver implementation |
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.
The commit message mentions added new tests, but all I find in the diff are changes to existing tests?
In this case here, the test doesn't even get changed, just its name.
I'm confused, sorry.
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.
The idea of this PR is to make possible running all the above-mentioned test cases for raw volumes.
Currently when sanity tests are executed with the flag --csi.testvolumeaccesstype=block
above mentioned test cases are still executed for mount
volumes.
My patch is based on the point, that all those cases use MakeCreateVolumeReq
function for volume creation and I've just made it to produce raw volume when tests are executed for raw volumes.
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.
@pohly In commit message I wanted to say that raw volumes support was added to all those tests.
I've checked that list of tests cases and sure that when tests are executed with --csi.testvolumeaccesstype=block
flag, all calls which bear volume access type are constructed with proper volume access type.
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 still find the release notes confusing:
Raw volumes tests were introduced for the next cases: ExpandVolume [Controller Server], CreateSnapshot [Controller Server], DeleteSnapshot [Controller Server], ListSnapshots [Controller Server], ControllerPublishVolume, Create Volume from snapshot, Clone Volume.
Is the following description correct? If so, please update the release notes:
--csi.testvolumeaccesstype=block is now also used by the following tests: ExpandVolume [Controller Server], CreateSnapshot [Controller Server], DeleteSnapshot [Controller Server], ListSnapshots [Controller Server], ControllerPublishVolume, Create Volume from snapshot, Clone Volume
I agree I've updated release note. |
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.
/lgtm
@jsafrane do you want to approve? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly, taaraora 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 |
Raw volumes were added to the next cases:
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: