This job view page is being replaced by Spyglass soon. Check out the new job view.

PR	hccheng72: [V2] fix: prevent requesting replica attachment in a row for one volume
Result	ABORTED
Tests	0 failed / 0 succeeded
Started	2023-01-18 23:05
Elapsed	1h12m
Revision	d8ba0aca670d0c02f92f6a79df1d42fdac692933
Refs	1693

• artifacts
• build log

No Test Failures!

---

Error lines from build-log.txt

• Expand Skipped Lines
• Raw build-log.txt

... skipping 244 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11345  100 11345    0     0   173k      0 --:--:-- --:--:-- --:--:--  173k
Downloading https://get.helm.sh/helm-v3.11.0-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-e549890dfb2509639488eabe74ec6eabdacdbd4d || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d not found: manifest unknown: manifest tagged by "latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d" 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-e549890dfb2509639488eabe74ec6eabdacdbd4d -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=e549890dfb2509639488eabe74ec6eabdacdbd4d -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-18T23:09:58Z -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 687 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d not found: manifest unknown: manifest tagged by "latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d" 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 1046 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 1069 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 353 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 122 lines ...
  test/e2e/framework/framework.go:188
Jan 18 23:21:40.741: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumelimits-7364" 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":18,"completed":1,"skipped":119,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
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
... skipping 2 lines ...
STEP: Building a namespace api object, basename provisioning
W0118 23:21:39.358028   41711 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Jan 18 23:21:39.358: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled
Jan 18 23:21:39.465: INFO: No PSP annotation exists on dry run pod; assuming PodSecurityPolicy is disabled
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
Jan 18 23:21:39.891: INFO: Creating resource for dynamic PV
Jan 18 23:21:39.891: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9579-e2e-sctcxk5
STEP: creating a claim
Jan 18 23:21:39.999: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jan 18 23:21:40.108: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com75ffv] to have phase Bound
Jan 18 23:21:40.215: INFO: PersistentVolumeClaim test.csi.azure.com75ffv found but phase is Pending instead of Bound.
Jan 18 23:21:42.324: INFO: PersistentVolumeClaim test.csi.azure.com75ffv found but phase is Pending instead of Bound.
Jan 18 23:21:44.432: INFO: PersistentVolumeClaim test.csi.azure.com75ffv found and phase=Bound (4.323954118s)
STEP: Creating pod pod-subpath-test-dynamicpv-68hb
STEP: Checking for subpath error in container status
Jan 18 23:22:20.975: INFO: Deleting pod "pod-subpath-test-dynamicpv-68hb" in namespace "provisioning-9579"
Jan 18 23:22:21.084: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-68hb" to be fully deleted
STEP: Deleting pod
Jan 18 23:22:23.329: INFO: Deleting pod "pod-subpath-test-dynamicpv-68hb" in namespace "provisioning-9579"
STEP: Deleting pvc
Jan 18 23:22:23.435: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com75ffv"
... skipping 16 lines ...

• [SLOW TEST:86.130 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":30,"completed":1,"skipped":17,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support existing directory
  test/e2e/storage/testsuites/subpath.go:207
... skipping 20 lines ...
Jan 18 23:21:40.153: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comnzh6p] to have phase Bound
Jan 18 23:21:40.261: INFO: PersistentVolumeClaim test.csi.azure.comnzh6p found but phase is Pending instead of Bound.
Jan 18 23:21:42.370: INFO: PersistentVolumeClaim test.csi.azure.comnzh6p found but phase is Pending instead of Bound.
Jan 18 23:21:44.478: INFO: PersistentVolumeClaim test.csi.azure.comnzh6p found and phase=Bound (4.325342504s)
STEP: Creating pod pod-subpath-test-dynamicpv-xpvr
STEP: Creating a pod to test subpath
Jan 18 23:21:44.802: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xpvr" in namespace "provisioning-5504" to be "Succeeded or Failed"
Jan 18 23:21:44.913: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 110.433284ms
Jan 18 23:21:47.022: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219776648s
Jan 18 23:21:49.130: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328047448s
Jan 18 23:21:51.240: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437093087s
Jan 18 23:21:53.348: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545849887s
Jan 18 23:21:55.457: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.654353982s
... skipping 8 lines ...
Jan 18 23:22:14.438: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 29.636007365s
Jan 18 23:22:16.547: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 31.74442495s
Jan 18 23:22:18.656: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 33.853945194s
Jan 18 23:22:20.765: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Pending", Reason="", readiness=false. Elapsed: 35.962475506s
Jan 18 23:22:22.874: INFO: Pod "pod-subpath-test-dynamicpv-xpvr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.07207416s
STEP: Saw pod success
Jan 18 23:22:22.875: INFO: Pod "pod-subpath-test-dynamicpv-xpvr" satisfied condition "Succeeded or Failed"
Jan 18 23:22:22.983: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod pod-subpath-test-dynamicpv-xpvr container test-container-volume-dynamicpv-xpvr: <nil>
STEP: delete the pod
Jan 18 23:22:23.238: INFO: Waiting for pod pod-subpath-test-dynamicpv-xpvr to disappear
Jan 18 23:22:23.345: INFO: Pod pod-subpath-test-dynamicpv-xpvr no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xpvr
Jan 18 23:22:23.345: INFO: Deleting pod "pod-subpath-test-dynamicpv-xpvr" in namespace "provisioning-5504"
... 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 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":38,"completed":1,"skipped":17,"failed":0}

S
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support creating multiple subpath from same volumes [Slow]
  test/e2e/storage/testsuites/subpath.go:296
... skipping 17 lines ...
Jan 18 23:21:41.236: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com4jpqp] to have phase Bound
Jan 18 23:21:41.344: INFO: PersistentVolumeClaim test.csi.azure.com4jpqp found but phase is Pending instead of Bound.
Jan 18 23:21:43.453: INFO: PersistentVolumeClaim test.csi.azure.com4jpqp found but phase is Pending instead of Bound.
Jan 18 23:21:45.563: INFO: PersistentVolumeClaim test.csi.azure.com4jpqp found and phase=Bound (4.326483927s)
STEP: Creating pod pod-subpath-test-dynamicpv-z7sl
STEP: Creating a pod to test multi_subpath
Jan 18 23:21:45.889: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-z7sl" in namespace "provisioning-5272" to be "Succeeded or Failed"
Jan 18 23:21:45.997: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 107.920301ms
Jan 18 23:21:48.106: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216513224s
Jan 18 23:21:50.215: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325741435s
Jan 18 23:21:52.323: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434281126s
Jan 18 23:21:54.433: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544092411s
Jan 18 23:21:56.542: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.653428616s
... skipping 10 lines ...
Jan 18 23:22:19.750: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 33.861145595s
Jan 18 23:22:21.859: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 35.970024242s
Jan 18 23:22:23.968: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 38.079359922s
Jan 18 23:22:26.077: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Pending", Reason="", readiness=false. Elapsed: 40.188190451s
Jan 18 23:22:28.186: INFO: Pod "pod-subpath-test-dynamicpv-z7sl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.297274674s
STEP: Saw pod success
Jan 18 23:22:28.186: INFO: Pod "pod-subpath-test-dynamicpv-z7sl" satisfied condition "Succeeded or Failed"
Jan 18 23:22:28.294: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000002 pod pod-subpath-test-dynamicpv-z7sl container test-container-subpath-dynamicpv-z7sl: <nil>
STEP: delete the pod
Jan 18 23:22:28.544: INFO: Waiting for pod pod-subpath-test-dynamicpv-z7sl to disappear
Jan 18 23:22:28.655: INFO: Pod pod-subpath-test-dynamicpv-z7sl no longer exists
STEP: Deleting pod
Jan 18 23:22:28.656: INFO: Deleting pod "pod-subpath-test-dynamicpv-z7sl" in namespace "provisioning-5272"
... skipping 21 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":36,"completed":1,"skipped":20,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
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 ...
Jan 18 23:21:41.953: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comh6w24] to have phase Bound
Jan 18 23:21:42.061: INFO: PersistentVolumeClaim test.csi.azure.comh6w24 found but phase is Pending instead of Bound.
Jan 18 23:21:44.169: INFO: PersistentVolumeClaim test.csi.azure.comh6w24 found but phase is Pending instead of Bound.
Jan 18 23:21:46.277: INFO: PersistentVolumeClaim test.csi.azure.comh6w24 found and phase=Bound (4.323880538s)
STEP: Creating pod exec-volume-test-dynamicpv-vql2
STEP: Creating a pod to test exec-volume-test
Jan 18 23:21:46.599: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-vql2" in namespace "volume-6399" to be "Succeeded or Failed"
Jan 18 23:21:46.707: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 108.118765ms
Jan 18 23:21:48.814: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215646888s
Jan 18 23:21:50.922: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323852964s
Jan 18 23:21:53.030: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.431705863s
Jan 18 23:21:55.139: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54019367s
Jan 18 23:21:57.248: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.649471896s
... skipping 10 lines ...
Jan 18 23:22:20.442: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.84347376s
Jan 18 23:22:22.551: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 35.952167229s
Jan 18 23:22:24.658: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 38.059727307s
Jan 18 23:22:26.766: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Pending", Reason="", readiness=false. Elapsed: 40.167563776s
Jan 18 23:22:28.877: INFO: Pod "exec-volume-test-dynamicpv-vql2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.277954338s
STEP: Saw pod success
Jan 18 23:22:28.877: INFO: Pod "exec-volume-test-dynamicpv-vql2" satisfied condition "Succeeded or Failed"
Jan 18 23:22:28.983: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod exec-volume-test-dynamicpv-vql2 container exec-container-dynamicpv-vql2: <nil>
STEP: delete the pod
Jan 18 23:22:29.209: INFO: Waiting for pod exec-volume-test-dynamicpv-vql2 to disappear
Jan 18 23:22:29.316: INFO: Pod exec-volume-test-dynamicpv-vql2 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-vql2
Jan 18 23:22:29.316: INFO: Deleting pod "exec-volume-test-dynamicpv-vql2" in namespace "volume-6399"
... skipping 21 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":18,"completed":2,"skipped":137,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:23:11.084: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 152 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":41,"completed":1,"skipped":8,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:24:42.755: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 71 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":30,"completed":2,"skipped":72,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:25:23.222: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 153 lines ...
Jan 18 23:21:40.179: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comcqt2z] to have phase Bound
Jan 18 23:21:40.286: INFO: PersistentVolumeClaim test.csi.azure.comcqt2z found but phase is Pending instead of Bound.
Jan 18 23:21:42.393: INFO: PersistentVolumeClaim test.csi.azure.comcqt2z found but phase is Pending instead of Bound.
Jan 18 23:21:44.501: INFO: PersistentVolumeClaim test.csi.azure.comcqt2z found and phase=Bound (4.321952777s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Jan 18 23:21:44.935: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-dglc9" in namespace "snapshotting-9636" to be "Succeeded or Failed"
Jan 18 23:21:45.043: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 107.088148ms
Jan 18 23:21:47.151: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215110368s
Jan 18 23:21:49.258: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322547256s
Jan 18 23:21:51.366: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.430669445s
Jan 18 23:21:53.475: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539828841s
Jan 18 23:21:55.584: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.648645062s
... skipping 7 lines ...
Jan 18 23:22:12.451: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 27.515943345s
Jan 18 23:22:14.562: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 29.626031027s
Jan 18 23:22:16.671: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 31.735380796s
Jan 18 23:22:18.778: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.842929794s
Jan 18 23:22:20.887: INFO: Pod "pvc-snapshottable-tester-dglc9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.951354989s
STEP: Saw pod success
Jan 18 23:22:20.887: INFO: Pod "pvc-snapshottable-tester-dglc9" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Jan 18 23:22:20.994: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comcqt2z] to have phase Bound
Jan 18 23:22:21.102: INFO: PersistentVolumeClaim test.csi.azure.comcqt2z found and phase=Bound (107.713257ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Jan 18 23:22:21.450: INFO: Pod pvc-snapshottable-tester-dglc9 has the following logs: 
... skipping 33 lines ...
Jan 18 23:22:29.741: INFO: WaitUntil finished successfully after 111.042991ms
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
Jan 18 23:22:30.287: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-cf26g" in namespace "snapshotting-9636" to be "Succeeded or Failed"
Jan 18 23:22:30.394: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 107.094514ms
Jan 18 23:22:32.503: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216277377s
Jan 18 23:22:34.612: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324627886s
Jan 18 23:22:36.720: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433308723s
Jan 18 23:22:38.830: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542773097s
Jan 18 23:22:40.939: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651776994s
... skipping 27 lines ...
Jan 18 23:23:40.004: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.716984229s
Jan 18 23:23:42.112: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Pending", Reason="", readiness=false. Elapsed: 1m11.824939362s
Jan 18 23:23:44.221: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Running", Reason="", readiness=false. Elapsed: 1m13.933813958s
Jan 18 23:23:46.330: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.043214255s
Jan 18 23:23:48.440: INFO: Pod "pvc-snapshottable-data-tester-cf26g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m18.152573819s
STEP: Saw pod success
Jan 18 23:23:48.440: INFO: Pod "pvc-snapshottable-data-tester-cf26g" satisfied condition "Succeeded or Failed"
Jan 18 23:23:48.658: INFO: Pod pvc-snapshottable-data-tester-cf26g has the following logs: 
Jan 18 23:23:48.658: INFO: Deleting pod "pvc-snapshottable-data-tester-cf26g" in namespace "snapshotting-9636"
Jan 18 23:23:48.772: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-cf26g" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the snapshot
Jan 18 23:25:35.316: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-lnogpxmn.westeurope.cloudapp.azure.com --kubeconfig=/root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json --namespace=snapshotting-9636 exec restored-pvc-tester-m6lq8 --namespace=snapshotting-9636 -- cat /mnt/test/data'
... skipping 33 lines ...
Jan 18 23:26:01.553: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
Jan 18 23:26:02.663: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
Jan 18 23:26:03.771: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
Jan 18 23:26:04.879: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
Jan 18 23:26:05.988: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
Jan 18 23:26:07.096: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
Jan 18 23:26:08.097: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  test/e2e/storage/testsuites/snapshottable.go:172
Jan 18 23:26:08.203: INFO: Error getting logs for pod restored-pvc-tester-m6lq8: the server could not find the requested resource (get pods restored-pvc-tester-m6lq8)
Jan 18 23:26:08.203: INFO: Deleting pod "restored-pvc-tester-m6lq8" in namespace "snapshotting-9636"
Jan 18 23:26:08.311: INFO: deleting claim "snapshotting-9636"/"pvc-2vm6v"
Jan 18 23:26:08.418: INFO: deleting snapshot "snapshotting-9636"/"pre-provisioned-snapshot-05f50d2b-66b8-4085-8b6d-7b9069995a63"
Jan 18 23:26:08.525: INFO: deleting snapshot content "pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63"
Jan 18 23:26:08.863: INFO: Waiting up to 5m0s for volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 to be deleted
Jan 18 23:26:08.971: INFO: volumesnapshotcontents pre-provisioned-snapcontent-05f50d2b-66b8-4085-8b6d-7b9069995a63 has been found and is not deleted
... skipping 27 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":35,"completed":1,"skipped":38,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:26:26.499: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 166 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":32,"completed":1,"skipped":87,"failed":0}

SSS
------------------------------
[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 97 lines ...
Jan 18 23:23:12.058: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com695r7] to have phase Bound
Jan 18 23:23:12.165: INFO: PersistentVolumeClaim test.csi.azure.com695r7 found but phase is Pending instead of Bound.
Jan 18 23:23:14.272: INFO: PersistentVolumeClaim test.csi.azure.com695r7 found but phase is Pending instead of Bound.
Jan 18 23:23:16.380: INFO: PersistentVolumeClaim test.csi.azure.com695r7 found and phase=Bound (4.321527545s)
STEP: Creating pod exec-volume-test-dynamicpv-ll5p
STEP: Creating a pod to test exec-volume-test
Jan 18 23:23:16.711: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ll5p" in namespace "volume-4179" to be "Succeeded or Failed"
Jan 18 23:23:16.840: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 129.527524ms
Jan 18 23:23:18.948: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237315661s
Jan 18 23:23:21.066: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.354875752s
Jan 18 23:23:23.174: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.462578353s
Jan 18 23:23:25.281: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.570047212s
Jan 18 23:23:27.389: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.678009753s
... skipping 42 lines ...
Jan 18 23:24:58.059: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 1m41.348506156s
Jan 18 23:25:00.167: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 1m43.456518142s
Jan 18 23:25:02.275: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 1m45.564481224s
Jan 18 23:25:04.384: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Pending", Reason="", readiness=false. Elapsed: 1m47.673113799s
Jan 18 23:25:06.493: INFO: Pod "exec-volume-test-dynamicpv-ll5p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m49.782199654s
STEP: Saw pod success
Jan 18 23:25:06.493: INFO: Pod "exec-volume-test-dynamicpv-ll5p" satisfied condition "Succeeded or Failed"
Jan 18 23:25:06.601: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000002 pod exec-volume-test-dynamicpv-ll5p container exec-container-dynamicpv-ll5p: <nil>
STEP: delete the pod
Jan 18 23:25:06.845: INFO: Waiting for pod exec-volume-test-dynamicpv-ll5p to disappear
Jan 18 23:25:06.956: INFO: Pod exec-volume-test-dynamicpv-ll5p no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-ll5p
Jan 18 23:25:06.956: INFO: Deleting pod "exec-volume-test-dynamicpv-ll5p" in namespace "volume-4179"
... skipping 39 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":18,"completed":3,"skipped":169,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:27:20.702: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 193 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":38,"completed":2,"skipped":18,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:27:38.004: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/framework/framework.go:188

... skipping 158 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":41,"completed":2,"skipped":139,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] provisioning 
  should provision storage with pvc data source in parallel [Slow]
  test/e2e/storage/testsuites/provisioning.go:459
... skipping 336 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":36,"completed":2,"skipped":40,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:28:43.064: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 174 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":3,"skipped":283,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:28:48.359: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 3 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 77 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":38,"completed":3,"skipped":45,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Pre-provisioned 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 ...
Jan 18 23:26:38.669: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comx9qv2] to have phase Bound
Jan 18 23:26:38.778: INFO: PersistentVolumeClaim test.csi.azure.comx9qv2 found but phase is Pending instead of Bound.
Jan 18 23:26:40.888: INFO: PersistentVolumeClaim test.csi.azure.comx9qv2 found but phase is Pending instead of Bound.
Jan 18 23:26:42.999: INFO: PersistentVolumeClaim test.csi.azure.comx9qv2 found and phase=Bound (4.329262296s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Jan 18 23:26:43.435: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-cgwfc" in namespace "snapshotting-6018" to be "Succeeded or Failed"
Jan 18 23:26:43.544: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 108.137998ms
Jan 18 23:26:45.654: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218097567s
Jan 18 23:26:47.764: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328558377s
Jan 18 23:26:49.873: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437338263s
Jan 18 23:26:51.982: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.546202335s
Jan 18 23:26:54.092: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.656645202s
Jan 18 23:26:56.202: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.76639216s
Jan 18 23:26:58.312: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.876504756s
Jan 18 23:27:00.422: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.986927125s
Jan 18 23:27:02.533: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.097966014s
Jan 18 23:27:04.643: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Pending", Reason="", readiness=false. Elapsed: 21.207444002s
Jan 18 23:27:06.753: INFO: Pod "pvc-snapshottable-tester-cgwfc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.317666686s
STEP: Saw pod success
Jan 18 23:27:06.753: INFO: Pod "pvc-snapshottable-tester-cgwfc" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Jan 18 23:27:06.873: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comx9qv2] to have phase Bound
Jan 18 23:27:06.982: INFO: PersistentVolumeClaim test.csi.azure.comx9qv2 found and phase=Bound (108.751085ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Jan 18 23:27:07.333: INFO: Pod pvc-snapshottable-tester-cgwfc has the following logs: 
... skipping 32 lines ...
Jan 18 23:27:13.564: INFO: WaitUntil finished successfully after 108.517928ms
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
Jan 18 23:27:14.111: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-6sqbr" in namespace "snapshotting-6018" to be "Succeeded or Failed"
Jan 18 23:27:14.219: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 107.959657ms
Jan 18 23:27:16.329: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217816181s
Jan 18 23:27:18.440: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328840708s
Jan 18 23:27:20.549: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437907935s
Jan 18 23:27:22.658: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547736803s
Jan 18 23:27:24.770: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.658917358s
... skipping 20 lines ...
Jan 18 23:28:09.094: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 54.983707468s
Jan 18 23:28:11.207: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 57.096254652s
Jan 18 23:28:13.318: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 59.207310165s
Jan 18 23:28:15.429: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.318724171s
Jan 18 23:28:17.540: INFO: Pod "pvc-snapshottable-data-tester-6sqbr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m3.429723794s
STEP: Saw pod success
Jan 18 23:28:17.541: INFO: Pod "pvc-snapshottable-data-tester-6sqbr" satisfied condition "Succeeded or Failed"
Jan 18 23:28:17.766: INFO: Pod pvc-snapshottable-data-tester-6sqbr has the following logs: 
Jan 18 23:28:17.766: INFO: Deleting pod "pvc-snapshottable-data-tester-6sqbr" in namespace "snapshotting-6018"
Jan 18 23:28:17.880: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-6sqbr" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the snapshot
Jan 18 23:28:50.432: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-lnogpxmn.westeurope.cloudapp.azure.com --kubeconfig=/root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json --namespace=snapshotting-6018 exec restored-pvc-tester-pvklj --namespace=snapshotting-6018 -- 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: Pre-provisioned 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":32,"completed":2,"skipped":141,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:29:34.695: 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 154 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":18,"completed":4,"skipped":301,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:29:49.224: 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 123 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":35,"completed":2,"skipped":145,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
Jan 18 23:28:30.945: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 18 23:28:31.702: INFO: Creating resource for dynamic PV
Jan 18 23:28:31.702: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9850-e2e-scdrw4h
STEP: creating a claim
Jan 18 23:28:31.812: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jan 18 23:28:31.925: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com96qpt] to have phase Bound
Jan 18 23:28:32.033: INFO: PersistentVolumeClaim test.csi.azure.com96qpt found but phase is Pending instead of Bound.
Jan 18 23:28:34.141: INFO: PersistentVolumeClaim test.csi.azure.com96qpt found but phase is Pending instead of Bound.
Jan 18 23:28:36.249: INFO: PersistentVolumeClaim test.csi.azure.com96qpt found and phase=Bound (4.323824448s)
STEP: Creating pod pod-subpath-test-dynamicpv-9lcj
STEP: Checking for subpath error in container status
Jan 18 23:29:08.794: INFO: Deleting pod "pod-subpath-test-dynamicpv-9lcj" in namespace "provisioning-9850"
Jan 18 23:29:08.905: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9lcj" to be fully deleted
STEP: Deleting pod
Jan 18 23:29:11.124: INFO: Deleting pod "pod-subpath-test-dynamicpv-9lcj" in namespace "provisioning-9850"
STEP: Deleting pvc
Jan 18 23:29:11.231: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com96qpt"
... skipping 22 lines ...

• [SLOW TEST:112.599 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":3,"skipped":165,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:30:23.565: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 73 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":36,"completed":3,"skipped":54,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (block volmode) (late-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 (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":30,"completed":4,"skipped":432,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:31:20.373: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 38 lines ...
Jan 18 23:30:24.586: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comr7sbw] to have phase Bound
Jan 18 23:30:24.693: INFO: PersistentVolumeClaim test.csi.azure.comr7sbw found but phase is Pending instead of Bound.
Jan 18 23:30:26.801: INFO: PersistentVolumeClaim test.csi.azure.comr7sbw found but phase is Pending instead of Bound.
Jan 18 23:30:28.910: INFO: PersistentVolumeClaim test.csi.azure.comr7sbw found and phase=Bound (4.323981821s)
STEP: Creating pod pod-subpath-test-dynamicpv-zm2n
STEP: Creating a pod to test subpath
Jan 18 23:30:29.236: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zm2n" in namespace "provisioning-9290" to be "Succeeded or Failed"
Jan 18 23:30:29.345: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 109.00206ms
Jan 18 23:30:31.455: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219444801s
Jan 18 23:30:33.564: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328142199s
Jan 18 23:30:35.674: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.438346237s
Jan 18 23:30:37.784: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.548048482s
Jan 18 23:30:39.894: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.657597648s
... skipping 19 lines ...
Jan 18 23:31:22.093: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 52.856718174s
Jan 18 23:31:24.203: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 54.966877876s
Jan 18 23:31:26.312: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 57.076402204s
Jan 18 23:31:28.421: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Pending", Reason="", readiness=false. Elapsed: 59.18542732s
Jan 18 23:31:30.531: INFO: Pod "pod-subpath-test-dynamicpv-zm2n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m1.294698437s
STEP: Saw pod success
Jan 18 23:31:30.531: INFO: Pod "pod-subpath-test-dynamicpv-zm2n" satisfied condition "Succeeded or Failed"
Jan 18 23:31:30.639: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod pod-subpath-test-dynamicpv-zm2n container test-container-subpath-dynamicpv-zm2n: <nil>
STEP: delete the pod
Jan 18 23:31:30.895: INFO: Waiting for pod pod-subpath-test-dynamicpv-zm2n to disappear
Jan 18 23:31:31.004: INFO: Pod pod-subpath-test-dynamicpv-zm2n no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zm2n
Jan 18 23:31:31.004: INFO: Deleting pod "pod-subpath-test-dynamicpv-zm2n" in namespace "provisioning-9290"
... 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 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":41,"completed":4,"skipped":207,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 98 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should 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":35,"completed":3,"skipped":192,"failed":0}

SSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext3)] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161
... skipping 110 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":36,"completed":4,"skipped":71,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:32:51.987: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 134 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":30,"completed":5,"skipped":462,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 220 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":38,"completed":4,"skipped":86,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:33:17.765: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 152 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":18,"completed":5,"skipped":608,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Jan 18 23:34:03.830: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 18 23:34:04.579: INFO: Driver didn't provide topology keys -- skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/framework/framework.go:188
Jan 18 23:34:04.579: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "topology-3346" for this suite.


S [SKIPPING] [1.074 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 71 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":41,"completed":5,"skipped":357,"failed":0}

SSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:34:14.094: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 105 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":41,"completed":6,"skipped":467,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:35:11.164: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 279 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":38,"completed":5,"skipped":155,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:35:31.761: 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: 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 87 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":32,"completed":3,"skipped":171,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:35:33.649: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 87 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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
------------------------------
... skipping 8 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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 108 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":35,"completed":4,"skipped":203,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:35:35.894: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 86 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":30,"completed":6,"skipped":594,"failed":0}

SSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161
... skipping 103 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":18,"completed":6,"skipped":879,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:36:34.433: INFO: Driver "test.csi.azure.com" does not support volume expansion - skipping
... skipping 48 lines ...
Jan 18 23:35:32.924: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comswwrd] to have phase Bound
Jan 18 23:35:33.031: INFO: PersistentVolumeClaim test.csi.azure.comswwrd found but phase is Pending instead of Bound.
Jan 18 23:35:35.141: INFO: PersistentVolumeClaim test.csi.azure.comswwrd found but phase is Pending instead of Bound.
Jan 18 23:35:37.249: INFO: PersistentVolumeClaim test.csi.azure.comswwrd found and phase=Bound (4.324674327s)
STEP: Creating pod exec-volume-test-dynamicpv-m4vd
STEP: Creating a pod to test exec-volume-test
Jan 18 23:35:37.575: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-m4vd" in namespace "volume-9273" to be "Succeeded or Failed"
Jan 18 23:35:37.684: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 109.027395ms
Jan 18 23:35:39.792: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217127089s
Jan 18 23:35:41.901: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326133204s
Jan 18 23:35:44.009: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434505146s
Jan 18 23:35:46.119: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544293018s
Jan 18 23:35:48.227: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652744102s
... skipping 13 lines ...
Jan 18 23:36:17.757: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 40.182387472s
Jan 18 23:36:19.865: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 42.290464498s
Jan 18 23:36:21.975: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 44.400359435s
Jan 18 23:36:24.084: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Pending", Reason="", readiness=false. Elapsed: 46.50970276s
Jan 18 23:36:26.192: INFO: Pod "exec-volume-test-dynamicpv-m4vd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.617409403s
STEP: Saw pod success
Jan 18 23:36:26.192: INFO: Pod "exec-volume-test-dynamicpv-m4vd" satisfied condition "Succeeded or Failed"
Jan 18 23:36:26.300: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000002 pod exec-volume-test-dynamicpv-m4vd container exec-container-dynamicpv-m4vd: <nil>
STEP: delete the pod
Jan 18 23:36:26.545: INFO: Waiting for pod exec-volume-test-dynamicpv-m4vd to disappear
Jan 18 23:36:26.653: INFO: Pod exec-volume-test-dynamicpv-m4vd no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-m4vd
Jan 18 23:36:26.653: INFO: Deleting pod "exec-volume-test-dynamicpv-m4vd" in namespace "volume-9273"
... skipping 19 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":38,"completed":6,"skipped":411,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:36:58.188: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 87 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":36,"completed":5,"skipped":159,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:37:17.238: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 190 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":30,"completed":7,"skipped":605,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:37:32.639: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 155 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":4,"skipped":548,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:37:57.457: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 290 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":41,"completed":7,"skipped":604,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:38:18.688: 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: 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 91 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":35,"completed":5,"skipped":306,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:38:42.993: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 80 lines ...
Jan 18 23:37:33.720: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5g59n] to have phase Bound
Jan 18 23:37:33.827: INFO: PersistentVolumeClaim test.csi.azure.com5g59n found but phase is Pending instead of Bound.
Jan 18 23:37:35.937: INFO: PersistentVolumeClaim test.csi.azure.com5g59n found but phase is Pending instead of Bound.
Jan 18 23:37:38.047: INFO: PersistentVolumeClaim test.csi.azure.com5g59n found and phase=Bound (4.327005904s)
STEP: Creating pod pod-subpath-test-dynamicpv-4z2c
STEP: Creating a pod to test subpath
Jan 18 23:37:38.374: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4z2c" in namespace "provisioning-7397" to be "Succeeded or Failed"
Jan 18 23:37:38.482: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 108.021554ms
Jan 18 23:37:40.591: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21700848s
Jan 18 23:37:42.701: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326681941s
Jan 18 23:37:44.810: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435939343s
Jan 18 23:37:46.918: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544037435s
Jan 18 23:37:49.026: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652129075s
... skipping 13 lines ...
Jan 18 23:38:18.561: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 40.186953317s
Jan 18 23:38:20.670: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 42.296089003s
Jan 18 23:38:22.780: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 44.40549446s
Jan 18 23:38:24.889: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Pending", Reason="", readiness=false. Elapsed: 46.514856221s
Jan 18 23:38:27.003: INFO: Pod "pod-subpath-test-dynamicpv-4z2c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.628255188s
STEP: Saw pod success
Jan 18 23:38:27.003: INFO: Pod "pod-subpath-test-dynamicpv-4z2c" satisfied condition "Succeeded or Failed"
Jan 18 23:38:27.111: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000002 pod pod-subpath-test-dynamicpv-4z2c container test-container-volume-dynamicpv-4z2c: <nil>
STEP: delete the pod
Jan 18 23:38:27.363: INFO: Waiting for pod pod-subpath-test-dynamicpv-4z2c to disappear
Jan 18 23:38:27.472: INFO: Pod pod-subpath-test-dynamicpv-4z2c no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-4z2c
Jan 18 23:38:27.472: INFO: Deleting pod "pod-subpath-test-dynamicpv-4z2c" in namespace "provisioning-7397"
... skipping 29 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":8,"skipped":706,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] provisioning 
  should provision storage with pvc data source in parallel [Slow]
  test/e2e/storage/testsuites/provisioning.go:459
... skipping 328 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":36,"completed":6,"skipped":268,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:40:17.788: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 130 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":38,"completed":7,"skipped":428,"failed":0}

SSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:40:20.315: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 108 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":41,"completed":8,"skipped":680,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] capacity
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:41:03.784: INFO: Driver test.csi.azure.com doesn't publish storage capacity -- skipping
... skipping 144 lines ...
Jan 18 23:37:59.444: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comqp5g6] to have phase Bound
Jan 18 23:37:59.551: INFO: PersistentVolumeClaim test.csi.azure.comqp5g6 found but phase is Pending instead of Bound.
Jan 18 23:38:01.660: INFO: PersistentVolumeClaim test.csi.azure.comqp5g6 found but phase is Pending instead of Bound.
Jan 18 23:38:03.768: INFO: PersistentVolumeClaim test.csi.azure.comqp5g6 found and phase=Bound (4.323969193s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Jan 18 23:38:04.202: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-w6tfz" in namespace "snapshotting-5660" to be "Succeeded or Failed"
Jan 18 23:38:04.312: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 109.065568ms
Jan 18 23:38:06.421: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218427013s
Jan 18 23:38:08.530: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.327062697s
Jan 18 23:38:10.641: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.438543982s
Jan 18 23:38:12.750: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.547053825s
Jan 18 23:38:14.858: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.655434227s
... skipping 8 lines ...
Jan 18 23:38:33.848: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 29.64493529s
Jan 18 23:38:35.956: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 31.753364087s
Jan 18 23:38:38.065: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 33.862115194s
Jan 18 23:38:40.174: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Pending", Reason="", readiness=false. Elapsed: 35.970941981s
Jan 18 23:38:42.283: INFO: Pod "pvc-snapshottable-tester-w6tfz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.080178467s
STEP: Saw pod success
Jan 18 23:38:42.283: INFO: Pod "pvc-snapshottable-tester-w6tfz" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Jan 18 23:38:42.391: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comqp5g6] to have phase Bound
Jan 18 23:38:42.501: INFO: PersistentVolumeClaim test.csi.azure.comqp5g6 found and phase=Bound (110.304207ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Jan 18 23:38:42.864: INFO: Pod pvc-snapshottable-tester-w6tfz has the following logs: 
... skipping 13 lines ...
Jan 18 23:38:50.284: INFO: received snapshotStatus map[boundVolumeSnapshotContentName:snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 creationTime:2023-01-18T23:38:45Z readyToUse:true restoreSize:5Gi]
Jan 18 23:38:50.284: INFO: snapshotContentName snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jan 18 23:38:50.718: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-9rpkn" in namespace "snapshotting-5660" to be "Succeeded or Failed"
Jan 18 23:38:50.825: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 107.391616ms
Jan 18 23:38:52.933: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.214925369s
Jan 18 23:38:55.040: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.322583477s
Jan 18 23:38:57.150: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432210412s
Jan 18 23:38:59.258: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.539920192s
Jan 18 23:39:01.367: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.649155798s
... skipping 33 lines ...
Jan 18 23:40:13.090: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m22.37234397s
Jan 18 23:40:15.199: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m24.481711022s
Jan 18 23:40:17.335: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m26.617537725s
Jan 18 23:40:19.445: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m28.727521969s
Jan 18 23:40:21.553: INFO: Pod "pvc-snapshottable-data-tester-9rpkn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m30.835491919s
STEP: Saw pod success
Jan 18 23:40:21.553: INFO: Pod "pvc-snapshottable-data-tester-9rpkn" satisfied condition "Succeeded or Failed"
Jan 18 23:40:21.793: INFO: Pod pvc-snapshottable-data-tester-9rpkn has the following logs: 
Jan 18 23:40:21.793: INFO: Deleting pod "pvc-snapshottable-data-tester-9rpkn" in namespace "snapshotting-5660"
Jan 18 23:40:21.908: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-9rpkn" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the snapshot
Jan 18 23:40:44.456: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-lnogpxmn.westeurope.cloudapp.azure.com --kubeconfig=/root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json --namespace=snapshotting-5660 exec restored-pvc-tester-7kr7h --namespace=snapshotting-5660 -- cat /mnt/test/data'
... skipping 33 lines ...
Jan 18 23:41:10.655: INFO: volumesnapshotcontents snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 has been found and is not deleted
Jan 18 23:41:11.765: INFO: volumesnapshotcontents snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 has been found and is not deleted
Jan 18 23:41:12.875: INFO: volumesnapshotcontents snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 has been found and is not deleted
Jan 18 23:41:13.984: INFO: volumesnapshotcontents snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 has been found and is not deleted
Jan 18 23:41:15.095: INFO: volumesnapshotcontents snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 has been found and is not deleted
Jan 18 23:41:16.204: INFO: volumesnapshotcontents snapcontent-4ccc1214-061b-4f25-bb8d-cafbc3867dc5 has been found and is not deleted
Jan 18 23:41:17.205: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  test/e2e/storage/testsuites/snapshottable.go:172
Jan 18 23:41:17.342: INFO: Pod restored-pvc-tester-7kr7h has the following logs: 
Jan 18 23:41:17.342: INFO: Deleting pod "restored-pvc-tester-7kr7h" in namespace "snapshotting-5660"
Jan 18 23:41:17.451: INFO: Wait up to 5m0s for pod "restored-pvc-tester-7kr7h" to be fully deleted
Jan 18 23:41:19.670: INFO: deleting claim "snapshotting-5660"/"pvc-lwf2l"
... skipping 31 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 (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller  should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)","total":32,"completed":5,"skipped":614,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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":30,"completed":9,"skipped":820,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:41:38.460: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 115 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 224 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":35,"completed":6,"skipped":492,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:41:45.331: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 109 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":38,"completed":8,"skipped":488,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:42:23.530: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 63 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Jan 18 23:41:38.709: INFO: Creating resource for dynamic PV
Jan 18 23:41:38.710: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3440-e2e-sc6qb95
STEP: [init] starting a pod to use the claim
Jan 18 23:41:38.931: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-hqxjt" in namespace "snapshotting-3440" to be "Succeeded or Failed"
Jan 18 23:41:39.040: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 108.42553ms
Jan 18 23:41:41.149: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218326049s
Jan 18 23:41:43.259: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328226397s
Jan 18 23:41:45.370: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.438853674s
Jan 18 23:41:47.481: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.550222007s
Jan 18 23:41:49.594: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.662934208s
Jan 18 23:41:51.704: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.773151353s
Jan 18 23:41:53.815: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.883479218s
Jan 18 23:41:55.924: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.992646103s
Jan 18 23:41:58.035: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Pending", Reason="", readiness=false. Elapsed: 19.103621348s
Jan 18 23:42:00.145: INFO: Pod "pvc-snapshottable-tester-hqxjt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.213967567s
STEP: Saw pod success
Jan 18 23:42:00.145: INFO: Pod "pvc-snapshottable-tester-hqxjt" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
STEP: creating a dynamic VolumeSnapshot
Jan 18 23:42:00.595: INFO: Waiting up to 5m0s for VolumeSnapshot snapshot-q74st to become ready
Jan 18 23:42:00.704: INFO: VolumeSnapshot snapshot-q74st found but is not ready.
Jan 18 23:42:02.815: INFO: VolumeSnapshot snapshot-q74st found but is not ready.
... skipping 40 lines ...
Jan 18 23:43:06.762: INFO: volumesnapshotcontents snapcontent-3d3bf55e-ea43-41a0-9368-b7551b0ebcbe has been found and is not deleted
Jan 18 23:43:07.872: INFO: volumesnapshotcontents snapcontent-3d3bf55e-ea43-41a0-9368-b7551b0ebcbe has been found and is not deleted
Jan 18 23:43:08.982: INFO: volumesnapshotcontents snapcontent-3d3bf55e-ea43-41a0-9368-b7551b0ebcbe has been found and is not deleted
Jan 18 23:43:10.092: INFO: volumesnapshotcontents snapcontent-3d3bf55e-ea43-41a0-9368-b7551b0ebcbe has been found and is not deleted
Jan 18 23:43:11.202: INFO: volumesnapshotcontents snapcontent-3d3bf55e-ea43-41a0-9368-b7551b0ebcbe has been found and is not deleted
Jan 18 23:43:12.312: INFO: volumesnapshotcontents snapcontent-3d3bf55e-ea43-41a0-9368-b7551b0ebcbe has been found and is not deleted
Jan 18 23:43:13.312: INFO: WaitUntil failed after reaching the timeout 30s
[AfterEach] volume snapshot controller
  test/e2e/storage/testsuites/snapshottable.go:172
Jan 18 23:43:13.426: INFO: Pod restored-pvc-tester-tcf64 has the following logs: 
Jan 18 23:43:13.426: INFO: Deleting pod "restored-pvc-tester-tcf64" in namespace "snapshotting-3440"
Jan 18 23:43:13.537: INFO: Wait up to 5m0s for pod "restored-pvc-tester-tcf64" to be fully deleted
Jan 18 23:43:45.757: INFO: deleting snapshot "snapshotting-3440"/"snapshot-q74st"
... 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":32,"completed":6,"skipped":689,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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
Jan 18 23:41:45.335: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 18 23:41:46.092: INFO: Creating resource for dynamic PV
Jan 18 23:41:46.092: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7238-e2e-scps2np
STEP: creating a claim
Jan 18 23:41:46.201: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jan 18 23:41:46.312: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comr2tmr] to have phase Bound
Jan 18 23:41:46.420: INFO: PersistentVolumeClaim test.csi.azure.comr2tmr found but phase is Pending instead of Bound.
Jan 18 23:41:48.529: INFO: PersistentVolumeClaim test.csi.azure.comr2tmr found but phase is Pending instead of Bound.
Jan 18 23:41:50.637: INFO: PersistentVolumeClaim test.csi.azure.comr2tmr found and phase=Bound (4.324863212s)
STEP: Creating pod pod-subpath-test-dynamicpv-dgcq
STEP: Checking for subpath error in container status
Jan 18 23:42:43.179: INFO: Deleting pod "pod-subpath-test-dynamicpv-dgcq" in namespace "provisioning-7238"
Jan 18 23:42:43.289: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dgcq" to be fully deleted
STEP: Deleting pod
Jan 18 23:42:45.505: INFO: Deleting pod "pod-subpath-test-dynamicpv-dgcq" in namespace "provisioning-7238"
STEP: Deleting pvc
Jan 18 23:42:45.613: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comr2tmr"
... skipping 22 lines ...

• [SLOW TEST:132.567 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":35,"completed":7,"skipped":547,"failed":0}

SSSSSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/multivolume.go:209
... skipping 194 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":9,"skipped":821,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:44:00.769: 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 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 21 lines ...
  test/e2e/framework/framework.go:188
Jan 18 23:44:01.977: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumelimits-6577" 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":41,"completed":10,"skipped":897,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Jan 18 23:44:02.212: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 18 23:44:02.963: INFO: Driver didn't provide topology keys -- skipping
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/framework/framework.go:188
Jan 18 23:44:02.963: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "topology-7026" for this suite.


S [SKIPPING] [0.970 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 201 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":36,"completed":7,"skipped":399,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:44:23.004: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 59 lines ...
Jan 18 23:42:25.628: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comzb6fg] to have phase Bound
Jan 18 23:42:25.735: INFO: PersistentVolumeClaim test.csi.azure.comzb6fg found but phase is Pending instead of Bound.
Jan 18 23:42:27.843: INFO: PersistentVolumeClaim test.csi.azure.comzb6fg found but phase is Pending instead of Bound.
Jan 18 23:42:29.952: INFO: PersistentVolumeClaim test.csi.azure.comzb6fg found and phase=Bound (4.32417316s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Jan 18 23:42:30.383: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-phqf6" in namespace "snapshotting-8476" to be "Succeeded or Failed"
Jan 18 23:42:30.491: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 107.566798ms
Jan 18 23:42:32.600: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216913016s
Jan 18 23:42:34.709: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326011251s
Jan 18 23:42:36.819: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435545989s
Jan 18 23:42:38.928: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544189746s
Jan 18 23:42:41.035: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651965412s
... skipping 10 lines ...
Jan 18 23:43:04.236: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 33.852038271s
Jan 18 23:43:06.344: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 35.960198992s
Jan 18 23:43:08.452: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 38.068050081s
Jan 18 23:43:10.560: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Pending", Reason="", readiness=false. Elapsed: 40.176260671s
Jan 18 23:43:12.669: INFO: Pod "pvc-snapshottable-tester-phqf6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.285600509s
STEP: Saw pod success
Jan 18 23:43:12.669: INFO: Pod "pvc-snapshottable-tester-phqf6" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Jan 18 23:43:12.778: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comzb6fg] to have phase Bound
Jan 18 23:43:12.885: INFO: PersistentVolumeClaim test.csi.azure.comzb6fg found and phase=Bound (107.553652ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Jan 18 23:43:13.234: INFO: Pod pvc-snapshottable-tester-phqf6 has the following logs: 
... skipping 14 lines ...
Jan 18 23:43:22.858: INFO: received snapshotStatus map[boundVolumeSnapshotContentName:snapcontent-cf506038-23c8-44ad-b2a4-48f6dc1884fb creationTime:2023-01-18T23:43:18Z readyToUse:true restoreSize:5Gi]
Jan 18 23:43:22.858: INFO: snapshotContentName snapcontent-cf506038-23c8-44ad-b2a4-48f6dc1884fb
STEP: checking the snapshot
STEP: checking the SnapshotContent
STEP: Modifying source data test
STEP: modifying the data in the source PVC
Jan 18 23:43:23.291: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-data-tester-hwtt6" in namespace "snapshotting-8476" to be "Succeeded or Failed"
Jan 18 23:43:23.398: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 107.033741ms
Jan 18 23:43:25.507: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215921582s
Jan 18 23:43:27.616: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324475865s
Jan 18 23:43:29.725: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433822651s
Jan 18 23:43:31.833: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541852156s
Jan 18 23:43:33.943: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651283535s
... skipping 6 lines ...
Jan 18 23:43:48.708: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 25.416843543s
Jan 18 23:43:50.816: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 27.525194709s
Jan 18 23:43:52.925: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 29.633852323s
Jan 18 23:43:55.034: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Pending", Reason="", readiness=false. Elapsed: 31.742846026s
Jan 18 23:43:57.144: INFO: Pod "pvc-snapshottable-data-tester-hwtt6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.852436518s
STEP: Saw pod success
Jan 18 23:43:57.144: INFO: Pod "pvc-snapshottable-data-tester-hwtt6" satisfied condition "Succeeded or Failed"
Jan 18 23:43:57.389: INFO: Pod pvc-snapshottable-data-tester-hwtt6 has the following logs: 
Jan 18 23:43:57.389: INFO: Deleting pod "pvc-snapshottable-data-tester-hwtt6" in namespace "snapshotting-8476"
Jan 18 23:43:57.500: INFO: Wait up to 5m0s for pod "pvc-snapshottable-data-tester-hwtt6" to be fully deleted
STEP: creating a pvc from the snapshot
STEP: starting a pod to use the snapshot
Jan 18 23:44:32.047: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-lnogpxmn.westeurope.cloudapp.azure.com --kubeconfig=/root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json --namespace=snapshotting-8476 exec restored-pvc-tester-vr4vw --namespace=snapshotting-8476 -- 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":38,"completed":9,"skipped":544,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
... skipping 77 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 138 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":36,"completed":8,"skipped":491,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
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 17 lines ...
Jan 18 23:44:04.168: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comswp5t] to have phase Bound
Jan 18 23:44:04.276: INFO: PersistentVolumeClaim test.csi.azure.comswp5t found but phase is Pending instead of Bound.
Jan 18 23:44:06.384: INFO: PersistentVolumeClaim test.csi.azure.comswp5t found but phase is Pending instead of Bound.
Jan 18 23:44:08.491: INFO: PersistentVolumeClaim test.csi.azure.comswp5t found and phase=Bound (4.323111277s)
STEP: Creating pod pod-subpath-test-dynamicpv-ql7j
STEP: Creating a pod to test atomic-volume-subpath
Jan 18 23:44:08.815: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-ql7j" in namespace "provisioning-5777" to be "Succeeded or Failed"
Jan 18 23:44:08.922: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Pending", Reason="", readiness=false. Elapsed: 107.523989ms
Jan 18 23:44:11.030: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215345921s
Jan 18 23:44:13.139: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324449035s
Jan 18 23:44:15.260: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.445521679s
Jan 18 23:44:17.369: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.55406976s
Jan 18 23:44:19.478: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.663318448s
... skipping 26 lines ...
Jan 18 23:45:16.423: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Running", Reason="", readiness=true. Elapsed: 1m7.60854664s
Jan 18 23:45:18.531: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Running", Reason="", readiness=true. Elapsed: 1m9.716474756s
Jan 18 23:45:20.639: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Running", Reason="", readiness=true. Elapsed: 1m11.824368751s
Jan 18 23:45:22.747: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Running", Reason="", readiness=false. Elapsed: 1m13.932140494s
Jan 18 23:45:24.855: INFO: Pod "pod-subpath-test-dynamicpv-ql7j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m16.040037971s
STEP: Saw pod success
Jan 18 23:45:24.855: INFO: Pod "pod-subpath-test-dynamicpv-ql7j" satisfied condition "Succeeded or Failed"
Jan 18 23:45:24.962: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod pod-subpath-test-dynamicpv-ql7j container test-container-subpath-dynamicpv-ql7j: <nil>
STEP: delete the pod
Jan 18 23:45:25.191: INFO: Waiting for pod pod-subpath-test-dynamicpv-ql7j to disappear
Jan 18 23:45:25.298: INFO: Pod pod-subpath-test-dynamicpv-ql7j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-ql7j
Jan 18 23:45:25.298: INFO: Deleting pod "pod-subpath-test-dynamicpv-ql7j" in namespace "provisioning-5777"
... skipping 29 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support file as subpath [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:232
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":41,"completed":11,"skipped":925,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:46:37.829: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 237 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":7,"skipped":737,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:47:04.529: INFO: Driver "test.csi.azure.com" does not support volume type "CSIInlineVolume" - skipping
... skipping 210 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":36,"completed":9,"skipped":508,"failed":0}

SSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:47:46.288: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 128 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":35,"completed":8,"skipped":557,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:47:52.963: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 275 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":38,"completed":10,"skipped":781,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy 
  (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
  test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
... skipping 113 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":35,"completed":9,"skipped":636,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:49:14.411: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 113 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Jan 18 23:47:05.343: INFO: Creating resource for dynamic PV
Jan 18 23:47:05.343: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3592-e2e-sctsltr
STEP: [init] starting a pod to use the claim
Jan 18 23:47:05.562: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nswqr" in namespace "snapshotting-3592" to be "Succeeded or Failed"
Jan 18 23:47:05.669: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 107.143307ms
Jan 18 23:47:07.777: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215262651s
Jan 18 23:47:09.885: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323222101s
Jan 18 23:47:11.994: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432123319s
Jan 18 23:47:14.103: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.540894562s
Jan 18 23:47:16.212: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.649742071s
... skipping 9 lines ...
Jan 18 23:47:37.310: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 31.747800111s
Jan 18 23:47:39.418: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 33.856222252s
Jan 18 23:47:41.526: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 35.964374767s
Jan 18 23:47:43.636: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Pending", Reason="", readiness=false. Elapsed: 38.073549749s
Jan 18 23:47:45.744: INFO: Pod "pvc-snapshottable-tester-nswqr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.181494056s
STEP: Saw pod success
Jan 18 23:47:45.744: INFO: Pod "pvc-snapshottable-tester-nswqr" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
STEP: creating a dynamic VolumeSnapshot
Jan 18 23:47:46.180: INFO: Waiting up to 5m0s for VolumeSnapshot snapshot-jf8ql to become ready
Jan 18 23:47:46.291: INFO: VolumeSnapshot snapshot-jf8ql found but is not ready.
Jan 18 23:47:48.400: INFO: VolumeSnapshot snapshot-jf8ql 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":32,"completed":8,"skipped":812,"failed":0}

SSSSSSSSSSSS
------------------------------
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 183 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":38,"completed":11,"skipped":826,"failed":0}

SSSSSS
------------------------------
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
Jan 18 23:49:31.932: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 18 23:49:32.686: INFO: Creating resource for dynamic PV
Jan 18 23:49:32.686: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2929-e2e-scc5r76
STEP: creating a claim
Jan 18 23:49:32.907: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comc45xr] to have phase Bound
Jan 18 23:49:33.015: INFO: PersistentVolumeClaim test.csi.azure.comc45xr found but phase is Pending instead of Bound.
Jan 18 23:49:35.123: INFO: PersistentVolumeClaim test.csi.azure.comc45xr found but phase is Pending instead of Bound.
Jan 18 23:49:37.231: INFO: PersistentVolumeClaim test.csi.azure.comc45xr found and phase=Bound (4.32406427s)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jan 18 23:49:37.773: INFO: Deleting pod "pod-78de4b79-419d-4a64-b363-46e5fdb13164" in namespace "volumemode-2929"
Jan 18 23:49:37.882: INFO: Wait up to 5m0s for pod "pod-78de4b79-419d-4a64-b363-46e5fdb13164" to be fully deleted
STEP: Deleting pvc
Jan 18 23:49:40.098: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comc45xr"
Jan 18 23:49:40.211: INFO: Waiting up to 5m0s for PersistentVolume pvc-aafcbb91-d068-438f-adef-b88b80a2d100 to get deleted
Jan 18 23:49:40.319: INFO: PersistentVolume pvc-aafcbb91-d068-438f-adef-b88b80a2d100 found and phase=Released (107.888922ms)
... skipping 20 lines ...

• [SLOW TEST:80.457 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":9,"skipped":824,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:50:52.397: 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
------------------------------
SSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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

{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] volumes should store data","total":41,"completed":12,"skipped":971,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Jan 18 23:48:16.035: INFO: >>> kubeConfig: /root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json
... skipping 181 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":13,"skipped":971,"failed":0}

S
------------------------------
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 256 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":35,"completed":10,"skipped":779,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:53:01.925: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 328 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":32,"completed":10,"skipped":854,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/multivolume.go:248
... skipping 189 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":14,"skipped":972,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:53:28.201: INFO: Driver "test.csi.azure.com" does not support volume expansion - skipping
... skipping 16 lines ...
SSSSS
------------------------------
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
  test/e2e/storage/testsuites/multivolume.go:168

{"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":36,"completed":10,"skipped":553,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Jan 18 23:49:50.612: INFO: >>> kubeConfig: /root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json
... skipping 187 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":36,"completed":11,"skipped":553,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:53:41.517: 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: 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
------------------------------
SSSSSS
------------------------------
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
  test/e2e/storage/testsuites/multivolume.go:423

{"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":38,"completed":12,"skipped":832,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Jan 18 23:52:15.234: INFO: >>> kubeConfig: /root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json
... skipping 80 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":38,"completed":13,"skipped":832,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:54:22.448: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 90 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":32,"completed":11,"skipped":875,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161
... skipping 221 lines ...
Jan 18 23:53:42.550: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comnkbbq] to have phase Bound
Jan 18 23:53:42.656: INFO: PersistentVolumeClaim test.csi.azure.comnkbbq found but phase is Pending instead of Bound.
Jan 18 23:53:44.764: INFO: PersistentVolumeClaim test.csi.azure.comnkbbq found but phase is Pending instead of Bound.
Jan 18 23:53:46.872: INFO: PersistentVolumeClaim test.csi.azure.comnkbbq found and phase=Bound (4.322058446s)
STEP: Creating pod pod-subpath-test-dynamicpv-xhvt
STEP: Creating a pod to test subpath
Jan 18 23:53:47.195: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xhvt" in namespace "provisioning-5057" to be "Succeeded or Failed"
Jan 18 23:53:47.302: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 107.363218ms
Jan 18 23:53:49.411: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215786274s
Jan 18 23:53:51.519: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.323953873s
Jan 18 23:53:53.628: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.432756423s
Jan 18 23:53:55.737: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541931028s
Jan 18 23:53:57.845: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.65041061s
... skipping 19 lines ...
Jan 18 23:54:40.029: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 52.833761558s
Jan 18 23:54:42.137: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 54.941772933s
Jan 18 23:54:44.245: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 57.050281125s
Jan 18 23:54:46.355: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Pending", Reason="", readiness=false. Elapsed: 59.159656968s
Jan 18 23:54:48.463: INFO: Pod "pod-subpath-test-dynamicpv-xhvt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m1.268465199s
STEP: Saw pod success
Jan 18 23:54:48.464: INFO: Pod "pod-subpath-test-dynamicpv-xhvt" satisfied condition "Succeeded or Failed"
Jan 18 23:54:48.571: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod pod-subpath-test-dynamicpv-xhvt container test-container-subpath-dynamicpv-xhvt: <nil>
STEP: delete the pod
Jan 18 23:54:48.818: INFO: Waiting for pod pod-subpath-test-dynamicpv-xhvt to disappear
Jan 18 23:54:48.925: INFO: Pod pod-subpath-test-dynamicpv-xhvt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xhvt
Jan 18 23:54:48.925: INFO: Deleting pod "pod-subpath-test-dynamicpv-xhvt" in namespace "provisioning-5057"
... skipping 29 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":36,"completed":12,"skipped":625,"failed":0}

SSS
------------------------------
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
Jan 18 23:54:22.462: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 18 23:54:23.217: INFO: Creating resource for dynamic PV
Jan 18 23:54:23.217: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass volumemode-2331-e2e-sczvhn6
STEP: creating a claim
Jan 18 23:54:23.436: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comw2rcq] to have phase Bound
Jan 18 23:54:23.544: INFO: PersistentVolumeClaim test.csi.azure.comw2rcq found but phase is Pending instead of Bound.
Jan 18 23:54:25.651: INFO: PersistentVolumeClaim test.csi.azure.comw2rcq found but phase is Pending instead of Bound.
Jan 18 23:54:27.759: INFO: PersistentVolumeClaim test.csi.azure.comw2rcq found and phase=Bound (4.322516709s)
STEP: Creating pod
STEP: Waiting for the pod to fail
Jan 18 23:54:30.411: INFO: Deleting pod "pod-81695c3f-0770-4d8b-8efe-09e3a678827c" in namespace "volumemode-2331"
Jan 18 23:54:30.521: INFO: Wait up to 5m0s for pod "pod-81695c3f-0770-4d8b-8efe-09e3a678827c" to be fully deleted
STEP: Deleting pvc
Jan 18 23:54:32.738: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comw2rcq"
Jan 18 23:54:32.848: INFO: Waiting up to 5m0s for PersistentVolume pvc-bc0cb69c-8da0-4230-a7f7-e7e02ca46432 to get deleted
Jan 18 23:54:32.955: INFO: PersistentVolume pvc-bc0cb69c-8da0-4230-a7f7-e7e02ca46432 found and phase=Released (107.086613ms)
... skipping 32 lines ...

• [SLOW TEST:143.862 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":38,"completed":14,"skipped":861,"failed":0}

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

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:57:59.540: INFO: Distro debian doesn't support ntfs -- skipping
... skipping 26 lines ...


External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161

{"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":41,"completed":15,"skipped":997,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] volumes
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Jan 18 23:55:57.379: INFO: >>> kubeConfig: /root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json
... skipping 109 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (xfs)][Slow] 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 (xfs)][Slow] volumes should store data","total":41,"completed":16,"skipped":997,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
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

{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes should store data","total":35,"completed":11,"skipped":1002,"failed":0}
[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
Jan 18 23:55:36.416: INFO: >>> kubeConfig: /root/tmp3832101812/kubeconfig/kubeconfig.westeurope.json
... skipping 10 lines ...
Jan 18 23:55:37.388: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comjm9wc] to have phase Bound
Jan 18 23:55:37.495: INFO: PersistentVolumeClaim test.csi.azure.comjm9wc found but phase is Pending instead of Bound.
Jan 18 23:55:39.603: INFO: PersistentVolumeClaim test.csi.azure.comjm9wc found but phase is Pending instead of Bound.
Jan 18 23:55:41.712: INFO: PersistentVolumeClaim test.csi.azure.comjm9wc found and phase=Bound (4.323873415s)
STEP: Creating pod pod-subpath-test-dynamicpv-p7vv
STEP: Creating a pod to test subpath
Jan 18 23:55:42.038: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p7vv" in namespace "provisioning-5372" to be "Succeeded or Failed"
Jan 18 23:55:42.146: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 107.814739ms
Jan 18 23:55:44.255: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21643516s
Jan 18 23:55:46.364: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325640863s
Jan 18 23:55:48.473: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434493802s
Jan 18 23:55:50.584: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.54526283s
Jan 18 23:55:52.693: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.654378871s
Jan 18 23:55:54.801: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.762654542s
Jan 18 23:55:56.909: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.870631412s
Jan 18 23:55:59.020: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.981666082s
Jan 18 23:56:01.129: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 19.090773673s
Jan 18 23:56:03.239: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.199942469s
STEP: Saw pod success
Jan 18 23:56:03.239: INFO: Pod "pod-subpath-test-dynamicpv-p7vv" satisfied condition "Succeeded or Failed"
Jan 18 23:56:03.346: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000002 pod pod-subpath-test-dynamicpv-p7vv container test-container-subpath-dynamicpv-p7vv: <nil>
STEP: delete the pod
Jan 18 23:56:03.592: INFO: Waiting for pod pod-subpath-test-dynamicpv-p7vv to disappear
Jan 18 23:56:03.699: INFO: Pod pod-subpath-test-dynamicpv-p7vv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p7vv
Jan 18 23:56:03.699: INFO: Deleting pod "pod-subpath-test-dynamicpv-p7vv" in namespace "provisioning-5372"
STEP: Creating pod pod-subpath-test-dynamicpv-p7vv
STEP: Creating a pod to test subpath
Jan 18 23:56:03.915: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-p7vv" in namespace "provisioning-5372" to be "Succeeded or Failed"
Jan 18 23:56:04.024: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 108.900515ms
Jan 18 23:56:06.133: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217609031s
Jan 18 23:56:08.241: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326599032s
Jan 18 23:56:10.351: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435974562s
Jan 18 23:56:12.460: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.545399524s
Jan 18 23:56:14.569: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.654590978s
... skipping 25 lines ...
Jan 18 23:57:09.404: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.488976694s
Jan 18 23:57:11.513: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.598455971s
Jan 18 23:57:13.623: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.708306099s
Jan 18 23:57:15.732: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Pending", Reason="", readiness=false. Elapsed: 1m11.816970648s
Jan 18 23:57:17.841: INFO: Pod "pod-subpath-test-dynamicpv-p7vv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m13.926064659s
STEP: Saw pod success
Jan 18 23:57:17.841: INFO: Pod "pod-subpath-test-dynamicpv-p7vv" satisfied condition "Succeeded or Failed"
Jan 18 23:57:17.949: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000002 pod pod-subpath-test-dynamicpv-p7vv container test-container-subpath-dynamicpv-p7vv: <nil>
STEP: delete the pod
Jan 18 23:57:18.176: INFO: Waiting for pod pod-subpath-test-dynamicpv-p7vv to disappear
Jan 18 23:57:18.283: INFO: Pod pod-subpath-test-dynamicpv-p7vv no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-p7vv
Jan 18 23:57:18.283: INFO: Deleting pod "pod-subpath-test-dynamicpv-p7vv" in namespace "provisioning-5372"
... skipping 29 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":35,"completed":12,"skipped":1002,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:58:30.781: 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 31 lines ...
Jan 18 23:56:02.274: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jan 18 23:56:02.393: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comrrgsz] to have phase Bound
Jan 18 23:56:02.502: INFO: PersistentVolumeClaim test.csi.azure.comrrgsz found but phase is Pending instead of Bound.
Jan 18 23:56:04.611: INFO: PersistentVolumeClaim test.csi.azure.comrrgsz found but phase is Pending instead of Bound.
Jan 18 23:56:06.720: INFO: PersistentVolumeClaim test.csi.azure.comrrgsz found and phase=Bound (4.326400055s)
STEP: Creating pod to format volume volume-prep-provisioning-9544
Jan 18 23:56:07.043: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9544" in namespace "provisioning-9544" to be "Succeeded or Failed"
Jan 18 23:56:07.150: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 107.48015ms
Jan 18 23:56:09.258: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215109456s
Jan 18 23:56:11.367: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324127747s
Jan 18 23:56:13.476: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433099532s
Jan 18 23:56:15.584: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 8.541305972s
Jan 18 23:56:17.692: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 10.649772772s
... skipping 11 lines ...
Jan 18 23:56:42.993: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 35.950825008s
Jan 18 23:56:45.113: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 38.070376363s
Jan 18 23:56:47.221: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 40.178830866s
Jan 18 23:56:49.330: INFO: Pod "volume-prep-provisioning-9544": Phase="Pending", Reason="", readiness=false. Elapsed: 42.28755942s
Jan 18 23:56:51.441: INFO: Pod "volume-prep-provisioning-9544": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.398007036s
STEP: Saw pod success
Jan 18 23:56:51.441: INFO: Pod "volume-prep-provisioning-9544" satisfied condition "Succeeded or Failed"
Jan 18 23:56:51.441: INFO: Deleting pod "volume-prep-provisioning-9544" in namespace "provisioning-9544"
Jan 18 23:56:51.554: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9544" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-tln7
STEP: Checking for subpath error in container status
Jan 18 23:57:25.990: INFO: Deleting pod "pod-subpath-test-dynamicpv-tln7" in namespace "provisioning-9544"
Jan 18 23:57:26.099: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tln7" to be fully deleted
STEP: Deleting pod
Jan 18 23:57:28.315: INFO: Deleting pod "pod-subpath-test-dynamicpv-tln7" in namespace "provisioning-9544"
STEP: Deleting pvc
Jan 18 23:57:28.423: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comrrgsz"
... skipping 25 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":36,"completed":13,"skipped":628,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Jan 18 23:58:40.738: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 94 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":36,"completed":14,"skipped":780,"failed":0}

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

SSSSSSSS
------------------------------
Jan 19 00:00:21.084: INFO: Running AfterSuite actions on all nodes
Jan 19 00:00:21.084: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Jan 19 00:00:21.084: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
... skipping 27 lines ...
Jan 19 00:00:10.471: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2ttvh] to have phase Bound
Jan 19 00:00:10.578: INFO: PersistentVolumeClaim test.csi.azure.com2ttvh found but phase is Pending instead of Bound.
Jan 19 00:00:12.686: INFO: PersistentVolumeClaim test.csi.azure.com2ttvh found but phase is Pending instead of Bound.
Jan 19 00:00:14.798: INFO: PersistentVolumeClaim test.csi.azure.com2ttvh found and phase=Bound (4.326897294s)
STEP: Creating pod pod-subpath-test-dynamicpv-x6lq
STEP: Creating a pod to test subpath
Jan 19 00:00:15.124: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-x6lq" in namespace "provisioning-4727" to be "Succeeded or Failed"
Jan 19 00:00:15.232: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 107.806575ms
Jan 19 00:00:17.342: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216968476s
Jan 19 00:00:19.450: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325753046s
Jan 19 00:00:21.559: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434556998s
Jan 19 00:00:23.668: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.543219646s
Jan 19 00:00:25.777: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652369568s
... skipping 2 lines ...
Jan 19 00:00:32.103: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 16.978610154s
Jan 19 00:00:34.212: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 19.087260119s
Jan 19 00:00:36.321: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 21.196379376s
Jan 19 00:00:38.430: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Pending", Reason="", readiness=false. Elapsed: 23.305667997s
Jan 19 00:00:40.539: INFO: Pod "pod-subpath-test-dynamicpv-x6lq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 25.414717863s
STEP: Saw pod success
Jan 19 00:00:40.539: INFO: Pod "pod-subpath-test-dynamicpv-x6lq" satisfied condition "Succeeded or Failed"
Jan 19 00:00:40.647: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod pod-subpath-test-dynamicpv-x6lq container test-container-subpath-dynamicpv-x6lq: <nil>
STEP: delete the pod
Jan 19 00:00:40.896: INFO: Waiting for pod pod-subpath-test-dynamicpv-x6lq to disappear
Jan 19 00:00:41.004: INFO: Pod pod-subpath-test-dynamicpv-x6lq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-x6lq
Jan 19 00:00:41.004: INFO: Deleting pod "pod-subpath-test-dynamicpv-x6lq" in namespace "provisioning-4727"
... 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 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":36,"completed":15,"skipped":802,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext3)] volumes 
  should allow exec of files on the volume
  test/e2e/storage/testsuites/volumes.go:198
... skipping 17 lines ...
Jan 19 00:02:55.828: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com429dz] to have phase Bound
Jan 19 00:02:55.938: INFO: PersistentVolumeClaim test.csi.azure.com429dz found but phase is Pending instead of Bound.
Jan 19 00:02:58.046: INFO: PersistentVolumeClaim test.csi.azure.com429dz found but phase is Pending instead of Bound.
Jan 19 00:03:00.154: INFO: PersistentVolumeClaim test.csi.azure.com429dz found and phase=Bound (4.325884339s)
STEP: Creating pod exec-volume-test-dynamicpv-kmh4
STEP: Creating a pod to test exec-volume-test
Jan 19 00:03:00.487: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-kmh4" in namespace "volume-2491" to be "Succeeded or Failed"
Jan 19 00:03:00.602: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 115.631985ms
Jan 19 00:03:02.711: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.224264833s
Jan 19 00:03:04.819: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.33275655s
Jan 19 00:03:06.929: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.441885651s
Jan 19 00:03:09.037: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.549967926s
Jan 19 00:03:11.145: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.658508921s
Jan 19 00:03:13.255: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.768067505s
Jan 19 00:03:15.364: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.87732834s
Jan 19 00:03:17.473: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.985868041s
Jan 19 00:03:19.582: INFO: Pod "exec-volume-test-dynamicpv-kmh4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 19.095112513s
STEP: Saw pod success
Jan 19 00:03:19.582: INFO: Pod "exec-volume-test-dynamicpv-kmh4" satisfied condition "Succeeded or Failed"
Jan 19 00:03:19.689: INFO: Trying to get logs from node k8s-agentpool1-37698423-vmss000000 pod exec-volume-test-dynamicpv-kmh4 container exec-container-dynamicpv-kmh4: <nil>
STEP: delete the pod
Jan 19 00:03:19.951: INFO: Waiting for pod exec-volume-test-dynamicpv-kmh4 to disappear
Jan 19 00:03:20.059: INFO: Pod exec-volume-test-dynamicpv-kmh4 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-kmh4
Jan 19 00:03:20.059: INFO: Deleting pod "exec-volume-test-dynamicpv-kmh4" in namespace "volume-2491"
... 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":36,"completed":16,"skipped":826,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Jan 19 00:04:01.898: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 75 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":36,"completed":17,"skipped":946,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Jan 19 00:07:09.987: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 13 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
S
------------------------------
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
Jan 19 00:07:09.990: INFO: >>> kubeConfig: /root/tmp3832101812/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
Jan 19 00:07:10.747: INFO: Creating resource for dynamic PV
Jan 19 00:07:10.747: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9172-e2e-scjtnlc
STEP: creating a claim
Jan 19 00:07:10.856: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Jan 19 00:07:10.967: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.commfrwd] to have phase Bound
Jan 19 00:07:11.075: INFO: PersistentVolumeClaim test.csi.azure.commfrwd found but phase is Pending instead of Bound.
Jan 19 00:07:13.185: INFO: PersistentVolumeClaim test.csi.azure.commfrwd found but phase is Pending instead of Bound.
Jan 19 00:07:15.295: INFO: PersistentVolumeClaim test.csi.azure.commfrwd found and phase=Bound (4.328546477s)
STEP: Creating pod pod-subpath-test-dynamicpv-t8jx
STEP: Checking for subpath error in container status
Jan 19 00:07:57.845: INFO: Deleting pod "pod-subpath-test-dynamicpv-t8jx" in namespace "provisioning-9172"
Jan 19 00:07:57.955: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-t8jx" to be fully deleted
STEP: Deleting pod
Jan 19 00:08:00.175: INFO: Deleting pod "pod-subpath-test-dynamicpv-t8jx" in namespace "provisioning-9172"
STEP: Deleting pvc
Jan 19 00:08:00.284: INFO: Deleting PersistentVolumeClaim "test.csi.azure.commfrwd"
... skipping 16 lines ...

• [SLOW TEST:91.941 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":36,"completed":18,"skipped":978,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSS