This job view page is being replaced by Spyglass soon. Check out the new job view.
PRZeroMagic: fix: cancel the context when timeout of deleting file share
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-09-14 00:58
Elapsed33m12s
Revision710fccddc349b2db037388a1ea1cb9034bfb2485
Refs 1085

No Test Failures!


Error lines from build-log.txt

... skipping 232 lines ...

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

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 435 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 47 lines ...
Sep 14 01:20:15.832: INFO: PersistentVolumeClaim test.csi.azure.comw698d found but phase is Pending instead of Bound.
Sep 14 01:20:17.871: INFO: PersistentVolumeClaim test.csi.azure.comw698d found but phase is Pending instead of Bound.
Sep 14 01:20:19.910: INFO: PersistentVolumeClaim test.csi.azure.comw698d found but phase is Pending instead of Bound.
Sep 14 01:20:21.952: INFO: PersistentVolumeClaim test.csi.azure.comw698d found and phase=Bound (57.156622606s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep 14 01:20:22.110: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-nrxzq" in namespace "snapshotting-3682" to be "Succeeded or Failed"
Sep 14 01:20:22.149: INFO: Pod "pvc-snapshottable-tester-nrxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 38.528031ms
Sep 14 01:20:24.189: INFO: Pod "pvc-snapshottable-tester-nrxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.079124894s
Sep 14 01:20:26.230: INFO: Pod "pvc-snapshottable-tester-nrxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.119945986s
Sep 14 01:20:28.269: INFO: Pod "pvc-snapshottable-tester-nrxzq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.158885567s
Sep 14 01:20:30.309: INFO: Pod "pvc-snapshottable-tester-nrxzq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.198622931s
STEP: Saw pod success
Sep 14 01:20:30.309: INFO: Pod "pvc-snapshottable-tester-nrxzq" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep 14 01:20:30.348: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comw698d] to have phase Bound
Sep 14 01:20:30.387: INFO: PersistentVolumeClaim test.csi.azure.comw698d found and phase=Bound (39.011227ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep 14 01:20:30.748: INFO: Pod pvc-snapshottable-tester-nrxzq has the following logs: 
... skipping 119 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSSSS
------------------------------
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
... skipping 2 lines ...
STEP: Building a namespace api object, basename provisioning
W0914 01:19:24.354305   36998 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep 14 01:19:24.354: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled
Sep 14 01:19:24.392: 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 subpath directory is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:242
Sep 14 01:19:24.533: INFO: Creating resource for dynamic PV
Sep 14 01:19:24.533: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5145-e2e-scvwsgn
STEP: creating a claim
Sep 14 01:19:24.585: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
... skipping 25 lines ...
Sep 14 01:20:13.571: INFO: PersistentVolumeClaim test.csi.azure.comdjvtz found but phase is Pending instead of Bound.
Sep 14 01:20:15.607: INFO: PersistentVolumeClaim test.csi.azure.comdjvtz found but phase is Pending instead of Bound.
Sep 14 01:20:17.644: INFO: PersistentVolumeClaim test.csi.azure.comdjvtz found but phase is Pending instead of Bound.
Sep 14 01:20:19.680: INFO: PersistentVolumeClaim test.csi.azure.comdjvtz found but phase is Pending instead of Bound.
Sep 14 01:20:21.716: INFO: PersistentVolumeClaim test.csi.azure.comdjvtz found and phase=Bound (57.089312187s)
STEP: Creating pod pod-subpath-test-dynamicpv-7wjn
STEP: Checking for subpath error in container status
Sep 14 01:20:29.898: INFO: Deleting pod "pod-subpath-test-dynamicpv-7wjn" in namespace "provisioning-5145"
Sep 14 01:20:29.939: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7wjn" to be fully deleted
STEP: Deleting pod
Sep 14 01:20:34.013: INFO: Deleting pod "pod-subpath-test-dynamicpv-7wjn" in namespace "provisioning-5145"
STEP: Deleting pvc
Sep 14 01:20:34.049: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comdjvtz"
... skipping 9 lines ...

• [SLOW TEST:75.090 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":38,"completed":1,"skipped":90,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:20:39.305: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
[AfterEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/framework/framework.go:188

... skipping 52 lines ...

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

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

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 140 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":34,"completed":1,"skipped":98,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand 
  Verify if offline PVC expansion works
  test/e2e/storage/testsuites/volume_expand.go:176
... skipping 81 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    Verify if offline PVC expansion works
    test/e2e/storage/testsuites/volume_expand.go:176
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":25,"completed":1,"skipped":83,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:20:50.191: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 100 lines ...
Sep 14 01:20:36.590: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:20:36.630: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5cp6w] to have phase Bound
Sep 14 01:20:36.669: INFO: PersistentVolumeClaim test.csi.azure.com5cp6w found but phase is Pending instead of Bound.
Sep 14 01:20:38.713: INFO: PersistentVolumeClaim test.csi.azure.com5cp6w found and phase=Bound (2.082390562s)
STEP: Creating pod exec-volume-test-dynamicpv-sjxf
STEP: Creating a pod to test exec-volume-test
Sep 14 01:20:38.829: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-sjxf" in namespace "volume-5775" to be "Succeeded or Failed"
Sep 14 01:20:38.867: INFO: Pod "exec-volume-test-dynamicpv-sjxf": Phase="Pending", Reason="", readiness=false. Elapsed: 38.278135ms
Sep 14 01:20:40.908: INFO: Pod "exec-volume-test-dynamicpv-sjxf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07852299s
Sep 14 01:20:42.948: INFO: Pod "exec-volume-test-dynamicpv-sjxf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.118567506s
Sep 14 01:20:44.987: INFO: Pod "exec-volume-test-dynamicpv-sjxf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.158208582s
STEP: Saw pod success
Sep 14 01:20:44.987: INFO: Pod "exec-volume-test-dynamicpv-sjxf" satisfied condition "Succeeded or Failed"
Sep 14 01:20:45.026: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000001 pod exec-volume-test-dynamicpv-sjxf container exec-container-dynamicpv-sjxf: <nil>
STEP: delete the pod
Sep 14 01:20:45.116: INFO: Waiting for pod exec-volume-test-dynamicpv-sjxf to disappear
Sep 14 01:20:45.155: INFO: Pod exec-volume-test-dynamicpv-sjxf no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-sjxf
Sep 14 01:20:45.155: INFO: Deleting pod "exec-volume-test-dynamicpv-sjxf" in namespace "volume-5775"
... skipping 14 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:50
    should allow exec of files on the volume
    test/e2e/storage/testsuites/volumes.go:198
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume","total":35,"completed":1,"skipped":388,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] capacity
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:20:50.517: INFO: Driver test.csi.azure.com doesn't publish storage capacity -- skipping
... skipping 76 lines ...

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

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

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 88 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":32,"completed":1,"skipped":18,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:03.651: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 66 lines ...

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

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

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 64 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":1,"skipped":398,"failed":0}

SSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:04.614: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 226 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":41,"completed":1,"skipped":144,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:07.384: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 104 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":38,"completed":2,"skipped":198,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:08.837: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 3 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 60 lines ...
STEP: creating a claim
Sep 14 01:20:51.289: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:20:51.330: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comw8smn] to have phase Bound
Sep 14 01:20:51.368: INFO: PersistentVolumeClaim test.csi.azure.comw8smn found but phase is Pending instead of Bound.
Sep 14 01:20:53.408: INFO: PersistentVolumeClaim test.csi.azure.comw8smn found and phase=Bound (2.077803428s)
STEP: Creating pod to format volume volume-prep-provisioning-3676
Sep 14 01:20:53.524: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-3676" in namespace "provisioning-3676" to be "Succeeded or Failed"
Sep 14 01:20:53.563: INFO: Pod "volume-prep-provisioning-3676": Phase="Pending", Reason="", readiness=false. Elapsed: 38.694884ms
Sep 14 01:20:55.603: INFO: Pod "volume-prep-provisioning-3676": Phase="Pending", Reason="", readiness=false. Elapsed: 2.078547889s
Sep 14 01:20:57.642: INFO: Pod "volume-prep-provisioning-3676": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.117809315s
STEP: Saw pod success
Sep 14 01:20:57.642: INFO: Pod "volume-prep-provisioning-3676" satisfied condition "Succeeded or Failed"
Sep 14 01:20:57.642: INFO: Deleting pod "volume-prep-provisioning-3676" in namespace "provisioning-3676"
Sep 14 01:20:57.686: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-3676" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-8zqt
STEP: Checking for subpath error in container status
Sep 14 01:21:03.842: INFO: Deleting pod "pod-subpath-test-dynamicpv-8zqt" in namespace "provisioning-3676"
Sep 14 01:21:03.890: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-8zqt" to be fully deleted
STEP: Deleting pod
Sep 14 01:21:03.936: INFO: Deleting pod "pod-subpath-test-dynamicpv-8zqt" in namespace "provisioning-3676"
STEP: Deleting pvc
Sep 14 01:21:03.975: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comw8smn"
... skipping 12 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should verify container cannot write to subpath readonly volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:425
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]","total":35,"completed":2,"skipped":504,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode 
  should not mount / map unused volumes in a pod [LinuxOnly]
  test/e2e/storage/testsuites/volumemode.go:354
... skipping 55 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":25,"completed":2,"skipped":370,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:09.927: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 58 lines ...
Sep 14 01:20:47.773: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:20:47.812: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comwvkx6] to have phase Bound
Sep 14 01:20:47.850: INFO: PersistentVolumeClaim test.csi.azure.comwvkx6 found but phase is Pending instead of Bound.
Sep 14 01:20:49.888: INFO: PersistentVolumeClaim test.csi.azure.comwvkx6 found and phase=Bound (2.076266053s)
STEP: Creating pod pod-subpath-test-dynamicpv-872z
STEP: Creating a pod to test subpath
Sep 14 01:20:50.002: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-872z" in namespace "provisioning-5031" to be "Succeeded or Failed"
Sep 14 01:20:50.039: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 37.306584ms
Sep 14 01:20:52.077: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075314966s
Sep 14 01:20:54.115: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.113070915s
Sep 14 01:20:56.153: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.151276527s
Sep 14 01:20:58.191: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.189391413s
STEP: Saw pod success
Sep 14 01:20:58.192: INFO: Pod "pod-subpath-test-dynamicpv-872z" satisfied condition "Succeeded or Failed"
Sep 14 01:20:58.229: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000000 pod pod-subpath-test-dynamicpv-872z container test-container-subpath-dynamicpv-872z: <nil>
STEP: delete the pod
Sep 14 01:20:58.669: INFO: Waiting for pod pod-subpath-test-dynamicpv-872z to disappear
Sep 14 01:20:58.706: INFO: Pod pod-subpath-test-dynamicpv-872z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-872z
Sep 14 01:20:58.706: INFO: Deleting pod "pod-subpath-test-dynamicpv-872z" in namespace "provisioning-5031"
STEP: Creating pod pod-subpath-test-dynamicpv-872z
STEP: Creating a pod to test subpath
Sep 14 01:20:58.782: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-872z" in namespace "provisioning-5031" to be "Succeeded or Failed"
Sep 14 01:20:58.819: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 37.250748ms
Sep 14 01:21:00.857: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0754679s
Sep 14 01:21:02.899: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.117105026s
Sep 14 01:21:04.938: INFO: Pod "pod-subpath-test-dynamicpv-872z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.155657344s
STEP: Saw pod success
Sep 14 01:21:04.938: INFO: Pod "pod-subpath-test-dynamicpv-872z" satisfied condition "Succeeded or Failed"
Sep 14 01:21:04.978: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000000 pod pod-subpath-test-dynamicpv-872z container test-container-subpath-dynamicpv-872z: <nil>
STEP: delete the pod
Sep 14 01:21:05.061: INFO: Waiting for pod pod-subpath-test-dynamicpv-872z to disappear
Sep 14 01:21:05.099: INFO: Pod pod-subpath-test-dynamicpv-872z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-872z
Sep 14 01:21:05.099: INFO: Deleting pod "pod-subpath-test-dynamicpv-872z" in namespace "provisioning-5031"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing directories when readOnly specified in the volumeSource
    test/e2e/storage/testsuites/subpath.go:397
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":34,"completed":2,"skipped":131,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:10.469: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 227 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep 14 01:21:04.931: INFO: Creating resource for dynamic PV
Sep 14 01:21:04.931: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-1644-e2e-scdjhgj
STEP: [init] starting a pod to use the claim
Sep 14 01:21:05.018: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kxj9t" in namespace "snapshotting-1644" to be "Succeeded or Failed"
Sep 14 01:21:05.055: INFO: Pod "pvc-snapshottable-tester-kxj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 37.254429ms
Sep 14 01:21:07.093: INFO: Pod "pvc-snapshottable-tester-kxj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075055214s
Sep 14 01:21:09.130: INFO: Pod "pvc-snapshottable-tester-kxj9t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11227149s
Sep 14 01:21:11.169: INFO: Pod "pvc-snapshottable-tester-kxj9t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.150414319s
STEP: Saw pod success
Sep 14 01:21:11.169: INFO: Pod "pvc-snapshottable-tester-kxj9t" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep 14 01:21:11.206: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep 14 01:21:11.207: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-kxj9t-my-volume] to have phase Bound
Sep 14 01:21:11.244: INFO: PersistentVolumeClaim pvc-snapshottable-tester-kxj9t-my-volume found and phase=Bound (37.260294ms)
STEP: [init] checking the PV
... skipping 112 lines ...
Sep 14 01:21:11.743: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:21:11.782: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comw62xw] to have phase Bound
Sep 14 01:21:11.820: INFO: PersistentVolumeClaim test.csi.azure.comw62xw found but phase is Pending instead of Bound.
Sep 14 01:21:13.857: INFO: PersistentVolumeClaim test.csi.azure.comw62xw found and phase=Bound (2.074711978s)
STEP: Creating pod pod-subpath-test-dynamicpv-rk94
STEP: Creating a pod to test subpath
Sep 14 01:21:13.974: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rk94" in namespace "provisioning-8074" to be "Succeeded or Failed"
Sep 14 01:21:14.011: INFO: Pod "pod-subpath-test-dynamicpv-rk94": Phase="Pending", Reason="", readiness=false. Elapsed: 37.406139ms
Sep 14 01:21:16.050: INFO: Pod "pod-subpath-test-dynamicpv-rk94": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075601304s
Sep 14 01:21:18.089: INFO: Pod "pod-subpath-test-dynamicpv-rk94": Phase="Pending", Reason="", readiness=false. Elapsed: 4.114851178s
Sep 14 01:21:20.127: INFO: Pod "pod-subpath-test-dynamicpv-rk94": Phase="Pending", Reason="", readiness=false. Elapsed: 6.153218115s
Sep 14 01:21:22.167: INFO: Pod "pod-subpath-test-dynamicpv-rk94": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.192904664s
STEP: Saw pod success
Sep 14 01:21:22.167: INFO: Pod "pod-subpath-test-dynamicpv-rk94" satisfied condition "Succeeded or Failed"
Sep 14 01:21:22.205: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000001 pod pod-subpath-test-dynamicpv-rk94 container test-container-subpath-dynamicpv-rk94: <nil>
STEP: delete the pod
Sep 14 01:21:22.305: INFO: Waiting for pod pod-subpath-test-dynamicpv-rk94 to disappear
Sep 14 01:21:22.342: INFO: Pod pod-subpath-test-dynamicpv-rk94 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-rk94
Sep 14 01:21:22.342: INFO: Deleting pod "pod-subpath-test-dynamicpv-rk94" in namespace "provisioning-8074"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly file specified in the volumeMount [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:382
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":34,"completed":3,"skipped":568,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:27.703: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 140 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 109 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should resize volume when PVC is edited while pod is using it
    test/e2e/storage/testsuites/volume_expand.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":25,"completed":3,"skipped":450,"failed":0}

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

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

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

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

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 12 lines ...
Sep 14 01:21:34.394: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:21:34.432: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8tznw] to have phase Bound
Sep 14 01:21:34.467: INFO: PersistentVolumeClaim test.csi.azure.com8tznw found but phase is Pending instead of Bound.
Sep 14 01:21:36.503: INFO: PersistentVolumeClaim test.csi.azure.com8tznw found and phase=Bound (2.071642334s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep 14 01:21:36.647: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-c2r9x" in namespace "snapshotting-8490" to be "Succeeded or Failed"
Sep 14 01:21:36.682: INFO: Pod "pvc-snapshottable-tester-c2r9x": Phase="Pending", Reason="", readiness=false. Elapsed: 35.254348ms
Sep 14 01:21:38.720: INFO: Pod "pvc-snapshottable-tester-c2r9x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072711754s
Sep 14 01:21:40.760: INFO: Pod "pvc-snapshottable-tester-c2r9x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.1131926s
STEP: Saw pod success
Sep 14 01:21:40.760: INFO: Pod "pvc-snapshottable-tester-c2r9x" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep 14 01:21:40.796: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8tznw] to have phase Bound
Sep 14 01:21:40.831: INFO: PersistentVolumeClaim test.csi.azure.com8tznw found and phase=Bound (35.319759ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep 14 01:21:40.941: INFO: Pod pvc-snapshottable-tester-c2r9x has the following logs: 
... skipping 182 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single volume from pods on different node
    test/e2e/storage/testsuites/multivolume.go:451
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node","total":32,"completed":2,"skipped":217,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
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 38 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read-only inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:175
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume","total":41,"completed":2,"skipped":222,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:21:46.891: INFO: Driver test.csi.azure.com doesn't support ext4 -- 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 272 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":25,"completed":4,"skipped":527,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral 
  should support multiple inline ephemeral volumes
  test/e2e/storage/testsuites/ephemeral.go:254
... skipping 37 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":36,"completed":2,"skipped":543,"failed":0}

SSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:04.929: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 90 lines ...
Sep 14 01:21:28.734: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:21:28.773: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comz2t9g] to have phase Bound
Sep 14 01:21:28.810: INFO: PersistentVolumeClaim test.csi.azure.comz2t9g found but phase is Pending instead of Bound.
Sep 14 01:21:30.848: INFO: PersistentVolumeClaim test.csi.azure.comz2t9g found and phase=Bound (2.074820587s)
STEP: Expanding non-expandable pvc
Sep 14 01:21:30.922: INFO: currentPvcSize {{5368709120 0} {<nil>} 5Gi BinarySI}, newSize {{6442450944 0} {<nil>}  BinarySI}
Sep 14 01:21:30.998: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:33.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:35.073: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:37.074: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:39.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:41.074: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:43.074: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:45.077: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:47.074: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:49.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:51.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:53.076: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:55.078: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:57.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:21:59.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:22:01.075: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep 14 01:22:01.151: INFO: Error updating pvc test.csi.azure.comz2t9g: persistentvolumeclaims "test.csi.azure.comz2t9g" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Sep 14 01:22:01.151: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comz2t9g"
Sep 14 01:22:01.190: INFO: Waiting up to 5m0s for PersistentVolume pvc-b24ffc25-de70-47a3-b928-6c47d78273a0 to get deleted
Sep 14 01:22:01.228: INFO: PersistentVolume pvc-b24ffc25-de70-47a3-b928-6c47d78273a0 found and phase=Released (37.650144ms)
Sep 14 01:22:06.277: INFO: PersistentVolume pvc-b24ffc25-de70-47a3-b928-6c47d78273a0 was removed
STEP: Deleting sc
... skipping 8 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should not allow expansion of pvcs without AllowVolumeExpansion property
    test/e2e/storage/testsuites/volume_expand.go:159
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property","total":34,"completed":4,"skipped":918,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:06.455: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 113 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":32,"completed":3,"skipped":360,"failed":0}

SSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:13.101: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 129 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 84 lines ...
Sep 14 01:21:57.217: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:21:57.257: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comw6jcq] to have phase Bound
Sep 14 01:21:57.297: INFO: PersistentVolumeClaim test.csi.azure.comw6jcq found but phase is Pending instead of Bound.
Sep 14 01:21:59.337: INFO: PersistentVolumeClaim test.csi.azure.comw6jcq found and phase=Bound (2.079866299s)
STEP: Creating pod pod-subpath-test-dynamicpv-jwdz
STEP: Creating a pod to test subpath
Sep 14 01:21:59.456: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-jwdz" in namespace "provisioning-6747" to be "Succeeded or Failed"
Sep 14 01:21:59.496: INFO: Pod "pod-subpath-test-dynamicpv-jwdz": Phase="Pending", Reason="", readiness=false. Elapsed: 39.151521ms
Sep 14 01:22:01.536: INFO: Pod "pod-subpath-test-dynamicpv-jwdz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.079549584s
Sep 14 01:22:03.578: INFO: Pod "pod-subpath-test-dynamicpv-jwdz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.121389719s
Sep 14 01:22:05.618: INFO: Pod "pod-subpath-test-dynamicpv-jwdz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.161115626s
Sep 14 01:22:07.661: INFO: Pod "pod-subpath-test-dynamicpv-jwdz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.205007228s
Sep 14 01:22:09.701: INFO: Pod "pod-subpath-test-dynamicpv-jwdz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.244885419s
STEP: Saw pod success
Sep 14 01:22:09.701: INFO: Pod "pod-subpath-test-dynamicpv-jwdz" satisfied condition "Succeeded or Failed"
Sep 14 01:22:09.740: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000000 pod pod-subpath-test-dynamicpv-jwdz container test-container-subpath-dynamicpv-jwdz: <nil>
STEP: delete the pod
Sep 14 01:22:09.833: INFO: Waiting for pod pod-subpath-test-dynamicpv-jwdz to disappear
Sep 14 01:22:09.871: INFO: Pod pod-subpath-test-dynamicpv-jwdz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-jwdz
Sep 14 01:22:09.871: INFO: Deleting pod "pod-subpath-test-dynamicpv-jwdz" in namespace "provisioning-6747"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing single file [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:221
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]","total":25,"completed":5,"skipped":555,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:15.306: INFO: Driver test.csi.azure.com doesn't specify stress test options -- skipping
... skipping 146 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":41,"completed":3,"skipped":271,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:16.137: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 111 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:50
    should store data
    test/e2e/storage/testsuites/volumes.go:161
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes should store data","total":38,"completed":5,"skipped":289,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep 14 01:22:20.193: INFO: >>> kubeConfig: /root/tmp3547499596/kubeconfig/kubeconfig.southcentralus.json
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299
Sep 14 01:22:20.446: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep 14 01:22:20.446: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-3360" for this suite.


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

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

    test/e2e/storage/testsuites/volumes.go:114
------------------------------
... skipping 92 lines ...

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

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

    test/e2e/storage/testsuites/topology.go:93
------------------------------
... skipping 74 lines ...
Sep 14 01:22:05.879: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:05.920: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comw9lvv] to have phase Bound
Sep 14 01:22:05.957: INFO: PersistentVolumeClaim test.csi.azure.comw9lvv found but phase is Pending instead of Bound.
Sep 14 01:22:07.994: INFO: PersistentVolumeClaim test.csi.azure.comw9lvv found and phase=Bound (2.073948547s)
STEP: Creating pod pod-subpath-test-dynamicpv-qp4z
STEP: Creating a pod to test subpath
Sep 14 01:22:08.118: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qp4z" in namespace "provisioning-4374" to be "Succeeded or Failed"
Sep 14 01:22:08.157: INFO: Pod "pod-subpath-test-dynamicpv-qp4z": Phase="Pending", Reason="", readiness=false. Elapsed: 38.297341ms
Sep 14 01:22:10.198: INFO: Pod "pod-subpath-test-dynamicpv-qp4z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.079278189s
Sep 14 01:22:12.237: INFO: Pod "pod-subpath-test-dynamicpv-qp4z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.118825624s
Sep 14 01:22:14.277: INFO: Pod "pod-subpath-test-dynamicpv-qp4z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.157905673s
Sep 14 01:22:16.315: INFO: Pod "pod-subpath-test-dynamicpv-qp4z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.196512883s
STEP: Saw pod success
Sep 14 01:22:16.315: INFO: Pod "pod-subpath-test-dynamicpv-qp4z" satisfied condition "Succeeded or Failed"
Sep 14 01:22:16.353: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000000 pod pod-subpath-test-dynamicpv-qp4z container test-container-subpath-dynamicpv-qp4z: <nil>
STEP: delete the pod
Sep 14 01:22:16.444: INFO: Waiting for pod pod-subpath-test-dynamicpv-qp4z to disappear
Sep 14 01:22:16.481: INFO: Pod pod-subpath-test-dynamicpv-qp4z no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qp4z
Sep 14 01:22:16.481: INFO: Deleting pod "pod-subpath-test-dynamicpv-qp4z" in namespace "provisioning-4374"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly directory specified in the volumeMount
    test/e2e/storage/testsuites/subpath.go:367
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":36,"completed":3,"skipped":652,"failed":0}

SSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:21.884: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 lines ...

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

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

    test/e2e/storage/testsuites/topology.go:93
------------------------------
... skipping 11 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep 14 01:22:22.234: INFO: Creating resource for dynamic PV
Sep 14 01:22:22.234: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-9753-e2e-scvbctt
STEP: [init] starting a pod to use the claim
Sep 14 01:22:22.316: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8fkmg" in namespace "snapshotting-9753" to be "Succeeded or Failed"
Sep 14 01:22:22.352: INFO: Pod "pvc-snapshottable-tester-8fkmg": Phase="Pending", Reason="", readiness=false. Elapsed: 36.400828ms
Sep 14 01:22:24.391: INFO: Pod "pvc-snapshottable-tester-8fkmg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075319061s
Sep 14 01:22:26.444: INFO: Pod "pvc-snapshottable-tester-8fkmg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128399908s
Sep 14 01:22:28.484: INFO: Pod "pvc-snapshottable-tester-8fkmg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.167788288s
STEP: Saw pod success
Sep 14 01:22:28.484: INFO: Pod "pvc-snapshottable-tester-8fkmg" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep 14 01:22:28.521: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep 14 01:22:28.523: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-8fkmg-my-volume] to have phase Bound
Sep 14 01:22:28.560: INFO: PersistentVolumeClaim pvc-snapshottable-tester-8fkmg-my-volume found and phase=Bound (36.975694ms)
STEP: [init] checking the PV
... skipping 105 lines ...

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

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep 14 01:22:13.762: INFO: >>> kubeConfig: /root/tmp3547499596/kubeconfig/kubeconfig.southcentralus.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:280
Sep 14 01:22:14.013: INFO: Creating resource for dynamic PV
Sep 14 01:22:14.013: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-7156-e2e-scf89qz
STEP: creating a claim
Sep 14 01:22:14.051: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:14.090: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comhjsr2] to have phase Bound
Sep 14 01:22:14.134: INFO: PersistentVolumeClaim test.csi.azure.comhjsr2 found but phase is Pending instead of Bound.
Sep 14 01:22:16.171: INFO: PersistentVolumeClaim test.csi.azure.comhjsr2 found and phase=Bound (2.081310728s)
STEP: Creating pod pod-subpath-test-dynamicpv-nt7s
STEP: Checking for subpath error in container status
Sep 14 01:22:22.351: INFO: Deleting pod "pod-subpath-test-dynamicpv-nt7s" in namespace "provisioning-7156"
Sep 14 01:22:22.388: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-nt7s" to be fully deleted
STEP: Deleting pod
Sep 14 01:22:24.460: INFO: Deleting pod "pod-subpath-test-dynamicpv-nt7s" in namespace "provisioning-7156"
STEP: Deleting pvc
Sep 14 01:22:24.495: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comhjsr2"
... skipping 9 lines ...

• [SLOW TEST:15.993 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
------------------------------
S
------------------------------
{"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":32,"completed":4,"skipped":731,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:29.810: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 118 lines ...

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

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep 14 01:22:21.403: INFO: >>> kubeConfig: /root/tmp3547499596/kubeconfig/kubeconfig.southcentralus.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:258
Sep 14 01:22:21.654: INFO: Creating resource for dynamic PV
Sep 14 01:22:21.654: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-1056-e2e-sc6jn4d
STEP: creating a claim
Sep 14 01:22:21.691: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:21.729: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxjlb4] to have phase Bound
Sep 14 01:22:21.765: INFO: PersistentVolumeClaim test.csi.azure.comxjlb4 found but phase is Pending instead of Bound.
Sep 14 01:22:23.800: INFO: PersistentVolumeClaim test.csi.azure.comxjlb4 found and phase=Bound (2.071308598s)
STEP: Creating pod pod-subpath-test-dynamicpv-2tp4
STEP: Checking for subpath error in container status
Sep 14 01:22:29.989: INFO: Deleting pod "pod-subpath-test-dynamicpv-2tp4" in namespace "provisioning-1056"
Sep 14 01:22:30.027: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2tp4" to be fully deleted
STEP: Deleting pod
Sep 14 01:22:34.100: INFO: Deleting pod "pod-subpath-test-dynamicpv-2tp4" in namespace "provisioning-1056"
STEP: Deleting pvc
Sep 14 01:22:34.137: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comxjlb4"
... skipping 9 lines ...

• [SLOW TEST:17.995 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":38,"completed":6,"skipped":481,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[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 12 lines ...
Sep 14 01:22:30.462: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:30.500: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comprv8v] to have phase Bound
Sep 14 01:22:30.540: INFO: PersistentVolumeClaim test.csi.azure.comprv8v found but phase is Pending instead of Bound.
Sep 14 01:22:32.576: INFO: PersistentVolumeClaim test.csi.azure.comprv8v found and phase=Bound (2.076500253s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep 14 01:22:32.742: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-6svl8" in namespace "snapshotting-3267" to be "Succeeded or Failed"
Sep 14 01:22:32.780: INFO: Pod "pvc-snapshottable-tester-6svl8": Phase="Pending", Reason="", readiness=false. Elapsed: 38.068636ms
Sep 14 01:22:34.822: INFO: Pod "pvc-snapshottable-tester-6svl8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.080621032s
Sep 14 01:22:36.859: INFO: Pod "pvc-snapshottable-tester-6svl8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.116870288s
STEP: Saw pod success
Sep 14 01:22:36.859: INFO: Pod "pvc-snapshottable-tester-6svl8" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep 14 01:22:36.894: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comprv8v] to have phase Bound
Sep 14 01:22:36.931: INFO: PersistentVolumeClaim test.csi.azure.comprv8v found and phase=Bound (36.578489ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep 14 01:22:37.043: INFO: Pod pvc-snapshottable-tester-6svl8 has the following logs: 
... skipping 120 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 5 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep 14 01:22:43.136: INFO: >>> kubeConfig: /root/tmp3547499596/kubeconfig/kubeconfig.southcentralus.json
STEP: Building a namespace api object, basename volumemode
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299
Sep 14 01:22:43.384: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep 14 01:22:43.384: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5268" for this suite.


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

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

    test/e2e/storage/testsuites/volumes.go:114
------------------------------
... skipping 120 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":41,"completed":4,"skipped":400,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:45.335: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 59 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":34,"completed":5,"skipped":1014,"failed":0}

SSSSSSSSSSSSSS
------------------------------
Sep 14 01:22:46.277: INFO: Running AfterSuite actions on all nodes
Sep 14 01:22:46.277: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Sep 14 01:22:46.277: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
... skipping 53 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":36,"completed":4,"skipped":998,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance
... skipping 68 lines ...
Sep 14 01:22:39.793: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:39.832: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8jkr6] to have phase Bound
Sep 14 01:22:39.872: INFO: PersistentVolumeClaim test.csi.azure.com8jkr6 found but phase is Pending instead of Bound.
Sep 14 01:22:41.908: INFO: PersistentVolumeClaim test.csi.azure.com8jkr6 found and phase=Bound (2.076875595s)
STEP: Creating pod pod-subpath-test-dynamicpv-snvq
STEP: Creating a pod to test multi_subpath
Sep 14 01:22:42.017: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-snvq" in namespace "provisioning-2397" to be "Succeeded or Failed"
Sep 14 01:22:42.056: INFO: Pod "pod-subpath-test-dynamicpv-snvq": Phase="Pending", Reason="", readiness=false. Elapsed: 38.920581ms
Sep 14 01:22:44.093: INFO: Pod "pod-subpath-test-dynamicpv-snvq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07538565s
Sep 14 01:22:46.130: INFO: Pod "pod-subpath-test-dynamicpv-snvq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.112372495s
Sep 14 01:22:48.167: INFO: Pod "pod-subpath-test-dynamicpv-snvq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.149595157s
STEP: Saw pod success
Sep 14 01:22:48.167: INFO: Pod "pod-subpath-test-dynamicpv-snvq" satisfied condition "Succeeded or Failed"
Sep 14 01:22:48.203: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000000 pod pod-subpath-test-dynamicpv-snvq container test-container-subpath-dynamicpv-snvq: <nil>
STEP: delete the pod
Sep 14 01:22:48.288: INFO: Waiting for pod pod-subpath-test-dynamicpv-snvq to disappear
Sep 14 01:22:48.324: INFO: Pod pod-subpath-test-dynamicpv-snvq no longer exists
STEP: Deleting pod
Sep 14 01:22:48.324: INFO: Deleting pod "pod-subpath-test-dynamicpv-snvq" in namespace "provisioning-2397"
... skipping 14 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support creating multiple subpath from same volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:296
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]","total":38,"completed":7,"skipped":514,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:53.645: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 194 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":35,"completed":3,"skipped":546,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:56.806: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 116 lines ...

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

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep 14 01:22:45.392: INFO: >>> kubeConfig: /root/tmp3547499596/kubeconfig/kubeconfig.southcentralus.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:269
Sep 14 01:22:45.637: INFO: Creating resource for dynamic PV
Sep 14 01:22:45.637: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-744-e2e-scvx8g9
STEP: creating a claim
Sep 14 01:22:45.672: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:45.708: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com4788j] to have phase Bound
Sep 14 01:22:45.742: INFO: PersistentVolumeClaim test.csi.azure.com4788j found but phase is Pending instead of Bound.
Sep 14 01:22:47.777: INFO: PersistentVolumeClaim test.csi.azure.com4788j found and phase=Bound (2.069241948s)
STEP: Creating pod pod-subpath-test-dynamicpv-7tdm
STEP: Checking for subpath error in container status
Sep 14 01:22:51.970: INFO: Deleting pod "pod-subpath-test-dynamicpv-7tdm" in namespace "provisioning-744"
Sep 14 01:22:52.009: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7tdm" to be fully deleted
STEP: Deleting pod
Sep 14 01:22:54.080: INFO: Deleting pod "pod-subpath-test-dynamicpv-7tdm" in namespace "provisioning-744"
STEP: Deleting pvc
Sep 14 01:22:54.114: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com4788j"
... skipping 9 lines ...

• [SLOW TEST:13.968 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":41,"completed":5,"skipped":477,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:22:59.532: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 107 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":25,"completed":6,"skipped":651,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:23:03.924: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 108 lines ...

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

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

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 69 lines ...
Sep 14 01:22:54.920: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:54.963: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.commrrp4] to have phase Bound
Sep 14 01:22:54.999: INFO: PersistentVolumeClaim test.csi.azure.commrrp4 found but phase is Pending instead of Bound.
Sep 14 01:22:57.036: INFO: PersistentVolumeClaim test.csi.azure.commrrp4 found and phase=Bound (2.072427802s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep 14 01:22:57.181: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-rq44k" in namespace "snapshotting-4483" to be "Succeeded or Failed"
Sep 14 01:22:57.217: INFO: Pod "pvc-snapshottable-tester-rq44k": Phase="Pending", Reason="", readiness=false. Elapsed: 35.740963ms
Sep 14 01:22:59.255: INFO: Pod "pvc-snapshottable-tester-rq44k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073936387s
Sep 14 01:23:01.293: INFO: Pod "pvc-snapshottable-tester-rq44k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.111424619s
STEP: Saw pod success
Sep 14 01:23:01.293: INFO: Pod "pvc-snapshottable-tester-rq44k" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep 14 01:23:01.329: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.commrrp4] to have phase Bound
Sep 14 01:23:01.365: INFO: PersistentVolumeClaim test.csi.azure.commrrp4 found and phase=Bound (35.784167ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep 14 01:23:01.482: INFO: Pod pvc-snapshottable-tester-rq44k has the following logs: 
... skipping 101 lines ...
Sep 14 01:22:57.326: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:22:57.367: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com6vdhm] to have phase Bound
Sep 14 01:22:57.405: INFO: PersistentVolumeClaim test.csi.azure.com6vdhm found but phase is Pending instead of Bound.
Sep 14 01:22:59.446: INFO: PersistentVolumeClaim test.csi.azure.com6vdhm found and phase=Bound (2.079337119s)
STEP: Creating pod pod-subpath-test-dynamicpv-n4q9
STEP: Creating a pod to test subpath
Sep 14 01:22:59.569: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-n4q9" in namespace "provisioning-4498" to be "Succeeded or Failed"
Sep 14 01:22:59.609: INFO: Pod "pod-subpath-test-dynamicpv-n4q9": Phase="Pending", Reason="", readiness=false. Elapsed: 39.501307ms
Sep 14 01:23:01.652: INFO: Pod "pod-subpath-test-dynamicpv-n4q9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08274813s
Sep 14 01:23:03.693: INFO: Pod "pod-subpath-test-dynamicpv-n4q9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12331727s
Sep 14 01:23:05.732: INFO: Pod "pod-subpath-test-dynamicpv-n4q9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.162796117s
STEP: Saw pod success
Sep 14 01:23:05.732: INFO: Pod "pod-subpath-test-dynamicpv-n4q9" satisfied condition "Succeeded or Failed"
Sep 14 01:23:05.772: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000001 pod pod-subpath-test-dynamicpv-n4q9 container test-container-volume-dynamicpv-n4q9: <nil>
STEP: delete the pod
Sep 14 01:23:05.861: INFO: Waiting for pod pod-subpath-test-dynamicpv-n4q9 to disappear
Sep 14 01:23:05.904: INFO: Pod pod-subpath-test-dynamicpv-n4q9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-n4q9
Sep 14 01:23:05.904: INFO: Deleting pod "pod-subpath-test-dynamicpv-n4q9" in namespace "provisioning-4498"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing directory
    test/e2e/storage/testsuites/subpath.go:207
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory","total":35,"completed":4,"skipped":640,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:23:11.289: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 199 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":38,"completed":8,"skipped":926,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:23:43.966: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 3 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.009 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 50 lines ...
Sep 14 01:23:11.653: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:23:11.693: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comkdwb9] to have phase Bound
Sep 14 01:23:11.733: INFO: PersistentVolumeClaim test.csi.azure.comkdwb9 found but phase is Pending instead of Bound.
Sep 14 01:23:13.773: INFO: PersistentVolumeClaim test.csi.azure.comkdwb9 found and phase=Bound (2.079526857s)
STEP: Creating pod pod-subpath-test-dynamicpv-s7k7
STEP: Creating a pod to test atomic-volume-subpath
Sep 14 01:23:13.893: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-s7k7" in namespace "provisioning-7692" to be "Succeeded or Failed"
Sep 14 01:23:13.932: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Pending", Reason="", readiness=false. Elapsed: 39.524061ms
Sep 14 01:23:15.972: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.079644266s
Sep 14 01:23:18.013: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120391426s
Sep 14 01:23:20.053: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=true. Elapsed: 6.160645049s
Sep 14 01:23:22.093: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=true. Elapsed: 8.199996909s
Sep 14 01:23:24.132: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=true. Elapsed: 10.239722212s
... skipping 3 lines ...
Sep 14 01:23:32.297: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=true. Elapsed: 18.404812807s
Sep 14 01:23:34.338: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=true. Elapsed: 20.445744867s
Sep 14 01:23:36.380: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=true. Elapsed: 22.487393422s
Sep 14 01:23:38.419: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Running", Reason="", readiness=false. Elapsed: 24.526049411s
Sep 14 01:23:40.458: INFO: Pod "pod-subpath-test-dynamicpv-s7k7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.565005357s
STEP: Saw pod success
Sep 14 01:23:40.458: INFO: Pod "pod-subpath-test-dynamicpv-s7k7" satisfied condition "Succeeded or Failed"
Sep 14 01:23:40.496: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000001 pod pod-subpath-test-dynamicpv-s7k7 container test-container-subpath-dynamicpv-s7k7: <nil>
STEP: delete the pod
Sep 14 01:23:40.597: INFO: Waiting for pod pod-subpath-test-dynamicpv-s7k7 to disappear
Sep 14 01:23:40.638: INFO: Pod pod-subpath-test-dynamicpv-s7k7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-s7k7
Sep 14 01:23:40.638: INFO: Deleting pod "pod-subpath-test-dynamicpv-s7k7" in namespace "provisioning-7692"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support file as subpath [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:232
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]","total":35,"completed":5,"skipped":670,"failed":0}

SSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:23:46.029: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 91 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition","total":41,"completed":6,"skipped":547,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:24:14.031: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 56 lines ...
Sep 14 01:24:14.483: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep 14 01:24:14.521: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comhzd82] to have phase Bound
Sep 14 01:24:14.555: INFO: PersistentVolumeClaim test.csi.azure.comhzd82 found but phase is Pending instead of Bound.
Sep 14 01:24:16.590: INFO: PersistentVolumeClaim test.csi.azure.comhzd82 found and phase=Bound (2.069361856s)
STEP: Creating pod pod-subpath-test-dynamicpv-t4jf
STEP: Creating a pod to test subpath
Sep 14 01:24:16.697: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-t4jf" in namespace "provisioning-7008" to be "Succeeded or Failed"
Sep 14 01:24:16.731: INFO: Pod "pod-subpath-test-dynamicpv-t4jf": Phase="Pending", Reason="", readiness=false. Elapsed: 34.76497ms
Sep 14 01:24:18.767: INFO: Pod "pod-subpath-test-dynamicpv-t4jf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070167519s
Sep 14 01:24:20.803: INFO: Pod "pod-subpath-test-dynamicpv-t4jf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106002732s
Sep 14 01:24:22.840: INFO: Pod "pod-subpath-test-dynamicpv-t4jf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.14331092s
STEP: Saw pod success
Sep 14 01:24:22.840: INFO: Pod "pod-subpath-test-dynamicpv-t4jf" satisfied condition "Succeeded or Failed"
Sep 14 01:24:22.875: INFO: Trying to get logs from node k8s-agentpool1-85858805-vmss000000 pod pod-subpath-test-dynamicpv-t4jf container test-container-volume-dynamicpv-t4jf: <nil>
STEP: delete the pod
Sep 14 01:24:22.954: INFO: Waiting for pod pod-subpath-test-dynamicpv-t4jf to disappear
Sep 14 01:24:22.989: INFO: Pod pod-subpath-test-dynamicpv-t4jf no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-t4jf
Sep 14 01:24:22.989: INFO: Deleting pod "pod-subpath-test-dynamicpv-t4jf" in namespace "provisioning-7008"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support non-existent path
    test/e2e/storage/testsuites/subpath.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path","total":41,"completed":7,"skipped":666,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:24:28.318: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 125 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (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 82 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":6,"skipped":759,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:25:12.238: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 165 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":41,"completed":8,"skipped":830,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep 14 01:25:49.416: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 260 lines ...
Sep 14 01:25:13.198: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep 14 01:25:13.198: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3
Sep 14 01:25:59.101: INFO: Running AfterSuite actions on node 1


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

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

Streaming logs below:
I0914 01:19:15.440630       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-5eab3595ee1680400af0b992b38afe5c8d626ead e2e-test
I0914 01:19:15.441060       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:15.459658       1 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0914 01:19:15.459679       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:15.459686       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0914 01:19:15.459712       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0914 01:19:15.460733       1 azure_auth.go:245] Using AzurePublicCloud environment
I0914 01:19:15.460783       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0914 01:19:15.460803       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 436 lines ...
I0914 01:21:33.005064       1 controllerserver.go:449] begin to create file share(pvcn-23030496-604f-430a-bba5-cbb444b6821e) on account(ff0392c5e4b314cabb6274c) type(Premium_LRS) subID() rg(kubetest-rvnem0gj) location() size(100) protocol(NFS)
I0914 01:21:33.192112       1 controllerserver.go:471] create file share pvcn-23030496-604f-430a-bba5-cbb444b6821e on storage account ff0392c5e4b314cabb6274c successfully
I0914 01:21:33.192172       1 azure_metrics.go:115] "Observed Request Latency" latency_seconds=0.187113081 request="azurefile_csi_driver_controller_create_volume" resource_group="kubetest-rvnem0gj" subscription_id="" source="test.csi.azure.com" volumeid="kubetest-rvnem0gj#ff0392c5e4b314cabb6274c#pvcn-23030496-604f-430a-bba5-cbb444b6821e###multivolume-9245" result_code="succeeded"
I0914 01:21:33.192187       1 utils.go:83] GRPC response: {"volume":{"capacity_bytes":5368709120,"volume_context":{"csi.storage.k8s.io/pv/name":"pvc-23030496-604f-430a-bba5-cbb444b6821e","csi.storage.k8s.io/pvc/name":"test.csi.azure.comqx2t5","csi.storage.k8s.io/pvc/namespace":"multivolume-9245","protocol":"nfs","secretnamespace":"multivolume-9245","skuName":"Premium_LRS"},"volume_id":"kubetest-rvnem0gj#ff0392c5e4b314cabb6274c#pvcn-23030496-604f-430a-bba5-cbb444b6821e###multivolume-9245"}}
I0914 01:21:33.839454       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0914 01:21:33.839482       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-043d67b2-ffb7-4f19-8bc6-1fe828df2aae","parameters":{"csi.storage.k8s.io/pv/name":"pvc-043d67b2-ffb7-4f19-8bc6-1fe828df2aae","csi.storage.k8s.io/pvc/name":"pvc-sbtjv","csi.storage.k8s.io/pvc/namespace":"volumemode-5277","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0914 01:21:33.839837       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0914 01:21:33.979365       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0914 01:21:33.979460       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-043d67b2-ffb7-4f19-8bc6-1fe828df2aae","parameters":{"csi.storage.k8s.io/pv/name":"pvc-043d67b2-ffb7-4f19-8bc6-1fe828df2aae","csi.storage.k8s.io/pvc/name":"pvc-sbtjv","csi.storage.k8s.io/pvc/namespace":"volumemode-5277","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0914 01:21:33.979762       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0914 01:21:34.425479       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0914 01:21:34.425504       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-033a2de3-96d2-4d8c-8277-f4f1284307bd","parameters":{"csi.storage.k8s.io/pv/name":"pvc-033a2de3-96d2-4d8c-8277-f4f1284307bd","csi.storage.k8s.io/pvc/name":"test.csi.azure.com8tznw","csi.storage.k8s.io/pvc/namespace":"snapshotting-8490","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Mount":{}},"access_mode":{"mode":7}}]}
I0914 01:21:34.425667       1 controllerserver.go:294] set vnetResourceID(/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-rvnem0gj/providers/Microsoft.Network/virtualNetworks/k8s-vnet-85858805/subnets/k8s-subnet) for NFS protocol
I0914 01:21:34.425675       1 azure.go:180] updateSubnetServiceEndpoints on vnetName: k8s-vnet-85858805, subnetName: k8s-subnet, location: southcentralus
I0914 01:21:34.465361       1 azure.go:209] serviceEndpoint(Microsoft.Storage) is already in subnet(k8s-subnet)
I0914 01:21:34.545457       1 controllerserver.go:449] begin to create file share(pvcn-033a2de3-96d2-4d8c-8277-f4f1284307bd) on account(ff0392c5e4b314cabb6274c) type(Premium_LRS) subID() rg(kubetest-rvnem0gj) location() size(100) protocol(NFS)
... skipping 501 lines ...
Go Version: go1.19.1
Platform: linux/amd64

Streaming logs below:
I0914 01:19:18.365935       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-5eab3595ee1680400af0b992b38afe5c8d626ead e2e-test
I0914 01:19:18.366425       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:18.388000       1 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0914 01:19:18.388028       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:18.388035       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0914 01:19:18.388073       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0914 01:19:18.388840       1 azure_auth.go:245] Using AzurePublicCloud environment
I0914 01:19:18.388883       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0914 01:19:18.388908       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 105 lines ...
Go Version: go1.19.1
Platform: linux/amd64

Streaming logs below:
I0914 01:19:13.804719       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-5eab3595ee1680400af0b992b38afe5c8d626ead e2e-test
I0914 01:19:13.805164       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:13.827131       1 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0914 01:19:13.827157       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:13.827167       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0914 01:19:13.827198       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0914 01:19:13.828871       1 azure_auth.go:245] Using AzurePublicCloud environment
I0914 01:19:13.828939       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0914 01:19:13.828965       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1469 lines ...
Go Version: go1.19.1
Platform: linux/amd64

Streaming logs below:
I0914 01:19:07.893194       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-5eab3595ee1680400af0b992b38afe5c8d626ead e2e-test
I0914 01:19:07.893500       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:07.912964       1 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0914 01:19:07.912986       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:07.912992       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0914 01:19:07.913008       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0914 01:19:07.913635       1 azure_auth.go:245] Using AzurePublicCloud environment
I0914 01:19:07.913672       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0914 01:19:07.913713       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 72 lines ...
Go Version: go1.19.1
Platform: linux/amd64

Streaming logs below:
I0914 01:19:11.622403       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-5eab3595ee1680400af0b992b38afe5c8d626ead e2e-test
I0914 01:19:11.622791       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:11.644682       1 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0914 01:19:11.644706       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0914 01:19:11.644713       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0914 01:19:11.644735       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0914 01:19:11.645392       1 azure_auth.go:245] Using AzurePublicCloud environment
I0914 01:19:11.645438       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0914 01:19:11.645468       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1170 lines ...
2022/09/14 01:26:53 process.go:153: Running: chmod +x /root/tmp3547499596/win-ci-logs-collector.sh
2022/09/14 01:26:53 process.go:155: Step 'chmod +x /root/tmp3547499596/win-ci-logs-collector.sh' finished in 1.171714ms
2022/09/14 01:26:53 process.go:153: Running: bash -c /root/tmp3547499596/win-ci-logs-collector.sh kubetest-rvnem0gj.southcentralus.cloudapp.azure.com /root/tmp3547499596 /root/.ssh/id_rsa
ssh key file /root/.ssh/id_rsa does not exist. Exiting.
2022/09/14 01:26:53 process.go:155: Step 'bash -c /root/tmp3547499596/win-ci-logs-collector.sh kubetest-rvnem0gj.southcentralus.cloudapp.azure.com /root/tmp3547499596 /root/.ssh/id_rsa' finished in 4.982639ms
2022/09/14 01:26:53 aksengine.go:1141: Deleting resource group: kubetest-rvnem0gj.
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-09-14T01:30:17Z"}
++ early_exit_handler
++ '[' -n 176 ']'
++ kill -TERM 176
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 4 lines ...