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.

Sign up for GitHub

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

Jump to bottom

Align CRD in Deploy Folder with Generated CRDs #874

Merged
merged 4 commits into from
Jan 28, 2025
Merged

Align CRD in Deploy Folder with Generated CRDs #874

merged 4 commits into from
Jan 28, 2025

Conversation

falfaroc
Copy link
Contributor

@falfaroc falfaroc commented Jan 24, 2025 •
edited
Loading

Description

Update the CRDs in the deploy folder with the autogenerated CRDs from the config folder.

Note: Most of the changes are formatting descriptions. Main change, the replicas default to 2 for CRs that don't a replica field. This would be most important for minimal manifest since this is not supplied.

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1721

Checklist:

  • I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
  • I have verified that new and existing unit tests pass locally with my changes
  • I have not allowed coverage numbers to degenerate
  • I have maintained at least 90% code coverage
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • I have maintained backward compatibility
  • I have executed the relevant end-to-end test scenarios

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

  • Ensure CRDs are uninstalled correctly.
$ bash scripts/uninstall.sh
******
Deleting the Operator Deployment
******
serviceaccount "dell-csm-operator-manager-service-account" deleted
role.rbac.authorization.k8s.io "dell-csm-operator-leader-election-role" deleted
clusterrole.rbac.authorization.k8s.io "dell-csm-operator-application-mobility-velero-server" deleted
clusterrole.rbac.authorization.k8s.io "dell-csm-operator-manager-role" deleted
clusterrole.rbac.authorization.k8s.io "dell-csm-operator-metrics-reader" deleted
clusterrole.rbac.authorization.k8s.io "dell-csm-operator-proxy-role" deleted
rolebinding.rbac.authorization.k8s.io "dell-csm-operator-leader-election-rolebinding" deleted
clusterrolebinding.rbac.authorization.k8s.io "dell-csm-operator-application-mobility-velero-server-rolebinding" deleted
clusterrolebinding.rbac.authorization.k8s.io "dell-csm-operator-manager-rolebinding" deleted
clusterrolebinding.rbac.authorization.k8s.io "dell-csm-operator-proxy-rolebinding" deleted
configmap "dell-csm-operator-manager-config" deleted
service "dell-csm-operator-controller-manager-metrics-service" deleted
deployment.apps "dell-csm-operator-controller-manager" deleted

******
Deleting the Operator CRDs
******
customresourcedefinition.apiextensions.k8s.io "containerstoragemodules.storage.dell.com" deleted
  • Verify Minimal Manifest Replica count
    With Fix
Spec:
  Driver:
    Config Version:       v2.13.0
    Csi Driver Type:      powermax
    Force Remove Driver:  true
    Replicas:             2

Without Fix and E2E Error

Spec:
  Driver:
    Config Version:       v2.13.0
    Csi Driver Type:      powermax
    Force Remove Driver:  true
    Replicas:             0 
...
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 16:11:46.534
  STEP:      Executing  Validate [powermax] driver spec from CR [1] @ 01/27/25 16:12:06.617

err: replicas should have a non-zero value

err: replicas should have a non-zero value
  • Run E2E Tests to Verfiy Changes (PowerMax)
-> # bash run-e2e-test.sh --pmax --minimal
/root/git/public/dell/csm-operator/tests/e2e
  W0127 15:27:31.397708   15521 test_context.go:541] Unable to find in-cluster config, using default host : https://127.0.0.1:6443
  I0127 15:27:31.398947 15521 test_context.go:564] The --provider flag is not set. Continuing as if --provider=skeleton had been used.
Running Suite: CSM Operator End-to-End Tests - /root/git/public/dell/csm-operator/tests/e2e
===========================================================================================
Random Seed: 1737991637

Will run 1 of 1 specs
------------------------------
[BeforeSuite]
/root/git/public/dell/csm-operator/tests/e2e/e2e_test.go:98
  STEP: Getting test environment variables @ 01/27/25 15:27:31.399
  STEP: [powermax] @ 01/27/25 15:27:31.399
  STEP: Reading values file @ 01/27/25 15:27:31.399
  STEP: Getting a k8s client @ 01/27/25 15:27:31.551
[BeforeSuite] PASSED [0.162 seconds]
------------------------------
[run-e2e-test] E2E Testing Running all test Given Test Scenarios
/root/git/public/dell/csm-operator/tests/e2e/e2e_test.go:139
  STEP: Starting: Install PowerStore Driver (Minimal, Standalone)  @ 01/27/25 15:27:31.561
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.561
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.561
  STEP: Ending: Install PowerStore Driver (Minimal, Standalone)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerStore Driver (Minimal, With Resiliency)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerStore Driver (Minimal, With Resiliency)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerStore Driver (Minimal, Standalone), Enable Resiliency  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerStore Driver (Minimal, Standalone), Enable Resiliency
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerStore Driver (Minimal, With no forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerStore Driver (Minimal, With no forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerStore Driver (Minimal, With false forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerStore Driver (Minimal, With false forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install Unity Driver (Minimal, Standalone)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install Unity Driver (Minimal, Standalone)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install Unity Driver (Minimal, With false forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install Unity Driver (Minimal, With false forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install Unity Driver (Minimal, With no forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install Unity Driver (Minimal, With no forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, Standalone)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, Standalone)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With no forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With no forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With false forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With false forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With Resiliency)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With Resiliency)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, Standalone), Enable/Disable Resiliency  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, Standalone), Enable/Disable Resiliency
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With Authorization V2)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With Authorization V2)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With Authorization V1)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With Authorization V1)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With Observability)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With Observability)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerFlex Driver (Minimal, With Observability and Custom Cert for Otel-Collector)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerFlex Driver (Minimal, With Observability and Custom Cert for Otel-Collector)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, Standalone)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, Standalone)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, With no forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, With no forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, With false forceRemoveDriver)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, With false forceRemoveDriver)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, Standalone), Enable/Disable Resiliency  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, Standalone), Enable/Disable Resiliency
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, With Resiliency)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, With Resiliency)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, With Replication)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, With Replication)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, Standalone), Enable/Disable Replication  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Install PowerScale Driver (Minimal, Standalone), Enable/Disable Replication
   @ 01/27/25 15:27:31.562
  STEP: Starting: Uninstall PowerScale Driver (Minimal)  @ 01/27/25 15:27:31.562
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.562
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.562
  STEP: Ending: Uninstall PowerScale Driver (Minimal)
   @ 01/27/25 15:27:31.562
  STEP: Starting: Install PowerScale Driver (Minimal, Standalone), Enable/Disable Observability  @ 01/27/25 15:27:31.563
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.563
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.563
  STEP: Ending: Install PowerScale Driver (Minimal, Standalone), Enable/Disable Observability
   @ 01/27/25 15:27:31.563
  STEP: Starting: Install PowerScale Driver (Minimal, With Observability and Custom Certs)  @ 01/27/25 15:27:31.563
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.563
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.563
  STEP: Ending: Install PowerScale Driver (Minimal, With Observability and Custom Certs)
   @ 01/27/25 15:27:31.563
  STEP: Starting: Install PowerScale Driver (Minimal, With Authorization V1)  @ 01/27/25 15:27:31.563
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.563
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.563
  STEP: Ending: Install PowerScale Driver (Minimal, With Authorization V1)
   @ 01/27/25 15:27:31.563
  STEP: Starting: Install PowerScale Driver (Minimal), Enable/Disable Authorization V1 module  @ 01/27/25 15:27:31.563
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.563
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.563
  STEP: Ending: Install PowerScale Driver (Minimal), Enable/Disable Authorization V1 module
   @ 01/27/25 15:27:31.563
  STEP: Starting: Install PowerScale Driver (Minimal, With Authorization V2)  @ 01/27/25 15:27:31.563
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.563
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.563
  STEP: Ending: Install PowerScale Driver (Minimal, With Authorization V2)
   @ 01/27/25 15:27:31.563
  STEP: Starting: Install Powerflex Driver (Minimal, With Replication)  @ 01/27/25 15:27:31.563
  STEP: No matching tags for scenario @ 01/27/25 15:27:31.563
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:27:31.563
  STEP: Ending: Install Powerflex Driver (Minimal, With Replication)
   @ 01/27/25 15:27:31.563
  STEP: Starting: Install PowerMax Driver (Minimal, Standalone)  @ 01/27/25 15:27:31.563
  STEP: Returning false here @ 01/27/25 15:27:31.563
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:27:31.563
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:27:31.66
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:27:32.825
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:27:33.542
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:27:34.359
  I0127 15:27:34.359485 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:27:35.085584 15521 builder.go:146] stderr: ""
  I0127 15:27:35.085651 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:27:35.085

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:28:25.193
  STEP:      Executing  Validate [powermax] driver spec from CR [1] @ 01/27/25 15:28:45.281
  STEP:      Executing  Run custom test @ 01/27/25 15:28:45.306
  I0127 15:28:45.306200 15521 util.go:650] Running cert-csi [test vio --sc op-e2e-pmax --chainLength 1 --chainNumber 1]
[2025-01-27 15:28:45]  INFO Starting cert-csi; ver. 1.4.1
[2025-01-27 15:28:45]  INFO Using EVENT observer type
[2025-01-27 15:28:45]  INFO Using config from /root/.kube/config
[2025-01-27 15:28:45]  INFO Successfully loaded config. Host: https://10.227.248.175:6443
[2025-01-27 15:28:45]  INFO Created new KubeClient
[2025-01-27 15:28:45]  INFO Running 1 iteration(s)
[2025-01-27 15:28:45]  INFO     *** ITERATION NUMBER 1 ***
[2025-01-27 15:28:45]  INFO Starting VolumeIoSuite with op-e2e-pmax storage class
[2025-01-27 15:28:45]  INFO Successfully created namespace volumeio-test-e728d916
[2025-01-27 15:28:45]  INFO Using default number of volumes
[2025-01-27 15:28:45]  INFO Using default image: docker.io/centos:latest
[2025-01-27 15:28:45]  INFO Creating IO pod
[2025-01-27 15:28:45]  INFO Waiting for pod iowriter-test-np8z8 to be READY
[2025-01-27 15:29:29]  INFO Executing command: [/bin/bash -c dd if=/dev/urandom bs=1M count=128 oflag=sync > /data0/writer-0.data]
[2025-01-27 15:29:30]  INFO Executing command: [/bin/bash -c sha512sum /data0/writer-0.data > /data0/writer-0.sha512]
[2025-01-27 15:29:33]  INFO Waiting until no Volume Attachments with PV  left
[2025-01-27 15:29:33]  INFO VolumeAttachment deleted
[2025-01-27 15:29:33]  INFO Deleting all resources in namespace volumeio-test-e728d916
[2025-01-27 15:29:45]  INFO Namespace volumeio-test-e728d916 was deleted in 12.094175353s
[2025-01-27 15:29:50]  INFO SUCCESS: VolumeIoSuite in 1m5.201272681s
[2025-01-27 15:29:50]  INFO Started generating reports...
Collecting metrics
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/sCollecting metrics
[2025-01-27 15:29:50]  INFO Started generating reports...
Generating plots
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s1 / 1 [--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->] 100.00% ? p/s1 / 1 [---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% 81 p/s[2025-01-27 15:29:51]  WARN No ResourceUsageMetrics provided
[2025-01-27 15:29:51] ERROR no ResourceUsageMetrics provided
report-test-run-c5586934:
Name: test-run-c5586934
Host: https://10.227.248.175:6443
StorageClass: op-e2e-pmax
Minimum and Maximum EntityOverTime charts:

/root/.cert-csi/reports/test-run-c5586934/PodsCreatingOverTime.png

/root/.cert-csi/reports/test-run-c5586934/PodsReadyOverTime.png

/root/.cert-csi/reports/test-run-c5586934/PodsTerminatingOverTime.png

/root/.cert-csi/reports/test-run-c5586934/PvcsCreatingOverTime.png

/root/.cert-csi/reports/test-run-c5586934/PvcsBoundOverTime.png

Tests:
--------------------------------------------------------------
1. TestCase: VolumeIoSuite
            Started:   2025-01-27 15:28:45.54048573 +0000 UTC
            Ended:     2025-01-27 15:29:50.744453161 +0000 UTC
            Result:    SUCCESS

            Stage metrics:
                    PVCAttachment:
                        Avg: 6.947816295s
                        Min: 6.947816295s
                        Max: 6.947816295s
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCAttachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCAttachment_boxplot.png
                    PVCBind:
                        Avg: 2.605698589s
                        Min: 2.605698589s
                        Max: 2.605698589s
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCBind.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCBind_boxplot.png
                    PVCCreation:
                        Avg: 9.969632911s
                        Min: 9.969632911s
                        Max: 9.969632911s
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCCreation_boxplot.png
                    PVCDeletion:
                        Avg: 8.22227ms
                        Min: 8.22227ms
                        Max: 8.22227ms
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCDeletion_boxplot.png
                    PVCUnattachment:
                        Avg: 1.847062028s
                        Min: 1.847062028s
                        Max: 1.847062028s
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCUnattachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PVCUnattachment_boxplot.png
                    PodCreation:
                        Avg: 42.765276345s
                        Min: 42.765276345s
                        Max: 42.765276345s
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PodCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PodCreation_boxplot.png
                    PodDeletion:
                        Avg: 790.481901ms
                        Min: 790.481901ms
                        Max: 790.481901ms
                        Histogram:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PodDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/PodDeletion_boxplot.png
                        EntityNumberOverTime:
        /root/.cert-csi/reports/test-run-c5586934/VolumeIoSuite21/EntityNumberOverTime.png

[2025-01-27 15:29:51]  INFO Avg time of a run:   48.26s
[2025-01-27 15:29:51]  INFO Avg time of a del:   12.09s
[2025-01-27 15:29:51]  INFO Avg time of all:     65.20s
[2025-01-27 15:29:51]  INFO During this run 100.0% of suites succeeded
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:29:51.259
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:29:51.31
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:29:51.361
2025/01/27 15:29:51 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-556c8cbd76-8s6z5,powermax-controller-556c8cbd76-jsgwd,
2025/01/27 15:30:21 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:30:41.469
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:30:41.522
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:30:41.572
  STEP: Ending: Install PowerMax Driver (Minimal, Standalone)
   @ 01/27/25 15:30:41.595
  STEP: Starting: Install PowerMax Driver (Minimal, With no forceRemoveDriver)  @ 01/27/25 15:30:46.599
  STEP: Returning false here @ 01/27/25 15:30:46.599
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:30:46.599
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:30:46.627
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:30:47.34
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:30:47.777
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:30:48.296
  I0127 15:30:48.296809 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:30:48.677590 15521 builder.go:146] stderr: ""
  I0127 15:30:48.677655 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:30:48.677

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [1] CSM has forceRemoveDriver set to true @ 01/27/25 15:31:38.749
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:31:38.773
  STEP:      Executing  Run custom test @ 01/27/25 15:31:58.843
  I0127 15:31:58.843422 15521 util.go:650] Running cert-csi [test vio --sc op-e2e-pmax --chainLength 1 --chainNumber 1]
[2025-01-27 15:31:58]  INFO Starting cert-csi; ver. 1.4.1
[2025-01-27 15:31:58]  INFO Using EVENT observer type
[2025-01-27 15:31:58]  INFO Using config from /root/.kube/config
[2025-01-27 15:31:58]  INFO Successfully loaded config. Host: https://10.227.248.175:6443
[2025-01-27 15:31:59]  INFO Created new KubeClient
[2025-01-27 15:31:59]  INFO Running 1 iteration(s)
[2025-01-27 15:31:59]  INFO     *** ITERATION NUMBER 1 ***
[2025-01-27 15:31:59]  INFO Starting VolumeIoSuite with op-e2e-pmax storage class
[2025-01-27 15:31:59]  INFO Successfully created namespace volumeio-test-447b545e
[2025-01-27 15:31:59]  INFO Using default number of volumes
[2025-01-27 15:31:59]  INFO Using default image: docker.io/centos:latest
[2025-01-27 15:31:59]  INFO Creating IO pod
[2025-01-27 15:31:59]  INFO Waiting for pod iowriter-test-6xw47 to be READY
[2025-01-27 15:32:43]  INFO Executing command: [/bin/bash -c dd if=/dev/urandom bs=1M count=128 oflag=sync > /data0/writer-0.data]
[2025-01-27 15:32:44]  INFO Executing command: [/bin/bash -c sha512sum /data0/writer-0.data > /data0/writer-0.sha512]
[2025-01-27 15:32:47]  INFO Waiting until no Volume Attachments with PV  left
[2025-01-27 15:32:47]  INFO VolumeAttachment deleted
[2025-01-27 15:32:47]  INFO Deleting all resources in namespace volumeio-test-447b545e
[2025-01-27 15:32:59]  INFO Namespace volumeio-test-447b545e was deleted in 12.096011273s
[2025-01-27 15:33:04]  INFO SUCCESS: VolumeIoSuite in 1m5.200384597s
[2025-01-27 15:33:04]  INFO Started generating reports...
Collecting metrics
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s[2025-01-27 15:33:04]  INFO Started generating reports...
Collecting metrics
Generating plots
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s1 / 1 [--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->] 100.00% ? p/s1 / 1 [--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% 113 p/s[2025-01-27 15:33:04]  WARN No ResourceUsageMetrics provided
[2025-01-27 15:33:04] ERROR no ResourceUsageMetrics provided
report-test-run-d1397923:
Name: test-run-d1397923
Host: https://10.227.248.175:6443
StorageClass: op-e2e-pmax
Minimum and Maximum EntityOverTime charts:

/root/.cert-csi/reports/test-run-d1397923/PodsCreatingOverTime.png

/root/.cert-csi/reports/test-run-d1397923/PodsReadyOverTime.png

/root/.cert-csi/reports/test-run-d1397923/PodsTerminatingOverTime.png

/root/.cert-csi/reports/test-run-d1397923/PvcsCreatingOverTime.png

/root/.cert-csi/reports/test-run-d1397923/PvcsBoundOverTime.png

Tests:
--------------------------------------------------------------
1. TestCase: VolumeIoSuite
            Started:   2025-01-27 15:31:59.068763329 +0000 UTC
            Ended:     2025-01-27 15:33:04.273235656 +0000 UTC
            Result:    SUCCESS

            Stage metrics:
                    PVCAttachment:
                        Avg: 6.309848173s
                        Min: 6.309848173s
                        Max: 6.309848173s
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCAttachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCAttachment_boxplot.png
                    PVCBind:
                        Avg: 2.862163994s
                        Min: 2.862163994s
                        Max: 2.862163994s
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCBind.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCBind_boxplot.png
                    PVCCreation:
                        Avg: 9.412792402s
                        Min: 9.412792402s
                        Max: 9.412792402s
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCCreation_boxplot.png
                    PVCDeletion:
                        Avg: 9.432464ms
                        Min: 9.432464ms
                        Max: 9.432464ms
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCDeletion_boxplot.png
                    PVCUnattachment:
                        Avg: 1.884830098s
                        Min: 1.884830098s
                        Max: 1.884830098s
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCUnattachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PVCUnattachment_boxplot.png
                    PodCreation:
                        Avg: 43.968623784s
                        Min: 43.968623784s
                        Max: 43.968623784s
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PodCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PodCreation_boxplot.png
                    PodDeletion:
                        Avg: 1.650501288s
                        Min: 1.650501288s
                        Max: 1.650501288s
                        Histogram:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PodDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/PodDeletion_boxplot.png
                        EntityNumberOverTime:
        /root/.cert-csi/reports/test-run-d1397923/VolumeIoSuite22/EntityNumberOverTime.png

[2025-01-27 15:33:04]  INFO Avg time of a run:   48.64s
[2025-01-27 15:33:04]  INFO Avg time of a del:   12.10s
[2025-01-27 15:33:04]  INFO Avg time of all:     65.20s
[2025-01-27 15:33:04]  INFO During this run 100.0% of suites succeeded
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:33:04.773
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:33:04.824
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:33:04.873
2025/01/27 15:33:04 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-556c8cbd76-8kmjd,powermax-controller-556c8cbd76-mxk7f,
2025/01/27 15:33:34 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:33:54.966
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:33:55.01
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:33:55.059
  STEP: Ending: Install PowerMax Driver (Minimal, With no forceRemoveDriver)
   @ 01/27/25 15:33:55.093
  STEP: Starting: Install PowerMax Driver (Minimal, With false forceRemoveDriver)  @ 01/27/25 15:34:00.097
  STEP: Returning false here @ 01/27/25 15:34:00.098
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:34:00.098
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:34:00.122
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:34:00.768
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:34:01.158
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:34:01.642
  I0127 15:34:01.643044 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:34:01.975675 15521 builder.go:146] stderr: ""
  I0127 15:34:01.975725 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:34:01.975

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [1] CSM has forceRemoveDriver set to false @ 01/27/25 15:34:52.056
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:34:52.08
  STEP:      Executing  Run custom test @ 01/27/25 15:35:12.163
  I0127 15:35:12.164054 15521 util.go:650] Running cert-csi [test vio --sc op-e2e-pmax --chainLength 1 --chainNumber 1]
[2025-01-27 15:35:12]  INFO Starting cert-csi; ver. 1.4.1
[2025-01-27 15:35:12]  INFO Using EVENT observer type
[2025-01-27 15:35:12]  INFO Using config from /root/.kube/config
[2025-01-27 15:35:12]  INFO Successfully loaded config. Host: https://10.227.248.175:6443
[2025-01-27 15:35:12]  INFO Created new KubeClient
[2025-01-27 15:35:12]  INFO Running 1 iteration(s)
[2025-01-27 15:35:12]  INFO     *** ITERATION NUMBER 1 ***
[2025-01-27 15:35:12]  INFO Starting VolumeIoSuite with op-e2e-pmax storage class
[2025-01-27 15:35:12]  INFO Successfully created namespace volumeio-test-f37ef435
[2025-01-27 15:35:12]  INFO Using default number of volumes
[2025-01-27 15:35:12]  INFO Using default image: docker.io/centos:latest
[2025-01-27 15:35:12]  INFO Creating IO pod
[2025-01-27 15:35:12]  INFO Waiting for pod iowriter-test-vwztd to be READY
[2025-01-27 15:35:54]  INFO Executing command: [/bin/bash -c dd if=/dev/urandom bs=1M count=128 oflag=sync > /data0/writer-0.data]
[2025-01-27 15:35:55]  INFO Executing command: [/bin/bash -c sha512sum /data0/writer-0.data > /data0/writer-0.sha512]
[2025-01-27 15:35:59]  INFO Waiting until no Volume Attachments with PV  left
[2025-01-27 15:35:59]  INFO VolumeAttachment deleted
[2025-01-27 15:35:59]  INFO Deleting all resources in namespace volumeio-test-f37ef435
[2025-01-27 15:36:11]  INFO Namespace volumeio-test-f37ef435 was deleted in 12.097608038s
[2025-01-27 15:36:12]  INFO SUCCESS: VolumeIoSuite in 1m0.184262404s
[2025-01-27 15:36:12]  INFO Started generating reports...
Collecting metrics
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s[2025-01-27 15:36:12]  INFO Started generating reports...
Collecting metrics
Generating plots
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s[2025-01-27 15:36:12]  WARN No ResourceUsageMetrics provided
[2025-01-27 15:36:12] ERROR no ResourceUsageMetrics provided
report-test-run-c6fa5cf3:
Name: test-run-c6fa5cf3
Host: https://10.227.248.175:6443
StorageClass: op-e2e-pmax
Minimum and Maximum EntityOverTime charts:

/root/.cert-csi/reports/test-run-c6fa5cf3/PodsCreatingOverTime.png

/root/.cert-csi/reports/test-run-c6fa5cf3/PodsReadyOverTime.png

/root/.cert-csi/reports/test-run-c6fa5cf3/PodsTerminatingOverTime.png

/root/.cert-csi/reports/test-run-c6fa5cf3/PvcsCreatingOverTime.png

/root/.cert-csi/reports/test-run-c6fa5cf3/PvcsBoundOverTime.png

Tests:
--------------------------------------------------------------
1. TestCase: VolumeIoSuite
            Started:   2025-01-27 15:35:12.372005832 +0000 UTC
            Ended:     2025-01-27 15:36:12.5987969 +0000 UTC
            Result:    SUCCESS

            Stage metrics:
                    PVCAttachment:
                        Avg: 6.351454478s
                        Min: 6.351454478s
                        Max: 6.351454478s
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCAttachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCAttachment_boxplot.png
                    PVCBind:
                        Avg: 2.82991619s
                        Min: 2.82991619s
                        Max: 2.82991619s
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCBind.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCBind_boxplot.png
                    PVCCreation:
                        Avg: 9.393527683s
                        Min: 9.393527683s
                        Max: 9.393527683s
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCCreation_boxplot.png
                    PVCDeletion:
                        Avg: 7.158192ms
                        Min: 7.158192ms
                        Max: 7.158192ms
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCDeletion_boxplot.png
                    PVCUnattachment:
                        Avg: 1.989726511s
                        Min: 1.989726511s
                        Max: 1.989726511s
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCUnattachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PVCUnattachment_boxplot.png
                    PodCreation:
                        Avg: 41.411598674s
                        Min: 41.411598674s
                        Max: 41.411598674s
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PodCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PodCreation_boxplot.png
                    PodDeletion:
                        Avg: 2.04485041s
                        Min: 2.04485041s
                        Max: 2.04485041s
                        Histogram:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PodDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/PodDeletion_boxplot.png
                        EntityNumberOverTime:
        /root/.cert-csi/reports/test-run-c6fa5cf3/VolumeIoSuite23/EntityNumberOverTime.png

[2025-01-27 15:36:13]  INFO Avg time of a run:   46.66s
[2025-01-27 15:36:13]  INFO Avg time of a del:   12.10s
[2025-01-27 15:36:13]  INFO Avg time of all:     60.18s
[2025-01-27 15:36:13]  INFO During this run 100.0% of suites succeeded
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:36:13.068
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:36:13.119
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:36:33.195
  I0127 15:36:33.195700 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:36:33.530842 15521 builder.go:146] stderr: ""
  I0127 15:36:33.530902 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:36:33.53

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:37:23.59
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:37:23.642
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:37:23.692
2025/01/27 15:37:23 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-556c8cbd76-hfkkf,powermax-controller-556c8cbd76-wcwcl,
2025/01/27 15:37:53 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:38:13.782
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:38:13.842
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:38:13.909
  STEP: Ending: Install PowerMax Driver (Minimal, With false forceRemoveDriver)
   @ 01/27/25 15:38:13.936
  STEP: Starting: Install PowerMax Driver (Minimal, With Observability)  @ 01/27/25 15:38:18.94
  STEP: Returning false here @ 01/27/25 15:38:18.94
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:38:18.94
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:38:18.964
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:38:19.613
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:38:19.978
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:38:20.451
  I0127 15:38:20.452023 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:38:20.795301 15521 builder.go:146] stderr: ""
  I0127 15:38:20.795365 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:38:20.795

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:39:10.872
  STEP:      Executing  Validate [observability] module from CR [1] is installed @ 01/27/25 15:39:30.939
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:39:41.121
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:39:41.172
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:39:41.224
2025/01/27 15:39:41 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-556c8cbd76-nc8wq,powermax-controller-556c8cbd76-prwl7,
2025/01/27 15:40:11 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:40:31.332
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:40:31.377
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:40:31.422
  STEP: Ending: Install PowerMax Driver (Minimal, With Observability)
   @ 01/27/25 15:40:31.448
  STEP: Starting: Install PowerMax Driver (Minimal, With Auth V1 module)  @ 01/27/25 15:40:36.452
  STEP: Returning false here @ 01/27/25 15:40:36.452
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:40:36.452
  STEP:      Executing  Create [authorization-proxy-server] prerequisites from CR [1] @ 01/27/25 15:40:36.476
=== Creating Authorization Proxy Server Prerequisites ===

Deleting all CSM from namespace: authorization
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:40:44.396
  I0127 15:40:44.396614 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=authorization apply --validate=true -f -'
  I0127 15:40:44.871476 15521 builder.go:146] stderr: ""
  I0127 15:40:44.871536 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/authorization created\nconfigmap/csm-config-params created\n"
  STEP:      Executing  Validate [authorization-proxy-server] module from CR [1] is installed @ 01/27/25 15:40:44.871
  STEP:      Executing  Configure authorization-proxy-server for [powermax] for CR [1] @ 01/27/25 15:41:15.008
=== Configuring Authorization Proxy Server ===
Address: csm-authorization.com
=====Waiting for everything to be up and running, adding a sleep time of 120 seconds before creating the role, tenant and role binding===
=== Generating Admin Token ===
=== Writing Admin Token to Tmp File ===


=== Checking Storage ===

=== Checking Storage ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml storage list --insecure --addr csm-authorization.com:31163

=== Creating Storage ===

=== Storage ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml storage create --type powermax --endpoint https://10.230.24.220:8443 --system-id 000120001607 --user smc --password smc --array-insecure --insecure --addr csm-authorization.com:31163


=== Creating Tenant ===

=== Tenant ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml tenant create -n PancakeGroup --insecure --addr csm-authorization.com:31163
=== Checking Roles ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml role list --insecure --addr csm-authorization.com:31163


=== Creating Role ===

=== Role ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml role create --role=CSIGold=powermax=000120001607=SRP_1=100000000 --insecure --addr csm-authorization.com:31163


=== Creating RoleBinding ===

=== Binding Role ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml rolebinding create --tenant PancakeGroup --role CSIGold --insecure --addr csm-authorization.com:31163


=== Generating token ===

=== Token ===
 /usr/local/bin/karavictl --admin-token /tmp/adminToken.yaml generate token --tenant PancakeGroup --insecure --addr csm-authorization.com:31163 --access-token-expiration 2h0m0s


=== Applying token ===

=== Token Applied ===

  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:43:21.553
  STEP:      Executing  Set up secret with template [testfiles/powermax-templates/csm-authorization-config.json] name [karavi-authorization-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:43:22.202
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:43:22.688
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config_auth.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxReverseProxy] @ 01/27/25 15:43:23.068
  STEP:      Executing  Apply custom resource [2] @ 01/27/25 15:43:23.54
  I0127 15:43:23.540945 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:43:23.907802 15521 builder.go:146] stderr: ""
  I0127 15:43:23.907852 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [2] @ 01/27/25 15:43:23.907

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [powermax] driver from CR [2] is installed @ 01/27/25 15:44:14.034
  STEP:      Executing  Validate [authorization] module from CR [2] is installed @ 01/27/25 15:44:34.117
map[com.dell.karavi-authorization-proxy:true deployment.kubernetes.io/revision:1]
map[com.dell.karavi-authorization-proxy:true deprecated.daemonset.template.generation:1]
  STEP:      Executing  Run custom test @ 01/27/25 15:44:44.205
  I0127 15:44:44.205632 15521 util.go:650] Running cert-csi [test vio --sc op-e2e-pmax  --chainLength 1 --chainNumber 1]
[2025-01-27 15:44:44]  INFO Starting cert-csi; ver. 1.4.1
[2025-01-27 15:44:44]  INFO Using EVENT observer type
[2025-01-27 15:44:44]  INFO Using config from /root/.kube/config
[2025-01-27 15:44:44]  INFO Successfully loaded config. Host: https://10.227.248.175:6443
[2025-01-27 15:44:44]  INFO Created new KubeClient
[2025-01-27 15:44:44]  INFO Running 1 iteration(s)
[2025-01-27 15:44:44]  INFO     *** ITERATION NUMBER 1 ***
[2025-01-27 15:44:44]  INFO Starting VolumeIoSuite with op-e2e-pmax storage class
[2025-01-27 15:44:44]  INFO Successfully created namespace volumeio-test-fbe48445
[2025-01-27 15:44:44]  INFO Using default number of volumes
[2025-01-27 15:44:44]  INFO Using default image: docker.io/centos:latest
[2025-01-27 15:44:44]  INFO Creating IO pod
[2025-01-27 15:44:44]  INFO Waiting for pod iowriter-test-zjq28 to be READY
[2025-01-27 15:45:30]  INFO Executing command: [/bin/bash -c dd if=/dev/urandom bs=1M count=128 oflag=sync > /data0/writer-0.data]
[2025-01-27 15:45:31]  INFO Executing command: [/bin/bash -c sha512sum /data0/writer-0.data > /data0/writer-0.sha512]
[2025-01-27 15:45:34]  INFO Waiting until no Volume Attachments with PV  left
[2025-01-27 15:45:34]  INFO VolumeAttachment deleted
[2025-01-27 15:45:34]  INFO Deleting all resources in namespace volumeio-test-fbe48445
[2025-01-27 15:45:46]  INFO Namespace volumeio-test-fbe48445 was deleted in 12.093297115s
[2025-01-27 15:45:49]  INFO SUCCESS: VolumeIoSuite in 1m5.191898s
[2025-01-27 15:45:49]  INFO Started generating reports...
Collecting metrics
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s[2025-01-27 15:45:49]  INFO Started generating reports...
Collecting metrics
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/sGenerating plots
1 / 1 [----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s[2025-01-27 15:45:49]  WARN No ResourceUsageMetrics provided
[2025-01-27 15:45:49] ERROR no ResourceUsageMetrics provided
report-test-run-f45cc2fa:
Name: test-run-f45cc2fa
Host: https://10.227.248.175:6443
StorageClass: op-e2e-pmax
Minimum and Maximum EntityOverTime charts:

/root/.cert-csi/reports/test-run-f45cc2fa/PodsCreatingOverTime.png

/root/.cert-csi/reports/test-run-f45cc2fa/PodsReadyOverTime.png

/root/.cert-csi/reports/test-run-f45cc2fa/PodsTerminatingOverTime.png

/root/.cert-csi/reports/test-run-f45cc2fa/PvcsCreatingOverTime.png

/root/.cert-csi/reports/test-run-f45cc2fa/PvcsBoundOverTime.png

Tests:
--------------------------------------------------------------
1. TestCase: VolumeIoSuite
            Started:   2025-01-27 15:44:44.410455072 +0000 UTC
            Ended:     2025-01-27 15:45:49.645271356 +0000 UTC
            Result:    SUCCESS

            Stage metrics:
                    PVCAttachment:
                        Avg: 7.005098128s
                        Min: 7.005098128s
                        Max: 7.005098128s
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCAttachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCAttachment_boxplot.png
                    PVCBind:
                        Avg: 3.288301241s
                        Min: 3.288301241s
                        Max: 3.288301241s
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCBind.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCBind_boxplot.png
                    PVCCreation:
                        Avg: 11.069174548s
                        Min: 11.069174548s
                        Max: 11.069174548s
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCCreation_boxplot.png
                    PVCDeletion:
                        Avg: 12.77246ms
                        Min: 12.77246ms
                        Max: 12.77246ms
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCDeletion_boxplot.png
                    PVCUnattachment:
                        Avg: 1.890373154s
                        Min: 1.890373154s
                        Max: 1.890373154s
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCUnattachment.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PVCUnattachment_boxplot.png
                    PodCreation:
                        Avg: 44.483850926s
                        Min: 44.483850926s
                        Max: 44.483850926s
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PodCreation.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PodCreation_boxplot.png
                    PodDeletion:
                        Avg: 821.425534ms
                        Min: 821.425534ms
                        Max: 821.425534ms
                        Histogram:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PodDeletion.png
                        BoxPlot:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/PodDeletion_boxplot.png
                        EntityNumberOverTime:
        /root/.cert-csi/reports/test-run-f45cc2fa/VolumeIoSuite24/EntityNumberOverTime.png

[2025-01-27 15:45:50]  INFO Avg time of a run:   49.96s
[2025-01-27 15:45:50]  INFO Avg time of a del:   12.09s
[2025-01-27 15:45:50]  INFO Avg time of all:     65.19s
[2025-01-27 15:45:50]  INFO During this run 100.0% of suites succeeded
  STEP:      Executing  Enable forceRemoveDriver on CR [2] @ 01/27/25 15:45:50.109
  STEP:      Executing  Delete custom resource [2] @ 01/27/25 15:45:50.158
  STEP:      Executing  Validate [powermax] driver from CR [2] is not installed @ 01/27/25 15:45:50.207
2025/01/27 15:45:50 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-6bc5b4d5d8-ts7cr,powermax-controller-6bc5b4d5d8-wldj2,
2025/01/27 15:46:20 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:46:40.31
  STEP:      Executing  Validate [authorization] module pods from CR [1] is not installed @ 01/27/25 15:46:40.361
  STEP:      Executing  Restore template [testfiles/powermax-templates/csm-authorization-config.json] for [pmaxAuthSidecar] @ 01/27/25 15:47:00.385
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:47:00.425
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config_auth.yaml] for [pmaxReverseProxy] @ 01/27/25 15:47:00.447
  STEP: Ending: Install PowerMax Driver (Minimal, With Auth V1 module)
   @ 01/27/25 15:47:00.481
  STEP: Starting: Install Powermax Driver (Minimal, With Authorization v2)  @ 01/27/25 15:47:05.484
  STEP: No matching tags for scenario @ 01/27/25 15:47:05.484
  STEP: Not tagged for this test run, skipping @ 01/27/25 15:47:05.484
  STEP: Ending: Install Powermax Driver (Minimal, With Authorization v2)
   @ 01/27/25 15:47:05.484
  STEP: Starting: Install Powermax Driver (Minimal, Standalone), Enable Resiliency  @ 01/27/25 15:47:05.484
  STEP: Returning false here @ 01/27/25 15:47:05.484
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:47:05.484
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:47:05.507
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:47:06.159
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:47:06.514
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:47:06.991
  I0127 15:47:06.992313 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:47:07.334305 15521 builder.go:146] stderr: ""
  I0127 15:47:07.334354 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:47:07.334

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:47:57.403
  STEP:      Executing  Validate [resiliency] module from CR [1] is not installed @ 01/27/25 15:48:17.486
  STEP:      Executing  Enable [resiliency] module from CR [1] @ 01/27/25 15:48:27.556
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:48:42.621

err:
The pod(powermax-controller-5dc8c6b4c5-f8jpq) is Pending
The pod(powermax-controller-5dc8c6b4c5-xstjz) is Pending
The pod(powermax-node-96w25) is Pending

err:
The pod(powermax-controller-5dc8c6b4c5-f8jpq) is Pending
The container(attacher) in pod(powermax-controller-5dc8c6b4c5-xstjz) is {&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 10s restarting failed container=attacher pod=powermax-controller-5dc8c6b4c5-xstjz_powermax(3a9d2d03-fbac-4195-8ce6-e966ee48c5ac),} nil nil}
  STEP:      Executing  Validate [resiliency] module from CR [1] is installed @ 01/27/25 15:50:02.827
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:50:12.943
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:50:12.994
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:50:13.045
2025/01/27 15:50:13 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-5dc8c6b4c5-f8jpq,powermax-controller-5dc8c6b4c5-xstjz,
2025/01/27 15:50:43 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:51:03.115
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:51:03.157
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:51:03.198
  STEP: Ending: Install Powermax Driver (Minimal, Standalone), Enable Resiliency
   @ 01/27/25 15:51:03.222
  STEP: Starting: Install Powermax Driver (Minimal, With Resiliency), Disable Resiliency module  @ 01/27/25 15:51:08.225
  STEP: Returning false here @ 01/27/25 15:51:08.225
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:51:08.225
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:51:08.248
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:51:08.91
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:51:09.276
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:51:09.757
  I0127 15:51:09.757857 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:51:10.102263 15521 builder.go:146] stderr: ""
  I0127 15:51:10.102314 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:51:10.102

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:52:00.184
  STEP:      Executing  Validate [resiliency] module from CR [1] is installed @ 01/27/25 15:52:20.249
  STEP:      Executing  Disable [resiliency] module from CR [1] @ 01/27/25 15:52:30.356
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:52:30.406

err:
The pod(powermax-controller-556c8cbd76-dfdr8) is Pending
The pod(powermax-controller-556c8cbd76-fhpg6) is Pending

err:
The pod(powermax-controller-556c8cbd76-dfdr8) is Pending
The container(attacher) in pod(powermax-controller-556c8cbd76-fhpg6) is {&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 10s restarting failed container=attacher pod=powermax-controller-556c8cbd76-fhpg6_powermax(dc29e605-0d49-4817-af1d-f28221a3e220),} nil nil}

err:
The container(attacher) in pod(powermax-controller-556c8cbd76-dfdr8) is {nil nil &ContainerStateTerminated{ExitCode:1,Signal:0,Reason:Error,Message:Lost connection to CSI driver, exiting,StartedAt:2025-01-27 15:53:43 +0000 UTC,FinishedAt:2025-01-27 15:53:45 +0000 UTC,ContainerID:containerd://8201122020a189e9867fbb1e4cb5b569a4d0544296bf3c7744f5e634f9de50e7,}}
  STEP:      Executing  Validate [resiliency] module from CR [1] is not installed @ 01/27/25 15:54:20.702
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:54:30.773
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:54:30.822
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:54:30.872
2025/01/27 15:54:30 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-556c8cbd76-dfdr8,powermax-controller-556c8cbd76-fhpg6,
2025/01/27 15:55:00 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:55:20.971
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:55:21.012
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:55:21.059
  STEP: Ending: Install Powermax Driver (Minimal, With Resiliency), Disable Resiliency module
   @ 01/27/25 15:55:21.086
  STEP: Starting: Install Powermax Driver (Minimal, With Replication)  @ 01/27/25 15:55:26.088
  STEP: Returning false here @ 01/27/25 15:55:26.088
  STEP:      Executing  Given an environment with k8s or openshift, and CSM operator installed @ 01/27/25 15:55:26.088
  STEP:      Executing  Create storageclass with name [op-e2e-pmax] and template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:55:26.112
  STEP:      Executing  Set up creds with template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:55:26.749
  STEP:      Executing  Set up configMap with template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] name [powermax-reverseproxy-config] in namespace [powermax] for [pmaxAuthSidecar] @ 01/27/25 15:55:27.108
  STEP:      Executing  Apply custom resource [1] @ 01/27/25 15:55:27.574
  I0127 15:55:27.575048 15521 builder.go:121] Running '/usr/bin/kubectl --namespace=powermax apply --validate=true -f -'
  I0127 15:55:27.923899 15521 builder.go:146] stderr: ""
  I0127 15:55:27.923972 15521 builder.go:147] stdout: "containerstoragemodule.storage.dell.com/powermax created\n"
  STEP:      Executing  Validate custom resource [1] @ 01/27/25 15:55:27.924

err: expected custom resource status to be Succeeded. Got: Failed
  STEP:      Executing  Validate [powermax] driver from CR [1] is installed @ 01/27/25 15:56:18.003
  STEP:      Executing  Validate [replication] module from CR [1] is installed @ 01/27/25 15:56:38.07
  STEP:      Executing  Run custom test @ 01/27/25 15:56:48.287
  I0127 15:56:48.287844 15521 util.go:650] Running echo ["no current test implemented for replication"]
"no current test implemented for replication"
  STEP:      Executing  Enable forceRemoveDriver on CR [1] @ 01/27/25 15:56:48.49
  STEP:      Executing  Delete custom resource [1] @ 01/27/25 15:56:48.539
  STEP:      Executing  Validate [powermax] driver from CR [1] is not installed @ 01/27/25 15:56:48.588
2025/01/27 15:56:48 [validateDriverNotInstalled] making sure driver isn't installed

err: found the following pods: powermax-controller-8674d8686f-p2d56,powermax-controller-8674d8686f-q6v8g,
2025/01/27 15:57:18 [validateDriverNotInstalled] making sure driver isn't installed
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax_reverse_proxy_config.yaml] for [pmaxAuthSidecar] @ 01/27/25 15:57:38.657
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-storageclass-template.yaml] for [pmax] @ 01/27/25 15:57:38.706
  STEP:      Executing  Restore template [testfiles/powermax-templates/powermax-secret-template.yaml] for [pmaxCreds] @ 01/27/25 15:57:38.756
  STEP: Ending: Install Powermax Driver (Minimal, With Replication)
   @ 01/27/25 15:57:38.785
• [1812.224 seconds]
------------------------------

Ran 1 of 1 Specs in 1812.386 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 30m25.99675419s
Test Suite Passed

@falfaroc falfaroc marked this pull request as ready for review January 27, 2025 15:02
@jooseppi-luna
Copy link
Contributor

Did you run the E2E test scenario you fixed?

@falfaroc
Copy link
Contributor Author

Did you run the E2E test scenario you fixed?

@jooseppi-luna Currently running e2e tests verifying changes. Only actual code change is the default: 2 for replicas. Everything else is formatted/copied existing changes from the config folder.

jooseppi-luna
jooseppi-luna approved these changes Jan 27, 2025
View reviewed changes
Copy link
Contributor

@jooseppi-luna jooseppi-luna left a comment

Choose a reason for hiding this comment

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

lgtm, thanks!

@falfaroc falfaroc merged commit a67dd62 into main Jan 28, 2025
7 checks passed
@falfaroc falfaroc deleted the usr/falfaroc/align-deploy-crds branch January 28, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tdawe tdawe tdawe approved these changes

@jooseppi-luna jooseppi-luna jooseppi-luna approved these changes

@lukeatdell lukeatdell lukeatdell approved these changes

@abhi16394 abhi16394 Awaiting requested review from abhi16394 abhi16394 is a code owner

@mbasha-dell mbasha-dell Awaiting requested review from mbasha-dell mbasha-dell is a code owner

@alikdell alikdell Awaiting requested review from alikdell alikdell is a code owner

@bharathsreekanth bharathsreekanth Awaiting requested review from bharathsreekanth bharathsreekanth is a code owner

@chimanjain chimanjain Awaiting requested review from chimanjain chimanjain is a code owner

@coulof coulof Awaiting requested review from coulof coulof is a code owner

@Deepak-Ghivari Deepak-Ghivari Awaiting requested review from Deepak-Ghivari Deepak-Ghivari is a code owner

@gallacher gallacher Awaiting requested review from gallacher gallacher is a code owner

@gilltaran gilltaran Awaiting requested review from gilltaran gilltaran is a code owner

@harishp8889 harishp8889 Awaiting requested review from harishp8889 harishp8889 is a code owner

@HarishH-DELL HarishH-DELL Awaiting requested review from HarishH-DELL HarishH-DELL is a code owner

@JacobGros JacobGros Awaiting requested review from JacobGros JacobGros is a code owner

@karthikk92 karthikk92 Awaiting requested review from karthikk92 karthikk92 is a code owner

@kumarkgosa kumarkgosa Awaiting requested review from kumarkgosa kumarkgosa is a code owner

@bandak2 bandak2 Awaiting requested review from bandak2 bandak2 is a code owner

@meggm meggm Awaiting requested review from meggm meggm is a code owner

@mgandharva mgandharva Awaiting requested review from mgandharva mgandharva is a code owner

@mjsdell mjsdell Awaiting requested review from mjsdell mjsdell is a code owner

@nitesh3108 nitesh3108 Awaiting requested review from nitesh3108 nitesh3108 is a code owner

@Prabhu-Dell Prabhu-Dell Awaiting requested review from Prabhu-Dell Prabhu-Dell is a code owner

@rajendraindukuri rajendraindukuri Awaiting requested review from rajendraindukuri rajendraindukuri is a code owner

@rajkumar-palani rajkumar-palani Awaiting requested review from rajkumar-palani rajkumar-palani is a code owner

@shefali-malhotra shefali-malhotra Awaiting requested review from shefali-malhotra shefali-malhotra is a code owner

@panigs7 panigs7 Awaiting requested review from panigs7 panigs7 is a code owner

@shaynafinocchiaro shaynafinocchiaro Awaiting requested review from shaynafinocchiaro shaynafinocchiaro is a code owner

@atye atye Awaiting requested review from atye atye is a code owner

@sharmilarama sharmilarama Awaiting requested review from sharmilarama sharmilarama is a code owner

@shanmydell shanmydell Awaiting requested review from shanmydell shanmydell is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@falfaroc @jooseppi-luna @tdawe @lukeatdell