This job view page is being replaced by Spyglass soon. Check out the new job view.
PRcvvz: feat: support cross subscription with management api
Resultsuccess
Tests 0 failed / 14 succeeded
Started2022-09-08 09:04
Elapsed33m10s
Revision
Refs 1077
uploadercrier

No Test Failures!


Show 14 Passed Tests

Error lines from build-log.txt

... skipping 232 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   178k      0 --:--:-- --:--:-- --:--:--  178k
Downloading https://get.helm.sh/helm-v3.9.4-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azurefile-csi:e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a not found: manifest unknown: manifest tagged by "e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a" 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-de8bd9dbb158d2b06fd4d580693b51f81522d37a -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=de8bd9dbb158d2b06fd4d580693b51f81522d37a -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-09-08T09:08:31Z -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 1854 lines ...
                    type: string
                type: object
                oneOf:
                - required: ["persistentVolumeClaimName"]
                - required: ["volumeSnapshotContentName"]
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown.
                format: date-time
                type: string
              error:
                description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown.
                pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                x-kubernetes-int-or-string: true
            type: object
        required:
        - spec
        type: object
... skipping 60 lines ...
                    type: string
                  volumeSnapshotContentName:
                    description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable.
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown.
                format: date-time
                type: string
              error:
                description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown.
                pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                x-kubernetes-int-or-string: true
            type: object
        required:
        - spec
        type: object
... skipping 254 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC.
                format: int64
                type: integer
              error:
                description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown.
                format: int64
                minimum: 0
                type: integer
              snapshotHandle:
                description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress.
                type: string
            type: object
        required:
        - spec
        type: object
    served: true
... skipping 108 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC.
                format: int64
                type: integer
              error:
                description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown.
                format: int64
                minimum: 0
                type: integer
              snapshotHandle:
                description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress.
                type: string
            type: object
        required:
        - spec
        type: object
    served: true
... skipping 937 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.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 249 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:242

    Driver test.csi.azure.com doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 121 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:269

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 383 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should not mount / map unused volumes in a pod [LinuxOnly]
    test/e2e/storage/testsuites/volumemode.go:354
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":27,"completed":1,"skipped":16,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:09.202: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 201 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    Verify if offline PVC expansion works
    test/e2e/storage/testsuites/volume_expand.go:176
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":45,"completed":1,"skipped":370,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:13.118: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 217 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents","total":29,"completed":1,"skipped":32,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:16.739: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 37 lines ...
Sep  8 09:23:10.299: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:23:10.404: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comgrg2f] to have phase Bound
Sep  8 09:23:10.506: INFO: PersistentVolumeClaim test.csi.azure.comgrg2f found but phase is Pending instead of Bound.
Sep  8 09:23:12.609: INFO: PersistentVolumeClaim test.csi.azure.comgrg2f found and phase=Bound (2.20532975s)
STEP: Creating pod exec-volume-test-dynamicpv-4g8c
STEP: Creating a pod to test exec-volume-test
Sep  8 09:23:12.917: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-4g8c" in namespace "volume-6053" to be "Succeeded or Failed"
Sep  8 09:23:13.020: INFO: Pod "exec-volume-test-dynamicpv-4g8c": Phase="Pending", Reason="", readiness=false. Elapsed: 103.033386ms
Sep  8 09:23:15.124: INFO: Pod "exec-volume-test-dynamicpv-4g8c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206453375s
Sep  8 09:23:17.227: INFO: Pod "exec-volume-test-dynamicpv-4g8c": Phase="Running", Reason="", readiness=false. Elapsed: 4.30987243s
Sep  8 09:23:19.330: INFO: Pod "exec-volume-test-dynamicpv-4g8c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.412439161s
STEP: Saw pod success
Sep  8 09:23:19.330: INFO: Pod "exec-volume-test-dynamicpv-4g8c" satisfied condition "Succeeded or Failed"
Sep  8 09:23:19.432: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000000 pod exec-volume-test-dynamicpv-4g8c container exec-container-dynamicpv-4g8c: <nil>
STEP: delete the pod
Sep  8 09:23:19.650: INFO: Waiting for pod exec-volume-test-dynamicpv-4g8c to disappear
Sep  8 09:23:19.752: INFO: Pod exec-volume-test-dynamicpv-4g8c no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-4g8c
Sep  8 09:23:19.752: INFO: Deleting pod "exec-volume-test-dynamicpv-4g8c" in namespace "volume-6053"
... skipping 14 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:50
    should allow exec of files on the volume
    test/e2e/storage/testsuites/volumes.go:198
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume","total":27,"completed":2,"skipped":355,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral 
  should create read/write inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:196
... skipping 41 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read/write inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read/write inline ephemeral volume","total":38,"completed":1,"skipped":78,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:37.354: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 250 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with the same volume mode and retain data across pod recreation on different node
    test/e2e/storage/testsuites/multivolume.go:168
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node","total":37,"completed":1,"skipped":15,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:38.281: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 144 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/storage/framework/testsuite.go:50
    should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
    test/e2e/storage/testsuites/topology.go:194

    Driver "test.csi.azure.com" does not support topology - skipping

    test/e2e/storage/testsuites/topology.go:93
------------------------------
... skipping 79 lines ...

    test/e2e/storage/testsuites/volumes.go:114
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] volumeMode 
  should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
  test/e2e/storage/testsuites/volumemode.go:260

[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:23:39.576: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
  test/e2e/storage/testsuites/volumemode.go:260
STEP: Creating sc
STEP: Creating pv and pvc
STEP: Deleting pvc
Sep  8 09:23:40.799: INFO: Deleting PersistentVolumeClaim "pvc-mmjnx"
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  8 09:23:41.005: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-9257" for this suite.

•
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] volumeMode should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]","total":37,"completed":2,"skipped":497,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:269

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:23:25.607: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:269
Sep  8 09:23:26.323: INFO: Creating resource for dynamic PV
Sep  8 09:23:26.323: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8070-e2e-scdnfgg
STEP: creating a claim
Sep  8 09:23:26.427: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:23:26.531: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comp6bhb] to have phase Bound
Sep  8 09:23:26.633: INFO: PersistentVolumeClaim test.csi.azure.comp6bhb found but phase is Pending instead of Bound.
Sep  8 09:23:28.736: INFO: PersistentVolumeClaim test.csi.azure.comp6bhb found and phase=Bound (2.205240903s)
STEP: Creating pod pod-subpath-test-dynamicpv-lvwv
STEP: Checking for subpath error in container status
Sep  8 09:23:33.252: INFO: Deleting pod "pod-subpath-test-dynamicpv-lvwv" in namespace "provisioning-8070"
Sep  8 09:23:33.356: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-lvwv" to be fully deleted
STEP: Deleting pod
Sep  8 09:23:35.561: INFO: Deleting pod "pod-subpath-test-dynamicpv-lvwv" in namespace "provisioning-8070"
STEP: Deleting pvc
Sep  8 09:23:35.664: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comp6bhb"
... skipping 9 lines ...

• [SLOW TEST:15.782 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:269
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]","total":27,"completed":3,"skipped":378,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:41.408: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 135 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents","total":29,"completed":2,"skipped":60,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:23:44.765: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 54 lines ...
Sep  8 09:23:42.046: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:23:42.150: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5xgfs] to have phase Bound
Sep  8 09:23:42.252: INFO: PersistentVolumeClaim test.csi.azure.com5xgfs found but phase is Pending instead of Bound.
Sep  8 09:23:44.355: INFO: PersistentVolumeClaim test.csi.azure.com5xgfs found and phase=Bound (2.20502101s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 09:23:44.762: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6d2x8" in namespace "snapshotting-212" to be "Succeeded or Failed"
Sep  8 09:23:44.864: INFO: Pod "pvc-snapshottable-tester-6d2x8": Phase="Pending", Reason="", readiness=false. Elapsed: 101.930601ms
Sep  8 09:23:46.968: INFO: Pod "pvc-snapshottable-tester-6d2x8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205137402s
Sep  8 09:23:49.070: INFO: Pod "pvc-snapshottable-tester-6d2x8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.307675728s
STEP: Saw pod success
Sep  8 09:23:49.070: INFO: Pod "pvc-snapshottable-tester-6d2x8" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 09:23:49.172: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5xgfs] to have phase Bound
Sep  8 09:23:49.273: INFO: PersistentVolumeClaim test.csi.azure.com5xgfs found and phase=Bound (101.385876ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 09:23:49.583: INFO: Pod pvc-snapshottable-tester-6d2x8 has the following logs: 
... skipping 67 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:242

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 225 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with the same volume mode and retain data across pod recreation on the same node
    test/e2e/storage/testsuites/multivolume.go:138
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node","total":45,"completed":2,"skipped":458,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral 
  should support two pods which have the same volume definition
  test/e2e/storage/testsuites/ephemeral.go:216
... skipping 52 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition","total":31,"completed":1,"skipped":11,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:24:11.993: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299
Sep  8 09:24:12.705: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  8 09:24:12.706: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3178" for this suite.


S [SKIPPING] [0.919 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow] [Measurement]
    test/e2e/storage/testsuites/volumemode.go:299

    Driver "test.csi.azure.com" does not provide raw block - skipping

    test/e2e/storage/testsuites/volumes.go:114
------------------------------
... skipping 57 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition","total":34,"completed":1,"skipped":21,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:15.507: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 3 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow] [BeforeEach]
    test/e2e/storage/testsuites/volumemode.go:299

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 21 lines ...
Sep  8 09:23:56.590: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:23:56.694: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxfm9m] to have phase Bound
Sep  8 09:23:56.796: INFO: PersistentVolumeClaim test.csi.azure.comxfm9m found but phase is Pending instead of Bound.
Sep  8 09:23:58.898: INFO: PersistentVolumeClaim test.csi.azure.comxfm9m found and phase=Bound (2.204429211s)
STEP: Creating pod pod-subpath-test-dynamicpv-qvh6
STEP: Creating a pod to test subpath
Sep  8 09:23:59.206: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qvh6" in namespace "provisioning-8705" to be "Succeeded or Failed"
Sep  8 09:23:59.310: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 104.507378ms
Sep  8 09:24:01.414: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208099852s
Sep  8 09:24:03.522: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31639461s
Sep  8 09:24:05.625: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.419661362s
Sep  8 09:24:07.728: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.522541286s
Sep  8 09:24:09.831: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.624863567s
STEP: Saw pod success
Sep  8 09:24:09.831: INFO: Pod "pod-subpath-test-dynamicpv-qvh6" satisfied condition "Succeeded or Failed"
Sep  8 09:24:09.933: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000001 pod pod-subpath-test-dynamicpv-qvh6 container test-container-subpath-dynamicpv-qvh6: <nil>
STEP: delete the pod
Sep  8 09:24:10.144: INFO: Waiting for pod pod-subpath-test-dynamicpv-qvh6 to disappear
Sep  8 09:24:10.246: INFO: Pod pod-subpath-test-dynamicpv-qvh6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qvh6
Sep  8 09:24:10.246: INFO: Deleting pod "pod-subpath-test-dynamicpv-qvh6" in namespace "provisioning-8705"
STEP: Creating pod pod-subpath-test-dynamicpv-qvh6
STEP: Creating a pod to test subpath
Sep  8 09:24:10.455: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qvh6" in namespace "provisioning-8705" to be "Succeeded or Failed"
Sep  8 09:24:10.557: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 101.858832ms
Sep  8 09:24:12.660: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204535662s
Sep  8 09:24:14.763: INFO: Pod "pod-subpath-test-dynamicpv-qvh6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.307352933s
STEP: Saw pod success
Sep  8 09:24:14.763: INFO: Pod "pod-subpath-test-dynamicpv-qvh6" satisfied condition "Succeeded or Failed"
Sep  8 09:24:14.865: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000001 pod pod-subpath-test-dynamicpv-qvh6 container test-container-subpath-dynamicpv-qvh6: <nil>
STEP: delete the pod
Sep  8 09:24:15.075: INFO: Waiting for pod pod-subpath-test-dynamicpv-qvh6 to disappear
Sep  8 09:24:15.177: INFO: Pod pod-subpath-test-dynamicpv-qvh6 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qvh6
Sep  8 09:24:15.177: INFO: Deleting pod "pod-subpath-test-dynamicpv-qvh6" in namespace "provisioning-8705"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing directories when readOnly specified in the volumeSource
    test/e2e/storage/testsuites/subpath.go:397
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":37,"completed":3,"skipped":686,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
... skipping 23 lines ...

    test/e2e/storage/testsuites/volumelimits.go:130
------------------------------
SSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:242

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:24:04.686: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:242
Sep  8 09:24:05.421: INFO: Creating resource for dynamic PV
Sep  8 09:24:05.421: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-295-e2e-scwg6vg
STEP: creating a claim
Sep  8 09:24:05.525: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:05.630: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comnccqj] to have phase Bound
Sep  8 09:24:05.734: INFO: PersistentVolumeClaim test.csi.azure.comnccqj found but phase is Pending instead of Bound.
Sep  8 09:24:07.839: INFO: PersistentVolumeClaim test.csi.azure.comnccqj found and phase=Bound (2.208479065s)
STEP: Creating pod pod-subpath-test-dynamicpv-2w7n
STEP: Checking for subpath error in container status
Sep  8 09:24:14.360: INFO: Deleting pod "pod-subpath-test-dynamicpv-2w7n" in namespace "provisioning-295"
Sep  8 09:24:14.465: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2w7n" to be fully deleted
STEP: Deleting pod
Sep  8 09:24:16.675: INFO: Deleting pod "pod-subpath-test-dynamicpv-2w7n" in namespace "provisioning-295"
STEP: Deleting pvc
Sep  8 09:24:16.778: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comnccqj"
... skipping 9 lines ...

• [SLOW TEST:17.828 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:242
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]","total":45,"completed":3,"skipped":489,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:22.531: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 3 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow] [BeforeEach]
    test/e2e/storage/testsuites/volumemode.go:299

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 176 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:242

    Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 122 lines ...
Sep  8 09:24:13.736: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:13.839: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comc6cms] to have phase Bound
Sep  8 09:24:13.941: INFO: PersistentVolumeClaim test.csi.azure.comc6cms found but phase is Pending instead of Bound.
Sep  8 09:24:16.044: INFO: PersistentVolumeClaim test.csi.azure.comc6cms found and phase=Bound (2.205169858s)
STEP: Creating pod pod-subpath-test-dynamicpv-5mp8
STEP: Creating a pod to test subpath
Sep  8 09:24:16.356: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-5mp8" in namespace "provisioning-227" to be "Succeeded or Failed"
Sep  8 09:24:16.458: INFO: Pod "pod-subpath-test-dynamicpv-5mp8": Phase="Pending", Reason="", readiness=false. Elapsed: 102.354289ms
Sep  8 09:24:18.561: INFO: Pod "pod-subpath-test-dynamicpv-5mp8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205496088s
Sep  8 09:24:20.676: INFO: Pod "pod-subpath-test-dynamicpv-5mp8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.320416399s
Sep  8 09:24:22.779: INFO: Pod "pod-subpath-test-dynamicpv-5mp8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.42325986s
STEP: Saw pod success
Sep  8 09:24:22.779: INFO: Pod "pod-subpath-test-dynamicpv-5mp8" satisfied condition "Succeeded or Failed"
Sep  8 09:24:22.881: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000000 pod pod-subpath-test-dynamicpv-5mp8 container test-container-subpath-dynamicpv-5mp8: <nil>
STEP: delete the pod
Sep  8 09:24:23.095: INFO: Waiting for pod pod-subpath-test-dynamicpv-5mp8 to disappear
Sep  8 09:24:23.197: INFO: Pod pod-subpath-test-dynamicpv-5mp8 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-5mp8
Sep  8 09:24:23.197: INFO: Deleting pod "pod-subpath-test-dynamicpv-5mp8" in namespace "provisioning-227"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly file specified in the volumeMount [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:382
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":31,"completed":2,"skipped":44,"failed":0}

SSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:29.138: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 3 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:269

    Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 5 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:24:29.201: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299
Sep  8 09:24:29.915: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  8 09:24:29.916: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6177" for this suite.


S [SKIPPING] [0.920 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should fail to use a volume in a pod with mismatched mode [Slow] [Measurement]
    test/e2e/storage/testsuites/volumemode.go:299

    Driver "test.csi.azure.com" does not provide raw block - skipping

    test/e2e/storage/testsuites/volumes.go:114
------------------------------
... skipping 63 lines ...
Sep  8 09:24:16.375: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:16.478: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com9zw6j] to have phase Bound
Sep  8 09:24:16.581: INFO: PersistentVolumeClaim test.csi.azure.com9zw6j found but phase is Pending instead of Bound.
Sep  8 09:24:18.685: INFO: PersistentVolumeClaim test.csi.azure.com9zw6j found and phase=Bound (2.206597201s)
STEP: Creating pod pod-subpath-test-dynamicpv-nt5f
STEP: Creating a pod to test subpath
Sep  8 09:24:19.004: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-nt5f" in namespace "provisioning-9436" to be "Succeeded or Failed"
Sep  8 09:24:19.107: INFO: Pod "pod-subpath-test-dynamicpv-nt5f": Phase="Pending", Reason="", readiness=false. Elapsed: 102.843392ms
Sep  8 09:24:21.214: INFO: Pod "pod-subpath-test-dynamicpv-nt5f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209178414s
Sep  8 09:24:23.317: INFO: Pod "pod-subpath-test-dynamicpv-nt5f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312175478s
Sep  8 09:24:25.421: INFO: Pod "pod-subpath-test-dynamicpv-nt5f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.415969116s
STEP: Saw pod success
Sep  8 09:24:25.421: INFO: Pod "pod-subpath-test-dynamicpv-nt5f" satisfied condition "Succeeded or Failed"
Sep  8 09:24:25.523: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000001 pod pod-subpath-test-dynamicpv-nt5f container test-container-subpath-dynamicpv-nt5f: <nil>
STEP: delete the pod
Sep  8 09:24:25.735: INFO: Waiting for pod pod-subpath-test-dynamicpv-nt5f to disappear
Sep  8 09:24:25.837: INFO: Pod pod-subpath-test-dynamicpv-nt5f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-nt5f
Sep  8 09:24:25.837: INFO: Deleting pod "pod-subpath-test-dynamicpv-nt5f" in namespace "provisioning-9436"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly directory specified in the volumeMount
    test/e2e/storage/testsuites/subpath.go:367
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":34,"completed":2,"skipped":153,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:31.772: INFO: Driver "test.csi.azure.com" does not support topology - skipping
... skipping 3 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/framework/testsuite.go:50
    should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
    test/e2e/storage/testsuites/topology.go:194

    Driver "test.csi.azure.com" does not support topology - skipping

    test/e2e/storage/testsuites/topology.go:93
------------------------------
... skipping 163 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single volume from pods on different node
    test/e2e/storage/testsuites/multivolume.go:451
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node","total":27,"completed":4,"skipped":404,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral 
  should create read/write inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:196
... skipping 39 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read/write inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume","total":29,"completed":3,"skipped":290,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:33.923: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should fail to create pod by failing to mount volume [Slow] [BeforeEach]
    test/e2e/storage/testsuites/volumemode.go:199

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 8 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:280

    Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 343 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should be able to unmount after the subpath directory is deleted [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:447
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":37,"completed":4,"skipped":719,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:39.963: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 27 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  8 09:24:37.173: INFO: Creating resource for dynamic PV
Sep  8 09:24:37.173: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-2151-e2e-scgxm2k
STEP: [init] starting a pod to use the claim
Sep  8 09:24:37.382: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-snvxb" in namespace "snapshotting-2151" to be "Succeeded or Failed"
Sep  8 09:24:37.483: INFO: Pod "pvc-snapshottable-tester-snvxb": Phase="Pending", Reason="", readiness=false. Elapsed: 101.483466ms
Sep  8 09:24:39.586: INFO: Pod "pvc-snapshottable-tester-snvxb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204336263s
Sep  8 09:24:41.689: INFO: Pod "pvc-snapshottable-tester-snvxb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.306893044s
Sep  8 09:24:43.802: INFO: Pod "pvc-snapshottable-tester-snvxb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.419920183s
STEP: Saw pod success
Sep  8 09:24:43.802: INFO: Pod "pvc-snapshottable-tester-snvxb" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  8 09:24:43.904: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  8 09:24:43.904: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-snvxb-my-volume] to have phase Bound
Sep  8 09:24:44.006: INFO: PersistentVolumeClaim pvc-snapshottable-tester-snvxb-my-volume found and phase=Bound (101.733467ms)
STEP: [init] checking the PV
... skipping 101 lines ...
STEP: creating a claim
Sep  8 09:24:31.053: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:31.157: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.commjk7r] to have phase Bound
Sep  8 09:24:31.259: INFO: PersistentVolumeClaim test.csi.azure.commjk7r found but phase is Pending instead of Bound.
Sep  8 09:24:33.361: INFO: PersistentVolumeClaim test.csi.azure.commjk7r found and phase=Bound (2.203971816s)
STEP: Creating pod to format volume volume-prep-provisioning-7010
Sep  8 09:24:33.670: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-7010" in namespace "provisioning-7010" to be "Succeeded or Failed"
Sep  8 09:24:33.771: INFO: Pod "volume-prep-provisioning-7010": Phase="Pending", Reason="", readiness=false. Elapsed: 101.786506ms
Sep  8 09:24:35.879: INFO: Pod "volume-prep-provisioning-7010": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209540603s
Sep  8 09:24:37.981: INFO: Pod "volume-prep-provisioning-7010": Phase="Pending", Reason="", readiness=false. Elapsed: 4.31182344s
Sep  8 09:24:40.087: INFO: Pod "volume-prep-provisioning-7010": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.417621075s
STEP: Saw pod success
Sep  8 09:24:40.087: INFO: Pod "volume-prep-provisioning-7010" satisfied condition "Succeeded or Failed"
Sep  8 09:24:40.087: INFO: Deleting pod "volume-prep-provisioning-7010" in namespace "provisioning-7010"
Sep  8 09:24:40.196: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-7010" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-vhlw
STEP: Checking for subpath error in container status
Sep  8 09:24:42.604: INFO: Deleting pod "pod-subpath-test-dynamicpv-vhlw" in namespace "provisioning-7010"
Sep  8 09:24:42.707: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vhlw" to be fully deleted
STEP: Deleting pod
Sep  8 09:24:46.911: INFO: Deleting pod "pod-subpath-test-dynamicpv-vhlw" in namespace "provisioning-7010"
STEP: Deleting pvc
Sep  8 09:24:47.013: INFO: Deleting PersistentVolumeClaim "test.csi.azure.commjk7r"
... skipping 12 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should verify container cannot write to subpath readonly volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:425
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]","total":31,"completed":3,"skipped":237,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:52.752: INFO: Driver test.csi.azure.com doesn't support ext3 -- skipping
... skipping 188 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents","total":27,"completed":5,"skipped":451,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:24:56.343: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 87 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:280

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 18 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:280

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:24:45.977: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:280
Sep  8 09:24:46.688: INFO: Creating resource for dynamic PV
Sep  8 09:24:46.688: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9898-e2e-scpvs27
STEP: creating a claim
Sep  8 09:24:46.791: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:46.894: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comtv9pd] to have phase Bound
Sep  8 09:24:46.996: INFO: PersistentVolumeClaim test.csi.azure.comtv9pd found but phase is Pending instead of Bound.
Sep  8 09:24:49.099: INFO: PersistentVolumeClaim test.csi.azure.comtv9pd found and phase=Bound (2.204354264s)
STEP: Creating pod pod-subpath-test-dynamicpv-xqqv
STEP: Checking for subpath error in container status
Sep  8 09:24:53.610: INFO: Deleting pod "pod-subpath-test-dynamicpv-xqqv" in namespace "provisioning-9898"
Sep  8 09:24:53.713: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-xqqv" to be fully deleted
STEP: Deleting pod
Sep  8 09:24:55.917: INFO: Deleting pod "pod-subpath-test-dynamicpv-xqqv" in namespace "provisioning-9898"
STEP: Deleting pvc
Sep  8 09:24:56.019: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comtv9pd"
... skipping 9 lines ...

• [SLOW TEST:15.757 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:280
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]","total":29,"completed":4,"skipped":926,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:25:01.791: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:280

    Driver test.csi.azure.com doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 175 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single volume from pods on the same node
    test/e2e/storage/testsuites/multivolume.go:298
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node","total":45,"completed":4,"skipped":762,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:25:02.127: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 253 lines ...
Sep  8 09:24:53.671: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:53.774: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comsk4n7] to have phase Bound
Sep  8 09:24:53.876: INFO: PersistentVolumeClaim test.csi.azure.comsk4n7 found but phase is Pending instead of Bound.
Sep  8 09:24:55.979: INFO: PersistentVolumeClaim test.csi.azure.comsk4n7 found and phase=Bound (2.204958255s)
STEP: Creating pod pod-subpath-test-dynamicpv-65x2
STEP: Creating a pod to test subpath
Sep  8 09:24:56.289: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-65x2" in namespace "provisioning-1786" to be "Succeeded or Failed"
Sep  8 09:24:56.396: INFO: Pod "pod-subpath-test-dynamicpv-65x2": Phase="Pending", Reason="", readiness=false. Elapsed: 107.487504ms
Sep  8 09:24:58.500: INFO: Pod "pod-subpath-test-dynamicpv-65x2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211017675s
Sep  8 09:25:00.603: INFO: Pod "pod-subpath-test-dynamicpv-65x2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.314031855s
Sep  8 09:25:02.705: INFO: Pod "pod-subpath-test-dynamicpv-65x2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.416471648s
STEP: Saw pod success
Sep  8 09:25:02.705: INFO: Pod "pod-subpath-test-dynamicpv-65x2" satisfied condition "Succeeded or Failed"
Sep  8 09:25:02.808: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000000 pod pod-subpath-test-dynamicpv-65x2 container test-container-subpath-dynamicpv-65x2: <nil>
STEP: delete the pod
Sep  8 09:25:03.019: INFO: Waiting for pod pod-subpath-test-dynamicpv-65x2 to disappear
Sep  8 09:25:03.120: INFO: Pod pod-subpath-test-dynamicpv-65x2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-65x2
Sep  8 09:25:03.120: INFO: Deleting pod "pod-subpath-test-dynamicpv-65x2" in namespace "provisioning-1786"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing single file [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:221
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]","total":31,"completed":4,"skipped":354,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:25:09.103: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:258

    Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 189 lines ...
Sep  8 09:24:32.626: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:24:32.730: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com9pb6p] to have phase Bound
Sep  8 09:24:32.832: INFO: PersistentVolumeClaim test.csi.azure.com9pb6p found but phase is Pending instead of Bound.
Sep  8 09:24:34.936: INFO: PersistentVolumeClaim test.csi.azure.com9pb6p found and phase=Bound (2.205447468s)
STEP: Expanding non-expandable pvc
Sep  8 09:24:35.142: INFO: currentPvcSize {{5368709120 0} {<nil>} 5Gi BinarySI}, newSize {{6442450944 0} {<nil>}  BinarySI}
Sep  8 09:24:35.347: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:37.556: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:39.559: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:41.555: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:43.555: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:45.557: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:47.556: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:49.556: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:51.557: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:53.555: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:55.557: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:57.555: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:24:59.557: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:25:01.555: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:25:03.558: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:25:05.561: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 09:25:05.769: INFO: Error updating pvc test.csi.azure.com9pb6p: persistentvolumeclaims "test.csi.azure.com9pb6p" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Sep  8 09:25:05.769: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com9pb6p"
Sep  8 09:25:05.873: INFO: Waiting up to 5m0s for PersistentVolume pvc-40693811-bf8c-48f7-bfc1-9f12a1cdafdd to get deleted
Sep  8 09:25:05.976: INFO: PersistentVolume pvc-40693811-bf8c-48f7-bfc1-9f12a1cdafdd found and phase=Released (103.080474ms)
Sep  8 09:25:11.082: INFO: PersistentVolume pvc-40693811-bf8c-48f7-bfc1-9f12a1cdafdd was removed
STEP: Deleting sc
... skipping 8 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should not allow expansion of pvcs without AllowVolumeExpansion property
    test/e2e/storage/testsuites/volume_expand.go:159
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property","total":34,"completed":3,"skipped":201,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:25:11.558: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 98 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support multiple inline ephemeral volumes
    test/e2e/storage/testsuites/ephemeral.go:254
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support multiple inline ephemeral volumes","total":37,"completed":5,"skipped":767,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support restarting containers using file as subpath [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:333
... skipping 57 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support restarting containers using file as subpath [Slow][LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:333
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]","total":38,"completed":2,"skipped":207,"failed":0}

SSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral 
  should create read-only inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:175
... skipping 38 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read-only inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:175
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read-only inline ephemeral volume","total":27,"completed":6,"skipped":769,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:25:36.427: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:269

    Driver test.csi.azure.com doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 19 lines ...
Sep  8 09:25:22.131: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:25:22.236: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comk7pcr] to have phase Bound
Sep  8 09:25:22.338: INFO: PersistentVolumeClaim test.csi.azure.comk7pcr found but phase is Pending instead of Bound.
Sep  8 09:25:24.440: INFO: PersistentVolumeClaim test.csi.azure.comk7pcr found and phase=Bound (2.204224507s)
STEP: Creating pod pod-subpath-test-dynamicpv-8svt
STEP: Creating a pod to test multi_subpath
Sep  8 09:25:24.748: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8svt" in namespace "provisioning-2935" to be "Succeeded or Failed"
Sep  8 09:25:24.850: INFO: Pod "pod-subpath-test-dynamicpv-8svt": Phase="Pending", Reason="", readiness=false. Elapsed: 102.114777ms
Sep  8 09:25:26.953: INFO: Pod "pod-subpath-test-dynamicpv-8svt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205658893s
Sep  8 09:25:29.058: INFO: Pod "pod-subpath-test-dynamicpv-8svt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309844768s
Sep  8 09:25:31.163: INFO: Pod "pod-subpath-test-dynamicpv-8svt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.415441498s
STEP: Saw pod success
Sep  8 09:25:31.163: INFO: Pod "pod-subpath-test-dynamicpv-8svt" satisfied condition "Succeeded or Failed"
Sep  8 09:25:31.265: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000001 pod pod-subpath-test-dynamicpv-8svt container test-container-subpath-dynamicpv-8svt: <nil>
STEP: delete the pod
Sep  8 09:25:31.478: INFO: Waiting for pod pod-subpath-test-dynamicpv-8svt to disappear
Sep  8 09:25:31.580: INFO: Pod pod-subpath-test-dynamicpv-8svt no longer exists
STEP: Deleting pod
Sep  8 09:25:31.580: INFO: Deleting pod "pod-subpath-test-dynamicpv-8svt" in namespace "provisioning-2935"
... skipping 14 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support creating multiple subpath from same volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:296
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]","total":37,"completed":6,"skipped":817,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy 
  (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
  test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
... skipping 105 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents","total":31,"completed":5,"skipped":829,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:25:40.343: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 130 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:258

    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 27 lines ...
Sep  8 09:25:37.275: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:25:37.379: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com255fz] to have phase Bound
Sep  8 09:25:37.481: INFO: PersistentVolumeClaim test.csi.azure.com255fz found but phase is Pending instead of Bound.
Sep  8 09:25:39.584: INFO: PersistentVolumeClaim test.csi.azure.com255fz found and phase=Bound (2.205614926s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 09:25:39.997: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-g6jlb" in namespace "snapshotting-437" to be "Succeeded or Failed"
Sep  8 09:25:40.099: INFO: Pod "pvc-snapshottable-tester-g6jlb": Phase="Pending", Reason="", readiness=false. Elapsed: 102.448348ms
Sep  8 09:25:42.202: INFO: Pod "pvc-snapshottable-tester-g6jlb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205049818s
Sep  8 09:25:44.305: INFO: Pod "pvc-snapshottable-tester-g6jlb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.308331175s
STEP: Saw pod success
Sep  8 09:25:44.305: INFO: Pod "pvc-snapshottable-tester-g6jlb" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 09:25:44.407: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com255fz] to have phase Bound
Sep  8 09:25:44.510: INFO: PersistentVolumeClaim test.csi.azure.com255fz found and phase=Bound (102.305776ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 09:25:44.818: INFO: Pod pvc-snapshottable-tester-g6jlb has the following logs: 
... skipping 129 lines ...
Sep  8 09:25:51.034: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func9.2
Sep  8 09:25:51.034: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep  8 09:25:51.034: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3


External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should fail if subpath file is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:258

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 09:25:37.415: INFO: >>> kubeConfig: /root/tmp2667319938/kubeconfig/kubeconfig.uksouth.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:258
Sep  8 09:25:38.130: INFO: Creating resource for dynamic PV
Sep  8 09:25:38.130: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7813-e2e-sczdvdn
STEP: creating a claim
Sep  8 09:25:38.233: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:25:38.337: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comjg9dr] to have phase Bound
Sep  8 09:25:38.439: INFO: PersistentVolumeClaim test.csi.azure.comjg9dr found but phase is Pending instead of Bound.
Sep  8 09:25:40.544: INFO: PersistentVolumeClaim test.csi.azure.comjg9dr found and phase=Bound (2.207126037s)
STEP: Creating pod pod-subpath-test-dynamicpv-fwgw
STEP: Checking for subpath error in container status
Sep  8 09:25:45.067: INFO: Deleting pod "pod-subpath-test-dynamicpv-fwgw" in namespace "provisioning-7813"
Sep  8 09:25:45.170: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-fwgw" to be fully deleted
STEP: Deleting pod
Sep  8 09:25:47.374: INFO: Deleting pod "pod-subpath-test-dynamicpv-fwgw" in namespace "provisioning-7813"
STEP: Deleting pvc
Sep  8 09:25:47.476: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comjg9dr"
... skipping 9 lines ...

• [SLOW TEST:15.789 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:258
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]","total":37,"completed":7,"skipped":836,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 143 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:50
    should store data
    test/e2e/storage/testsuites/volumes.go:161
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes should store data","total":38,"completed":3,"skipped":215,"failed":0}

SSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy 
  (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
  test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
... skipping 105 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents","total":38,"completed":4,"skipped":225,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:26:24.522: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 533 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volumeIO
  test/e2e/storage/framework/testsuite.go:50
    should write files of various sizes, verify size, validate content [Slow]
    test/e2e/storage/testsuites/volume_io.go:149
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]","total":37,"completed":8,"skipped":900,"failed":0}

SSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:26:40.593: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 138 lines ...
Sep  8 09:26:38.629: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:26:38.732: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2gsfq] to have phase Bound
Sep  8 09:26:38.834: INFO: PersistentVolumeClaim test.csi.azure.com2gsfq found but phase is Pending instead of Bound.
Sep  8 09:26:40.936: INFO: PersistentVolumeClaim test.csi.azure.com2gsfq found and phase=Bound (2.203625662s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 09:26:41.344: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-jlqsn" in namespace "snapshotting-829" to be "Succeeded or Failed"
Sep  8 09:26:41.446: INFO: Pod "pvc-snapshottable-tester-jlqsn": Phase="Pending", Reason="", readiness=false. Elapsed: 102.096613ms
Sep  8 09:26:43.549: INFO: Pod "pvc-snapshottable-tester-jlqsn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204582521s
Sep  8 09:26:45.654: INFO: Pod "pvc-snapshottable-tester-jlqsn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.310197877s
STEP: Saw pod success
Sep  8 09:26:45.655: INFO: Pod "pvc-snapshottable-tester-jlqsn" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 09:26:45.756: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2gsfq] to have phase Bound
Sep  8 09:26:45.858: INFO: PersistentVolumeClaim test.csi.azure.com2gsfq found and phase=Bound (101.774807ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 09:26:46.165: INFO: Pod pvc-snapshottable-tester-jlqsn has the following logs: 
... skipping 59 lines ...
Sep  8 09:26:41.503: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:26:41.607: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comgh7xq] to have phase Bound
Sep  8 09:26:41.708: INFO: PersistentVolumeClaim test.csi.azure.comgh7xq found but phase is Pending instead of Bound.
Sep  8 09:26:43.811: INFO: PersistentVolumeClaim test.csi.azure.comgh7xq found and phase=Bound (2.204133742s)
STEP: Creating pod pod-subpath-test-dynamicpv-f9kn
STEP: Creating a pod to test subpath
Sep  8 09:26:44.119: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-f9kn" in namespace "provisioning-7818" to be "Succeeded or Failed"
Sep  8 09:26:44.221: INFO: Pod "pod-subpath-test-dynamicpv-f9kn": Phase="Pending", Reason="", readiness=false. Elapsed: 101.92732ms
Sep  8 09:26:46.323: INFO: Pod "pod-subpath-test-dynamicpv-f9kn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204348104s
Sep  8 09:26:48.425: INFO: Pod "pod-subpath-test-dynamicpv-f9kn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.3064172s
Sep  8 09:26:50.528: INFO: Pod "pod-subpath-test-dynamicpv-f9kn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.409142739s
STEP: Saw pod success
Sep  8 09:26:50.528: INFO: Pod "pod-subpath-test-dynamicpv-f9kn" satisfied condition "Succeeded or Failed"
Sep  8 09:26:50.630: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000001 pod pod-subpath-test-dynamicpv-f9kn container test-container-volume-dynamicpv-f9kn: <nil>
STEP: delete the pod
Sep  8 09:26:50.842: INFO: Waiting for pod pod-subpath-test-dynamicpv-f9kn to disappear
Sep  8 09:26:50.943: INFO: Pod pod-subpath-test-dynamicpv-f9kn no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-f9kn
Sep  8 09:26:50.943: INFO: Deleting pod "pod-subpath-test-dynamicpv-f9kn" in namespace "provisioning-7818"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support non-existent path
    test/e2e/storage/testsuites/subpath.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path","total":37,"completed":9,"skipped":1009,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 99 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support restarting containers using directory as subpath [Slow]
    test/e2e/storage/testsuites/subpath.go:322
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]","total":34,"completed":4,"skipped":284,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
... skipping 66 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should resize volume when PVC is edited while pod is using it
    test/e2e/storage/testsuites/volume_expand.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":38,"completed":5,"skipped":666,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:27:08.634: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 203 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read-only inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:175
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume","total":34,"completed":5,"skipped":394,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:27:42.300: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 108 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:258

    Driver test.csi.azure.com doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 120 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single read-only volume from pods on the same node
    test/e2e/storage/testsuites/multivolume.go:423
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":34,"completed":6,"skipped":660,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:28:12.704: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 75 lines ...
Sep  8 09:28:13.622: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:28:13.727: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combxwx8] to have phase Bound
Sep  8 09:28:13.830: INFO: PersistentVolumeClaim test.csi.azure.combxwx8 found but phase is Pending instead of Bound.
Sep  8 09:28:15.934: INFO: PersistentVolumeClaim test.csi.azure.combxwx8 found and phase=Bound (2.206465604s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 09:28:16.348: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-v28rr" in namespace "snapshotting-7263" to be "Succeeded or Failed"
Sep  8 09:28:16.451: INFO: Pod "pvc-snapshottable-tester-v28rr": Phase="Pending", Reason="", readiness=false. Elapsed: 102.919078ms
Sep  8 09:28:18.556: INFO: Pod "pvc-snapshottable-tester-v28rr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207911184s
Sep  8 09:28:20.660: INFO: Pod "pvc-snapshottable-tester-v28rr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.311561229s
STEP: Saw pod success
Sep  8 09:28:20.660: INFO: Pod "pvc-snapshottable-tester-v28rr" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 09:28:20.763: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combxwx8] to have phase Bound
Sep  8 09:28:20.867: INFO: PersistentVolumeClaim test.csi.azure.combxwx8 found and phase=Bound (103.242299ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 09:28:21.183: INFO: Pod pvc-snapshottable-tester-v28rr has the following logs: 
... skipping 59 lines ...
Sep  8 09:28:28.063: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:28:28.168: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comjj9qs] to have phase Bound
Sep  8 09:28:28.271: INFO: PersistentVolumeClaim test.csi.azure.comjj9qs found but phase is Pending instead of Bound.
Sep  8 09:28:30.375: INFO: PersistentVolumeClaim test.csi.azure.comjj9qs found and phase=Bound (2.206986s)
STEP: Creating pod pod-subpath-test-dynamicpv-k9br
STEP: Creating a pod to test atomic-volume-subpath
Sep  8 09:28:30.686: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-k9br" in namespace "provisioning-5847" to be "Succeeded or Failed"
Sep  8 09:28:30.790: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Pending", Reason="", readiness=false. Elapsed: 103.340442ms
Sep  8 09:28:32.893: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20659339s
Sep  8 09:28:34.998: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 4.311276088s
Sep  8 09:28:37.103: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 6.41605385s
Sep  8 09:28:39.207: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 8.51998905s
Sep  8 09:28:41.310: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 10.623647092s
... skipping 2 lines ...
Sep  8 09:28:47.623: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 16.936180098s
Sep  8 09:28:49.726: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 19.039895688s
Sep  8 09:28:51.831: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=true. Elapsed: 21.144811016s
Sep  8 09:28:53.935: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Running", Reason="", readiness=false. Elapsed: 23.248505849s
Sep  8 09:28:56.040: INFO: Pod "pod-subpath-test-dynamicpv-k9br": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.353684881s
STEP: Saw pod success
Sep  8 09:28:56.040: INFO: Pod "pod-subpath-test-dynamicpv-k9br" satisfied condition "Succeeded or Failed"
Sep  8 09:28:56.144: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000000 pod pod-subpath-test-dynamicpv-k9br container test-container-subpath-dynamicpv-k9br: <nil>
STEP: delete the pod
Sep  8 09:28:56.358: INFO: Waiting for pod pod-subpath-test-dynamicpv-k9br to disappear
Sep  8 09:28:56.461: INFO: Pod pod-subpath-test-dynamicpv-k9br no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-k9br
Sep  8 09:28:56.461: INFO: Deleting pod "pod-subpath-test-dynamicpv-k9br" in namespace "provisioning-5847"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support file as subpath [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:232
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":34,"completed":7,"skipped":777,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:29:02.422: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 27 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  8 09:29:03.211: INFO: Creating resource for dynamic PV
Sep  8 09:29:03.212: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7791-e2e-scm2dlj
STEP: [init] starting a pod to use the claim
Sep  8 09:29:03.423: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-cm5rs" in namespace "snapshotting-7791" to be "Succeeded or Failed"
Sep  8 09:29:03.526: INFO: Pod "pvc-snapshottable-tester-cm5rs": Phase="Pending", Reason="", readiness=false. Elapsed: 103.421694ms
Sep  8 09:29:05.630: INFO: Pod "pvc-snapshottable-tester-cm5rs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207189612s
Sep  8 09:29:07.734: INFO: Pod "pvc-snapshottable-tester-cm5rs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.311416104s
Sep  8 09:29:09.839: INFO: Pod "pvc-snapshottable-tester-cm5rs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.416087888s
STEP: Saw pod success
Sep  8 09:29:09.839: INFO: Pod "pvc-snapshottable-tester-cm5rs" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  8 09:29:09.942: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  8 09:29:09.943: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-cm5rs-my-volume] to have phase Bound
Sep  8 09:29:10.047: INFO: PersistentVolumeClaim pvc-snapshottable-tester-cm5rs-my-volume found and phase=Bound (103.245033ms)
STEP: [init] checking the PV
... skipping 70 lines ...
Sep  8 09:29:11.732: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 09:29:11.837: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comfr7f5] to have phase Bound
Sep  8 09:29:11.940: INFO: PersistentVolumeClaim test.csi.azure.comfr7f5 found but phase is Pending instead of Bound.
Sep  8 09:29:14.044: INFO: PersistentVolumeClaim test.csi.azure.comfr7f5 found and phase=Bound (2.207414727s)
STEP: Creating pod pod-subpath-test-dynamicpv-d2k9
STEP: Creating a pod to test subpath
Sep  8 09:29:14.356: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-d2k9" in namespace "provisioning-2813" to be "Succeeded or Failed"
Sep  8 09:29:14.459: INFO: Pod "pod-subpath-test-dynamicpv-d2k9": Phase="Pending", Reason="", readiness=false. Elapsed: 103.394384ms
Sep  8 09:29:16.565: INFO: Pod "pod-subpath-test-dynamicpv-d2k9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20872043s
Sep  8 09:29:18.669: INFO: Pod "pod-subpath-test-dynamicpv-d2k9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.312819031s
Sep  8 09:29:20.773: INFO: Pod "pod-subpath-test-dynamicpv-d2k9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.417066366s
Sep  8 09:29:22.879: INFO: Pod "pod-subpath-test-dynamicpv-d2k9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.522698422s
STEP: Saw pod success
Sep  8 09:29:22.879: INFO: Pod "pod-subpath-test-dynamicpv-d2k9" satisfied condition "Succeeded or Failed"
Sep  8 09:29:22.982: INFO: Trying to get logs from node k8s-agentpool1-35403124-vmss000000 pod pod-subpath-test-dynamicpv-d2k9 container test-container-volume-dynamicpv-d2k9: <nil>
STEP: delete the pod
Sep  8 09:29:23.198: INFO: Waiting for pod pod-subpath-test-dynamicpv-d2k9 to disappear
Sep  8 09:29:23.301: INFO: Pod pod-subpath-test-dynamicpv-d2k9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-d2k9
Sep  8 09:29:23.301: INFO: Deleting pod "pod-subpath-test-dynamicpv-d2k9" in namespace "provisioning-2813"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing directory
    test/e2e/storage/testsuites/subpath.go:207
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory","total":34,"completed":8,"skipped":894,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 09:29:29.250: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 55 lines ...
Sep  8 09:27:10.163: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep  8 09:27:10.163: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3
Sep  8 09:29:29.400: INFO: Running AfterSuite actions on node 1


Ran 41 of 7229 Specs in 461.606 seconds
SUCCESS! -- 41 Passed | 0 Failed | 0 Pending | 7188 Skipped 

Ginkgo ran 1 suite in 7m46.230852802s
Test Suite Passed
+ print_logs
+ bash ./hack/verify-examples.sh linux
begin to create deployment examples ...
... skipping 72 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 09:21:39.096080       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a e2e-test
I0908 09:21:39.096358       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:39.115456       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
I0908 09:21:39.115473       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:39.115479       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 09:21:39.115497       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 09:21:39.116020       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 09:21:39.116050       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 09:21:39.116068       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 104 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 09:21:38.513424       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a e2e-test
I0908 09:21:38.513710       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:38.533220       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
I0908 09:21:38.533247       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:38.533254       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 09:21:38.533277       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 09:21:38.534298       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 09:21:38.534347       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 09:21:38.534368       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 318 lines ...
I0908 09:23:40.417668       1 azure_storage.go:69] share pvcn-b7ec804b-4d7a-4b77-98e6-4b927d85656d deleted
I0908 09:23:40.417699       1 controllerserver.go:603] azure file(pvcn-b7ec804b-4d7a-4b77-98e6-4b927d85656d) under subsID(0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e) rg(kubetest-2kztefxj) account(f1d0fdf69e34a4424a55f25) volume(kubetest-2kztefxj#f1d0fdf69e34a4424a55f25#pvcn-b7ec804b-4d7a-4b77-98e6-4b927d85656d###ephemeral-1818#) is deleted successfully
I0908 09:23:40.417728       1 azure_metrics.go:115] "Observed Request Latency" latency_seconds=0.179234886 request="azurefile_csi_driver_controller_delete_volume" resource_group="kubetest-2kztefxj" subscription_id="0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e" source="test.csi.azure.com" volumeid="kubetest-2kztefxj#f1d0fdf69e34a4424a55f25#pvcn-b7ec804b-4d7a-4b77-98e6-4b927d85656d###ephemeral-1818#" result_code="succeeded"
I0908 09:23:40.417740       1 utils.go:83] GRPC response: {}
I0908 09:23:40.461540       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0908 09:23:40.461552       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-03f30963-bae7-4d0b-88f8-bbf1aea1fa16","parameters":{"csi.storage.k8s.io/pv/name":"pvc-03f30963-bae7-4d0b-88f8-bbf1aea1fa16","csi.storage.k8s.io/pvc/name":"pvc-mmjnx","csi.storage.k8s.io/pvc/namespace":"volumemode-9257","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0908 09:23:40.461672       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0908 09:23:40.856649       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0908 09:23:40.856661       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-03f30963-bae7-4d0b-88f8-bbf1aea1fa16","parameters":{"csi.storage.k8s.io/pv/name":"pvc-03f30963-bae7-4d0b-88f8-bbf1aea1fa16","csi.storage.k8s.io/pvc/name":"pvc-mmjnx","csi.storage.k8s.io/pvc/namespace":"volumemode-9257","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0908 09:23:40.856795       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0908 09:23:42.109612       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0908 09:23:42.109623       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-dab72946-7cfe-4cf6-b5cc-7433e72c79f9","parameters":{"csi.storage.k8s.io/pv/name":"pvc-dab72946-7cfe-4cf6-b5cc-7433e72c79f9","csi.storage.k8s.io/pvc/name":"test.csi.azure.com5xgfs","csi.storage.k8s.io/pvc/namespace":"snapshotting-212","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Mount":{}},"access_mode":{"mode":7}}]}
I0908 09:23:42.109753       1 controllerserver.go:294] set vnetResourceID(/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-2kztefxj/providers/Microsoft.Network/virtualNetworks/k8s-vnet-35403124/subnets/k8s-subnet) for NFS protocol
I0908 09:23:42.109759       1 azure.go:180] updateSubnetServiceEndpoints on vnetName: k8s-vnet-35403124, subnetName: k8s-subnet, location: uksouth
I0908 09:23:42.160336       1 azure.go:209] serviceEndpoint(Microsoft.Storage) is already in subnet(k8s-subnet)
I0908 09:23:42.221903       1 controllerserver.go:449] begin to create file share(pvcn-dab72946-7cfe-4cf6-b5cc-7433e72c79f9) on account(f1d0fdf69e34a4424a55f25) type(Premium_LRS) subID() rg(kubetest-2kztefxj) location() size(100) protocol(NFS)
... skipping 621 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 09:21:29.655850       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a e2e-test
I0908 09:21:29.656142       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:29.678972       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
I0908 09:21:29.678991       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:29.678996       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 09:21:29.679117       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 09:21:29.679709       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 09:21:29.679806       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 09:21:29.679829       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 72 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 09:21:34.980851       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a e2e-test
I0908 09:21:34.981137       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:35.005393       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
I0908 09:21:35.005414       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:35.005419       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 09:21:35.005434       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 09:21:35.006414       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 09:21:35.006451       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 09:21:35.006468       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1231 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 09:21:34.188696       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-de8bd9dbb158d2b06fd4d580693b51f81522d37a e2e-test
I0908 09:21:34.188980       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:34.213483       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
I0908 09:21:34.213499       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 09:21:34.213505       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 09:21:34.213521       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 09:21:34.214123       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 09:21:34.214157       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 09:21:34.214176       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1427 lines ...