This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: chore: refine the log printing in getAccountKeyFromSecret process
Resultsuccess
Tests 0 failed / 14 succeeded
Started2022-09-05 01:44
Elapsed38m28s
Revision
Refs 1079
uploadercrier
uploadercrier

No Test Failures!


Show 14 Passed Tests

Error lines from build-log.txt

... skipping 232 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0  62324      0 --:--:-- --:--:-- --:--:-- 62324
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-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 not found: manifest unknown: manifest tagged by "e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468" 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-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=8c4ac86e0a136f2e10fd01d3a2ae65d071711468 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-09-05T01:50:54Z -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 1853 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 273 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 454 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 73 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 236 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 236 lines ...
Sep  5 02:09:28.019: INFO: PersistentVolumeClaim test.csi.azure.compjwrl found but phase is Pending instead of Bound.
Sep  5 02:09:30.046: INFO: PersistentVolumeClaim test.csi.azure.compjwrl found but phase is Pending instead of Bound.
Sep  5 02:09:32.072: INFO: PersistentVolumeClaim test.csi.azure.compjwrl found but phase is Pending instead of Bound.
Sep  5 02:09:34.099: INFO: PersistentVolumeClaim test.csi.azure.compjwrl found and phase=Bound (54.736073376s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  5 02:09:34.199: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-n9lw7" in namespace "snapshotting-423" to be "Succeeded or Failed"
Sep  5 02:09:34.227: INFO: Pod "pvc-snapshottable-tester-n9lw7": Phase="Pending", Reason="", readiness=false. Elapsed: 28.19396ms
Sep  5 02:09:36.255: INFO: Pod "pvc-snapshottable-tester-n9lw7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055341437s
Sep  5 02:09:38.281: INFO: Pod "pvc-snapshottable-tester-n9lw7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.082287075s
Sep  5 02:09:40.308: INFO: Pod "pvc-snapshottable-tester-n9lw7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.109121296s
STEP: Saw pod success
Sep  5 02:09:40.308: INFO: Pod "pvc-snapshottable-tester-n9lw7" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  5 02:09:40.334: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.compjwrl] to have phase Bound
Sep  5 02:09:40.359: INFO: PersistentVolumeClaim test.csi.azure.compjwrl found and phase=Bound (25.594007ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  5 02:09:40.986: INFO: Pod pvc-snapshottable-tester-n9lw7 has the following logs: 
... skipping 105 lines ...
Sep  5 02:09:29.182: INFO: PersistentVolumeClaim test.csi.azure.comt8pm2 found but phase is Pending instead of Bound.
Sep  5 02:09:31.211: INFO: PersistentVolumeClaim test.csi.azure.comt8pm2 found but phase is Pending instead of Bound.
Sep  5 02:09:33.241: INFO: PersistentVolumeClaim test.csi.azure.comt8pm2 found but phase is Pending instead of Bound.
Sep  5 02:09:35.270: INFO: PersistentVolumeClaim test.csi.azure.comt8pm2 found and phase=Bound (54.836704433s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  5 02:09:35.389: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8sx4h" in namespace "snapshotting-5338" to be "Succeeded or Failed"
Sep  5 02:09:35.418: INFO: Pod "pvc-snapshottable-tester-8sx4h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.676466ms
Sep  5 02:09:37.448: INFO: Pod "pvc-snapshottable-tester-8sx4h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059193394s
Sep  5 02:09:39.479: INFO: Pod "pvc-snapshottable-tester-8sx4h": Phase="Running", Reason="", readiness=false. Elapsed: 4.090120793s
Sep  5 02:09:41.508: INFO: Pod "pvc-snapshottable-tester-8sx4h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.119207719s
STEP: Saw pod success
Sep  5 02:09:41.508: INFO: Pod "pvc-snapshottable-tester-8sx4h" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  5 02:09:41.537: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comt8pm2] to have phase Bound
Sep  5 02:09:41.569: INFO: PersistentVolumeClaim test.csi.azure.comt8pm2 found and phase=Bound (31.848795ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  5 02:09:41.709: INFO: Pod pvc-snapshottable-tester-8sx4h has the following logs: 
... skipping 71 lines ...

        volume type "DynamicPV" is not ephemeral

        test/e2e/storage/testsuites/snapshottable.go:179
------------------------------
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  5 02:09:47.374: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.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  5 02:09:47.723: INFO: Deleting PersistentVolumeClaim "pvc-nlnpf"
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  5 02:09:47.782: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-6247" 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":34,"completed":1,"skipped":324,"failed":0}

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:09:50.814: 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 142 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 117 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":34,"completed":1,"skipped":244,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:03.118: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 232 lines ...
  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
------------------------------
SS
------------------------------
{"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":513,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:03.626: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 168 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":45,"completed":1,"skipped":73,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:09.544: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 181 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":34,"completed":2,"skipped":392,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:13.214: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 204 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":36,"completed":1,"skipped":215,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:15.595: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 97 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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  5 02:10:01.829: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.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  5 02:10:02.031: INFO: Creating resource for dynamic PV
Sep  5 02:10:02.031: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9916-e2e-scwjw7t
STEP: creating a claim
Sep  5 02:10:02.060: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:02.090: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com9rdnf] to have phase Bound
Sep  5 02:10:02.118: INFO: PersistentVolumeClaim test.csi.azure.com9rdnf found but phase is Pending instead of Bound.
Sep  5 02:10:04.147: INFO: PersistentVolumeClaim test.csi.azure.com9rdnf found and phase=Bound (2.056774125s)
STEP: Creating pod pod-subpath-test-dynamicpv-k4k8
STEP: Checking for subpath error in container status
Sep  5 02:10:10.308: INFO: Deleting pod "pod-subpath-test-dynamicpv-k4k8" in namespace "provisioning-9916"
Sep  5 02:10:10.338: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-k4k8" to be fully deleted
STEP: Deleting pod
Sep  5 02:10:14.405: INFO: Deleting pod "pod-subpath-test-dynamicpv-k4k8" in namespace "provisioning-9916"
STEP: Deleting pvc
Sep  5 02:10:14.433: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com9rdnf"
... skipping 9 lines ...

• [SLOW TEST:17.851 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":27,"completed":2,"skipped":344,"failed":0}

SSSSSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/volume_expand.go:248
... skipping 43 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":34,"completed":2,"skipped":525,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 59 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  5 02:10:16.154: INFO: Creating resource for dynamic PV
Sep  5 02:10:16.154: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7934-e2e-scdmgkc
STEP: [init] starting a pod to use the claim
Sep  5 02:10:16.221: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-mhk7f" in namespace "snapshotting-7934" to be "Succeeded or Failed"
Sep  5 02:10:16.249: INFO: Pod "pvc-snapshottable-tester-mhk7f": Phase="Pending", Reason="", readiness=false. Elapsed: 27.892089ms
Sep  5 02:10:18.279: INFO: Pod "pvc-snapshottable-tester-mhk7f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058012677s
Sep  5 02:10:20.313: INFO: Pod "pvc-snapshottable-tester-mhk7f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091859547s
Sep  5 02:10:22.343: INFO: Pod "pvc-snapshottable-tester-mhk7f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.121909959s
STEP: Saw pod success
Sep  5 02:10:22.343: INFO: Pod "pvc-snapshottable-tester-mhk7f" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  5 02:10:22.373: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  5 02:10:22.375: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-mhk7f-my-volume] to have phase Bound
Sep  5 02:10:22.403: INFO: PersistentVolumeClaim pvc-snapshottable-tester-mhk7f-my-volume found and phase=Bound (28.202612ms)
STEP: [init] checking the PV
... skipping 99 lines ...
Sep  5 02:10:09.973: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:10.001: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com9p2pc] to have phase Bound
Sep  5 02:10:10.029: INFO: PersistentVolumeClaim test.csi.azure.com9p2pc found but phase is Pending instead of Bound.
Sep  5 02:10:12.055: INFO: PersistentVolumeClaim test.csi.azure.com9p2pc found and phase=Bound (2.053435042s)
STEP: Creating pod pod-subpath-test-dynamicpv-gllx
STEP: Creating a pod to test multi_subpath
Sep  5 02:10:12.132: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gllx" in namespace "provisioning-8352" to be "Succeeded or Failed"
Sep  5 02:10:12.156: INFO: Pod "pod-subpath-test-dynamicpv-gllx": Phase="Pending", Reason="", readiness=false. Elapsed: 24.823004ms
Sep  5 02:10:14.186: INFO: Pod "pod-subpath-test-dynamicpv-gllx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.054330343s
Sep  5 02:10:16.217: INFO: Pod "pod-subpath-test-dynamicpv-gllx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.085757881s
Sep  5 02:10:18.245: INFO: Pod "pod-subpath-test-dynamicpv-gllx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.113319335s
STEP: Saw pod success
Sep  5 02:10:18.245: INFO: Pod "pod-subpath-test-dynamicpv-gllx" satisfied condition "Succeeded or Failed"
Sep  5 02:10:18.271: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000001 pod pod-subpath-test-dynamicpv-gllx container test-container-subpath-dynamicpv-gllx: <nil>
STEP: delete the pod
Sep  5 02:10:18.331: INFO: Waiting for pod pod-subpath-test-dynamicpv-gllx to disappear
Sep  5 02:10:18.356: INFO: Pod pod-subpath-test-dynamicpv-gllx no longer exists
STEP: Deleting pod
Sep  5 02:10:18.356: INFO: Deleting pod "pod-subpath-test-dynamicpv-gllx" in namespace "provisioning-8352"
... 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":45,"completed":2,"skipped":166,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:23.617: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 110 lines ...
Sep  5 02:10:14.089: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:14.121: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comvmrhn] to have phase Bound
Sep  5 02:10:14.153: INFO: PersistentVolumeClaim test.csi.azure.comvmrhn found but phase is Pending instead of Bound.
Sep  5 02:10:16.185: INFO: PersistentVolumeClaim test.csi.azure.comvmrhn found and phase=Bound (2.063684981s)
STEP: Creating pod pod-subpath-test-dynamicpv-sjsl
STEP: Creating a pod to test subpath
Sep  5 02:10:16.281: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-sjsl" in namespace "provisioning-4824" to be "Succeeded or Failed"
Sep  5 02:10:16.310: INFO: Pod "pod-subpath-test-dynamicpv-sjsl": Phase="Pending", Reason="", readiness=false. Elapsed: 28.587771ms
Sep  5 02:10:18.344: INFO: Pod "pod-subpath-test-dynamicpv-sjsl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062990783s
Sep  5 02:10:20.377: INFO: Pod "pod-subpath-test-dynamicpv-sjsl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096061787s
Sep  5 02:10:22.409: INFO: Pod "pod-subpath-test-dynamicpv-sjsl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.128057382s
STEP: Saw pod success
Sep  5 02:10:22.410: INFO: Pod "pod-subpath-test-dynamicpv-sjsl" satisfied condition "Succeeded or Failed"
Sep  5 02:10:22.442: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000000 pod pod-subpath-test-dynamicpv-sjsl container test-container-volume-dynamicpv-sjsl: <nil>
STEP: delete the pod
Sep  5 02:10:22.517: INFO: Waiting for pod pod-subpath-test-dynamicpv-sjsl to disappear
Sep  5 02:10:22.546: INFO: Pod pod-subpath-test-dynamicpv-sjsl no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-sjsl
Sep  5 02:10:22.546: INFO: Deleting pod "pod-subpath-test-dynamicpv-sjsl" in namespace "provisioning-4824"
... 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":34,"completed":3,"skipped":679,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:27.972: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath 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 11 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  5 02:10:28.397: INFO: Creating resource for dynamic PV
Sep  5 02:10:28.397: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-3771-e2e-scb6mw5
STEP: [init] starting a pod to use the claim
Sep  5 02:10:28.462: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gvtxt" in namespace "snapshotting-3771" to be "Succeeded or Failed"
Sep  5 02:10:28.490: INFO: Pod "pvc-snapshottable-tester-gvtxt": Phase="Pending", Reason="", readiness=false. Elapsed: 28.318689ms
Sep  5 02:10:30.520: INFO: Pod "pvc-snapshottable-tester-gvtxt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058185343s
Sep  5 02:10:32.553: INFO: Pod "pvc-snapshottable-tester-gvtxt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.091755177s
Sep  5 02:10:34.584: INFO: Pod "pvc-snapshottable-tester-gvtxt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.122119618s
Sep  5 02:10:36.614: INFO: Pod "pvc-snapshottable-tester-gvtxt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.15251375s
STEP: Saw pod success
Sep  5 02:10:36.614: INFO: Pod "pvc-snapshottable-tester-gvtxt" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  5 02:10:36.644: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  5 02:10:36.645: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-gvtxt-my-volume] to have phase Bound
Sep  5 02:10:36.674: INFO: PersistentVolumeClaim pvc-snapshottable-tester-gvtxt-my-volume found and phase=Bound (28.420564ms)
STEP: [init] checking the PV
... skipping 119 lines ...
Sep  5 02:10:24.377: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:24.405: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comthns8] to have phase Bound
Sep  5 02:10:24.429: INFO: PersistentVolumeClaim test.csi.azure.comthns8 found but phase is Pending instead of Bound.
Sep  5 02:10:26.455: INFO: PersistentVolumeClaim test.csi.azure.comthns8 found and phase=Bound (2.050779031s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  5 02:10:26.558: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-xw7j5" in namespace "snapshotting-4350" to be "Succeeded or Failed"
Sep  5 02:10:26.583: INFO: Pod "pvc-snapshottable-tester-xw7j5": Phase="Pending", Reason="", readiness=false. Elapsed: 24.725807ms
Sep  5 02:10:28.613: INFO: Pod "pvc-snapshottable-tester-xw7j5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055074933s
Sep  5 02:10:30.640: INFO: Pod "pvc-snapshottable-tester-xw7j5": Phase="Running", Reason="", readiness=true. Elapsed: 4.081149713s
Sep  5 02:10:32.667: INFO: Pod "pvc-snapshottable-tester-xw7j5": Phase="Running", Reason="", readiness=true. Elapsed: 6.10824383s
Sep  5 02:10:34.693: INFO: Pod "pvc-snapshottable-tester-xw7j5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.134144121s
STEP: Saw pod success
Sep  5 02:10:34.693: INFO: Pod "pvc-snapshottable-tester-xw7j5" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  5 02:10:34.720: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comthns8] to have phase Bound
Sep  5 02:10:34.750: INFO: PersistentVolumeClaim test.csi.azure.comthns8 found and phase=Bound (29.441415ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  5 02:10:34.833: INFO: Pod pvc-snapshottable-tester-xw7j5 has the following logs: 
... skipping 80 lines ...
Sep  5 02:10:20.268: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:20.305: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comqnxn9] to have phase Bound
Sep  5 02:10:20.337: INFO: PersistentVolumeClaim test.csi.azure.comqnxn9 found but phase is Pending instead of Bound.
Sep  5 02:10:22.367: INFO: PersistentVolumeClaim test.csi.azure.comqnxn9 found and phase=Bound (2.061080095s)
STEP: Creating pod pod-subpath-test-dynamicpv-h45j
STEP: Creating a pod to test subpath
Sep  5 02:10:22.466: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h45j" in namespace "provisioning-3048" to be "Succeeded or Failed"
Sep  5 02:10:22.496: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Pending", Reason="", readiness=false. Elapsed: 29.497654ms
Sep  5 02:10:24.529: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062966502s
Sep  5 02:10:26.559: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092559758s
Sep  5 02:10:28.592: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12508672s
Sep  5 02:10:30.626: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.160024453s
STEP: Saw pod success
Sep  5 02:10:30.627: INFO: Pod "pod-subpath-test-dynamicpv-h45j" satisfied condition "Succeeded or Failed"
Sep  5 02:10:30.655: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000000 pod pod-subpath-test-dynamicpv-h45j container test-container-subpath-dynamicpv-h45j: <nil>
STEP: delete the pod
Sep  5 02:10:30.726: INFO: Waiting for pod pod-subpath-test-dynamicpv-h45j to disappear
Sep  5 02:10:30.756: INFO: Pod pod-subpath-test-dynamicpv-h45j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h45j
Sep  5 02:10:30.756: INFO: Deleting pod "pod-subpath-test-dynamicpv-h45j" in namespace "provisioning-3048"
STEP: Creating pod pod-subpath-test-dynamicpv-h45j
STEP: Creating a pod to test subpath
Sep  5 02:10:30.814: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-h45j" in namespace "provisioning-3048" to be "Succeeded or Failed"
Sep  5 02:10:30.851: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Pending", Reason="", readiness=false. Elapsed: 36.421187ms
Sep  5 02:10:32.881: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066683422s
Sep  5 02:10:34.913: INFO: Pod "pod-subpath-test-dynamicpv-h45j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.099317577s
STEP: Saw pod success
Sep  5 02:10:34.914: INFO: Pod "pod-subpath-test-dynamicpv-h45j" satisfied condition "Succeeded or Failed"
Sep  5 02:10:34.945: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000001 pod pod-subpath-test-dynamicpv-h45j container test-container-subpath-dynamicpv-h45j: <nil>
STEP: delete the pod
Sep  5 02:10:35.013: INFO: Waiting for pod pod-subpath-test-dynamicpv-h45j to disappear
Sep  5 02:10:35.047: INFO: Pod pod-subpath-test-dynamicpv-h45j no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-h45j
Sep  5 02:10:35.047: INFO: Deleting pod "pod-subpath-test-dynamicpv-h45j" in namespace "provisioning-3048"
... skipping 18 lines ...
  test/e2e/storage/framework/testsuite.go:50
    should support existing directories when readOnly specified in the volumeSource
    test/e2e/storage/testsuites/subpath.go:397
------------------------------
S
------------------------------
{"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":3,"skipped":575,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:40.337: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 45 lines ...

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

SSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral 
  should create read-only inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:175
... skipping 40 lines ...
  test/e2e/storage/framework/testsuite.go:50
    should create read-only inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:175
------------------------------
SS
------------------------------
{"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":34,"completed":2,"skipped":556,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:10:44.976: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 45 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (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 8 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: 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 236 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition","total":31,"completed":1,"skipped":200,"failed":0}

SS
------------------------------
[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 145 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volumeIO
  test/e2e/storage/framework/testsuite.go:50
    should write files of various sizes, verify size, validate content [Slow]
    test/e2e/storage/testsuites/volume_io.go:149
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]","total":36,"completed":2,"skipped":525,"failed":0}

SS
------------------------------
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 51 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    Verify if offline PVC expansion works
    test/e2e/storage/testsuites/volume_expand.go:176
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":45,"completed":3,"skipped":518,"failed":0}

SSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:09.026: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 78 lines ...
STEP: creating a claim
Sep  5 02:10:54.557: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:54.592: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comcj9mp] to have phase Bound
Sep  5 02:10:54.616: INFO: PersistentVolumeClaim test.csi.azure.comcj9mp found but phase is Pending instead of Bound.
Sep  5 02:10:56.642: INFO: PersistentVolumeClaim test.csi.azure.comcj9mp found and phase=Bound (2.050442386s)
STEP: Creating pod to format volume volume-prep-provisioning-7266
Sep  5 02:10:56.719: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-7266" in namespace "provisioning-7266" to be "Succeeded or Failed"
Sep  5 02:10:56.745: INFO: Pod "volume-prep-provisioning-7266": Phase="Pending", Reason="", readiness=false. Elapsed: 26.054381ms
Sep  5 02:10:58.771: INFO: Pod "volume-prep-provisioning-7266": Phase="Pending", Reason="", readiness=false. Elapsed: 2.052149454s
Sep  5 02:11:00.798: INFO: Pod "volume-prep-provisioning-7266": Phase="Pending", Reason="", readiness=false. Elapsed: 4.079166929s
Sep  5 02:11:02.824: INFO: Pod "volume-prep-provisioning-7266": Phase="Pending", Reason="", readiness=false. Elapsed: 6.104727634s
Sep  5 02:11:04.850: INFO: Pod "volume-prep-provisioning-7266": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.131123388s
STEP: Saw pod success
Sep  5 02:11:04.850: INFO: Pod "volume-prep-provisioning-7266" satisfied condition "Succeeded or Failed"
Sep  5 02:11:04.850: INFO: Deleting pod "volume-prep-provisioning-7266" in namespace "provisioning-7266"
Sep  5 02:11:04.882: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-7266" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-b9tf
STEP: Checking for subpath error in container status
Sep  5 02:11:08.989: INFO: Deleting pod "pod-subpath-test-dynamicpv-b9tf" in namespace "provisioning-7266"
Sep  5 02:11:09.015: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-b9tf" to be fully deleted
STEP: Deleting pod
Sep  5 02:11:11.077: INFO: Deleting pod "pod-subpath-test-dynamicpv-b9tf" in namespace "provisioning-7266"
STEP: Deleting pvc
Sep  5 02:11:11.109: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comcj9mp"
... skipping 37 lines ...
Sep  5 02:10:45.642: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:10:45.673: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comntx8g] to have phase Bound
Sep  5 02:10:45.701: INFO: PersistentVolumeClaim test.csi.azure.comntx8g found but phase is Pending instead of Bound.
Sep  5 02:10:47.729: INFO: PersistentVolumeClaim test.csi.azure.comntx8g found and phase=Bound (2.056433882s)
STEP: Creating pod pod-subpath-test-dynamicpv-52db
STEP: Creating a pod to test atomic-volume-subpath
Sep  5 02:10:47.817: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-52db" in namespace "provisioning-9955" to be "Succeeded or Failed"
Sep  5 02:10:47.846: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Pending", Reason="", readiness=false. Elapsed: 28.19816ms
Sep  5 02:10:49.878: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060165264s
Sep  5 02:10:51.907: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 4.089533516s
Sep  5 02:10:53.937: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 6.119870209s
Sep  5 02:10:55.967: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 8.149779454s
Sep  5 02:10:57.997: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 10.179572521s
... skipping 3 lines ...
Sep  5 02:11:06.114: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 18.296140203s
Sep  5 02:11:08.144: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 20.326140615s
Sep  5 02:11:10.177: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=true. Elapsed: 22.360016687s
Sep  5 02:11:12.214: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Running", Reason="", readiness=false. Elapsed: 24.396060384s
Sep  5 02:11:14.249: INFO: Pod "pod-subpath-test-dynamicpv-52db": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.431982346s
STEP: Saw pod success
Sep  5 02:11:14.250: INFO: Pod "pod-subpath-test-dynamicpv-52db" satisfied condition "Succeeded or Failed"
Sep  5 02:11:14.281: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000001 pod pod-subpath-test-dynamicpv-52db container test-container-subpath-dynamicpv-52db: <nil>
STEP: delete the pod
Sep  5 02:11:14.348: INFO: Waiting for pod pod-subpath-test-dynamicpv-52db to disappear
Sep  5 02:11:14.376: INFO: Pod pod-subpath-test-dynamicpv-52db no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-52db
Sep  5 02:11:14.376: INFO: Deleting pod "pod-subpath-test-dynamicpv-52db" in namespace "provisioning-9955"
... 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":27,"completed":4,"skipped":656,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:19.693: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 45 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
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  5 02:11:09.137: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.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  5 02:11:09.330: INFO: Creating resource for dynamic PV
Sep  5 02:11:09.330: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4685-e2e-scdttx6
STEP: creating a claim
Sep  5 02:11:09.357: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:11:09.384: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comcj2h9] to have phase Bound
Sep  5 02:11:09.409: INFO: PersistentVolumeClaim test.csi.azure.comcj2h9 found but phase is Pending instead of Bound.
Sep  5 02:11:11.439: INFO: PersistentVolumeClaim test.csi.azure.comcj2h9 found and phase=Bound (2.054274941s)
STEP: Creating pod pod-subpath-test-dynamicpv-rmcg
STEP: Checking for subpath error in container status
Sep  5 02:11:17.583: INFO: Deleting pod "pod-subpath-test-dynamicpv-rmcg" in namespace "provisioning-4685"
Sep  5 02:11:17.610: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rmcg" to be fully deleted
STEP: Deleting pod
Sep  5 02:11:19.660: INFO: Deleting pod "pod-subpath-test-dynamicpv-rmcg" in namespace "provisioning-4685"
STEP: Deleting pvc
Sep  5 02:11:19.685: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comcj2h9"
... skipping 9 lines ...

• [SLOW TEST:15.729 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":45,"completed":4,"skipped":581,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] provisioning
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:24.890: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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 26 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  5 02:11:25.086: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.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  5 02:11:25.266: 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  5 02:11:25.268: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-1949" for this suite.


S [SKIPPING] [0.259 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 288 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":34,"completed":3,"skipped":776,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:26.364: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 45 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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 92 lines ...
Sep  5 02:11:20.468: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:11:20.497: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comtkkql] to have phase Bound
Sep  5 02:11:20.525: INFO: PersistentVolumeClaim test.csi.azure.comtkkql found but phase is Pending instead of Bound.
Sep  5 02:11:22.557: INFO: PersistentVolumeClaim test.csi.azure.comtkkql found and phase=Bound (2.059604315s)
STEP: Creating pod pod-subpath-test-dynamicpv-tjvq
STEP: Creating a pod to test subpath
Sep  5 02:11:22.643: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-tjvq" in namespace "provisioning-9517" to be "Succeeded or Failed"
Sep  5 02:11:22.672: INFO: Pod "pod-subpath-test-dynamicpv-tjvq": Phase="Pending", Reason="", readiness=false. Elapsed: 28.350037ms
Sep  5 02:11:24.700: INFO: Pod "pod-subpath-test-dynamicpv-tjvq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057136592s
Sep  5 02:11:26.730: INFO: Pod "pod-subpath-test-dynamicpv-tjvq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086580357s
Sep  5 02:11:28.760: INFO: Pod "pod-subpath-test-dynamicpv-tjvq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.116607557s
STEP: Saw pod success
Sep  5 02:11:28.760: INFO: Pod "pod-subpath-test-dynamicpv-tjvq" satisfied condition "Succeeded or Failed"
Sep  5 02:11:28.788: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000000 pod pod-subpath-test-dynamicpv-tjvq container test-container-subpath-dynamicpv-tjvq: <nil>
STEP: delete the pod
Sep  5 02:11:28.854: INFO: Waiting for pod pod-subpath-test-dynamicpv-tjvq to disappear
Sep  5 02:11:28.883: INFO: Pod pod-subpath-test-dynamicpv-tjvq no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-tjvq
Sep  5 02:11:28.884: INFO: Deleting pod "pod-subpath-test-dynamicpv-tjvq" in namespace "provisioning-9517"
... 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":27,"completed":5,"skipped":802,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:34.260: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 35 lines ...
Sep  5 02:11:25.832: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:11:25.862: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comv9kfx] to have phase Bound
Sep  5 02:11:25.887: INFO: PersistentVolumeClaim test.csi.azure.comv9kfx found but phase is Pending instead of Bound.
Sep  5 02:11:27.913: INFO: PersistentVolumeClaim test.csi.azure.comv9kfx found and phase=Bound (2.050984843s)
STEP: Creating pod pod-subpath-test-dynamicpv-bq6n
STEP: Creating a pod to test subpath
Sep  5 02:11:27.991: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-bq6n" in namespace "provisioning-1150" to be "Succeeded or Failed"
Sep  5 02:11:28.015: INFO: Pod "pod-subpath-test-dynamicpv-bq6n": Phase="Pending", Reason="", readiness=false. Elapsed: 24.61337ms
Sep  5 02:11:30.042: INFO: Pod "pod-subpath-test-dynamicpv-bq6n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.05113361s
Sep  5 02:11:32.068: INFO: Pod "pod-subpath-test-dynamicpv-bq6n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.077590379s
Sep  5 02:11:34.095: INFO: Pod "pod-subpath-test-dynamicpv-bq6n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.103668282s
STEP: Saw pod success
Sep  5 02:11:34.095: INFO: Pod "pod-subpath-test-dynamicpv-bq6n" satisfied condition "Succeeded or Failed"
Sep  5 02:11:34.119: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000000 pod pod-subpath-test-dynamicpv-bq6n container test-container-volume-dynamicpv-bq6n: <nil>
STEP: delete the pod
Sep  5 02:11:34.189: INFO: Waiting for pod pod-subpath-test-dynamicpv-bq6n to disappear
Sep  5 02:11:34.215: INFO: Pod pod-subpath-test-dynamicpv-bq6n no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-bq6n
Sep  5 02:11:34.215: INFO: Deleting pod "pod-subpath-test-dynamicpv-bq6n" in namespace "provisioning-1150"
... 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":45,"completed":5,"skipped":860,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:39.498: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 122 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read/write inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read/write inline ephemeral volume","total":36,"completed":3,"skipped":527,"failed":0}

SSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should be able to unmount after the subpath directory is deleted [LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:447
... skipping 43 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":27,"completed":6,"skipped":842,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 108 lines ...
Sep  5 02:11:39.801: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:11:39.829: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combv6dd] to have phase Bound
Sep  5 02:11:39.858: INFO: PersistentVolumeClaim test.csi.azure.combv6dd found but phase is Pending instead of Bound.
Sep  5 02:11:41.885: INFO: PersistentVolumeClaim test.csi.azure.combv6dd found and phase=Bound (2.05538665s)
STEP: Creating pod exec-volume-test-dynamicpv-qxps
STEP: Creating a pod to test exec-volume-test
Sep  5 02:11:41.962: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-qxps" in namespace "volume-9974" to be "Succeeded or Failed"
Sep  5 02:11:41.987: INFO: Pod "exec-volume-test-dynamicpv-qxps": Phase="Pending", Reason="", readiness=false. Elapsed: 24.757443ms
Sep  5 02:11:44.013: INFO: Pod "exec-volume-test-dynamicpv-qxps": Phase="Pending", Reason="", readiness=false. Elapsed: 2.050864441s
Sep  5 02:11:46.045: INFO: Pod "exec-volume-test-dynamicpv-qxps": Phase="Pending", Reason="", readiness=false. Elapsed: 4.083350325s
Sep  5 02:11:48.073: INFO: Pod "exec-volume-test-dynamicpv-qxps": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.110647326s
STEP: Saw pod success
Sep  5 02:11:48.073: INFO: Pod "exec-volume-test-dynamicpv-qxps" satisfied condition "Succeeded or Failed"
Sep  5 02:11:48.098: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000001 pod exec-volume-test-dynamicpv-qxps container exec-container-dynamicpv-qxps: <nil>
STEP: delete the pod
Sep  5 02:11:48.158: INFO: Waiting for pod exec-volume-test-dynamicpv-qxps to disappear
Sep  5 02:11:48.186: INFO: Pod exec-volume-test-dynamicpv-qxps no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-qxps
Sep  5 02:11:48.186: INFO: Deleting pod "exec-volume-test-dynamicpv-qxps" in namespace "volume-9974"
... 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":45,"completed":6,"skipped":923,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:53.467: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 89 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition","total":34,"completed":4,"skipped":589,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volume-stress
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:54.413: INFO: Driver test.csi.azure.com doesn't specify stress test options -- skipping
... skipping 45 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 (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 82 lines ...
SSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral 
  should create read/write inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:196

{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]","total":31,"completed":2,"skipped":417,"failed":0}
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  5 02:11:16.308: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.json
... skipping 31 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read/write inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume","total":31,"completed":3,"skipped":417,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:11:55.585: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 58 lines ...
Sep  5 02:11:49.291: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:11:49.321: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comvg6g7] to have phase Bound
Sep  5 02:11:49.353: INFO: PersistentVolumeClaim test.csi.azure.comvg6g7 found but phase is Pending instead of Bound.
Sep  5 02:11:51.383: INFO: PersistentVolumeClaim test.csi.azure.comvg6g7 found and phase=Bound (2.061941165s)
STEP: Creating pod pod-subpath-test-dynamicpv-9smz
STEP: Creating a pod to test subpath
Sep  5 02:11:51.472: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9smz" in namespace "provisioning-5151" to be "Succeeded or Failed"
Sep  5 02:11:51.508: INFO: Pod "pod-subpath-test-dynamicpv-9smz": Phase="Pending", Reason="", readiness=false. Elapsed: 35.012269ms
Sep  5 02:11:53.541: INFO: Pod "pod-subpath-test-dynamicpv-9smz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068909859s
Sep  5 02:11:55.572: INFO: Pod "pod-subpath-test-dynamicpv-9smz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099217235s
Sep  5 02:11:57.603: INFO: Pod "pod-subpath-test-dynamicpv-9smz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.130859565s
STEP: Saw pod success
Sep  5 02:11:57.604: INFO: Pod "pod-subpath-test-dynamicpv-9smz" satisfied condition "Succeeded or Failed"
Sep  5 02:11:57.634: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000000 pod pod-subpath-test-dynamicpv-9smz container test-container-subpath-dynamicpv-9smz: <nil>
STEP: delete the pod
Sep  5 02:11:57.710: INFO: Waiting for pod pod-subpath-test-dynamicpv-9smz to disappear
Sep  5 02:11:57.742: INFO: Pod pod-subpath-test-dynamicpv-9smz no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-9smz
Sep  5 02:11:57.742: INFO: Deleting pod "pod-subpath-test-dynamicpv-9smz" in namespace "provisioning-5151"
... 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":36,"completed":4,"skipped":584,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:03.090: INFO: Driver "test.csi.azure.com" does not support block volume mode - skipping
... skipping 214 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":34,"completed":4,"skipped":900,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:08.386: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 110 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support restarting containers using directory as subpath [Slow]
    test/e2e/storage/testsuites/subpath.go:322
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]","total":34,"completed":4,"skipped":892,"failed":0}

SSSSSSS
------------------------------
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
  test/e2e/storage/testsuites/multivolume.go:451
... skipping 141 lines ...
  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
------------------------------
SS
------------------------------
{"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":45,"completed":7,"skipped":1014,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:24.887: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 100 lines ...
Sep  5 02:11:55.880: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:11:55.907: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comvvs9b] to have phase Bound
Sep  5 02:11:55.945: INFO: PersistentVolumeClaim test.csi.azure.comvvs9b found but phase is Pending instead of Bound.
Sep  5 02:11:57.977: INFO: PersistentVolumeClaim test.csi.azure.comvvs9b found and phase=Bound (2.070056727s)
STEP: Expanding non-expandable pvc
Sep  5 02:11:58.029: INFO: currentPvcSize {{5368709120 0} {<nil>} 5Gi BinarySI}, newSize {{6442450944 0} {<nil>}  BinarySI}
Sep  5 02:11:58.083: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:00.137: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:02.137: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:04.140: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:06.147: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:08.177: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:10.142: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:12.137: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:14.143: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:16.135: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:18.149: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:20.138: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:22.136: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:24.149: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:26.137: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:28.135: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  5 02:12:28.186: INFO: Error updating pvc test.csi.azure.comvvs9b: persistentvolumeclaims "test.csi.azure.comvvs9b" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Sep  5 02:12:28.186: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comvvs9b"
Sep  5 02:12:28.211: INFO: Waiting up to 5m0s for PersistentVolume pvc-03651af7-9273-47f3-8474-d3d7dae20c75 to get deleted
Sep  5 02:12:28.237: INFO: PersistentVolume pvc-03651af7-9273-47f3-8474-d3d7dae20c75 found and phase=Released (25.282227ms)
Sep  5 02:12:33.262: INFO: PersistentVolume pvc-03651af7-9273-47f3-8474-d3d7dae20c75 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":31,"completed":4,"skipped":509,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:33.390: 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 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 8 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:50
    should fail to 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 295 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":34,"completed":5,"skipped":688,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:34.699: INFO: Driver test.csi.azure.com doesn't specify snapshot stress test options -- skipping
... skipping 80 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":36,"completed":5,"skipped":851,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:44.084: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 42 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  5 02:12:44.211: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.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  5 02:12:44.413: 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  5 02:12:44.414: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4255" for this suite.


S [SKIPPING] [0.262 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 38 lines ...
Sep  5 02:12:35.332: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:12:35.365: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8ln7x] to have phase Bound
Sep  5 02:12:35.393: INFO: PersistentVolumeClaim test.csi.azure.com8ln7x found but phase is Pending instead of Bound.
Sep  5 02:12:37.424: INFO: PersistentVolumeClaim test.csi.azure.com8ln7x found and phase=Bound (2.058182862s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  5 02:12:37.539: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-k8c9h" in namespace "snapshotting-4931" to be "Succeeded or Failed"
Sep  5 02:12:37.568: INFO: Pod "pvc-snapshottable-tester-k8c9h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.719489ms
Sep  5 02:12:39.598: INFO: Pod "pvc-snapshottable-tester-k8c9h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058875722s
Sep  5 02:12:41.628: INFO: Pod "pvc-snapshottable-tester-k8c9h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.08877087s
STEP: Saw pod success
Sep  5 02:12:41.628: INFO: Pod "pvc-snapshottable-tester-k8c9h" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  5 02:12:41.659: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8ln7x] to have phase Bound
Sep  5 02:12:41.688: INFO: PersistentVolumeClaim test.csi.azure.com8ln7x found and phase=Bound (28.339219ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  5 02:12:41.775: INFO: Pod pvc-snapshottable-tester-k8c9h has the following logs: 
... skipping 35 lines ...

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

[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  5 02:12:34.088: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.json
STEP: Building a namespace api object, basename provisioning
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:242
Sep  5 02:12:34.274: INFO: Creating resource for dynamic PV
Sep  5 02:12:34.274: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6402-e2e-scvll7m
STEP: creating a claim
Sep  5 02:12:34.301: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:12:34.329: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comdgpm4] to have phase Bound
Sep  5 02:12:34.357: INFO: PersistentVolumeClaim test.csi.azure.comdgpm4 found but phase is Pending instead of Bound.
Sep  5 02:12:36.383: INFO: PersistentVolumeClaim test.csi.azure.comdgpm4 found and phase=Bound (2.054103971s)
STEP: Creating pod pod-subpath-test-dynamicpv-4h9r
STEP: Checking for subpath error in container status
Sep  5 02:12:40.512: INFO: Deleting pod "pod-subpath-test-dynamicpv-4h9r" in namespace "provisioning-6402"
Sep  5 02:12:40.538: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-4h9r" to be fully deleted
STEP: Deleting pod
Sep  5 02:12:42.589: INFO: Deleting pod "pod-subpath-test-dynamicpv-4h9r" in namespace "provisioning-6402"
STEP: Deleting pvc
Sep  5 02:12:42.614: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comdgpm4"
... skipping 9 lines ...

• [SLOW TEST:13.711 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":31,"completed":5,"skipped":611,"failed":0}

SSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:12:47.828: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 87 lines ...

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

SSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (xfs)][Slow] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:13:07.956: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 163 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":34,"completed":6,"skipped":823,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:13:13.288: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 141 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":31,"completed":6,"skipped":924,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support readOnly file specified in the volumeMount [LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:382
... skipping 16 lines ...
Sep  5 02:14:33.577: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:14:33.605: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comg4jzt] to have phase Bound
Sep  5 02:14:33.630: INFO: PersistentVolumeClaim test.csi.azure.comg4jzt found but phase is Pending instead of Bound.
Sep  5 02:14:35.661: INFO: PersistentVolumeClaim test.csi.azure.comg4jzt found and phase=Bound (2.056061661s)
STEP: Creating pod pod-subpath-test-dynamicpv-khxc
STEP: Creating a pod to test subpath
Sep  5 02:14:35.746: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-khxc" in namespace "provisioning-6581" to be "Succeeded or Failed"
Sep  5 02:14:35.774: INFO: Pod "pod-subpath-test-dynamicpv-khxc": Phase="Pending", Reason="", readiness=false. Elapsed: 27.544941ms
Sep  5 02:14:37.804: INFO: Pod "pod-subpath-test-dynamicpv-khxc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057584279s
Sep  5 02:14:39.842: INFO: Pod "pod-subpath-test-dynamicpv-khxc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.095872875s
Sep  5 02:14:41.869: INFO: Pod "pod-subpath-test-dynamicpv-khxc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.123005103s
STEP: Saw pod success
Sep  5 02:14:41.869: INFO: Pod "pod-subpath-test-dynamicpv-khxc" satisfied condition "Succeeded or Failed"
Sep  5 02:14:41.898: INFO: Trying to get logs from node k8s-agentpool1-35155399-vmss000000 pod pod-subpath-test-dynamicpv-khxc container test-container-subpath-dynamicpv-khxc: <nil>
STEP: delete the pod
Sep  5 02:14:41.982: INFO: Waiting for pod pod-subpath-test-dynamicpv-khxc to disappear
Sep  5 02:14:42.009: INFO: Pod pod-subpath-test-dynamicpv-khxc no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-khxc
Sep  5 02:14:42.009: INFO: Deleting pod "pod-subpath-test-dynamicpv-khxc" in namespace "provisioning-6581"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly file specified in the volumeMount [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:382
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":31,"completed":7,"skipped":956,"failed":0}

SSSSSSSS
------------------------------
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  5 02:14:47.274: INFO: >>> kubeConfig: /root/tmp2366196617/kubeconfig/kubeconfig.centralus.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  5 02:14:47.457: INFO: Creating resource for dynamic PV
Sep  5 02:14:47.457: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-3747-e2e-scw7c6c
STEP: creating a claim
Sep  5 02:14:47.485: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  5 02:14:47.513: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comzg4zj] to have phase Bound
Sep  5 02:14:47.538: INFO: PersistentVolumeClaim test.csi.azure.comzg4zj found but phase is Pending instead of Bound.
Sep  5 02:14:49.564: INFO: PersistentVolumeClaim test.csi.azure.comzg4zj found and phase=Bound (2.05030285s)
STEP: Creating pod pod-subpath-test-dynamicpv-gvwz
STEP: Checking for subpath error in container status
Sep  5 02:14:53.696: INFO: Deleting pod "pod-subpath-test-dynamicpv-gvwz" in namespace "provisioning-3747"
Sep  5 02:14:53.733: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-gvwz" to be fully deleted
STEP: Deleting pod
Sep  5 02:14:55.786: INFO: Deleting pod "pod-subpath-test-dynamicpv-gvwz" in namespace "provisioning-3747"
STEP: Deleting pvc
Sep  5 02:14:55.811: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comzg4zj"
... skipping 9 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  5 02:15:01.167: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 34 lines ...
Sep  5 02:13:13.665: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep  5 02:13:13.665: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3
Sep  5 02:15:01.273: INFO: Running AfterSuite actions on node 1


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

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

Streaming logs below:
I0905 02:08:24.827096       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 e2e-test
I0905 02:08:24.827386       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:24.844499       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
I0905 02:08:24.844517       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:24.844523       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0905 02:08:24.844544       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0905 02:08:24.845067       1 azure_auth.go:245] Using AzurePublicCloud environment
I0905 02:08:24.845101       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0905 02:08:24.845120       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 198 lines ...
I0905 02:09:46.709792       1 controllerserver.go:452] begin to create file share(pvcn-2ac1c384-04ca-4090-b7d7-8d46c6d2edad) on account(f72910a55e024413b951f8d) type(Premium_LRS) rg(kubetest-fhg3oj4m) location() size(100) protocol(NFS)
I0905 02:09:46.896834       1 controllerserver.go:474] create file share pvcn-2ac1c384-04ca-4090-b7d7-8d46c6d2edad on storage account f72910a55e024413b951f8d successfully
I0905 02:09:46.896885       1 azure_metrics.go:115] "Observed Request Latency" latency_seconds=0.187101598 request="azurefile_csi_driver_controller_create_volume" resource_group="kubetest-fhg3oj4m" subscription_id="0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e" source="test.csi.azure.com" volumeid="kubetest-fhg3oj4m#f72910a55e024413b951f8d#pvcn-2ac1c384-04ca-4090-b7d7-8d46c6d2edad###fsgroupchangepolicy-358" result_code="succeeded"
I0905 02:09:46.897138       1 utils.go:83] GRPC response: {"volume":{"capacity_bytes":5368709120,"volume_context":{"csi.storage.k8s.io/pv/name":"pvc-2ac1c384-04ca-4090-b7d7-8d46c6d2edad","csi.storage.k8s.io/pvc/name":"test.csi.azure.comxlv8l","csi.storage.k8s.io/pvc/namespace":"fsgroupchangepolicy-358","protocol":"nfs","secretnamespace":"fsgroupchangepolicy-358","skuName":"Premium_LRS"},"volume_id":"kubetest-fhg3oj4m#f72910a55e024413b951f8d#pvcn-2ac1c384-04ca-4090-b7d7-8d46c6d2edad###fsgroupchangepolicy-358"}}
I0905 02:09:47.623311       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0905 02:09:47.623329       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-29b3bffe-9635-4380-b58f-44f9a2b38b9d","parameters":{"csi.storage.k8s.io/pv/name":"pvc-29b3bffe-9635-4380-b58f-44f9a2b38b9d","csi.storage.k8s.io/pvc/name":"pvc-nlnpf","csi.storage.k8s.io/pvc/namespace":"volumemode-6247","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0905 02:09:47.623611       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0905 02:09:47.740044       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0905 02:09:47.740062       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-29b3bffe-9635-4380-b58f-44f9a2b38b9d","parameters":{"csi.storage.k8s.io/pv/name":"pvc-29b3bffe-9635-4380-b58f-44f9a2b38b9d","csi.storage.k8s.io/pvc/name":"pvc-nlnpf","csi.storage.k8s.io/pvc/namespace":"volumemode-6247","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0905 02:09:47.740223       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0905 02:09:48.452600       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0905 02:09:48.452613       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-f643367c-f70c-445c-a50e-c2ed9ade6b71","parameters":{"csi.storage.k8s.io/pv/name":"pvc-f643367c-f70c-445c-a50e-c2ed9ade6b71","csi.storage.k8s.io/pvc/name":"test.csi.azure.comqhccx","csi.storage.k8s.io/pvc/namespace":"multivolume-1555","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Mount":{}},"access_mode":{"mode":7}}]}
I0905 02:09:48.452739       1 controllerserver.go:297] set vnetResourceID(/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fhg3oj4m/providers/Microsoft.Network/virtualNetworks/k8s-vnet-35155399/subnets/k8s-subnet) for NFS protocol
I0905 02:09:48.452745       1 azure.go:180] updateSubnetServiceEndpoints on vnetName: k8s-vnet-35155399, subnetName: k8s-subnet, location: centralus
I0905 02:09:48.512222       1 azure.go:209] serviceEndpoint(Microsoft.Storage) is already in subnet(k8s-subnet)
I0905 02:09:48.590708       1 controllerserver.go:452] begin to create file share(pvcn-f643367c-f70c-445c-a50e-c2ed9ade6b71) on account(f72910a55e024413b951f8d) type(Premium_LRS) rg(kubetest-fhg3oj4m) location() size(100) protocol(NFS)
... skipping 738 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0905 02:08:26.024582       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 e2e-test
I0905 02:08:26.025069       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:26.045520       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
I0905 02:08:26.045543       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:26.045549       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0905 02:08:26.045577       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0905 02:08:26.046131       1 azure_auth.go:245] Using AzurePublicCloud environment
I0905 02:08:26.046169       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0905 02:08:26.046198       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
Platform: linux/amd64

Streaming logs below:
I0905 02:08:19.060742       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 e2e-test
I0905 02:08:19.061085       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:19.079446       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
I0905 02:08:19.079463       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:19.079469       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0905 02:08:19.079499       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0905 02:08:19.080915       1 azure_auth.go:245] Using AzurePublicCloud environment
I0905 02:08:19.080950       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0905 02:08:19.080970       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 72 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0905 02:08:23.005884       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 e2e-test
I0905 02:08:23.006223       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:23.023993       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
I0905 02:08:23.024013       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:23.024019       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0905 02:08:23.024045       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0905 02:08:23.024707       1 azure_auth.go:245] Using AzurePublicCloud environment
I0905 02:08:23.024790       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0905 02:08:23.024847       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 802 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0905 02:08:21.940230       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-8c4ac86e0a136f2e10fd01d3a2ae65d071711468 e2e-test
I0905 02:08:21.942277       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:21.962969       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
I0905 02:08:21.962989       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0905 02:08:21.962994       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0905 02:08:21.963018       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0905 02:08:21.964136       1 azure_auth.go:245] Using AzurePublicCloud environment
I0905 02:08:21.964177       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0905 02:08:21.964195       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1636 lines ...