[BUG]: VolumeHealthMetricSuite test failure

[vincent1chen]

Bug Description

VolumeHealthMetricSuite always fail . Following doc,  I have enabled controller and node  “healthMonitor”  parameter.

[root@registry ~]# cat csi-powerstore/cert/wr-certify-config.yaml

storageClasses:

  - name: powerstore-ext4

    minSize: 2Gi

    rawBlock: false

    RWX: false

    VolumeHealth: true

    RWOP: false

    VGS: false

[root@registry ~]# cat csi-powerstore/cert/wr-certify-config.yaml
storageClasses:

• name: powerstore-ext4
  minSize: 2Gi
  rawBlock: false

  expansion: true

  clone: true

  snapshot: true

  RWX: false
  VolumeHealth: true
  RWOP: false
  VGS: false

[root@registry ~]# ./cert-csi certify --cert-config csi-powerstore/cert/wr-certify-config.yaml  --vsc powerstore-snapshot --vgs-volume-label wrvgslabel --driver-name csi-powerstore --vgs-name wrvgs --path csi-powerstore/cert/ --sequential -l 5

[2023-07-29 01:56:07]  INFO Starting cert-csi; ver. 0.8.1

[2023-07-29 01:56:07]  INFO Suites to run with powerstore-ext4 storage class:

[2023-07-29 01:56:07]  INFO 1. ScalingSuite {replicas: 2, volumes: 5, volumeSize: 2Gi}

[2023-07-29 01:56:07]  INFO 2. VolumeHealthMetricSuite {pods: 1, volumes: 1, size: 2Gi}

Does it look OK? (Y)es/(n)Y

… …

[2023-07-29 01:56:56]  INFO Starting VolumeHealthMetricSuite with powerstore-ext4 storage class

[2023-07-29 01:56:56]  INFO Successfully created namespace volume-health-metrics-74bd6cd2

[2023-07-29 01:56:56]  INFO Waiting for all pods in volume-health-metrics-74bd6cd2 to be READY

[2023-07-29 01:57:04]  INFO All pods are ready in 8.012472857s

[2023-07-29 01:57:06]  INFO Deleting all resources in namespace volume-health-metrics-74bd6cd2

[2023-07-29 01:57:20]  INFO Namespace volume-health-metrics-74bd6cd2 was deleted in 14.07634887s

[2023-07-29 01:57:21] ERROR suite VolumeHealthMetricSuite failed; error=exit status 1

[2023-07-29 01:57:21]  INFO FAILURE: VolumeHealthMetricSuite in 25.0916706s

Logs

Error.log

{"level":"error","msg":"suite VolumeHealthMetricSuite failed; error=exit status 1","time":"2023-07-28 12:51:28"}

{"level":"error","msg":"suite VolumeHealthMetricSuite failed; error=exit status 1","time":"2023-07-28 12:52:38"}

{"level":"error","msg":"no ResourceUsageMetrics provided","time":"2023-07-28 12:52:44"}

{"level":"error","msg":"suite VolumeHealthMetricSuite failed; error=exit status 1","time":"2023-07-29 01:57:21"}

Screenshots

No response

Additional Environment Information

[root@registry ~]# kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.3", GitCommit:"9e644106593f3f4aa98f8a84b23db5fa378900bd", GitTreeState:"clean", BuildDate:"2023-03-15T13:40:17Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.4", GitCommit:"95ee5ab382d64cfe6c28967f36b53970b8374491", GitTreeState:"clean", BuildDate:"2022-08-17T18:47:37Z", GoVersion:"go1.18.5", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.26) and server (1.24) exceeds the supported minor version skew of +/-1

Steps to Reproduce

1. install csi-powerstore and enable node health check
2. execute
   ”/cert-csi certify --cert-config csi-powerstore/cert/wr-certify-config.yaml  --vsc powerstore-snapshot --vgs-volume-label wrvgslabel --driver-name csi-powerstore --vgs-name wrvgs --path csi-powerstore/cert/ --sequential -l 5”

Expected Behavior

the test pass

CSM Driver(s)

CSI powerstore 2.1

Installation Type

No response

Container Storage Modules Enabled

No response

Container Orchestrator

K8s 1.24.4

Operating System

debian 11

[csmbot]

@vincent1chen: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and assign an appropriate priority label.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.

[AkshaySainiDell]

In order to run VolumeHealthMetricSuite; driver namespace must be passed in command line arguments. Correct syntax is
cert-csi functional-test volumehealthmetrics --sc <storage-class> --driver-ns <driver-namespace> --podNum <number-of-pods> --volNum <number-of-volumes>

Updated the same in CSM docs.