You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSI sanity test output reports ExpandVolume test case failed when my storage plugin tested through CSI sanity test v2.2.0. The CSI sanity test expect 11 GB, but my storage plugin returns 20 GB after expanding volume.
My storage system expands volume 10 GB each time. But the sanity test set the DefTestExpandIncrement as 1 GB each time. I think we can add a flag in CSI sanity test to allow user to set the TestVolumeExpandSize.
Test output:
------------------------------
••STEP: reusing connection to CSI driver at /var/lib/kubelet/plugins/disk.csi.qingcloud.com/csi.sock
STEP: creating mount and staging directories
STEP: creating a new volume
STEP: expanding the volume
cleanup: deleting sanity-expand-volume-D08CE596-10087AD6 = vol-9qxvld3m
------------------------------
• Failure [45.027 seconds]
ExpandVolume [Controller Server]
/root/mygo/src/github.com/kubernetes-csi/csi-test/pkg/sanity/tests.go:44
should work [It]
/root/mygo/src/github.com/kubernetes-csi/csi-test/pkg/sanity/controller.go:2123
Expected
<int64>: 21474836480
to equal
<int64>: 11811160064
/root/mygo/src/github.com/kubernetes-csi/csi-test/pkg/sanity/controller.go:2163
------------------------------
flag.BoolVar(&version, prefix+"version", false, "Version of this program")
flag.StringVar(&config.TargetPath, prefix+"mountdir", os.TempDir()+"/csi-mount", "Mount point for NodePublish")
flag.StringVar(&config.StagingPath, prefix+"stagingdir", os.TempDir()+"/csi-staging", "Mount point for NodeStage if staging is supported")
flag.StringVar(&config.CreateTargetPathCmd, prefix+"createmountpathcmd", "", "Command to run for target path creation")
flag.StringVar(&config.CreateStagingPathCmd, prefix+"createstagingpathcmd", "", "Command to run for staging path creation")
flag.IntVar(&config.CreatePathCmdTimeout, prefix+"createpathcmdtimeout", 10, "Timeout for the commands to create target and staging paths, in seconds")
flag.StringVar(&config.RemoveTargetPathCmd, prefix+"removemountpathcmd", "", "Command to run for target path removal")
flag.StringVar(&config.RemoveStagingPathCmd, prefix+"removestagingpathcmd", "", "Command to run for staging path removal")
flag.IntVar(&config.RemovePathCmdTimeout, prefix+"removepathcmdtimeout", 10, "Timeout for the commands to remove target and staging paths, in seconds")
CSI sanity test output reports ExpandVolume test case failed when my storage plugin tested through CSI sanity test v2.2.0. The CSI sanity test expect 11 GB, but my storage plugin returns 20 GB after expanding volume.
My storage system expands volume 10 GB each time. But the sanity test set the
DefTestExpandIncrement
as 1 GB each time. I think we can add a flag in CSI sanity test to allow user to set theTestVolumeExpandSize
.Test output:
csi-test/cmd/csi-sanity/sanity_test.go
Lines 37 to 55 in 82b0519
csi-test/pkg/sanity/controller.go
Lines 54 to 61 in 82b0519
The text was updated successfully, but these errors were encountered: