This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: test: support Win2022 test on capz
ResultFAILURE
Tests 1 failed / 19 succeeded
Started2022-04-20 06:30
Elapsed1h4m
Revision406a0d30aff10d48525d3e58710a2b1ac4047aa0
Refs 988

Test Failures


AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume on demand with mount options [kubernetes.io/azure-file] [file.csi.azure.com] [Windows] 9m7s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=AzureFile\sCSI\sDriver\sEnd\-to\-End\sTests\sDynamic\sProvisioning\sshould\screate\sa\svolume\son\sdemand\swith\smount\soptions\s\[kubernetes\.io\/azure\-file\]\s\[file\.csi\.azure\.com\]\s\[Windows\]$'
/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver/test/e2e/dynamic_provisioning_test.go:104
Unexpected error:
    <*errors.errorString | 0xc0007d72b0>: {
        s: "pod \"azurefile-volume-tester-hfw5n\" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.1.0.7 PodIP:192.168.113.4 PodIPs:[{IP:192.168.113.4}] StartTime:2022-04-20 07:05:14 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-tester State:{Waiting:&ContainerStateWaiting{Reason:RunContainerError,Message:context deadline exceeded,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:0,Signal:0,Reason:,Message:,StartedAt:0001-01-01 00:00:00 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1,}} Ready:false RestartCount:0 Image:mcr.microsoft.com/windows/servercore:ltsc2022 ImageID:mcr.microsoft.com/windows/servercore@sha256:378d85bd8e7388a777d25009f8523d1e95a5f544f131eaada83171045d5b2c1e ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1 Started:0xc00098e9e8}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
    }
    pod "azurefile-volume-tester-hfw5n" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.1.0.7 PodIP:192.168.113.4 PodIPs:[{IP:192.168.113.4}] StartTime:2022-04-20 07:05:14 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-tester State:{Waiting:&ContainerStateWaiting{Reason:RunContainerError,Message:context deadline exceeded,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:0,Signal:0,Reason:,Message:,StartedAt:0001-01-01 00:00:00 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1,}} Ready:false RestartCount:0 Image:mcr.microsoft.com/windows/servercore:ltsc2022 ImageID:mcr.microsoft.com/windows/servercore@sha256:378d85bd8e7388a777d25009f8523d1e95a5f544f131eaada83171045d5b2c1e ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1 Started:0xc00098e9e8}] QOSClass:BestEffort EphemeralContainerStatuses:[]}
occurred
/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver/test/e2e/testsuites/testsuites.go:691
				
				Click to see stdout/stderrfrom junit_01.xml

Find azurefile-volume-tester-hfw5n mentions in log files | View test history on testgrid


Show 19 Passed Tests

Show 14 Skipped Tests

Error lines from build-log.txt

... skipping 674 lines ...
certificate.cert-manager.io "selfsigned-cert" deleted
# Create secret for AzureClusterIdentity
./hack/create-identity-secret.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Error from server (NotFound): secrets "cluster-identity-secret" not found
secret/cluster-identity-secret created
secret/cluster-identity-secret labeled
# Deploy CAPI
curl --retry 3 -sSL https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.1.2/cluster-api-components.yaml | /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/envsubst-v2.0.0-20210730161058-179042472c46 | kubectl apply -f -
namespace/capi-system created
customresourcedefinition.apiextensions.k8s.io/clusterclasses.cluster.x-k8s.io created
... skipping 130 lines ...
timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-muexyd-kubeconfig; do sleep 1; done"
capz-muexyd-kubeconfig                 cluster.x-k8s.io/secret               1      1s
# Get kubeconfig and store it locally.
kubectl get secrets capz-muexyd-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! kubectl --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done"
Unable to connect to the server: dial tcp 20.23.51.247:6443: i/o timeout
error: the server doesn't have a resource type "nodes"
capz-muexyd-control-plane-mdlx9   NotReady   control-plane,master   13s   v1.23.5
run "kubectl --kubeconfig=./kubeconfig ..." to work with the new target cluster
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Waiting for 1 control plane machine(s), 2 worker machine(s), and 2 windows machine(s) to become Ready
node/capz-muex-6ltcc condition met
node/capz-muex-jlld4 condition met
... skipping 39 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   222k      0 --:--:-- --:--:-- --:--:--  222k
Downloading https://get.helm.sh/helm-v3.8.2-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull capzci.azurecr.io/azurefile-csi:e2e-500a03658af60fa873143a0181676422faa6f002 || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azurefile-csi:e2e-500a03658af60fa873143a0181676422faa6f002 not found: manifest unknown: manifest tagged by "e2e-500a03658af60fa873143a0181676422faa6f002" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.driverVersion=e2e-500a03658af60fa873143a0181676422faa6f002 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=500a03658af60fa873143a0181676422faa6f002 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-04-20T06:48:01Z -s -w -extldflags '-static'" -mod vendor -o _output/amd64/azurefileplugin.exe ./pkg/azurefileplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 2508 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.4.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - "--leader-election-namespace=kube-system"
            - '-handle-volume-inuse-error=false'
            - '-timeout=120s'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          imagePullPolicy: IfNotPresent
... skipping 148 lines ...
Git Commit: N/A
Go Version: go1.18.1
Platform: linux/amd64

Streaming logs below:
STEP: Building a namespace api object, basename azurefile
W0420 07:03:03.526860   37745 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
I0420 07:03:03.529901   37745 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME
I0420 07:03:03.529951   37745 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0420 07:03:03.529983   37745 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0420 07:03:03.530001   37745 driver.go:93] Enabling controller service capability: EXPAND_VOLUME
I0420 07:03:03.530018   37745 driver.go:93] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER
I0420 07:03:03.530046   37745 driver.go:112] Enabling volume access mode: SINGLE_NODE_WRITER
... skipping 121 lines ...
Apr 20 07:05:14.521: INFO: PersistentVolumeClaim pvc-v7lkz found and phase=Bound (1m43.384471173s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: sleep 1s waiting for volume ready in windows-2022
STEP: checking that the pods command exits with no error
Apr 20 07:05:15.848: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-hfw5n" in namespace "azurefile-2540" to be "Succeeded or Failed"
Apr 20 07:05:15.955: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 106.876955ms
Apr 20 07:05:18.063: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214468299s
Apr 20 07:05:20.171: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322551221s
Apr 20 07:05:22.279: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43044927s
Apr 20 07:05:24.390: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541863701s
Apr 20 07:05:26.502: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.653679639s
... skipping 192 lines ...
Apr 20 07:12:14.045: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 6m58.196494382s
Apr 20 07:12:16.156: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 7m0.307627839s
Apr 20 07:12:18.267: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 7m2.41894627s
Apr 20 07:12:20.379: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 7m4.530985159s
Apr 20 07:12:22.490: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 7m6.642150618s
Apr 20 07:12:24.602: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Pending", Reason="", readiness=false. Elapsed: 7m8.753707399s
Apr 20 07:12:26.714: INFO: Pod "azurefile-volume-tester-hfw5n": Phase="Failed", Reason="", readiness=false. Elapsed: 7m10.865684365s
Apr 20 07:12:26.715: INFO: deleting Pod "azurefile-2540"/"azurefile-volume-tester-hfw5n"
Apr 20 07:12:26.842: INFO: Pod azurefile-volume-tester-hfw5n has the following logs: 
STEP: Deleting pod azurefile-volume-tester-hfw5n in namespace azurefile-2540
Apr 20 07:12:26.960: INFO: deleting PVC "azurefile-2540"/"pvc-v7lkz"
Apr 20 07:12:26.960: INFO: Deleting PersistentVolumeClaim "pvc-v7lkz"
STEP: waiting for claim's PV "pvc-121bd7d4-4c85-48e4-9104-bf6e191df67d" to be deleted
... skipping 10 lines ...
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:05:13 +0000 UTC - event for pvc-v7lkz: {file.csi.azure.com_capz-muexyd-md-0-z94d5_678feea9-dc82-4b6b-acd4-b21659d25360 } ProvisioningSucceeded: Successfully provisioned volume pvc-121bd7d4-4c85-48e4-9104-bf6e191df67d
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:05:14 +0000 UTC - event for azurefile-volume-tester-hfw5n: {default-scheduler } Scheduled: Successfully assigned azurefile-2540/azurefile-volume-tester-hfw5n to capz-muex-6ltcc
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:05:27 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Pulling: Pulling image "mcr.microsoft.com/windows/servercore:ltsc2022"
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:10:24 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Pulled: Successfully pulled image "mcr.microsoft.com/windows/servercore:ltsc2022" in 4m57.8033942s
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:10:25 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Created: Created container volume-tester
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:12:25 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Pulled: Container image "mcr.microsoft.com/windows/servercore:ltsc2022" already present on machine
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:12:25 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Failed: Error: context deadline exceeded
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:12:31 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Started: Started container volume-tester
Apr 20 07:12:32.833: INFO: At 2022-04-20 07:12:31 +0000 UTC - event for azurefile-volume-tester-hfw5n: {kubelet capz-muex-6ltcc} Killing: Stopping container volume-tester
Apr 20 07:12:32.939: INFO: POD  NODE  PHASE  GRACE  CONDITIONS
Apr 20 07:12:32.939: INFO: 
Apr 20 07:12:33.085: INFO: 
Logging node info for node capz-muex-6ltcc
... skipping 114 lines ...
• Failure [547.974 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver/test/e2e/dynamic_provisioning_test.go:42
  should create a volume on demand with mount options [kubernetes.io/azure-file] [file.csi.azure.com] [Windows] [It]
  /home/prow/go/src/sigs.k8s.io/azurefile-csi-driver/test/e2e/dynamic_provisioning_test.go:104

  Unexpected error:
      <*errors.errorString | 0xc0007d72b0>: {
          s: "pod \"azurefile-volume-tester-hfw5n\" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.1.0.7 PodIP:192.168.113.4 PodIPs:[{IP:192.168.113.4}] StartTime:2022-04-20 07:05:14 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-tester State:{Waiting:&ContainerStateWaiting{Reason:RunContainerError,Message:context deadline exceeded,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:0,Signal:0,Reason:,Message:,StartedAt:0001-01-01 00:00:00 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1,}} Ready:false RestartCount:0 Image:mcr.microsoft.com/windows/servercore:ltsc2022 ImageID:mcr.microsoft.com/windows/servercore@sha256:378d85bd8e7388a777d25009f8523d1e95a5f544f131eaada83171045d5b2c1e ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1 Started:0xc00098e9e8}] QOSClass:BestEffort EphemeralContainerStatuses:[]}",
      }
      pod "azurefile-volume-tester-hfw5n" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-tester]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-04-20 07:05:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.1.0.7 PodIP:192.168.113.4 PodIPs:[{IP:192.168.113.4}] StartTime:2022-04-20 07:05:14 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-tester State:{Waiting:&ContainerStateWaiting{Reason:RunContainerError,Message:context deadline exceeded,} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:0,Signal:0,Reason:,Message:,StartedAt:0001-01-01 00:00:00 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1,}} Ready:false RestartCount:0 Image:mcr.microsoft.com/windows/servercore:ltsc2022 ImageID:mcr.microsoft.com/windows/servercore@sha256:378d85bd8e7388a777d25009f8523d1e95a5f544f131eaada83171045d5b2c1e ContainerID:containerd://2f90e6bacd22f5091e1301431c9354ef224c466f133230d4f87368f3547bd2d1 Started:0xc00098e9e8}] QOSClass:BestEffort EphemeralContainerStatuses:[]}
  occurred

  /home/prow/go/src/sigs.k8s.io/azurefile-csi-driver/test/e2e/testsuites/testsuites.go:691
------------------------------
Dynamic Provisioning 
  should create a pod with volume mount subpath [file.csi.azure.com] [Windows]
... skipping 26 lines ...
Apr 20 07:12:58.598: INFO: PersistentVolumeClaim pvc-v6wm4 found but phase is Pending instead of Bound.
Apr 20 07:13:00.707: INFO: PersistentVolumeClaim pvc-v6wm4 found and phase=Bound (21.188187065s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:13:01.029: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-rkcwl" in namespace "azurefile-4728" to be "Succeeded or Failed"
Apr 20 07:13:01.136: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 106.954021ms
Apr 20 07:13:03.245: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215339693s
Apr 20 07:13:05.355: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325572746s
Apr 20 07:13:07.466: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436498136s
Apr 20 07:13:09.577: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.548042818s
Apr 20 07:13:11.688: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.658904825s
Apr 20 07:13:13.799: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.769983277s
Apr 20 07:13:15.911: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.881292062s
Apr 20 07:13:18.022: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Running", Reason="", readiness=true. Elapsed: 16.99253421s
Apr 20 07:13:20.133: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Running", Reason="", readiness=true. Elapsed: 19.103669509s
Apr 20 07:13:22.244: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Running", Reason="", readiness=true. Elapsed: 21.214580188s
Apr 20 07:13:24.354: INFO: Pod "azurefile-volume-tester-rkcwl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.324440237s
STEP: Saw pod success
Apr 20 07:13:24.354: INFO: Pod "azurefile-volume-tester-rkcwl" satisfied condition "Succeeded or Failed"
Apr 20 07:13:24.354: INFO: deleting Pod "azurefile-4728"/"azurefile-volume-tester-rkcwl"
Apr 20 07:13:24.483: INFO: Pod azurefile-volume-tester-rkcwl has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-rkcwl in namespace azurefile-4728
Apr 20 07:13:24.603: INFO: deleting PVC "azurefile-4728"/"pvc-v6wm4"
Apr 20 07:13:24.603: INFO: Deleting PersistentVolumeClaim "pvc-v6wm4"
... skipping 116 lines ...
Apr 20 07:14:31.927: INFO: PersistentVolumeClaim pvc-8hms9 found but phase is Pending instead of Bound.
Apr 20 07:14:34.034: INFO: PersistentVolumeClaim pvc-8hms9 found and phase=Bound (23.297152759s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with an error
Apr 20 07:14:34.356: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-875rf" in namespace "azurefile-2790" to be "Error status code"
Apr 20 07:14:34.463: INFO: Pod "azurefile-volume-tester-875rf": Phase="Pending", Reason="", readiness=false. Elapsed: 106.78357ms
Apr 20 07:14:36.571: INFO: Pod "azurefile-volume-tester-875rf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21502611s
Apr 20 07:14:38.682: INFO: Pod "azurefile-volume-tester-875rf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325961917s
Apr 20 07:14:40.793: INFO: Pod "azurefile-volume-tester-875rf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436723145s
Apr 20 07:14:42.903: INFO: Pod "azurefile-volume-tester-875rf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547032715s
Apr 20 07:14:45.013: INFO: Pod "azurefile-volume-tester-875rf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.657589275s
Apr 20 07:14:47.125: INFO: Pod "azurefile-volume-tester-875rf": Phase="Running", Reason="", readiness=true. Elapsed: 12.768956278s
Apr 20 07:14:49.235: INFO: Pod "azurefile-volume-tester-875rf": Phase="Running", Reason="", readiness=true. Elapsed: 14.87920913s
Apr 20 07:14:51.345: INFO: Pod "azurefile-volume-tester-875rf": Phase="Running", Reason="", readiness=true. Elapsed: 16.989287419s
Apr 20 07:14:53.456: INFO: Pod "azurefile-volume-tester-875rf": Phase="Failed", Reason="", readiness=false. Elapsed: 19.100514069s
STEP: Saw pod failure
Apr 20 07:14:53.456: INFO: Pod "azurefile-volume-tester-875rf" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Apr 20 07:14:53.576: INFO: deleting Pod "azurefile-2790"/"azurefile-volume-tester-875rf"
Apr 20 07:14:53.689: INFO: Pod azurefile-volume-tester-875rf has the following logs: out-file : Access to the path 'C:\mnt\test-1\data' is denied.
At line:1 char:1
+ echo $null >> C:\mnt\test-1\data
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 202 lines ...
Apr 20 07:16:08.864: INFO: PersistentVolumeClaim pvc-btkt7 found but phase is Pending instead of Bound.
Apr 20 07:16:10.971: INFO: PersistentVolumeClaim pvc-btkt7 found and phase=Bound (2.214666805s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:16:11.293: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-8jb9x" in namespace "azurefile-4538" to be "Succeeded or Failed"
Apr 20 07:16:11.400: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 106.698952ms
Apr 20 07:16:13.509: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215223948s
Apr 20 07:16:15.616: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322451044s
Apr 20 07:16:17.727: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433325498s
Apr 20 07:16:19.838: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544434967s
Apr 20 07:16:21.949: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.655688055s
Apr 20 07:16:24.060: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Pending", Reason="", readiness=false. Elapsed: 12.766695964s
Apr 20 07:16:26.170: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Running", Reason="", readiness=true. Elapsed: 14.876969286s
Apr 20 07:16:28.281: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Running", Reason="", readiness=true. Elapsed: 16.988036635s
Apr 20 07:16:30.392: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Running", Reason="", readiness=true. Elapsed: 19.099015836s
Apr 20 07:16:32.502: INFO: Pod "azurefile-volume-tester-8jb9x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.20865358s
STEP: Saw pod success
Apr 20 07:16:32.502: INFO: Pod "azurefile-volume-tester-8jb9x" satisfied condition "Succeeded or Failed"
STEP: resizing the pvc
STEP: sleep 30s waiting for resize complete
STEP: checking the resizing result
STEP: checking the resizing PV result
STEP: checking the resizing azurefile result
Apr 20 07:17:03.354: INFO: deleting Pod "azurefile-4538"/"azurefile-volume-tester-8jb9x"
... skipping 303 lines ...
Apr 20 07:17:37.789: INFO: PersistentVolumeClaim pvc-2vqfz found but phase is Pending instead of Bound.
Apr 20 07:17:39.896: INFO: PersistentVolumeClaim pvc-2vqfz found and phase=Bound (2.214025642s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:17:40.222: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-59vp9" in namespace "azurefile-7726" to be "Succeeded or Failed"
Apr 20 07:17:40.332: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 109.624978ms
Apr 20 07:17:42.443: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220587385s
Apr 20 07:17:44.554: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.331514619s
Apr 20 07:17:46.665: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.442538651s
Apr 20 07:17:48.776: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.553960503s
Apr 20 07:17:50.887: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.664533996s
Apr 20 07:17:52.998: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.776056829s
Apr 20 07:17:55.108: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.886232449s
Apr 20 07:17:57.218: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Running", Reason="", readiness=true. Elapsed: 16.996073221s
Apr 20 07:17:59.329: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Running", Reason="", readiness=true. Elapsed: 19.106646799s
Apr 20 07:18:01.440: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Running", Reason="", readiness=true. Elapsed: 21.217757017s
Apr 20 07:18:03.551: INFO: Pod "azurefile-volume-tester-59vp9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.329294285s
STEP: Saw pod success
Apr 20 07:18:03.551: INFO: Pod "azurefile-volume-tester-59vp9" satisfied condition "Succeeded or Failed"
Apr 20 07:18:03.551: INFO: deleting Pod "azurefile-7726"/"azurefile-volume-tester-59vp9"
Apr 20 07:18:03.899: INFO: Pod azurefile-volume-tester-59vp9 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-59vp9 in namespace azurefile-7726
Apr 20 07:18:04.016: INFO: deleting PVC "azurefile-7726"/"pvc-2vqfz"
Apr 20 07:18:04.016: INFO: Deleting PersistentVolumeClaim "pvc-2vqfz"
... skipping 90 lines ...
check the driver pods if restarts ...
======================================================================================
2022/04/20 07:18:11 Check successfully
Apr 20 07:18:11.208: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
2022/04/20 07:18:11 run script: test/utils/get_storage_account_secret_name.sh
2022/04/20 07:18:11 got output: azure-storage-account-fe1ea328664a44cd4adcc00-secret
, error: <nil>
2022/04/20 07:18:11 got storage account secret name: azure-storage-account-fe1ea328664a44cd4adcc00-secret
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Apr 20 07:18:11.910: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8rpfc] to have phase Bound
Apr 20 07:18:12.017: INFO: PersistentVolumeClaim pvc-8rpfc found and phase=Bound (106.715462ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: sleep 1s waiting for volume ready in windows-2022
STEP: checking that the pods command exits with no error
Apr 20 07:18:13.340: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-h5pfb" in namespace "azurefile-1387" to be "Succeeded or Failed"
Apr 20 07:18:13.447: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Pending", Reason="", readiness=false. Elapsed: 107.048805ms
Apr 20 07:18:15.555: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214801235s
Apr 20 07:18:17.665: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32506075s
Apr 20 07:18:19.776: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435976559s
Apr 20 07:18:21.887: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.546893424s
Apr 20 07:18:23.997: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Running", Reason="", readiness=true. Elapsed: 10.657646552s
Apr 20 07:18:26.109: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Running", Reason="", readiness=true. Elapsed: 12.769059674s
Apr 20 07:18:28.220: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Running", Reason="", readiness=true. Elapsed: 14.880432906s
Apr 20 07:18:30.331: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Running", Reason="", readiness=true. Elapsed: 16.991002113s
Apr 20 07:18:32.444: INFO: Pod "azurefile-volume-tester-h5pfb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.103760679s
STEP: Saw pod success
Apr 20 07:18:32.444: INFO: Pod "azurefile-volume-tester-h5pfb" satisfied condition "Succeeded or Failed"
Apr 20 07:18:32.444: INFO: deleting Pod "azurefile-1387"/"azurefile-volume-tester-h5pfb"
Apr 20 07:18:32.561: INFO: Pod azurefile-volume-tester-h5pfb has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-h5pfb in namespace azurefile-1387
Apr 20 07:18:32.772: INFO: deleting PVC "azurefile-1387"/"pvc-8rpfc"
Apr 20 07:18:32.772: INFO: Deleting PersistentVolumeClaim "pvc-8rpfc"
... skipping 68 lines ...
Apr 20 07:19:47.105: INFO: PersistentVolumeClaim pvc-nfktq found and phase=Bound (1m11.803847972s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: sleep 1s waiting for volume ready in windows-2022
STEP: checking that the pods command exits with no error
Apr 20 07:19:48.427: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-8rmwd" in namespace "azurefile-4547" to be "Succeeded or Failed"
Apr 20 07:19:48.534: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Pending", Reason="", readiness=false. Elapsed: 107.246477ms
Apr 20 07:19:50.642: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215397151s
Apr 20 07:19:52.754: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326440925s
Apr 20 07:19:54.865: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43839706s
Apr 20 07:19:56.984: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.55739373s
Apr 20 07:19:59.095: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.667551308s
Apr 20 07:20:01.205: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Running", Reason="", readiness=true. Elapsed: 12.778348341s
Apr 20 07:20:03.317: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Running", Reason="", readiness=true. Elapsed: 14.889578726s
Apr 20 07:20:05.431: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Running", Reason="", readiness=true. Elapsed: 17.003596185s
Apr 20 07:20:07.542: INFO: Pod "azurefile-volume-tester-8rmwd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.114549399s
STEP: Saw pod success
Apr 20 07:20:07.542: INFO: Pod "azurefile-volume-tester-8rmwd" satisfied condition "Succeeded or Failed"
Apr 20 07:20:07.542: INFO: deleting Pod "azurefile-4547"/"azurefile-volume-tester-8rmwd"
Apr 20 07:20:07.673: INFO: Pod azurefile-volume-tester-8rmwd has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-8rmwd in namespace azurefile-4547
Apr 20 07:20:07.791: INFO: deleting PVC "azurefile-4547"/"pvc-nfktq"
Apr 20 07:20:07.791: INFO: Deleting PersistentVolumeClaim "pvc-nfktq"
... skipping 74 lines ...
check the driver pods if restarts ...
======================================================================================
2022/04/20 07:21:35 Check successfully
Apr 20 07:21:35.579: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
2022/04/20 07:21:35 run script: test/utils/get_storage_account_secret_name.sh
2022/04/20 07:21:36 got output: azure-storage-account-fe1ea328664a44cd4adcc00-secret
, error: <nil>
2022/04/20 07:21:36 got storage account secret name: azure-storage-account-fe1ea328664a44cd4adcc00-secret
STEP: Successfully provisioned AzureFile volume: "capz-muexyd#fe1ea328664a44cd4adcc00#csi-inline-smb-volume##csi-inline-smb-volume"

STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:21:37.857: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-6znr2" in namespace "azurefile-4801" to be "Succeeded or Failed"
Apr 20 07:21:37.964: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Pending", Reason="", readiness=false. Elapsed: 106.712701ms
Apr 20 07:21:40.071: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214235016s
Apr 20 07:21:42.181: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324476974s
Apr 20 07:21:44.292: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4352751s
Apr 20 07:21:46.403: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545810699s
Apr 20 07:21:48.513: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.656146815s
Apr 20 07:21:50.623: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Running", Reason="", readiness=true. Elapsed: 12.766571461s
Apr 20 07:21:52.735: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Running", Reason="", readiness=true. Elapsed: 14.877628107s
Apr 20 07:21:54.846: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Running", Reason="", readiness=true. Elapsed: 16.989381647s
Apr 20 07:21:56.956: INFO: Pod "azurefile-volume-tester-6znr2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.099071982s
STEP: Saw pod success
Apr 20 07:21:56.956: INFO: Pod "azurefile-volume-tester-6znr2" satisfied condition "Succeeded or Failed"
Apr 20 07:21:56.956: INFO: deleting Pod "azurefile-4801"/"azurefile-volume-tester-6znr2"
Apr 20 07:21:57.071: INFO: Pod azurefile-volume-tester-6znr2 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-6znr2 in namespace azurefile-4801
Apr 20 07:21:57.281: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azurefile-4801" for this suite.
... skipping 43 lines ...
======================================================================================
2022/04/20 07:22:00 Check successfully
Apr 20 07:22:00.614: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: creating secret smbcreds in namespace azurefile-1166
2022/04/20 07:22:00 run script: test/utils/get_smb_svc_public_ip.sh
2022/04/20 07:22:01 got output: 20.123.239.190
, error: <nil>
2022/04/20 07:22:01 use server on Windows: 20.123.239.190
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:22:01.321: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-4thkq" in namespace "azurefile-1166" to be "Succeeded or Failed"
Apr 20 07:22:01.427: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Pending", Reason="", readiness=false. Elapsed: 106.465835ms
Apr 20 07:22:03.534: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213584248s
Apr 20 07:22:05.645: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324328904s
Apr 20 07:22:07.755: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433868906s
Apr 20 07:22:09.865: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54440124s
Apr 20 07:22:11.976: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.655304164s
Apr 20 07:22:14.086: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Running", Reason="", readiness=true. Elapsed: 12.765590394s
Apr 20 07:22:16.197: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Running", Reason="", readiness=true. Elapsed: 14.876574018s
Apr 20 07:22:18.307: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Running", Reason="", readiness=true. Elapsed: 16.986549669s
Apr 20 07:22:20.421: INFO: Pod "azurefile-volume-tester-4thkq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.100176589s
STEP: Saw pod success
Apr 20 07:22:20.421: INFO: Pod "azurefile-volume-tester-4thkq" satisfied condition "Succeeded or Failed"
Apr 20 07:22:20.421: INFO: deleting Pod "azurefile-1166"/"azurefile-volume-tester-4thkq"
Apr 20 07:22:20.538: INFO: Pod azurefile-volume-tester-4thkq has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-4thkq in namespace azurefile-1166
Apr 20 07:22:20.652: INFO: deleting Secret smbcreds
Apr 20 07:22:20.760: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 132 lines ...
Apr 20 07:22:52.929: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-qhjcg] to have phase Bound
Apr 20 07:22:53.036: INFO: PersistentVolumeClaim pvc-qhjcg found and phase=Bound (106.709302ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with an error
Apr 20 07:22:53.357: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-45fnz" in namespace "azurefile-5320" to be "Error status code"
Apr 20 07:22:53.464: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Pending", Reason="", readiness=false. Elapsed: 106.63399ms
Apr 20 07:22:55.572: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214029374s
Apr 20 07:22:57.683: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325029899s
Apr 20 07:22:59.793: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435854448s
Apr 20 07:23:01.903: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545489745s
Apr 20 07:23:04.039: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.681684833s
Apr 20 07:23:06.149: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Running", Reason="", readiness=true. Elapsed: 12.791604206s
Apr 20 07:23:08.259: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Running", Reason="", readiness=true. Elapsed: 14.90176517s
Apr 20 07:23:10.370: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Running", Reason="", readiness=true. Elapsed: 17.012345224s
Apr 20 07:23:12.480: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Running", Reason="", readiness=true. Elapsed: 19.122520452s
Apr 20 07:23:14.591: INFO: Pod "azurefile-volume-tester-45fnz": Phase="Failed", Reason="", readiness=false. Elapsed: 21.233269351s
STEP: Saw pod failure
Apr 20 07:23:14.591: INFO: Pod "azurefile-volume-tester-45fnz" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Apr 20 07:23:14.719: INFO: deleting Pod "azurefile-5320"/"azurefile-volume-tester-45fnz"
Apr 20 07:23:14.831: INFO: Pod azurefile-volume-tester-45fnz has the following logs: Out-File : Access to the path 'C:\mnt\test-1\data.txt' is denied.
At line:1 char:22
+ ... cho 'hello world' | Out-File -FilePath C:\mnt\test-1\data.txt; Get-Co ...
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 55 lines ...
Apr 20 07:23:19.072: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-9ll7b] to have phase Bound
Apr 20 07:23:19.179: INFO: PersistentVolumeClaim pvc-9ll7b found and phase=Bound (106.951295ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:23:19.500: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-gm8x8" in namespace "azurefile-9103" to be "Succeeded or Failed"
Apr 20 07:23:19.606: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Pending", Reason="", readiness=false. Elapsed: 106.489938ms
Apr 20 07:23:21.715: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214827398s
Apr 20 07:23:23.825: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325540454s
Apr 20 07:23:25.935: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435671087s
Apr 20 07:23:28.046: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.546377235s
Apr 20 07:23:30.157: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.657407423s
Apr 20 07:23:32.268: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Running", Reason="", readiness=true. Elapsed: 12.76852056s
Apr 20 07:23:34.380: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Running", Reason="", readiness=true. Elapsed: 14.87995283s
Apr 20 07:23:36.490: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Running", Reason="", readiness=true. Elapsed: 16.990325649s
Apr 20 07:23:38.600: INFO: Pod "azurefile-volume-tester-gm8x8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.10035041s
STEP: Saw pod success
Apr 20 07:23:38.600: INFO: Pod "azurefile-volume-tester-gm8x8" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Apr 20 07:23:38.816: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-nhbbf] to have phase Bound
Apr 20 07:23:38.923: INFO: PersistentVolumeClaim pvc-nhbbf found and phase=Bound (106.316399ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:23:39.247: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-x294p" in namespace "azurefile-9103" to be "Succeeded or Failed"
Apr 20 07:23:39.357: INFO: Pod "azurefile-volume-tester-x294p": Phase="Pending", Reason="", readiness=false. Elapsed: 109.980248ms
Apr 20 07:23:41.464: INFO: Pod "azurefile-volume-tester-x294p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217106581s
Apr 20 07:23:43.576: INFO: Pod "azurefile-volume-tester-x294p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328306213s
Apr 20 07:23:45.686: INFO: Pod "azurefile-volume-tester-x294p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.438787932s
Apr 20 07:23:47.797: INFO: Pod "azurefile-volume-tester-x294p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.549640204s
Apr 20 07:23:49.908: INFO: Pod "azurefile-volume-tester-x294p": Phase="Running", Reason="", readiness=true. Elapsed: 10.660538814s
Apr 20 07:23:52.020: INFO: Pod "azurefile-volume-tester-x294p": Phase="Running", Reason="", readiness=true. Elapsed: 12.772531617s
Apr 20 07:23:54.130: INFO: Pod "azurefile-volume-tester-x294p": Phase="Running", Reason="", readiness=true. Elapsed: 14.882598118s
Apr 20 07:23:56.241: INFO: Pod "azurefile-volume-tester-x294p": Phase="Running", Reason="", readiness=true. Elapsed: 16.99337156s
Apr 20 07:23:58.350: INFO: Pod "azurefile-volume-tester-x294p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.103118354s
STEP: Saw pod success
Apr 20 07:23:58.351: INFO: Pod "azurefile-volume-tester-x294p" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Apr 20 07:23:58.570: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8cznp] to have phase Bound
Apr 20 07:23:58.677: INFO: PersistentVolumeClaim pvc-8cznp found and phase=Bound (106.659228ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:23:58.998: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-q886n" in namespace "azurefile-9103" to be "Succeeded or Failed"
Apr 20 07:23:59.104: INFO: Pod "azurefile-volume-tester-q886n": Phase="Pending", Reason="", readiness=false. Elapsed: 106.53803ms
Apr 20 07:24:01.212: INFO: Pod "azurefile-volume-tester-q886n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214543546s
Apr 20 07:24:03.323: INFO: Pod "azurefile-volume-tester-q886n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325039355s
Apr 20 07:24:05.433: INFO: Pod "azurefile-volume-tester-q886n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435563216s
Apr 20 07:24:07.544: INFO: Pod "azurefile-volume-tester-q886n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54646547s
Apr 20 07:24:09.655: INFO: Pod "azurefile-volume-tester-q886n": Phase="Running", Reason="", readiness=true. Elapsed: 10.657585723s
Apr 20 07:24:11.765: INFO: Pod "azurefile-volume-tester-q886n": Phase="Running", Reason="", readiness=true. Elapsed: 12.767624512s
Apr 20 07:24:13.876: INFO: Pod "azurefile-volume-tester-q886n": Phase="Running", Reason="", readiness=true. Elapsed: 14.878314311s
Apr 20 07:24:15.987: INFO: Pod "azurefile-volume-tester-q886n": Phase="Running", Reason="", readiness=true. Elapsed: 16.989109236s
Apr 20 07:24:18.097: INFO: Pod "azurefile-volume-tester-q886n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.09988243s
STEP: Saw pod success
Apr 20 07:24:18.098: INFO: Pod "azurefile-volume-tester-q886n" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Apr 20 07:24:18.312: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-xmgl5] to have phase Bound
Apr 20 07:24:18.419: INFO: PersistentVolumeClaim pvc-xmgl5 found and phase=Bound (106.654445ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:24:18.741: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-ndsdb" in namespace "azurefile-9103" to be "Succeeded or Failed"
Apr 20 07:24:18.847: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Pending", Reason="", readiness=false. Elapsed: 106.165218ms
Apr 20 07:24:20.954: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.213337036s
Apr 20 07:24:23.066: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324695035s
Apr 20 07:24:25.177: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435691434s
Apr 20 07:24:27.291: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.549468245s
Apr 20 07:24:29.401: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Running", Reason="", readiness=true. Elapsed: 10.660022059s
Apr 20 07:24:31.512: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Running", Reason="", readiness=true. Elapsed: 12.770985699s
Apr 20 07:24:33.622: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Running", Reason="", readiness=true. Elapsed: 14.881266338s
Apr 20 07:24:35.733: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Running", Reason="", readiness=true. Elapsed: 16.992345813s
Apr 20 07:24:37.844: INFO: Pod "azurefile-volume-tester-ndsdb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.102464715s
STEP: Saw pod success
Apr 20 07:24:37.844: INFO: Pod "azurefile-volume-tester-ndsdb" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Apr 20 07:24:38.062: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-gf79d] to have phase Bound
Apr 20 07:24:38.169: INFO: PersistentVolumeClaim pvc-gf79d found and phase=Bound (106.982915ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:24:38.491: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-s8hf4" in namespace "azurefile-9103" to be "Succeeded or Failed"
Apr 20 07:24:38.598: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Pending", Reason="", readiness=false. Elapsed: 106.458972ms
Apr 20 07:24:40.706: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214429235s
Apr 20 07:24:42.816: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324455565s
Apr 20 07:24:44.927: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435251639s
Apr 20 07:24:47.036: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545098068s
Apr 20 07:24:49.147: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.655780484s
Apr 20 07:24:51.261: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Running", Reason="", readiness=true. Elapsed: 12.769741131s
Apr 20 07:24:53.372: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Running", Reason="", readiness=true. Elapsed: 14.880621454s
Apr 20 07:24:55.482: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Running", Reason="", readiness=true. Elapsed: 16.99055523s
Apr 20 07:24:57.593: INFO: Pod "azurefile-volume-tester-s8hf4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.101277227s
STEP: Saw pod success
Apr 20 07:24:57.593: INFO: Pod "azurefile-volume-tester-s8hf4" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Apr 20 07:24:57.809: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-smckg] to have phase Bound
Apr 20 07:24:57.915: INFO: PersistentVolumeClaim pvc-smckg found and phase=Bound (106.552174ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:24:58.236: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-pwxdw" in namespace "azurefile-9103" to be "Succeeded or Failed"
Apr 20 07:24:58.343: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Pending", Reason="", readiness=false. Elapsed: 106.345598ms
Apr 20 07:25:00.451: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214780854s
Apr 20 07:25:02.562: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325479868s
Apr 20 07:25:04.672: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435601495s
Apr 20 07:25:06.783: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.546518892s
Apr 20 07:25:08.894: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Running", Reason="", readiness=true. Elapsed: 10.657415854s
Apr 20 07:25:11.004: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Running", Reason="", readiness=true. Elapsed: 12.768256993s
Apr 20 07:25:13.115: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Running", Reason="", readiness=true. Elapsed: 14.878434122s
Apr 20 07:25:15.225: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Running", Reason="", readiness=true. Elapsed: 16.988411866s
Apr 20 07:25:17.334: INFO: Pod "azurefile-volume-tester-pwxdw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.098317499s
STEP: Saw pod success
Apr 20 07:25:17.335: INFO: Pod "azurefile-volume-tester-pwxdw" satisfied condition "Succeeded or Failed"
Apr 20 07:25:17.335: INFO: deleting Pod "azurefile-9103"/"azurefile-volume-tester-pwxdw"
Apr 20 07:25:17.465: INFO: Pod azurefile-volume-tester-pwxdw has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-pwxdw in namespace azurefile-9103
Apr 20 07:25:17.579: INFO: deleting PVC "azurefile-9103"/"pvc-smckg"
Apr 20 07:25:17.579: INFO: Deleting PersistentVolumeClaim "pvc-smckg"
... skipping 148 lines ...
Apr 20 07:25:30.586: INFO: PersistentVolumeClaim pvc-zrxtg found but phase is Pending instead of Bound.
Apr 20 07:25:32.693: INFO: PersistentVolumeClaim pvc-zrxtg found and phase=Bound (2.214228273s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:25:33.018: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-4fkm9" in namespace "azurefile-8470" to be "Succeeded or Failed"
Apr 20 07:25:33.124: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Pending", Reason="", readiness=false. Elapsed: 106.384429ms
Apr 20 07:25:35.233: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214930849s
Apr 20 07:25:37.343: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325526722s
Apr 20 07:25:39.454: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436499797s
Apr 20 07:25:41.565: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547454105s
Apr 20 07:25:43.675: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.657664168s
Apr 20 07:25:45.785: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Running", Reason="", readiness=true. Elapsed: 12.76727573s
Apr 20 07:25:47.895: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Running", Reason="", readiness=true. Elapsed: 14.87764838s
Apr 20 07:25:50.005: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Running", Reason="", readiness=true. Elapsed: 16.987442187s
Apr 20 07:25:52.116: INFO: Pod "azurefile-volume-tester-4fkm9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.098503707s
STEP: Saw pod success
Apr 20 07:25:52.116: INFO: Pod "azurefile-volume-tester-4fkm9" satisfied condition "Succeeded or Failed"
Apr 20 07:25:52.116: INFO: deleting Pod "azurefile-8470"/"azurefile-volume-tester-4fkm9"
Apr 20 07:25:52.235: INFO: Pod azurefile-volume-tester-4fkm9 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-4fkm9 in namespace azurefile-8470
Apr 20 07:25:52.350: INFO: deleting PVC "azurefile-8470"/"pvc-zrxtg"
Apr 20 07:25:52.351: INFO: Deleting PersistentVolumeClaim "pvc-zrxtg"
... skipping 33 lines ...
Apr 20 07:25:56.527: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-vcrht] to have phase Bound
Apr 20 07:25:56.633: INFO: PersistentVolumeClaim pvc-vcrht found and phase=Bound (106.25577ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Apr 20 07:25:56.957: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-rmcz8" in namespace "azurefile-7029" to be "Succeeded or Failed"
Apr 20 07:25:57.064: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Pending", Reason="", readiness=false. Elapsed: 106.341939ms
Apr 20 07:25:59.172: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214482238s
Apr 20 07:26:01.283: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.32536539s
Apr 20 07:26:03.394: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437234846s
Apr 20 07:26:05.506: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.549271734s
Apr 20 07:26:07.617: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.660028733s
Apr 20 07:26:09.728: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Running", Reason="", readiness=true. Elapsed: 12.771065055s
Apr 20 07:26:11.839: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Running", Reason="", readiness=true. Elapsed: 14.881856904s
Apr 20 07:26:13.949: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Running", Reason="", readiness=true. Elapsed: 16.991790756s
Apr 20 07:26:16.060: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Running", Reason="", readiness=true. Elapsed: 19.102614652s
Apr 20 07:26:18.171: INFO: Pod "azurefile-volume-tester-rmcz8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.213507491s
STEP: Saw pod success
Apr 20 07:26:18.171: INFO: Pod "azurefile-volume-tester-rmcz8" satisfied condition "Succeeded or Failed"
Apr 20 07:26:18.171: INFO: deleting Pod "azurefile-7029"/"azurefile-volume-tester-rmcz8"
Apr 20 07:26:18.287: INFO: Pod azurefile-volume-tester-rmcz8 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-rmcz8 in namespace azurefile-7029
Apr 20 07:26:18.404: INFO: deleting PVC "azurefile-7029"/"pvc-vcrht"
Apr 20 07:26:18.404: INFO: Deleting PersistentVolumeClaim "pvc-vcrht"
... skipping 86 lines ...
Platform: linux/amd64

Streaming logs below:
I0420 07:01:52.644234       1 azurefile.go:267] driver userAgent: file.csi.azure.com/e2e-500a03658af60fa873143a0181676422faa6f002 gc/go1.18.1 (amd64-linux) e2e-test
I0420 07:01:52.644643       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0420 07:01:52.659275       1 round_trippers.go:553] GET https://10.96.0.1:443/api/v1/namespaces/kube-system/secrets/azure-cloud-provider 404 Not Found in 14 milliseconds
W0420 07:01:52.659621       1 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0420 07:01:52.659649       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0420 07:01:52.659662       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0420 07:01:52.659710       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0420 07:01:52.660551       1 azure_auth.go:245] Using AzurePublicCloud environment
I0420 07:01:52.660620       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0420 07:01:52.660737       1 azure_diskclient.go:67] Azure DisksClient using API version: 2021-04-01
... skipping 2455 lines ...
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 115
Expires: -1
X-Ms-Failure-Cause: service
X-Ms-Routing-Request-Id: WESTEUROPE:20220420T071916Z:3c7d6e3b-730c-4ec6-95e3-e26667274287
I0420 07:19:16.497473       1 azure_armclient.go:181] Send.sendRequest original response: {"error":{"code":"ServiceUnavailable","message":"The service is unavailable now. Please retry the request later."}}
I0420 07:19:16.497498       1 azure_armclient.go:186] Send.sendRequest: response body does not contain ResourceGroupNotFound error code. Skip retrying regional host
I0420 07:19:16.497537       1 azure_armclient.go:372] Received error in sendAsync.send: resourceID: https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-muexyd/providers/Microsoft.Storage/storageAccounts/f6fcde8fde68044c29d8b8a?api-version=2021-02-01, error: Retriable: true, RetryAfter: 0s, HTTPStatusCode: 503, RawError: {"error":{"code":"ServiceUnavailable","message":"The service is unavailable now. Please retry the request later."}}
I0420 07:19:16.497558       1 azure_armclient.go:572] Received error in put.send: resourceID: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-muexyd/providers/Microsoft.Storage/storageAccounts/f6fcde8fde68044c29d8b8a, error: Retriable: true, RetryAfter: 0s, HTTPStatusCode: 503, RawError: {"error":{"code":"ServiceUnavailable","message":"The service is unavailable now. Please retry the request later."}}
I0420 07:19:16.497593       1 azure_storageaccountclient.go:260] Received error in storageAccount.put.request: resourceID: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-muexyd/providers/Microsoft.Storage/storageAccounts/f6fcde8fde68044c29d8b8a, error: Retriable: true, RetryAfter: 0s, HTTPStatusCode: 503, RawError: {"error":{"code":"ServiceUnavailable","message":"The service is unavailable now. Please retry the request later."}}
I0420 07:19:16.497709       1 azure_metrics.go:112] "Observed Request Latency" latency_seconds=41.240930819 request="storage_account_create" resource_group="capz-muexyd" subscription_id="0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e" source="" error_code="ServiceUnavailable"
E0420 07:19:16.497811       1 utils.go:81] GRPC error: rpc error: code = Internal desc = failed to ensure storage account: failed to create storage account f6fcde8fde68044c29d8b8a, error: &{true 503 0001-01-01 00:00:00 +0000 UTC {"error":{"code":"ServiceUnavailable","message":"The service is unavailable now. Please retry the request later."}}}
I0420 07:19:17.499960       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0420 07:19:17.499983       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":10737418240},"name":"pvc-fcff0aa4-605f-4199-be4d-c23691d10822","parameters":{"createAccount":"true","csi.storage.k8s.io/pv/name":"pvc-fcff0aa4-605f-4199-be4d-c23691d10822","csi.storage.k8s.io/pvc/name":"pvc-nfktq","csi.storage.k8s.io/pvc/namespace":"azurefile-4547","disableDeleteRetentionPolicy":"true","secretNamespace":"kube-system","skuName":"Premium_LRS","useDataPlaneAPI":"true"},"volume_capabilities":[{"AccessType":{"Mount":{"mount_flags":["dir_mode=0777","file_mode=0777","uid=0","gid=0","mfsymlinks","cache=strict","nosharesock","vers=3.1.1"]}},"access_mode":{"mode":7}}]}
I0420 07:19:17.500203       1 azure_storageaccount.go:252] azure - no matching account found, begin to create a new account fc993781a2cf143dc9b9858 in resource group capz-muexyd, location: westeurope, accountType: Premium_LRS, accountKind: FileStorage, tags: map[k8s-azure-created-by:azure]
I0420 07:19:17.500230       1 azure_storageaccount.go:273] set AllowBlobPublicAccess(false) for storage account(fc993781a2cf143dc9b9858)
(2022-04-20T07:19:17.5003373Z) INFO: REQUEST: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-muexyd/providers/Microsoft.Storage/storageAccounts/fc993781a2cf143dc9b9858?api-version=2021-02-01
Authorization: **REDACTED**
... skipping 508 lines ...
Platform: windows/amd64

Streaming logs below:
I0420 07:02:56.969861    7108 azurefile.go:267] driver userAgent: file.csi.azure.com/e2e-500a03658af60fa873143a0181676422faa6f002 gc/go1.18.1 (amd64-windows) e2e-test
I0420 07:02:56.991156    7108 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0420 07:02:57.017569    7108 round_trippers.go:553] GET https://10.96.0.1:443/api/v1/namespaces/kube-system/secrets/azure-cloud-provider 404 Not Found in 20 milliseconds
W0420 07:02:57.018733    7108 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0420 07:02:57.018733    7108 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0420 07:02:57.018733    7108 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: C:\k\azure.json
I0420 07:02:57.018733    7108 azure.go:101] read cloud config from file: C:\k\azure.json successfully
I0420 07:02:57.027539    7108 azure_auth.go:245] Using AzurePublicCloud environment
I0420 07:02:57.028122    7108 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0420 07:02:57.029438    7108 azure_diskclient.go:67] Azure DisksClient using API version: 2021-04-01
... skipping 1306 lines ...
I0420 07:21:38.121687    7108 utils.go:76] GRPC call: /csi.v1.Node/NodeGetCapabilities
I0420 07:21:38.121687    7108 utils.go:77] GRPC request: {}
I0420 07:21:38.121687    7108 utils.go:83] GRPC response: {"capabilities":[{"Type":{"Rpc":{"type":1}}},{"Type":{"Rpc":{"type":5}}},{"Type":{"Rpc":{"type":6}}},{"Type":{"Rpc":{"type":2}}}]}
I0420 07:21:38.126890    7108 utils.go:76] GRPC call: /csi.v1.Node/NodePublishVolume
I0420 07:21:38.126890    7108 utils.go:77] GRPC request: {"target_path":"c:\\var\\lib\\kubelet\\pods\\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\\volumes\\kubernetes.io~csi\\test-volume-1\\mount","volume_capability":{"AccessType":{"Mount":{}},"access_mode":{"mode":7}},"volume_context":{"csi.storage.k8s.io/ephemeral":"true","csi.storage.k8s.io/pod.name":"azurefile-volume-tester-6znr2","csi.storage.k8s.io/pod.namespace":"azurefile-4801","csi.storage.k8s.io/pod.uid":"9ddb4889-88ae-4f9d-be7a-c1fd925dc77a","csi.storage.k8s.io/serviceAccount.name":"default","mountOptions":"cache=singleclient","secretName":"azure-storage-account-fe1ea328664a44cd4adcc00-secret","server":"","shareName":"csi-inline-smb-volume"},"volume_id":"csi-85d942f8f18fb534fc1d18d72f0b51c448c9cda8fd4baeeeba3c72292d06a441"}
I0420 07:21:38.126890    7108 nodeserver.go:68] NodePublishVolume: ephemeral volume(csi-85d942f8f18fb534fc1d18d72f0b51c448c9cda8fd4baeeeba3c72292d06a441) mount on c:\var\lib\kubelet\pods\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\volumes\kubernetes.io~csi\test-volume-1\mount, VolumeContext: map[csi.storage.k8s.io/ephemeral:true csi.storage.k8s.io/pod.name:azurefile-volume-tester-6znr2 csi.storage.k8s.io/pod.namespace:azurefile-4801 csi.storage.k8s.io/pod.uid:9ddb4889-88ae-4f9d-be7a-c1fd925dc77a csi.storage.k8s.io/serviceAccount.name:default getaccountkeyfromsecret:true mountOptions:cache=singleclient secretName:azure-storage-account-fe1ea328664a44cd4adcc00-secret secretnamespace:azurefile-4801 server: shareName:csi-inline-smb-volume storageaccount:]
W0420 07:21:38.126890    7108 azurefile.go:546] parsing volumeID(csi-85d942f8f18fb534fc1d18d72f0b51c448c9cda8fd4baeeeba3c72292d06a441) return with error: error parsing volume id: "csi-85d942f8f18fb534fc1d18d72f0b51c448c9cda8fd4baeeeba3c72292d06a441", should at least contain two #
I0420 07:21:38.138487    7108 round_trippers.go:553] GET https://10.96.0.1:443/api/v1/namespaces/azurefile-4801/secrets/azure-storage-account-fe1ea328664a44cd4adcc00-secret 200 OK in 10 milliseconds
I0420 07:21:38.140285    7108 nodeserver.go:268] cifsMountPath(c:\var\lib\kubelet\pods\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\volumes\kubernetes.io~csi\test-volume-1\mount) fstype() volumeID(csi-85d942f8f18fb534fc1d18d72f0b51c448c9cda8fd4baeeeba3c72292d06a441) context(map[csi.storage.k8s.io/ephemeral:true csi.storage.k8s.io/pod.name:azurefile-volume-tester-6znr2 csi.storage.k8s.io/pod.namespace:azurefile-4801 csi.storage.k8s.io/pod.uid:9ddb4889-88ae-4f9d-be7a-c1fd925dc77a csi.storage.k8s.io/serviceAccount.name:default getaccountkeyfromsecret:true mountOptions:cache=singleclient secretName:azure-storage-account-fe1ea328664a44cd4adcc00-secret secretnamespace:azurefile-4801 server: shareName:csi-inline-smb-volume storageaccount:]) mountflags([]) mountOptions([AZURE\fe1ea328664a44cd4adcc00]) volumeMountGroup()
I0420 07:21:38.140285    7108 safe_mounter_windows.go:163] IsLikelyNotMountPoint: c:\var\lib\kubelet\pods\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\volumes\kubernetes.io~csi\test-volume-1\mount
I0420 07:21:38.140285    7108 safe_mounter_windows.go:220] Exists path: c:\var\lib\kubelet\pods\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\volumes\kubernetes.io~csi\test-volume-1\mount
I0420 07:21:38.141794    7108 safe_mounter_windows.go:220] Exists path: c:\var\lib\kubelet\pods\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\volumes\kubernetes.io~csi\test-volume-1\mount
I0420 07:21:38.144295    7108 azure_common_windows.go:73] Removing path: c:\var\lib\kubelet\pods\9ddb4889-88ae-4f9d-be7a-c1fd925dc77a\volumes\kubernetes.io~csi\test-volume-1\mount
... skipping 20 lines ...
I0420 07:22:01.512873    7108 utils.go:76] GRPC call: /csi.v1.Node/NodeGetCapabilities
I0420 07:22:01.513410    7108 utils.go:77] GRPC request: {}
I0420 07:22:01.513410    7108 utils.go:83] GRPC response: {"capabilities":[{"Type":{"Rpc":{"type":1}}},{"Type":{"Rpc":{"type":5}}},{"Type":{"Rpc":{"type":6}}},{"Type":{"Rpc":{"type":2}}}]}
I0420 07:22:01.515414    7108 utils.go:76] GRPC call: /csi.v1.Node/NodePublishVolume
I0420 07:22:01.515414    7108 utils.go:77] GRPC request: {"target_path":"c:\\var\\lib\\kubelet\\pods\\45b80699-5465-450a-b88e-30b88dbb9c58\\volumes\\kubernetes.io~csi\\test-volume-1\\mount","volume_capability":{"AccessType":{"Mount":{}},"access_mode":{"mode":7}},"volume_context":{"csi.storage.k8s.io/ephemeral":"true","csi.storage.k8s.io/pod.name":"azurefile-volume-tester-4thkq","csi.storage.k8s.io/pod.namespace":"azurefile-1166","csi.storage.k8s.io/pod.uid":"45b80699-5465-450a-b88e-30b88dbb9c58","csi.storage.k8s.io/serviceAccount.name":"default","mountOptions":"cache=singleclient","secretName":"smbcreds","server":"20.123.239.190","shareName":"share"},"volume_id":"csi-715fe2a67e696afb397b0d4397118bd54cc3c0405aef1ac7a91bd625b234f594"}
I0420 07:22:01.515414    7108 nodeserver.go:68] NodePublishVolume: ephemeral volume(csi-715fe2a67e696afb397b0d4397118bd54cc3c0405aef1ac7a91bd625b234f594) mount on c:\var\lib\kubelet\pods\45b80699-5465-450a-b88e-30b88dbb9c58\volumes\kubernetes.io~csi\test-volume-1\mount, VolumeContext: map[csi.storage.k8s.io/ephemeral:true csi.storage.k8s.io/pod.name:azurefile-volume-tester-4thkq csi.storage.k8s.io/pod.namespace:azurefile-1166 csi.storage.k8s.io/pod.uid:45b80699-5465-450a-b88e-30b88dbb9c58 csi.storage.k8s.io/serviceAccount.name:default getaccountkeyfromsecret:true mountOptions:cache=singleclient secretName:smbcreds secretnamespace:azurefile-1166 server:20.123.239.190 shareName:share storageaccount:]
W0420 07:22:01.516031    7108 azurefile.go:546] parsing volumeID(csi-715fe2a67e696afb397b0d4397118bd54cc3c0405aef1ac7a91bd625b234f594) return with error: error parsing volume id: "csi-715fe2a67e696afb397b0d4397118bd54cc3c0405aef1ac7a91bd625b234f594", should at least contain two #
I0420 07:22:01.520510    7108 round_trippers.go:553] GET https://10.96.0.1:443/api/v1/namespaces/azurefile-1166/secrets/smbcreds 200 OK in 4 milliseconds
I0420 07:22:01.520758    7108 nodeserver.go:268] cifsMountPath(c:\var\lib\kubelet\pods\45b80699-5465-450a-b88e-30b88dbb9c58\volumes\kubernetes.io~csi\test-volume-1\mount) fstype() volumeID(csi-715fe2a67e696afb397b0d4397118bd54cc3c0405aef1ac7a91bd625b234f594) context(map[csi.storage.k8s.io/ephemeral:true csi.storage.k8s.io/pod.name:azurefile-volume-tester-4thkq csi.storage.k8s.io/pod.namespace:azurefile-1166 csi.storage.k8s.io/pod.uid:45b80699-5465-450a-b88e-30b88dbb9c58 csi.storage.k8s.io/serviceAccount.name:default getaccountkeyfromsecret:true mountOptions:cache=singleclient secretName:smbcreds secretnamespace:azurefile-1166 server:20.123.239.190 shareName:share storageaccount:]) mountflags([]) mountOptions([AZURE\USERNAME]) volumeMountGroup()
I0420 07:22:01.520816    7108 safe_mounter_windows.go:163] IsLikelyNotMountPoint: c:\var\lib\kubelet\pods\45b80699-5465-450a-b88e-30b88dbb9c58\volumes\kubernetes.io~csi\test-volume-1\mount
I0420 07:22:01.520816    7108 safe_mounter_windows.go:220] Exists path: c:\var\lib\kubelet\pods\45b80699-5465-450a-b88e-30b88dbb9c58\volumes\kubernetes.io~csi\test-volume-1\mount
I0420 07:22:01.522659    7108 safe_mounter_windows.go:220] Exists path: c:\var\lib\kubelet\pods\45b80699-5465-450a-b88e-30b88dbb9c58\volumes\kubernetes.io~csi\test-volume-1\mount
I0420 07:22:01.523216    7108 azure_common_windows.go:73] Removing path: c:\var\lib\kubelet\pods\45b80699-5465-450a-b88e-30b88dbb9c58\volumes\kubernetes.io~csi\test-volume-1\mount
... skipping 23 lines ...
I0420 07:22:53.554743    7108 utils.go:76] GRPC call: /csi.v1.Node/NodeGetCapabilities
I0420 07:22:53.554743    7108 utils.go:77] GRPC request: {}
I0420 07:22:53.554743    7108 utils.go:83] GRPC response: {"capabilities":[{"Type":{"Rpc":{"type":1}}},{"Type":{"Rpc":{"type":5}}},{"Type":{"Rpc":{"type":6}}},{"Type":{"Rpc":{"type":2}}}]}
I0420 07:22:53.555992    7108 utils.go:76] GRPC call: /csi.v1.Node/NodeStageVolume
I0420 07:22:53.555992    7108 utils.go:77] GRPC request: {"staging_target_path":"\\var\\lib\\kubelet\\plugins\\kubernetes.io\\csi\\pv\\azurefile-5320-file.csi.azure.com-preprovsioned-pv-h77mk\\globalmount","volume_capability":{"AccessType":{"Mount":{}},"access_mode":{"mode":7}},"volume_id":"capz-muexyd#f0b938293318c485d9e53db#pre-provisioned-readonly##pre-provisioned-readonly"}
I0420 07:22:53.561036    7108 round_trippers.go:553] GET https://10.96.0.1:443/api/v1/namespaces/default/secrets/azure-storage-account-f0b938293318c485d9e53db-secret 404 Not Found in 4 milliseconds
I0420 07:22:53.561036    7108 azurefile.go:616] could not get account(f0b938293318c485d9e53db) key from secret(azure-storage-account-f0b938293318c485d9e53db-secret), error: could not get secret(azure-storage-account-f0b938293318c485d9e53db-secret): secrets "azure-storage-account-f0b938293318c485d9e53db-secret" not found, use cluster identity to get account key instead
(2022-04-20T07:22:53.5627182Z) INFO: REQUEST: POST https://login.microsoftonline.com/097f89a0-9286-43d2-9a1a-08f1d49b1af8/oauth2/token
User-Agent: Go/go1.18.1 (amd64-windows) go-autorest/adal/v1.0.0
Content-Type: application/x-www-form-urlencoded
(2022-04-20T07:22:53.8655049Z) INFO: RESPONSE: 200 https://login.microsoftonline.com/097f89a0-9286-43d2-9a1a-08f1d49b1af8/oauth2/token
Expires: -1
Strict-Transport-Security: max-age=31536000; includeSubDomains
... skipping 706 lines ...
Platform: windows/amd64

Streaming logs below:
I0420 07:02:58.388731    6548 azurefile.go:267] driver userAgent: file.csi.azure.com/e2e-500a03658af60fa873143a0181676422faa6f002 gc/go1.18.1 (amd64-windows) e2e-test
I0420 07:02:58.407230    6548 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0420 07:02:58.432626    6548 round_trippers.go:553] GET https://10.96.0.1:443/api/v1/namespaces/kube-system/secrets/azure-cloud-provider 404 Not Found in 23 milliseconds
W0420 07:02:58.433515    6548 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0420 07:02:58.433515    6548 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0420 07:02:58.433515    6548 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: C:\k\azure.json
I0420 07:02:58.433515    6548 azure.go:101] read cloud config from file: C:\k\azure.json successfully
I0420 07:02:58.439828    6548 azure_auth.go:245] Using AzurePublicCloud environment
I0420 07:02:58.441758    6548 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0420 07:02:58.448775    6548 azure_diskclient.go:67] Azure DisksClient using API version: 2021-04-01
... skipping 590 lines ...

JUnit report was created: /logs/artifacts/junit_01.xml


Summarizing 1 Failure:

[Fail] Dynamic Provisioning [It] should create a volume on demand with mount options [kubernetes.io/azure-file] [file.csi.azure.com] [Windows] 
/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver/test/e2e/testsuites/testsuites.go:691

Ran 20 of 34 Specs in 2264.869 seconds
FAIL! -- 19 Passed | 1 Failed | 0 Pending | 14 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 5 lines ...
  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- FAIL: TestE2E (2264.88s)
FAIL
FAIL	sigs.k8s.io/azurefile-csi-driver/test/e2e	2264.932s
FAIL
make: *** [Makefile:85: e2e-test] Error 1
make: Nothing to be done for 'kubectl'.
================ DUMPING LOGS FOR MANAGEMENT CLUSTER ================
Exported logs for cluster "capz" to:
/logs/artifacts/management-cluster
================ DUMPING LOGS FOR WORKLOAD CLUSTER (Linux) ==========
Deploying log-dump-daemonset
... skipping 104 lines ...