csi-test
csi-test copied to clipboard
kubernetes-csi
CSI test frameworks
Squashed 'release-tools/' changes from e4dab7f..7fe5149 [7fe5149](https://github.com/kubernetes-csi/csi-release-tools/commit/7fe5149) Merge [pull request #200](https://github.com/kubernetes-csi/csi-release-tools/pull/200) from pohly/bump-kubernetes-version [70915a8](https://github.com/kubernetes-csi/csi-release-tools/commit/70915a8) prow.sh: update snapshotter version [31a3f38](https://github.com/kubernetes-csi/csi-release-tools/commit/31a3f38) Merge [pull request #199](https://github.com/kubernetes-csi/csi-release-tools/pull/199) from pohly/bump-kubernetes-version [7577454](https://github.com/kubernetes-csi/csi-release-tools/commit/7577454) prow.sh: bump Kubernetes to v1.22.0...
In some storage systems when trying to create a volume from an existing volume we have to wait for the copy process to be finish before we try to delete...
From https://github.com/kubernetes-csi/csi-test/pull/297#discussion_r568520680: We discussed this a bit further on Monday. @msau42 pointed out that it is valid when a CSI driver refuses to delete PVCs that have snapshots. It is...
All of the "should return empty when" tests have a conceptual problem: the don't ensure that there are snapshots to return. In other words, a broken driver that doesn't check...
This test makes the assumption that one can distinguish between a valid and invalid token and it also makes the assumption that `invalid-token` is actually an invalid token. AFAIK there...
According to the [CreateVolume specs](https://github.com/container-storage-interface/spec/blob/master/spec.md#createvolume) a volume should not set `CapacityBytes` (or set it to 0) to indicate that the capacity is unknown. ``` // The capacity of the volume...
This test specifically checks for "existing volumes" by doing a `ListVolumes` call then afterwards does `removing all listed volumes` This means that this test could removes all volumes listed even...
#### Brief: I am developing a CSI plugin, and at first stages I do not provide dynamic volume provisioning API support (which is a valid plugin according to CSI spec)....
The test (in pkg/sanity/controller.go) steps: Step 1: The test checks how many volumes are already present: vols, err := c.ListVolumes( context.Background(), &csi.ListVolumesRequest{}) totalVols := len(vols.GetEntries()) Step 2: The test adds...
~~~ // A token to specify where to start paginating. Set this field to // `next_token` returned by a previous `ListSnapshots` call to get the // next page of entries....
