Skip to content

Need to address csi-sanity tests failure  #495

Open
@Jainbrt

Description

@Jainbrt

Describe the bug
Need to address csi-sanity tests failure

To Reproduce
Steps to reproduce the behavior:

Command for running csi-sanity tests:

csi-sanity --csi.endpoint=/var/lib/kubelet/plugins/spectrumscale.csi.ibm.com/csi.sock -csi.mountdir=/ibm/fs1/sanity-2 -csi.testvolumeparameters parameter.yaml

failure Summary

[91m[1mSummarizing 23 Failures:[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] CreateVolume [0m[90mshould return appropriate values SingleNodeWriter NoCapacity [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] CreateVolume [0m[90mshould return appropriate values SingleNodeWriter WithCapacity 1Gi [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] CreateVolume [0m[90mshould not fail when requesting to create a volume with already existing name and same capacity [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[0mCreateVolume [0m[91m[1m[It] should fail when requesting to create a volume with already existing name and different capacity [0m
[37m/root/csi-test/pkg/sanity/controller.go:542[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] CreateVolume [0m[90mshould not fail when creating volume with maximum-length name [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] CreateVolume [0m[90mshould create volume from an existing source snapshot [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[0mCreateVolume [0m[91m[1m[It] should fail when the volume source snapshot is not found [0m
[37m/root/csi-test/pkg/sanity/controller.go:614[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[0mDeleteVolume [0m[91m[1m[It] should succeed when an invalid volume id is used [0m
[37m/root/csi-test/pkg/sanity/controller.go:695[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] ValidateVolumeCapabilities [0m[90mshould fail when no volume capabilities are provided [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] ValidateVolumeCapabilities [0m[90mshould return appropriate values (no optional values added) [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[0mValidateVolumeCapabilities [0m[91m[1m[It] should fail when the requested volume does not exist [0m
[37m/root/csi-test/pkg/sanity/controller.go:837[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[0mControllerPublishVolume [0m[91m[1m[It] should fail when no volume capability is provided [0m
[37m/root/csi-test/pkg/sanity/controller.go:897[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[0mControllerPublishVolume [0m[91m[1m[It] should fail when the node does not exist [0m
[37m/root/csi-test/pkg/sanity/controller.go:998[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] volume lifecycle [0m[90mshould work [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mController Service [Controller Server] [0m[91m[1m[AfterEach] volume lifecycle [0m[90mshould be idempotent [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mDeleteSnapshot [Controller Server] [0m[91m[1m[It] should succeed when an invalid snapshot id is used [0m
[37m/root/csi-test/pkg/sanity/controller.go:1348[0m

[91m[1m[Fail] [0m[90mDeleteSnapshot [Controller Server] [0m[91m[1m[AfterEach] should return appropriate values (no optional values added) [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mNode Service [0m[0mNodeUnpublishVolume [0m[91m[1m[It] should remove target path [0m
[37m/root/csi-test/pkg/sanity/node.go:280[0m

[91m[1m[Fail] [0m[90mNode Service [0m[91m[1m[It] should work [0m
[37m/root/csi-test/pkg/sanity/node.go:163[0m

[91m[1m[Fail] [0m[90mNode Service [0m[91m[1m[It] should be idempotent [0m
[37m/root/csi-test/pkg/sanity/node.go:163[0m

[91m[1m[Fail] [0m[90mCreateSnapshot [Controller Server] [0m[91m[1m[AfterEach] should succeed when requesting to create a snapshot with already existing name and same source volume ID [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[91m[1m[Fail] [0m[90mCreateSnapshot [Controller Server] [0m[91m[1m[It] should fail when requesting to create a snapshot with already existing name and different source volume ID [0m
[37m/root/csi-test/pkg/sanity/controller.go:1445[0m

[91m[1m[Fail] [0m[90mCreateSnapshot [Controller Server] [0m[91m[1m[AfterEach] should succeed when creating snapshot with maximum-length name [0m
[37m/root/csi-test/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113[0m

[1m[91mRan 46 of 78 Specs in 576.321 seconds[0m
[1m[91mFAIL![0m -- [32m[1m23 Passed[0m | [91m[1m23 Failed[0m | [33m[1m1 Pending[0m | [36m[1m31 Skipped[0m

Note : results has been attached for closer look

Expected behavior
csi-sanity tests should pass

Metadata

Metadata

Labels

Component: Unit TestCustomer Impact: Localized low impact(2) Temporary / limited perf impact, unnecessary failovers, issues occur while in degraded stateCustomer Probability: Low(1) Issue only occurs during failure condition - disk, server, network, test assert, ...Phase: TestIssue was discovered through TestSeverity: 2Indicates that the issue is critical and must be addressed before milestone.Type: BugIndicates issue is an undesired behavior, usually caused by code error.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions