This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsunpa93: [V2] fix: handle pre-provisioned volume deletion at the right time
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-11-15 22:21
Elapsed1h7m
Revision9a5e42178ca4c83ac5867595354a15fe091a42d6
Refs 1599

No Test Failures!


Error lines from build-log.txt

... skipping 236 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   170k      0 --:--:-- --:--:-- --:--:--  170k
Downloading https://get.helm.sh/helm-v3.10.2-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azuredisk-csi:latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1 not found: manifest unknown: manifest tagged by "latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=75c2db4ea25bbd08f4a0971c912f0752e0628fa1 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-11-15T22:25:45Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.exe ./pkg/azurediskplugin
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 699 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1 not found: manifest unknown: manifest tagged by "latest-v2-75c2db4ea25bbd08f4a0971c912f0752e0628fa1" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx rm container-builder || true
container-builder removed
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
... skipping 1027 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 occurs 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 occurs 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 359 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status Required
            properties:
              detail:
                description: Status summarizes the current attachment state of the
                  volume attachment Nil Status indicates that the volume has not yet
                  been attached to the node
                properties:
... skipping 7 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 90 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 13 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 169 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              detail:
                description: Current status detail of the AzVolume Nil detail indicates
                  that the volume has not been created
                properties:
                  accessible_topology:
... skipping 28 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 154 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 34 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 1063 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'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
            - "-timeout=240s"
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
... skipping 536 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":41,"completed":1,"skipped":38,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumeIO
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:38:55.735: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 223 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block 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 (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node","total":33,"completed":1,"skipped":8,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:39:03.054: 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 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 131 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:323
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":30,"completed":1,"skipped":50,"failed":0}

S
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] provisioning 
  should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
  test/e2e/storage/testsuites/provisioning.go:208
... skipping 129 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] provisioning
  test/e2e/storage/framework/testsuite.go:50
    should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
    test/e2e/storage/testsuites/provisioning.go:208
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]","total":40,"completed":1,"skipped":17,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
... skipping 134 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":32,"completed":1,"skipped":89,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:39:50.769: INFO: Distro debian doesn't support ntfs -- 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 (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

    Distro debian doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:127
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
Nov 15 22:38:55.825: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.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
Nov 15 22:38:56.590: INFO: Creating resource for dynamic PV
Nov 15 22:38:56.590: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1109-e2e-sc9bcnm
STEP: creating a claim
Nov 15 22:38:56.699: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Nov 15 22:38:56.811: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comv4mwm] to have phase Bound
Nov 15 22:38:56.920: INFO: PersistentVolumeClaim test.csi.azure.comv4mwm found but phase is Pending instead of Bound.
Nov 15 22:38:59.032: INFO: PersistentVolumeClaim test.csi.azure.comv4mwm found but phase is Pending instead of Bound.
Nov 15 22:39:01.141: INFO: PersistentVolumeClaim test.csi.azure.comv4mwm found and phase=Bound (4.33021776s)
STEP: Creating pod pod-subpath-test-dynamicpv-hzhp
STEP: Checking for subpath error in container status
Nov 15 22:39:57.690: INFO: Deleting pod "pod-subpath-test-dynamicpv-hzhp" in namespace "provisioning-1109"
Nov 15 22:39:57.811: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-hzhp" to be fully deleted
STEP: Deleting pod
Nov 15 22:40:00.029: INFO: Deleting pod "pod-subpath-test-dynamicpv-hzhp" in namespace "provisioning-1109"
STEP: Deleting pvc
Nov 15 22:40:00.138: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comv4mwm"
... skipping 16 lines ...

• [SLOW TEST:105.981 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":41,"completed":2,"skipped":135,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] 
  should access to two volumes with different volume mode and retain data across pod recreation on different node
  test/e2e/storage/testsuites/multivolume.go:248
... skipping 198 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with different volume mode and retain data across pod recreation on different node
    test/e2e/storage/testsuites/multivolume.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node","total":23,"completed":1,"skipped":32,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:40:44.239: 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 (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 276 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with different volume mode and retain data across pod recreation on different node
    test/e2e/storage/testsuites/multivolume.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node","total":31,"completed":1,"skipped":120,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:40:45.407: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 45 lines ...

    test/e2e/storage/testsuites/multivolume.go:458
------------------------------
SSSSSSS
------------------------------
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
Nov 15 22:39:13.659: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.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
Nov 15 22:39:14.437: INFO: Creating resource for dynamic PV
Nov 15 22:39:14.437: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1655-e2e-scrxxh8
STEP: creating a claim
Nov 15 22:39:14.547: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Nov 15 22:39:14.661: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2jdvh] to have phase Bound
Nov 15 22:39:14.770: INFO: PersistentVolumeClaim test.csi.azure.com2jdvh found but phase is Pending instead of Bound.
Nov 15 22:39:16.887: INFO: PersistentVolumeClaim test.csi.azure.com2jdvh found but phase is Pending instead of Bound.
Nov 15 22:39:18.997: INFO: PersistentVolumeClaim test.csi.azure.com2jdvh found and phase=Bound (4.336011664s)
STEP: Creating pod pod-subpath-test-dynamicpv-qgdk
STEP: Checking for subpath error in container status
Nov 15 22:40:11.550: INFO: Deleting pod "pod-subpath-test-dynamicpv-qgdk" in namespace "provisioning-1655"
Nov 15 22:40:11.662: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qgdk" to be fully deleted
STEP: Deleting pod
Nov 15 22:40:13.883: INFO: Deleting pod "pod-subpath-test-dynamicpv-qgdk" in namespace "provisioning-1655"
STEP: Deleting pvc
Nov 15 22:40:13.992: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com2jdvh"
... skipping 22 lines ...

• [SLOW TEST:132.682 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":30,"completed":2,"skipped":51,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
... skipping 221 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with different volume mode and retain data across pod recreation on the same node
    test/e2e/storage/testsuites/multivolume.go:209
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node","total":40,"completed":2,"skipped":70,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumeIO 
  should write files of various sizes, verify size, validate content [Slow]
  test/e2e/storage/testsuites/volume_io.go:149
... skipping 52 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":41,"completed":3,"skipped":155,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:42:26.562: 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: 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 154 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:50
    should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
    test/e2e/storage/testsuites/provisioning.go:208
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]","total":33,"completed":2,"skipped":171,"failed":0}

SSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] 
  should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
  test/e2e/storage/testsuites/multivolume.go:378
... skipping 82 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 volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:378
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":32,"completed":2,"skipped":144,"failed":0}

SSSSSSSSSSS
------------------------------
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 same fsgroup applied to the volume contents
  test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
... skipping 119 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 same 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 same fsgroup applied to the volume contents","total":31,"completed":2,"skipped":151,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:42:54.836: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 101 lines ...
Nov 15 22:41:28.389: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comwhgkn] to have phase Bound
Nov 15 22:41:28.499: INFO: PersistentVolumeClaim test.csi.azure.comwhgkn found but phase is Pending instead of Bound.
Nov 15 22:41:30.609: INFO: PersistentVolumeClaim test.csi.azure.comwhgkn found but phase is Pending instead of Bound.
Nov 15 22:41:32.720: INFO: PersistentVolumeClaim test.csi.azure.comwhgkn found and phase=Bound (4.330919378s)
STEP: Creating pod pod-subpath-test-dynamicpv-cpcf
STEP: Creating a pod to test subpath
Nov 15 22:41:33.056: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cpcf" in namespace "provisioning-8589" to be "Succeeded or Failed"
Nov 15 22:41:33.166: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 110.02826ms
Nov 15 22:41:35.276: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220257819s
Nov 15 22:41:37.387: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330815723s
Nov 15 22:41:39.498: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.442369538s
Nov 15 22:41:41.611: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.554584995s
Nov 15 22:41:43.722: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.666137755s
... skipping 16 lines ...
Nov 15 22:42:19.609: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 46.553225162s
Nov 15 22:42:21.720: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 48.663589074s
Nov 15 22:42:23.832: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 50.775566677s
Nov 15 22:42:25.942: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Pending", Reason="", readiness=false. Elapsed: 52.886201664s
Nov 15 22:42:28.053: INFO: Pod "pod-subpath-test-dynamicpv-cpcf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.996971829s
STEP: Saw pod success
Nov 15 22:42:28.053: INFO: Pod "pod-subpath-test-dynamicpv-cpcf" satisfied condition "Succeeded or Failed"
Nov 15 22:42:28.163: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000000 pod pod-subpath-test-dynamicpv-cpcf container test-container-volume-dynamicpv-cpcf: <nil>
STEP: delete the pod
Nov 15 22:42:28.419: INFO: Waiting for pod pod-subpath-test-dynamicpv-cpcf to disappear
Nov 15 22:42:28.529: INFO: Pod pod-subpath-test-dynamicpv-cpcf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cpcf
Nov 15 22:42:28.529: INFO: Deleting pod "pod-subpath-test-dynamicpv-cpcf" in namespace "provisioning-8589"
... skipping 23 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":30,"completed":3,"skipped":107,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumeIO
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:43:10.447: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 13 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
Nov 15 22:42:43.566: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.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
Nov 15 22:42:44.328: INFO: Creating resource for dynamic PV
Nov 15 22:42:44.328: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8038-e2e-sc7wf57
STEP: creating a claim
Nov 15 22:42:44.439: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Nov 15 22:42:44.559: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comlkfkq] to have phase Bound
Nov 15 22:42:44.676: INFO: PersistentVolumeClaim test.csi.azure.comlkfkq found but phase is Pending instead of Bound.
Nov 15 22:42:46.786: INFO: PersistentVolumeClaim test.csi.azure.comlkfkq found but phase is Pending instead of Bound.
Nov 15 22:42:48.896: INFO: PersistentVolumeClaim test.csi.azure.comlkfkq found and phase=Bound (4.337083218s)
STEP: Creating pod pod-subpath-test-dynamicpv-vfq4
STEP: Checking for subpath error in container status
Nov 15 22:43:21.447: INFO: Deleting pod "pod-subpath-test-dynamicpv-vfq4" in namespace "provisioning-8038"
Nov 15 22:43:21.561: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-vfq4" to be fully deleted
STEP: Deleting pod
Nov 15 22:43:23.784: INFO: Deleting pod "pod-subpath-test-dynamicpv-vfq4" in namespace "provisioning-8038"
STEP: Deleting pvc
Nov 15 22:43:23.894: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comlkfkq"
... skipping 22 lines ...

• [SLOW TEST:112.643 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":32,"completed":3,"skipped":155,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:44:36.256: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 211 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] provisioning
  test/e2e/storage/framework/testsuite.go:50
    should provision storage with pvc data source
    test/e2e/storage/testsuites/provisioning.go:421
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source","total":40,"completed":3,"skipped":107,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:44:42.638: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 128 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:323
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":23,"completed":2,"skipped":149,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:44:46.423: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 230 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block 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 (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node","total":31,"completed":3,"skipped":405,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:44:58.122: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 85 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":41,"completed":4,"skipped":263,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:45:19.854: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 166 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] 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 (ext4)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":30,"completed":4,"skipped":181,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:45:53.483: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 13 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] volumeMode 
  should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299

[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
Nov 15 22:44:38.403: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.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
Nov 15 22:44:39.180: INFO: Creating resource for dynamic PV
Nov 15 22:44:39.180: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-386-e2e-scr72bx
STEP: creating a claim
Nov 15 22:44:39.408: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comk6jfj] to have phase Bound
Nov 15 22:44:39.518: INFO: PersistentVolumeClaim test.csi.azure.comk6jfj found but phase is Pending instead of Bound.
Nov 15 22:44:41.628: INFO: PersistentVolumeClaim test.csi.azure.comk6jfj found but phase is Pending instead of Bound.
Nov 15 22:44:43.738: INFO: PersistentVolumeClaim test.csi.azure.comk6jfj found and phase=Bound (4.329728433s)
STEP: Creating pod
STEP: Waiting for the pod to fail
Nov 15 22:44:46.396: INFO: Deleting pod "pod-63be29ec-51d6-4c67-8c37-872b95c90ff9" in namespace "volumemode-386"
Nov 15 22:44:46.507: INFO: Wait up to 5m0s for pod "pod-63be29ec-51d6-4c67-8c37-872b95c90ff9" to be fully deleted
STEP: Deleting pvc
Nov 15 22:44:48.728: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comk6jfj"
Nov 15 22:44:48.842: INFO: Waiting up to 5m0s for PersistentVolume pvc-e89ee129-6477-46a7-afc0-77e1b6524556 to get deleted
Nov 15 22:44:48.952: INFO: PersistentVolume pvc-e89ee129-6477-46a7-afc0-77e1b6524556 found and phase=Released (109.551418ms)
... skipping 20 lines ...

• [SLOW TEST:82.664 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]
    test/e2e/storage/testsuites/volumemode.go:299
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]","total":32,"completed":4,"skipped":276,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:46:01.115: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 129 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:378
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":33,"completed":3,"skipped":183,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
... skipping 222 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] 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 (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on the same node","total":31,"completed":4,"skipped":426,"failed":0}

SSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext3)] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161
... skipping 108 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext3)] 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 (ext3)] volumes should store data","total":40,"completed":4,"skipped":145,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:46:37.726: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 34 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode 
  should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299

[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Nov 15 22:46:01.346: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.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
Nov 15 22:46:02.115: INFO: Creating resource for dynamic PV
Nov 15 22:46:02.115: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-4855-e2e-sclf5tv
STEP: creating a claim
Nov 15 22:46:02.342: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2544m] to have phase Bound
Nov 15 22:46:02.453: INFO: PersistentVolumeClaim test.csi.azure.com2544m found but phase is Pending instead of Bound.
Nov 15 22:46:04.564: INFO: PersistentVolumeClaim test.csi.azure.com2544m found but phase is Pending instead of Bound.
Nov 15 22:46:06.674: INFO: PersistentVolumeClaim test.csi.azure.com2544m found and phase=Bound (4.331154821s)
STEP: Creating pod
STEP: Waiting for the pod to fail
Nov 15 22:46:09.364: INFO: Deleting pod "pod-c2bb3068-f0d7-4604-bf05-ecbe8b3078ab" in namespace "volumemode-4855"
Nov 15 22:46:09.477: INFO: Wait up to 5m0s for pod "pod-c2bb3068-f0d7-4604-bf05-ecbe8b3078ab" to be fully deleted
STEP: Deleting pvc
Nov 15 22:46:11.703: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com2544m"
Nov 15 22:46:11.815: INFO: Waiting up to 5m0s for PersistentVolume pvc-8d6a8a64-c629-4623-954d-e468480e7c24 to get deleted
Nov 15 22:46:11.925: INFO: PersistentVolume pvc-8d6a8a64-c629-4623-954d-e468480e7c24 found and phase=Released (109.963787ms)
... skipping 20 lines ...

• [SLOW TEST:82.690 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]
    test/e2e/storage/testsuites/volumemode.go:299
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]","total":32,"completed":5,"skipped":440,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] 
  should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
  test/e2e/storage/testsuites/multivolume.go:378
... skipping 81 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:378
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":23,"completed":3,"skipped":267,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:47:29.620: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 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 195 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] 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 (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node","total":41,"completed":5,"skipped":335,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes 
  should allow exec of files on the volume
  test/e2e/storage/testsuites/volumes.go:198
... skipping 17 lines ...
Nov 15 22:45:54.546: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comd6jls] to have phase Bound
Nov 15 22:45:54.657: INFO: PersistentVolumeClaim test.csi.azure.comd6jls found but phase is Pending instead of Bound.
Nov 15 22:45:56.768: INFO: PersistentVolumeClaim test.csi.azure.comd6jls found but phase is Pending instead of Bound.
Nov 15 22:45:58.887: INFO: PersistentVolumeClaim test.csi.azure.comd6jls found and phase=Bound (4.341013833s)
STEP: Creating pod exec-volume-test-dynamicpv-t429
STEP: Creating a pod to test exec-volume-test
Nov 15 22:45:59.222: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-t429" in namespace "volume-4292" to be "Succeeded or Failed"
Nov 15 22:45:59.332: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 110.483747ms
Nov 15 22:46:01.444: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222256028s
Nov 15 22:46:03.557: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 4.334919092s
Nov 15 22:46:05.669: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 6.447359232s
Nov 15 22:46:07.780: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 8.558479116s
Nov 15 22:46:09.893: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 10.67092131s
... skipping 7 lines ...
Nov 15 22:46:26.788: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 27.566379614s
Nov 15 22:46:28.909: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 29.687657539s
Nov 15 22:46:31.022: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 31.800147997s
Nov 15 22:46:33.132: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Pending", Reason="", readiness=false. Elapsed: 33.910664334s
Nov 15 22:46:35.244: INFO: Pod "exec-volume-test-dynamicpv-t429": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.022038358s
STEP: Saw pod success
Nov 15 22:46:35.244: INFO: Pod "exec-volume-test-dynamicpv-t429" satisfied condition "Succeeded or Failed"
Nov 15 22:46:35.354: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000001 pod exec-volume-test-dynamicpv-t429 container exec-container-dynamicpv-t429: <nil>
STEP: delete the pod
Nov 15 22:46:35.631: INFO: Waiting for pod exec-volume-test-dynamicpv-t429 to disappear
Nov 15 22:46:35.742: INFO: Pod exec-volume-test-dynamicpv-t429 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-t429
Nov 15 22:46:35.742: INFO: Deleting pod "exec-volume-test-dynamicpv-t429" in namespace "volume-4292"
... skipping 27 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":30,"completed":5,"skipped":261,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumeIO
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:47:48.214: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 171 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":33,"completed":4,"skipped":264,"failed":0}

SSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
... skipping 83 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":31,"completed":5,"skipped":436,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:48:38.385: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 37 lines ...
  test/e2e/framework/framework.go:188
Nov 15 22:48:39.755: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumelimits-9809" for this suite.

•
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should verify that all csinodes have volume limits","total":31,"completed":6,"skipped":531,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:48:40.148: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 45 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

    Distro debian doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 95 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":32,"completed":6,"skipped":457,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/multivolume.go:298
... skipping 153 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":30,"completed":6,"skipped":299,"failed":0}

SSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral 
  should create read-only inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:175
... 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 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":23,"completed":4,"skipped":293,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161
... skipping 95 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] 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 (block volmode)] volumes should store data","total":41,"completed":6,"skipped":377,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:50:32.287: INFO: Distro debian doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/framework/framework.go:188

... skipping 55 lines ...
Nov 15 22:48:52.860: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Nov 15 22:48:52.973: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com4blct] to have phase Bound
Nov 15 22:48:53.082: INFO: PersistentVolumeClaim test.csi.azure.com4blct found but phase is Pending instead of Bound.
Nov 15 22:48:55.192: INFO: PersistentVolumeClaim test.csi.azure.com4blct found but phase is Pending instead of Bound.
Nov 15 22:48:57.303: INFO: PersistentVolumeClaim test.csi.azure.com4blct found and phase=Bound (4.329952426s)
STEP: Creating pod to format volume volume-prep-provisioning-6461
Nov 15 22:48:57.642: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6461" in namespace "provisioning-6461" to be "Succeeded or Failed"
Nov 15 22:48:57.751: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 109.068176ms
Nov 15 22:48:59.862: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22035065s
Nov 15 22:49:01.972: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330053915s
Nov 15 22:49:04.082: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 6.440185074s
Nov 15 22:49:06.192: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 8.550127583s
Nov 15 22:49:08.302: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 10.660597504s
... skipping 10 lines ...
Nov 15 22:49:31.514: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 33.872032058s
Nov 15 22:49:33.624: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 35.982404293s
Nov 15 22:49:35.734: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 38.092339101s
Nov 15 22:49:37.843: INFO: Pod "volume-prep-provisioning-6461": Phase="Pending", Reason="", readiness=false. Elapsed: 40.201923766s
Nov 15 22:49:39.956: INFO: Pod "volume-prep-provisioning-6461": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.314041375s
STEP: Saw pod success
Nov 15 22:49:39.956: INFO: Pod "volume-prep-provisioning-6461" satisfied condition "Succeeded or Failed"
Nov 15 22:49:39.956: INFO: Deleting pod "volume-prep-provisioning-6461" in namespace "provisioning-6461"
Nov 15 22:49:40.071: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6461" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-brh9
STEP: Checking for subpath error in container status
Nov 15 22:49:50.527: INFO: Deleting pod "pod-subpath-test-dynamicpv-brh9" in namespace "provisioning-6461"
Nov 15 22:49:50.646: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-brh9" to be fully deleted
STEP: Deleting pod
Nov 15 22:49:52.870: INFO: Deleting pod "pod-subpath-test-dynamicpv-brh9" in namespace "provisioning-6461"
STEP: Deleting pvc
Nov 15 22:49:52.986: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com4blct"
... skipping 19 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":32,"completed":7,"skipped":492,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] 
  should concurrently access the single read-only volume from pods on the same node
  test/e2e/storage/testsuites/multivolume.go:423
... skipping 88 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] 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 (xfs)][Slow] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":33,"completed":5,"skipped":302,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:51:15.014: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 59 lines ...
Nov 15 22:48:41.260: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comvhpgs] to have phase Bound
Nov 15 22:48:41.370: INFO: PersistentVolumeClaim test.csi.azure.comvhpgs found but phase is Pending instead of Bound.
Nov 15 22:48:43.481: INFO: PersistentVolumeClaim test.csi.azure.comvhpgs found but phase is Pending instead of Bound.
Nov 15 22:48:45.591: INFO: PersistentVolumeClaim test.csi.azure.comvhpgs found and phase=Bound (4.33079613s)
STEP: Creating pod pod-subpath-test-dynamicpv-jhtb
STEP: Creating a pod to test subpath
Nov 15 22:48:45.922: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jhtb" in namespace "provisioning-7716" to be "Succeeded or Failed"
Nov 15 22:48:46.033: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 110.61673ms
Nov 15 22:48:48.149: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.227201915s
Nov 15 22:48:50.260: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.33743575s
Nov 15 22:48:52.370: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.448131075s
Nov 15 22:48:54.480: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.558412902s
Nov 15 22:48:56.592: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.669758861s
... skipping 39 lines ...
Nov 15 22:50:21.030: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 1m35.107816931s
Nov 15 22:50:23.140: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 1m37.218249087s
Nov 15 22:50:25.256: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 1m39.333450929s
Nov 15 22:50:27.366: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Pending", Reason="", readiness=false. Elapsed: 1m41.444398885s
Nov 15 22:50:29.478: INFO: Pod "pod-subpath-test-dynamicpv-jhtb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m43.55604245s
STEP: Saw pod success
Nov 15 22:50:29.478: INFO: Pod "pod-subpath-test-dynamicpv-jhtb" satisfied condition "Succeeded or Failed"
Nov 15 22:50:29.588: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000001 pod pod-subpath-test-dynamicpv-jhtb container test-container-subpath-dynamicpv-jhtb: <nil>
STEP: delete the pod
Nov 15 22:50:29.842: INFO: Waiting for pod pod-subpath-test-dynamicpv-jhtb to disappear
Nov 15 22:50:29.952: INFO: Pod pod-subpath-test-dynamicpv-jhtb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jhtb
Nov 15 22:50:29.952: INFO: Deleting pod "pod-subpath-test-dynamicpv-jhtb" in namespace "provisioning-7716"
... skipping 25 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":7,"skipped":651,"failed":0}

S
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  
  should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
  test/e2e/storage/testsuites/snapshottable.go:278
... skipping 17 lines ...
Nov 15 22:46:38.885: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2xgl4] to have phase Bound
Nov 15 22:46:38.995: INFO: PersistentVolumeClaim test.csi.azure.com2xgl4 found but phase is Pending instead of Bound.
Nov 15 22:46:41.111: INFO: PersistentVolumeClaim test.csi.azure.com2xgl4 found but phase is Pending instead of Bound.
Nov 15 22:46:43.221: INFO: PersistentVolumeClaim test.csi.azure.com2xgl4 found and phase=Bound (4.335785469s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Nov 15 22:46:43.676: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-swrfw" in namespace "snapshotting-9989" to be "Succeeded or Failed"
Nov 15 22:46:43.804: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 128.650574ms
Nov 15 22:46:45.914: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237957684s
Nov 15 22:46:48.023: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.347408774s
Nov 15 22:46:50.133: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.457700594s
Nov 15 22:46:52.248: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.572834593s
Nov 15 22:46:54.359: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.683074435s
... skipping 14 lines ...
Nov 15 22:47:26.018: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 42.342503087s
Nov 15 22:47:28.133: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 44.457078465s
Nov 15 22:47:30.243: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 46.567279502s
Nov 15 22:47:32.359: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Pending", Reason="", readiness=false. Elapsed: 48.683830771s
Nov 15 22:47:34.473: INFO: Pod "pvc-snapshottable-tester-swrfw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.797187926s
STEP: Saw pod success
Nov 15 22:47:34.473: INFO: Pod "pvc-snapshottable-tester-swrfw" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Nov 15 22:47:34.592: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2xgl4] to have phase Bound
Nov 15 22:47:34.707: INFO: PersistentVolumeClaim test.csi.azure.com2xgl4 found and phase=Bound (114.887031ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Nov 15 22:47:35.086: INFO: Pod pvc-snapshottable-tester-swrfw has the following logs: 
... skipping 16 lines ...
Nov 15 22:47:49.225: INFO: received snapshotStatus map[boundVolumeSnapshotContentName:snapcontent-539e54f8-77d4-44f2-88f0-ccc2e297c562 creationTime:2022-11-15T22:47:44Z readyToUse:true restoreSize:5Gi]
Nov 15 22:47:49.225: INFO: snapshotContentName snapcontent-539e54f8-77d4-44f2-88f0-ccc2e297c562
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Nov 15 22:47:49.668: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-rwfm4" in namespace "snapshotting-9989" to be "Succeeded or Failed"
Nov 15 22:47:49.777: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 108.707139ms
Nov 15 22:47:51.886: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217832514s
Nov 15 22:47:53.997: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328631136s
Nov 15 22:47:56.106: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43837602s
Nov 15 22:47:58.217: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.549105567s
Nov 15 22:48:00.326: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.65834215s
... skipping 43 lines ...
Nov 15 22:49:33.212: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m43.544382663s
Nov 15 22:49:35.322: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m45.654370784s
Nov 15 22:49:37.434: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m47.765560071s
Nov 15 22:49:39.555: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Pending", Reason="", readiness=false. Elapsed: 1m49.887430311s
Nov 15 22:49:41.665: INFO: Pod "pvc-snapshottable-data-tester-rwfm4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m51.996956357s
STEP: Saw pod success
Nov 15 22:49:41.665: INFO: Pod "pvc-snapshottable-data-tester-rwfm4" satisfied condition "Succeeded or Failed"
Nov 15 22:49:41.908: INFO: Pod pvc-snapshottable-data-tester-rwfm4 has the following logs: 
Nov 15 22:49:41.908: INFO: Deleting pod "pvc-snapshottable-data-tester-rwfm4" in namespace "snapshotting-9989"
Nov 15 22:49:42.025: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-rwfm4" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the snapshot
Nov 15 22:50:54.577: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-c1byahsu.westeurope.cloudapp.azure.com --kubeconfig=/root/tmp2485039460/kubeconfig/kubeconfig.westeurope.json --namespace=snapshotting-9989 exec restored-pvc-tester-72ttp --namespace=snapshotting-9989 -- cat /mnt/test/data'
... skipping 47 lines ...
    test/e2e/storage/testsuites/snapshottable.go:113
      
      test/e2e/storage/testsuites/snapshottable.go:176
        should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
        test/e2e/storage/testsuites/snapshottable.go:278
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)","total":40,"completed":5,"skipped":206,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:51:38.955: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 97 lines ...
Nov 15 22:50:20.817: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.compmnh5] to have phase Bound
Nov 15 22:50:20.926: INFO: PersistentVolumeClaim test.csi.azure.compmnh5 found but phase is Pending instead of Bound.
Nov 15 22:50:23.042: INFO: PersistentVolumeClaim test.csi.azure.compmnh5 found but phase is Pending instead of Bound.
Nov 15 22:50:25.153: INFO: PersistentVolumeClaim test.csi.azure.compmnh5 found and phase=Bound (4.336227728s)
STEP: Creating pod pod-subpath-test-dynamicpv-l8qq
STEP: Creating a pod to test subpath
Nov 15 22:50:25.486: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l8qq" in namespace "provisioning-6104" to be "Succeeded or Failed"
Nov 15 22:50:25.599: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 112.915909ms
Nov 15 22:50:27.709: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.223371605s
Nov 15 22:50:29.819: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.333357045s
Nov 15 22:50:31.930: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.443729006s
Nov 15 22:50:34.048: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.561963927s
Nov 15 22:50:36.158: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.671829944s
... skipping 15 lines ...
Nov 15 22:51:09.920: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 44.434233755s
Nov 15 22:51:12.030: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 46.544039147s
Nov 15 22:51:14.140: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 48.653853699s
Nov 15 22:51:16.249: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Pending", Reason="", readiness=false. Elapsed: 50.763092598s
Nov 15 22:51:18.360: INFO: Pod "pod-subpath-test-dynamicpv-l8qq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 52.874290854s
STEP: Saw pod success
Nov 15 22:51:18.360: INFO: Pod "pod-subpath-test-dynamicpv-l8qq" satisfied condition "Succeeded or Failed"
Nov 15 22:51:18.469: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod pod-subpath-test-dynamicpv-l8qq container test-container-subpath-dynamicpv-l8qq: <nil>
STEP: delete the pod
Nov 15 22:51:18.708: INFO: Waiting for pod pod-subpath-test-dynamicpv-l8qq to disappear
Nov 15 22:51:18.816: INFO: Pod pod-subpath-test-dynamicpv-l8qq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-l8qq
Nov 15 22:51:18.816: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8qq" in namespace "provisioning-6104"
... skipping 19 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":23,"completed":5,"skipped":585,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 68 lines ...

        test/e2e/storage/testsuites/snapshottable.go:280
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
Nov 15 22:51:15.071: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.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
Nov 15 22:51:15.863: INFO: Creating resource for dynamic PV
Nov 15 22:51:15.863: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4952-e2e-sc4bzz2
STEP: creating a claim
Nov 15 22:51:15.972: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Nov 15 22:51:16.084: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com4jppc] to have phase Bound
Nov 15 22:51:16.196: INFO: PersistentVolumeClaim test.csi.azure.com4jppc found but phase is Pending instead of Bound.
Nov 15 22:51:18.306: INFO: PersistentVolumeClaim test.csi.azure.com4jppc found but phase is Pending instead of Bound.
Nov 15 22:51:20.416: INFO: PersistentVolumeClaim test.csi.azure.com4jppc found and phase=Bound (4.331645616s)
STEP: Creating pod pod-subpath-test-dynamicpv-mkxt
STEP: Checking for subpath error in container status
Nov 15 22:51:58.965: INFO: Deleting pod "pod-subpath-test-dynamicpv-mkxt" in namespace "provisioning-4952"
Nov 15 22:51:59.084: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-mkxt" to be fully deleted
STEP: Deleting pod
Nov 15 22:52:01.302: INFO: Deleting pod "pod-subpath-test-dynamicpv-mkxt" in namespace "provisioning-4952"
STEP: Deleting pvc
Nov 15 22:52:01.410: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com4jppc"
... skipping 16 lines ...

• [SLOW TEST:88.001 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":33,"completed":6,"skipped":364,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:52:43.089: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 197 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":30,"completed":7,"skipped":307,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:53:49.108: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 210 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:50
    should provision storage with pvc data source
    test/e2e/storage/testsuites/provisioning.go:421
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source","total":32,"completed":8,"skipped":523,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:53:55.813: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 59 lines ...
Nov 15 22:51:43.437: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com4ffsr] to have phase Bound
Nov 15 22:51:43.546: INFO: PersistentVolumeClaim test.csi.azure.com4ffsr found but phase is Pending instead of Bound.
Nov 15 22:51:45.655: INFO: PersistentVolumeClaim test.csi.azure.com4ffsr found but phase is Pending instead of Bound.
Nov 15 22:51:47.764: INFO: PersistentVolumeClaim test.csi.azure.com4ffsr found and phase=Bound (4.327376765s)
STEP: Creating pod exec-volume-test-dynamicpv-gwbz
STEP: Creating a pod to test exec-volume-test
Nov 15 22:51:48.095: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-gwbz" in namespace "volume-6875" to be "Succeeded or Failed"
Nov 15 22:51:48.206: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 110.557946ms
Nov 15 22:51:50.316: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.221175647s
Nov 15 22:51:52.426: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330957646s
Nov 15 22:51:54.537: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.442199864s
Nov 15 22:51:56.649: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.553981994s
Nov 15 22:51:58.759: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.664405919s
... skipping 39 lines ...
Nov 15 22:53:23.193: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 1m35.098208617s
Nov 15 22:53:25.303: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 1m37.208147651s
Nov 15 22:53:27.414: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 1m39.318967087s
Nov 15 22:53:29.525: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Pending", Reason="", readiness=false. Elapsed: 1m41.430167536s
Nov 15 22:53:31.635: INFO: Pod "exec-volume-test-dynamicpv-gwbz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m43.540154992s
STEP: Saw pod success
Nov 15 22:53:31.635: INFO: Pod "exec-volume-test-dynamicpv-gwbz" satisfied condition "Succeeded or Failed"
Nov 15 22:53:31.745: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod exec-volume-test-dynamicpv-gwbz container exec-container-dynamicpv-gwbz: <nil>
STEP: delete the pod
Nov 15 22:53:31.996: INFO: Waiting for pod exec-volume-test-dynamicpv-gwbz to disappear
Nov 15 22:53:32.105: INFO: Pod exec-volume-test-dynamicpv-gwbz no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-gwbz
Nov 15 22:53:32.105: INFO: Deleting pod "exec-volume-test-dynamicpv-gwbz" in namespace "volume-6875"
... skipping 21 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] 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 (xfs)][Slow] volumes should allow exec of files on the volume","total":23,"completed":6,"skipped":763,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:54:13.952: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 286 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with different volume mode and retain data across pod recreation on the same node
    test/e2e/storage/testsuites/multivolume.go:209
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node","total":41,"completed":7,"skipped":457,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:54:41.490: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 90 lines ...
  test/e2e/framework/framework.go:188
Nov 15 22:54:43.731: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumelimits-9735" for this suite.

•
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should verify that all csinodes have volume limits","total":41,"completed":8,"skipped":523,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:54:43.975: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 38 lines ...
Nov 15 22:53:50.421: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com892br] to have phase Bound
Nov 15 22:53:50.531: INFO: PersistentVolumeClaim test.csi.azure.com892br found but phase is Pending instead of Bound.
Nov 15 22:53:52.642: INFO: PersistentVolumeClaim test.csi.azure.com892br found but phase is Pending instead of Bound.
Nov 15 22:53:54.752: INFO: PersistentVolumeClaim test.csi.azure.com892br found and phase=Bound (4.330813768s)
STEP: Creating pod exec-volume-test-dynamicpv-2lw9
STEP: Creating a pod to test exec-volume-test
Nov 15 22:53:55.087: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-2lw9" in namespace "volume-1478" to be "Succeeded or Failed"
Nov 15 22:53:55.212: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 124.740623ms
Nov 15 22:53:57.323: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.23549548s
Nov 15 22:53:59.434: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.347146936s
Nov 15 22:54:01.548: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.461025369s
Nov 15 22:54:03.672: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.584344315s
Nov 15 22:54:05.784: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.696491871s
... skipping 4 lines ...
Nov 15 22:54:16.345: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 21.257272049s
Nov 15 22:54:18.460: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 23.372585433s
Nov 15 22:54:20.571: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 25.483852155s
Nov 15 22:54:22.684: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Pending", Reason="", readiness=false. Elapsed: 27.596624639s
Nov 15 22:54:24.795: INFO: Pod "exec-volume-test-dynamicpv-2lw9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.708032713s
STEP: Saw pod success
Nov 15 22:54:24.795: INFO: Pod "exec-volume-test-dynamicpv-2lw9" satisfied condition "Succeeded or Failed"
Nov 15 22:54:24.906: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod exec-volume-test-dynamicpv-2lw9 container exec-container-dynamicpv-2lw9: <nil>
STEP: delete the pod
Nov 15 22:54:25.140: INFO: Waiting for pod exec-volume-test-dynamicpv-2lw9 to disappear
Nov 15 22:54:25.250: INFO: Pod exec-volume-test-dynamicpv-2lw9 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-2lw9
Nov 15 22:54:25.250: INFO: Deleting pod "exec-volume-test-dynamicpv-2lw9" in namespace "volume-1478"
... skipping 21 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext3)] 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 (ext3)] volumes should allow exec of files on the volume","total":30,"completed":8,"skipped":673,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 42 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Nov 15 22:51:40.908: INFO: Creating resource for dynamic PV
Nov 15 22:51:40.908: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-4537-e2e-sc5j6r9
STEP: [init] starting a pod to use the claim
Nov 15 22:51:41.142: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6tz79" in namespace "snapshotting-4537" to be "Succeeded or Failed"
Nov 15 22:51:41.254: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 112.321783ms
Nov 15 22:51:43.365: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222964007s
Nov 15 22:51:45.475: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 4.333033008s
Nov 15 22:51:47.590: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 6.447622604s
Nov 15 22:51:49.699: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 8.556913359s
Nov 15 22:51:51.809: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 10.666433911s
... skipping 6 lines ...
Nov 15 22:52:06.586: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 25.444150026s
Nov 15 22:52:08.702: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 27.559565916s
Nov 15 22:52:10.812: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 29.670200891s
Nov 15 22:52:12.923: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Pending", Reason="", readiness=false. Elapsed: 31.781037421s
Nov 15 22:52:15.033: INFO: Pod "pvc-snapshottable-tester-6tz79": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.890969408s
STEP: Saw pod success
Nov 15 22:52:15.033: INFO: Pod "pvc-snapshottable-tester-6tz79" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
STEP: creating a dynamic VolumeSnapshot
Nov 15 22:52:15.482: INFO: Waiting up to 5m0s for VolumeSnapshot snapshot-2zl25 to become ready
Nov 15 22:52:15.591: INFO: VolumeSnapshot snapshot-2zl25 found but is not ready.
Nov 15 22:52:17.701: INFO: VolumeSnapshot snapshot-2zl25 found but is not ready.
... skipping 40 lines ...
Nov 15 22:54:29.694: INFO: volumesnapshotcontents snapcontent-7415484d-8c78-497e-b98a-be6c4d956348 has been found and is not deleted
Nov 15 22:54:30.804: INFO: volumesnapshotcontents snapcontent-7415484d-8c78-497e-b98a-be6c4d956348 has been found and is not deleted
Nov 15 22:54:31.914: INFO: volumesnapshotcontents snapcontent-7415484d-8c78-497e-b98a-be6c4d956348 has been found and is not deleted
Nov 15 22:54:33.026: INFO: volumesnapshotcontents snapcontent-7415484d-8c78-497e-b98a-be6c4d956348 has been found and is not deleted
Nov 15 22:54:34.135: INFO: volumesnapshotcontents snapcontent-7415484d-8c78-497e-b98a-be6c4d956348 has been found and is not deleted
Nov 15 22:54:35.244: INFO: volumesnapshotcontents snapcontent-7415484d-8c78-497e-b98a-be6c4d956348 has been found and is not deleted
Nov 15 22:54:36.245: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  test/e2e/storage/testsuites/snapshottable.go:172
Nov 15 22:54:36.359: INFO: Pod restored-pvc-tester-vr7gv has the following logs: 
Nov 15 22:54:36.359: INFO: Deleting pod "restored-pvc-tester-vr7gv" in namespace "snapshotting-4537"
Nov 15 22:54:36.469: INFO: Wait up to 5m0s for pod "restored-pvc-tester-vr7gv" to be fully deleted
Nov 15 22:55:08.687: INFO: deleting snapshot "snapshotting-4537"/"snapshot-2zl25"
... skipping 26 lines ...
    test/e2e/storage/testsuites/snapshottable.go:113
      
      test/e2e/storage/testsuites/snapshottable.go:176
        should check snapshot fields, check restore correctly works, check deletion (ephemeral)
        test/e2e/storage/testsuites/snapshottable.go:177
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  should check snapshot fields, check restore correctly works, check deletion (ephemeral)","total":40,"completed":6,"skipped":301,"failed":0}

SSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] 
  should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
  test/e2e/storage/testsuites/multivolume.go:378
... skipping 88 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:378
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":31,"completed":8,"skipped":652,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] 
  should access to two volumes with different volume mode and retain data across pod recreation on the same node
  test/e2e/storage/testsuites/multivolume.go:209
... skipping 195 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with different volume mode and retain data across pod recreation on the same node
    test/e2e/storage/testsuites/multivolume.go:209
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node","total":32,"completed":9,"skipped":558,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:57:11.604: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 45 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 50 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":31,"completed":9,"skipped":672,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:57:39.497: 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 340 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block volmode)] provisioning
  test/e2e/storage/framework/testsuite.go:50
    should provision storage with pvc data source in parallel [Slow]
    test/e2e/storage/testsuites/provisioning.go:459
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source in parallel [Slow]","total":23,"completed":7,"skipped":881,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
... skipping 97 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":30,"completed":9,"skipped":746,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:58:01.411: 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 (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 107 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":33,"completed":7,"skipped":537,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] 
  should concurrently access the single volume from pods on the same node
  test/e2e/storage/testsuites/multivolume.go:298
... skipping 148 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] 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 (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on the same node","total":32,"completed":10,"skipped":742,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
... skipping 49 lines ...
Nov 15 22:54:44.961: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comnqdcv] to have phase Bound
Nov 15 22:54:45.070: INFO: PersistentVolumeClaim test.csi.azure.comnqdcv found but phase is Pending instead of Bound.
Nov 15 22:54:47.180: INFO: PersistentVolumeClaim test.csi.azure.comnqdcv found but phase is Pending instead of Bound.
Nov 15 22:54:49.290: INFO: PersistentVolumeClaim test.csi.azure.comnqdcv found and phase=Bound (4.32812264s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Nov 15 22:54:49.727: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-9s99x" in namespace "snapshotting-9659" to be "Succeeded or Failed"
Nov 15 22:54:49.837: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 109.235402ms
Nov 15 22:54:51.947: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219783816s
Nov 15 22:54:54.057: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.329147704s
Nov 15 22:54:56.167: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.43921418s
Nov 15 22:54:58.280: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.552502569s
Nov 15 22:55:00.389: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.661906699s
... skipping 31 lines ...
Nov 15 22:56:07.931: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m18.203119452s
Nov 15 22:56:10.042: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m20.314586735s
Nov 15 22:56:12.152: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m22.424028885s
Nov 15 22:56:14.261: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Pending", Reason="", readiness=false. Elapsed: 1m24.533752074s
Nov 15 22:56:16.371: INFO: Pod "pvc-snapshottable-tester-9s99x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m26.643126607s
STEP: Saw pod success
Nov 15 22:56:16.371: INFO: Pod "pvc-snapshottable-tester-9s99x" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Nov 15 22:56:16.480: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comnqdcv] to have phase Bound
Nov 15 22:56:16.588: INFO: PersistentVolumeClaim test.csi.azure.comnqdcv found and phase=Bound (108.598876ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Nov 15 22:56:16.948: INFO: Pod pvc-snapshottable-tester-9s99x has the following logs: 
... skipping 35 lines ...
Nov 15 22:56:29.804: INFO: WaitUntil finished successfully after 109.093544ms
STEP: getting the snapshot and snapshot content
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Nov 15 22:56:30.351: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-rmsvr" in namespace "snapshotting-9659" to be "Succeeded or Failed"
Nov 15 22:56:30.460: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 108.857368ms
Nov 15 22:56:32.569: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218081667s
Nov 15 22:56:34.678: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.327192997s
Nov 15 22:56:36.787: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.436101488s
Nov 15 22:56:38.903: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.552136381s
Nov 15 22:56:41.013: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.662417773s
... skipping 24 lines ...
Nov 15 22:57:33.779: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.427952727s
Nov 15 22:57:35.889: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.537816019s
Nov 15 22:57:37.998: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.647227933s
Nov 15 22:57:40.108: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.757123828s
Nov 15 22:57:42.220: INFO: Pod "pvc-snapshottable-data-tester-rmsvr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m11.868975442s
STEP: Saw pod success
Nov 15 22:57:42.220: INFO: Pod "pvc-snapshottable-data-tester-rmsvr" satisfied condition "Succeeded or Failed"
Nov 15 22:57:42.447: INFO: Pod pvc-snapshottable-data-tester-rmsvr has the following logs: 
Nov 15 22:57:42.447: INFO: Deleting pod "pvc-snapshottable-data-tester-rmsvr" in namespace "snapshotting-9659"
Nov 15 22:57:42.564: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-rmsvr" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the snapshot
Nov 15 22:58:01.117: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-c1byahsu.westeurope.cloudapp.azure.com --kubeconfig=/root/tmp2485039460/kubeconfig/kubeconfig.westeurope.json --namespace=snapshotting-9659 exec restored-pvc-tester-6dmlr --namespace=snapshotting-9659 -- cat /mnt/test/data'
... skipping 33 lines ...
Nov 15 22:58:27.405: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
Nov 15 22:58:28.516: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
Nov 15 22:58:29.626: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
Nov 15 22:58:30.738: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
Nov 15 22:58:31.848: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
Nov 15 22:58:32.972: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
Nov 15 22:58:33.972: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  test/e2e/storage/testsuites/snapshottable.go:172
Nov 15 22:58:34.081: INFO: Error getting logs for pod restored-pvc-tester-6dmlr: the server could not find the requested resource (get pods restored-pvc-tester-6dmlr)
Nov 15 22:58:34.081: INFO: Deleting pod "restored-pvc-tester-6dmlr" in namespace "snapshotting-9659"
Nov 15 22:58:34.190: INFO: deleting claim "snapshotting-9659"/"pvc-hqn8q"
Nov 15 22:58:34.298: INFO: deleting snapshot "snapshotting-9659"/"pre-provisioned-snapshot-c9ede0f7-c54d-47e3-980d-43d8d809f836"
Nov 15 22:58:34.407: INFO: deleting snapshot content "pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836"
Nov 15 22:58:34.741: INFO: Waiting up to 5m0s for volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 to be deleted
Nov 15 22:58:34.851: INFO: volumesnapshotcontents pre-provisioned-snapcontent-c9ede0f7-c54d-47e3-980d-43d8d809f836 has been found and is not deleted
... skipping 39 lines ...
    test/e2e/storage/testsuites/snapshottable.go:113
      
      test/e2e/storage/testsuites/snapshottable.go:176
        should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
        test/e2e/storage/testsuites/snapshottable.go:278
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)","total":41,"completed":9,"skipped":549,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 22:59:53.771: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 234 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] 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 (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node","total":40,"completed":7,"skipped":309,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:00:45.527: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 38 lines ...
Nov 15 22:57:40.581: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comg9bhp] to have phase Bound
Nov 15 22:57:40.692: INFO: PersistentVolumeClaim test.csi.azure.comg9bhp found but phase is Pending instead of Bound.
Nov 15 22:57:42.802: INFO: PersistentVolumeClaim test.csi.azure.comg9bhp found but phase is Pending instead of Bound.
Nov 15 22:57:44.911: INFO: PersistentVolumeClaim test.csi.azure.comg9bhp found and phase=Bound (4.329305095s)
STEP: Creating pod pod-subpath-test-dynamicpv-vpzx
STEP: Creating a pod to test subpath
Nov 15 22:57:45.252: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vpzx" in namespace "provisioning-2526" to be "Succeeded or Failed"
Nov 15 22:57:45.361: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 108.912672ms
Nov 15 22:57:47.470: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217836157s
Nov 15 22:57:49.591: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.339237093s
Nov 15 22:57:51.702: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.450187942s
Nov 15 22:57:53.812: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.559941526s
Nov 15 22:57:55.922: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.67017701s
... skipping 18 lines ...
Nov 15 22:58:36.060: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 50.808421302s
Nov 15 22:58:38.170: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 52.918496057s
Nov 15 22:58:40.288: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 55.035888132s
Nov 15 22:58:42.399: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Pending", Reason="", readiness=false. Elapsed: 57.147014756s
Nov 15 22:58:44.510: INFO: Pod "pod-subpath-test-dynamicpv-vpzx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 59.257920756s
STEP: Saw pod success
Nov 15 22:58:44.510: INFO: Pod "pod-subpath-test-dynamicpv-vpzx" satisfied condition "Succeeded or Failed"
Nov 15 22:58:44.619: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000000 pod pod-subpath-test-dynamicpv-vpzx container test-container-volume-dynamicpv-vpzx: <nil>
STEP: delete the pod
Nov 15 22:58:44.854: INFO: Waiting for pod pod-subpath-test-dynamicpv-vpzx to disappear
Nov 15 22:58:44.962: INFO: Pod pod-subpath-test-dynamicpv-vpzx no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vpzx
Nov 15 22:58:44.962: INFO: Deleting pod "pod-subpath-test-dynamicpv-vpzx" in namespace "provisioning-2526"
... skipping 41 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":31,"completed":10,"skipped":762,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support existing single file [LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:221
... skipping 17 lines ...
Nov 15 22:57:44.186: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comg4bcd] to have phase Bound
Nov 15 22:57:44.295: INFO: PersistentVolumeClaim test.csi.azure.comg4bcd found but phase is Pending instead of Bound.
Nov 15 22:57:46.407: INFO: PersistentVolumeClaim test.csi.azure.comg4bcd found but phase is Pending instead of Bound.
Nov 15 22:57:48.518: INFO: PersistentVolumeClaim test.csi.azure.comg4bcd found and phase=Bound (4.33240389s)
STEP: Creating pod pod-subpath-test-dynamicpv-48fw
STEP: Creating a pod to test subpath
Nov 15 22:57:48.854: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-48fw" in namespace "provisioning-1013" to be "Succeeded or Failed"
Nov 15 22:57:48.963: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 109.374866ms
Nov 15 22:57:51.074: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220413933s
Nov 15 22:57:53.187: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.332871721s
Nov 15 22:57:55.298: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.443678398s
Nov 15 22:57:57.408: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.553769243s
Nov 15 22:57:59.521: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.666969822s
... skipping 75 lines ...
Nov 15 23:00:40.003: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2m51.149185013s
Nov 15 23:00:42.114: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2m53.259753348s
Nov 15 23:00:44.228: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2m55.374214908s
Nov 15 23:00:46.338: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2m57.484366627s
Nov 15 23:00:48.448: INFO: Pod "pod-subpath-test-dynamicpv-48fw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2m59.594340874s
STEP: Saw pod success
Nov 15 23:00:48.448: INFO: Pod "pod-subpath-test-dynamicpv-48fw" satisfied condition "Succeeded or Failed"
Nov 15 23:00:48.565: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000000 pod pod-subpath-test-dynamicpv-48fw container test-container-subpath-dynamicpv-48fw: <nil>
STEP: delete the pod
Nov 15 23:00:48.814: INFO: Waiting for pod pod-subpath-test-dynamicpv-48fw to disappear
Nov 15 23:00:48.923: INFO: Pod pod-subpath-test-dynamicpv-48fw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-48fw
Nov 15 23:00:48.923: INFO: Deleting pod "pod-subpath-test-dynamicpv-48fw" in namespace "provisioning-1013"
... skipping 23 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":23,"completed":8,"skipped":993,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support existing directories when readOnly specified in the volumeSource
  test/e2e/storage/testsuites/subpath.go:397
... skipping 17 lines ...
Nov 15 22:58:50.630: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.coms8wqx] to have phase Bound
Nov 15 22:58:50.739: INFO: PersistentVolumeClaim test.csi.azure.coms8wqx found but phase is Pending instead of Bound.
Nov 15 22:58:52.850: INFO: PersistentVolumeClaim test.csi.azure.coms8wqx found but phase is Pending instead of Bound.
Nov 15 22:58:54.959: INFO: PersistentVolumeClaim test.csi.azure.coms8wqx found and phase=Bound (4.329693347s)
STEP: Creating pod pod-subpath-test-dynamicpv-vqll
STEP: Creating a pod to test subpath
Nov 15 22:58:55.288: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vqll" in namespace "provisioning-8337" to be "Succeeded or Failed"
Nov 15 22:58:55.397: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 108.647058ms
Nov 15 22:58:57.507: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218430597s
Nov 15 22:58:59.617: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328650898s
Nov 15 22:59:01.728: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 6.439808758s
Nov 15 22:59:03.838: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 8.549809115s
Nov 15 22:59:05.949: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 10.660600754s
... skipping 32 lines ...
Nov 15 23:00:15.623: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 1m20.33481159s
Nov 15 23:00:17.734: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 1m22.446112002s
Nov 15 23:00:19.845: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 1m24.557005984s
Nov 15 23:00:21.956: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 1m26.667908641s
Nov 15 23:00:24.066: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m28.777852824s
STEP: Saw pod success
Nov 15 23:00:24.066: INFO: Pod "pod-subpath-test-dynamicpv-vqll" satisfied condition "Succeeded or Failed"
Nov 15 23:00:24.176: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod pod-subpath-test-dynamicpv-vqll container test-container-subpath-dynamicpv-vqll: <nil>
STEP: delete the pod
Nov 15 23:00:24.427: INFO: Waiting for pod pod-subpath-test-dynamicpv-vqll to disappear
Nov 15 23:00:24.536: INFO: Pod pod-subpath-test-dynamicpv-vqll no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vqll
Nov 15 23:00:24.536: INFO: Deleting pod "pod-subpath-test-dynamicpv-vqll" in namespace "provisioning-8337"
STEP: Creating pod pod-subpath-test-dynamicpv-vqll
STEP: Creating a pod to test subpath
Nov 15 23:00:24.763: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vqll" in namespace "provisioning-8337" to be "Succeeded or Failed"
Nov 15 23:00:24.873: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 109.687968ms
Nov 15 23:00:26.984: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220379075s
Nov 15 23:00:29.095: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Pending", Reason="", readiness=false. Elapsed: 4.331893226s
Nov 15 23:00:31.206: INFO: Pod "pod-subpath-test-dynamicpv-vqll": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.442751313s
STEP: Saw pod success
Nov 15 23:00:31.206: INFO: Pod "pod-subpath-test-dynamicpv-vqll" satisfied condition "Succeeded or Failed"
Nov 15 23:00:31.316: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod pod-subpath-test-dynamicpv-vqll container test-container-subpath-dynamicpv-vqll: <nil>
STEP: delete the pod
Nov 15 23:00:31.545: INFO: Waiting for pod pod-subpath-test-dynamicpv-vqll to disappear
Nov 15 23:00:31.654: INFO: Pod pod-subpath-test-dynamicpv-vqll no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-vqll
Nov 15 23:00:31.654: INFO: Deleting pod "pod-subpath-test-dynamicpv-vqll" in namespace "provisioning-8337"
... skipping 41 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":32,"completed":11,"skipped":766,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:02:45.551: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 45 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 49 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (block volmode) (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 (block volmode) (late-binding)] ephemeral should support multiple inline ephemeral volumes","total":40,"completed":8,"skipped":435,"failed":0}

SSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral 
  should support two pods which have the same volume definition
  test/e2e/storage/testsuites/ephemeral.go:216
... skipping 61 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (block volmode) (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 (block volmode) (late-binding)] ephemeral should support two pods which have the same volume definition","total":30,"completed":10,"skipped":808,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] 
  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
... skipping 190 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] 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 (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node","total":41,"completed":10,"skipped":620,"failed":0}

SSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support file as subpath [LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:232
... skipping 18 lines ...
Nov 15 23:01:00.040: INFO: PersistentVolumeClaim test.csi.azure.comw6vkm found but phase is Pending instead of Bound.
Nov 15 23:01:02.150: INFO: PersistentVolumeClaim test.csi.azure.comw6vkm found but phase is Pending instead of Bound.
Nov 15 23:01:04.262: INFO: PersistentVolumeClaim test.csi.azure.comw6vkm found but phase is Pending instead of Bound.
Nov 15 23:01:06.376: INFO: PersistentVolumeClaim test.csi.azure.comw6vkm found and phase=Bound (6.446052369s)
STEP: Creating pod pod-subpath-test-dynamicpv-8kb7
STEP: Creating a pod to test atomic-volume-subpath
Nov 15 23:01:06.708: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8kb7" in namespace "provisioning-8992" to be "Succeeded or Failed"
Nov 15 23:01:06.820: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Pending", Reason="", readiness=false. Elapsed: 112.78976ms
Nov 15 23:01:08.933: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.225776295s
Nov 15 23:01:11.045: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.337072647s
Nov 15 23:01:13.158: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.450023349s
Nov 15 23:01:15.269: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.561391622s
Nov 15 23:01:17.380: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.672233808s
... skipping 44 lines ...
Nov 15 23:02:52.425: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Running", Reason="", readiness=true. Elapsed: 1m45.717169919s
Nov 15 23:02:54.539: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Running", Reason="", readiness=true. Elapsed: 1m47.831231791s
Nov 15 23:02:56.649: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Running", Reason="", readiness=true. Elapsed: 1m49.941446455s
Nov 15 23:02:58.760: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.052060678s
Nov 15 23:03:00.870: INFO: Pod "pod-subpath-test-dynamicpv-8kb7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m54.161999533s
STEP: Saw pod success
Nov 15 23:03:00.870: INFO: Pod "pod-subpath-test-dynamicpv-8kb7" satisfied condition "Succeeded or Failed"
Nov 15 23:03:00.980: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod pod-subpath-test-dynamicpv-8kb7 container test-container-subpath-dynamicpv-8kb7: <nil>
STEP: delete the pod
Nov 15 23:03:01.232: INFO: Waiting for pod pod-subpath-test-dynamicpv-8kb7 to disappear
Nov 15 23:03:01.341: INFO: Pod pod-subpath-test-dynamicpv-8kb7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8kb7
Nov 15 23:03:01.341: INFO: Deleting pod "pod-subpath-test-dynamicpv-8kb7" in namespace "provisioning-8992"
... skipping 25 lines ...
  test/e2e/storage/framework/testsuite.go:50
    should support file as subpath [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:232
------------------------------
SS
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":31,"completed":11,"skipped":805,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:03:43.233: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 45 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

    Distro debian doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 145 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":33,"completed":8,"skipped":558,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] volumes 
  should allow exec of files on the volume
  test/e2e/storage/testsuites/volumes.go:198
... skipping 17 lines ...
Nov 15 23:02:46.663: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com7ng4l] to have phase Bound
Nov 15 23:02:46.772: INFO: PersistentVolumeClaim test.csi.azure.com7ng4l found but phase is Pending instead of Bound.
Nov 15 23:02:48.883: INFO: PersistentVolumeClaim test.csi.azure.com7ng4l found but phase is Pending instead of Bound.
Nov 15 23:02:50.992: INFO: PersistentVolumeClaim test.csi.azure.com7ng4l found and phase=Bound (4.328979018s)
STEP: Creating pod exec-volume-test-dynamicpv-bm7h
STEP: Creating a pod to test exec-volume-test
Nov 15 23:02:51.346: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-bm7h" in namespace "volume-1237" to be "Succeeded or Failed"
Nov 15 23:02:51.466: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 119.481939ms
Nov 15 23:02:53.576: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.230029685s
Nov 15 23:02:55.687: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.340393102s
Nov 15 23:02:57.798: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.451539045s
Nov 15 23:02:59.909: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.562809997s
Nov 15 23:03:02.019: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.672890491s
... skipping 13 lines ...
Nov 15 23:03:31.565: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 40.218684243s
Nov 15 23:03:33.676: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 42.329148978s
Nov 15 23:03:35.785: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 44.439004337s
Nov 15 23:03:37.896: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Pending", Reason="", readiness=false. Elapsed: 46.549663549s
Nov 15 23:03:40.022: INFO: Pod "exec-volume-test-dynamicpv-bm7h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.675997667s
STEP: Saw pod success
Nov 15 23:03:40.022: INFO: Pod "exec-volume-test-dynamicpv-bm7h" satisfied condition "Succeeded or Failed"
Nov 15 23:03:40.132: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000000 pod exec-volume-test-dynamicpv-bm7h container exec-container-dynamicpv-bm7h: <nil>
STEP: delete the pod
Nov 15 23:03:40.398: INFO: Waiting for pod exec-volume-test-dynamicpv-bm7h to disappear
Nov 15 23:03:40.508: INFO: Pod exec-volume-test-dynamicpv-bm7h no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-bm7h
Nov 15 23:03:40.508: INFO: Deleting pod "exec-volume-test-dynamicpv-bm7h" in namespace "volume-1237"
... skipping 21 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] 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 (ext4)] volumes should allow exec of files on the volume","total":32,"completed":12,"skipped":922,"failed":0}

SSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] 
  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
... skipping 196 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ext4)] 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 (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node","total":40,"completed":9,"skipped":441,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:06:06.615: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 182 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
    test/e2e/storage/testsuites/multivolume.go:323
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":23,"completed":9,"skipped":1008,"failed":0}

SSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  
  should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
... skipping 10 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Nov 15 23:03:44.047: INFO: Creating resource for dynamic PV
Nov 15 23:03:44.047: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1231-e2e-scjr856
STEP: [init] starting a pod to use the claim
Nov 15 23:03:44.271: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-fz5zp" in namespace "snapshotting-1231" to be "Succeeded or Failed"
Nov 15 23:03:44.381: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 109.798245ms
Nov 15 23:03:46.492: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220471559s
Nov 15 23:03:48.610: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.338616994s
Nov 15 23:03:50.721: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.449958853s
Nov 15 23:03:52.835: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.562987589s
Nov 15 23:03:54.946: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.674314539s
... skipping 29 lines ...
Nov 15 23:04:58.293: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 1m14.02127104s
Nov 15 23:05:00.414: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 1m16.142113642s
Nov 15 23:05:02.525: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 1m18.253528135s
Nov 15 23:05:04.637: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Pending", Reason="", readiness=false. Elapsed: 1m20.365061451s
Nov 15 23:05:06.747: INFO: Pod "pvc-snapshottable-tester-fz5zp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m22.475773873s
STEP: Saw pod success
Nov 15 23:05:06.747: INFO: Pod "pvc-snapshottable-tester-fz5zp" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
STEP: creating a dynamic VolumeSnapshot
Nov 15 23:05:07.194: INFO: Waiting up to 5m0s for VolumeSnapshot snapshot-krc5t to become ready
Nov 15 23:05:07.304: INFO: VolumeSnapshot snapshot-krc5t found but is not ready.
Nov 15 23:05:09.428: INFO: VolumeSnapshot snapshot-krc5t found but is not ready.
... skipping 49 lines ...
    test/e2e/storage/testsuites/snapshottable.go:113
      
      test/e2e/storage/testsuites/snapshottable.go:176
        should check snapshot fields, check restore correctly works, check deletion (ephemeral)
        test/e2e/storage/testsuites/snapshottable.go:177
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  should check snapshot fields, check restore correctly works, check deletion (ephemeral)","total":31,"completed":12,"skipped":854,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 146 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":33,"completed":9,"skipped":574,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:06:41.316: INFO: Distro debian doesn't support ntfs -- 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 (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

    Distro debian doesn't support ntfs -- skipping

    test/e2e/storage/framework/testsuite.go:127
------------------------------
... skipping 47 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Nov 15 23:06:41.526: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.json
STEP: Building a namespace api object, basename topology
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 schedule a pod which has topologies that conflict with AllowedTopologies
  test/e2e/storage/testsuites/topology.go:194
Nov 15 23:06:42.283: INFO: Driver didn't provide topology keys -- skipping
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/framework/framework.go:188
Nov 15 23:06:42.284: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "topology-8978" for this suite.


S [SKIPPING] [1.083 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 [Measurement]
    test/e2e/storage/testsuites/topology.go:194

    Driver didn't provide topology keys -- skipping

    test/e2e/storage/testsuites/topology.go:126
------------------------------
... skipping 92 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 223 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with different volume mode and retain data across pod recreation on different node
    test/e2e/storage/testsuites/multivolume.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node","total":41,"completed":11,"skipped":761,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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]
  test/e2e/storage/testsuites/subpath.go:447
... skipping 57 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":23,"completed":10,"skipped":1020,"failed":0}

SSS
------------------------------
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 52 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":32,"completed":13,"skipped":925,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:08:04.271: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 246 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":30,"completed":11,"skipped":825,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:08:25.580: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 91 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":40,"completed":10,"skipped":567,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
... skipping 377 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:50
    should provision storage with pvc data source in parallel [Slow]
    test/e2e/storage/testsuites/provisioning.go:459
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source in parallel [Slow]","total":31,"completed":13,"skipped":957,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:10:11.499: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 48 lines ...
Nov 15 23:08:26.593: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comm8x26] to have phase Bound
Nov 15 23:08:26.703: INFO: PersistentVolumeClaim test.csi.azure.comm8x26 found but phase is Pending instead of Bound.
Nov 15 23:08:28.814: INFO: PersistentVolumeClaim test.csi.azure.comm8x26 found but phase is Pending instead of Bound.
Nov 15 23:08:30.925: INFO: PersistentVolumeClaim test.csi.azure.comm8x26 found and phase=Bound (4.331554995s)
STEP: Creating pod pod-subpath-test-dynamicpv-l8xp
STEP: Creating a pod to test multi_subpath
Nov 15 23:08:31.258: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-l8xp" in namespace "provisioning-773" to be "Succeeded or Failed"
Nov 15 23:08:31.369: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 111.154297ms
Nov 15 23:08:33.481: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222325744s
Nov 15 23:08:35.592: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.333890528s
Nov 15 23:08:37.704: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.44591651s
Nov 15 23:08:39.815: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.556780693s
Nov 15 23:08:41.925: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.666954677s
... skipping 9 lines ...
Nov 15 23:09:03.033: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 31.774332895s
Nov 15 23:09:05.143: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 33.884668174s
Nov 15 23:09:07.258: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.000294903s
Nov 15 23:09:09.370: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Pending", Reason="", readiness=false. Elapsed: 38.111477348s
Nov 15 23:09:11.481: INFO: Pod "pod-subpath-test-dynamicpv-l8xp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.222449242s
STEP: Saw pod success
Nov 15 23:09:11.481: INFO: Pod "pod-subpath-test-dynamicpv-l8xp" satisfied condition "Succeeded or Failed"
Nov 15 23:09:11.591: INFO: Trying to get logs from node k8s-agentpool1-96866028-vmss000002 pod pod-subpath-test-dynamicpv-l8xp container test-container-subpath-dynamicpv-l8xp: <nil>
STEP: delete the pod
Nov 15 23:09:11.866: INFO: Waiting for pod pod-subpath-test-dynamicpv-l8xp to disappear
Nov 15 23:09:11.976: INFO: Pod pod-subpath-test-dynamicpv-l8xp no longer exists
STEP: Deleting pod
Nov 15 23:09:11.976: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8xp" in namespace "provisioning-773"
... skipping 27 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":30,"completed":12,"skipped":918,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:10:24.481: 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 (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 67 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block 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 (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]","total":40,"completed":11,"skipped":656,"failed":0}

SSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] 
  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
... skipping 188 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block 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 (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node","total":41,"completed":12,"skipped":819,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] 
  should concurrently access the single read-only volume from pods on the same node
  test/e2e/storage/testsuites/multivolume.go:423
... skipping 88 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (block 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 (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":30,"completed":13,"skipped":969,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
Nov 15 23:12:16.055: INFO: Running AfterSuite actions on all nodes
Nov 15 23:12:16.055: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Nov 15 23:12:16.055: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
... skipping 62 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":40,"completed":12,"skipped":661,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:13:29.283: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 147 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (block volmode) (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 (block volmode) (late-binding)] ephemeral should create read/write inline ephemeral volume","total":41,"completed":13,"skipped":838,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Nov 15 23:13:31.699: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 42 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Nov 15 23:13:31.721: INFO: >>> kubeConfig: /root/tmp2485039460/kubeconfig/kubeconfig.westeurope.json
STEP: Building a namespace api object, basename topology
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 schedule a pod which has topologies that conflict with AllowedTopologies
  test/e2e/storage/testsuites/topology.go:194
Nov 15 23:13:32.489: INFO: Driver didn't provide topology keys -- skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/framework/framework.go:188
Nov 15 23:13:32.489: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "topology-4116" for this suite.


S [SKIPPING] [0.991 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 [Measurement]
    test/e2e/storage/testsuites/topology.go:194

    Driver didn't provide topology keys -- skipping

    test/e2e/storage/testsuites/topology.go:126
------------------------------
... skipping 75 lines ...