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

Raw volumes coverage improvements #269

Merged
merged 1 commit into from
Jun 9, 2020

Conversation

taaraora
Copy link
Contributor

@taaraora taaraora commented May 31, 2020

Raw volumes were added to the next cases:

  • ExpandVolume [Controller Server]
  • CreateSnapshot [Controller Server]
  • DeleteSnapshot [Controller Server]
  • ListSnapshots [Controller Server]
  • ControllerPublishVolume
  • CreateVolume
    • from snapshot
    • from source volume

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

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?:

--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

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 31, 2020
@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 31, 2020
@k8s-ci-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 31, 2020
@taaraora taaraora force-pushed the raw-volumes-update branch 2 times, most recently from af9d6fb to e3f6925 Compare June 1, 2020 23:57
@@ -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
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@pohly
Copy link
Contributor

pohly commented Jun 2, 2020

/ok-to-test

Please add some short release note text to the PR description.

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 2, 2020
- 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>
@taaraora
Copy link
Contributor Author

taaraora commented Jun 3, 2020

/retest

@taaraora taaraora changed the title [WIP] Raw volumes coverage improvements Raw volumes coverage improvements Jun 3, 2020
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jun 3, 2020
@taaraora
Copy link
Contributor Author

taaraora commented Jun 3, 2020

@pohly release note text was added.

@taaraora taaraora requested a review from pohly June 3, 2020 17:29
@msau42
Copy link
Collaborator

msau42 commented Jun 4, 2020

/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
Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

Copy link
Contributor

@pohly pohly left a 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

@taaraora taaraora requested a review from pohly June 8, 2020 17:13
@taaraora
Copy link
Contributor Author

taaraora commented Jun 8, 2020

I agree I've updated release note.

Copy link
Contributor

@pohly pohly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 8, 2020
@pohly
Copy link
Contributor

pohly commented Jun 8, 2020

@jsafrane do you want to approve?

@pohly
Copy link
Contributor

pohly commented Jun 9, 2020

/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 9, 2020
@k8s-ci-robot k8s-ci-robot merged commit 2302fbd into kubernetes-csi:master Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants