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-04 14:37
Elapsed34m16s
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   170k      0 --:--:-- --:--:-- --:--:--  172k
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-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 not found: manifest unknown: manifest tagged by "e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7" 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-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-09-04T14:43:35Z -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 1862 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 686 lines ...
Sep  4 14:58:10.468: INFO: PersistentVolumeClaim test.csi.azure.comppc5k found but phase is Pending instead of Bound.
Sep  4 14:58:12.502: INFO: PersistentVolumeClaim test.csi.azure.comppc5k found but phase is Pending instead of Bound.
Sep  4 14:58:14.536: INFO: PersistentVolumeClaim test.csi.azure.comppc5k found but phase is Pending instead of Bound.
Sep  4 14:58:16.570: INFO: PersistentVolumeClaim test.csi.azure.comppc5k found and phase=Bound (55.151872913s)
STEP: Creating pod pod-subpath-test-dynamicpv-mqhb
STEP: Creating a pod to test subpath
Sep  4 14:58:16.671: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mqhb" in namespace "provisioning-3501" to be "Succeeded or Failed"
Sep  4 14:58:16.709: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Pending", Reason="", readiness=false. Elapsed: 37.853254ms
Sep  4 14:58:18.742: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071735145s
Sep  4 14:58:20.777: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10640137s
Sep  4 14:58:22.812: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.141453578s
Sep  4 14:58:24.846: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175392229s
Sep  4 14:58:26.881: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209874627s
Sep  4 14:58:28.916: INFO: Pod "pod-subpath-test-dynamicpv-mqhb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.244808866s
STEP: Saw pod success
Sep  4 14:58:28.916: INFO: Pod "pod-subpath-test-dynamicpv-mqhb" satisfied condition "Succeeded or Failed"
Sep  4 14:58:28.948: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000001 pod pod-subpath-test-dynamicpv-mqhb container test-container-subpath-dynamicpv-mqhb: <nil>
STEP: delete the pod
Sep  4 14:58:29.049: INFO: Waiting for pod pod-subpath-test-dynamicpv-mqhb to disappear
Sep  4 14:58:29.081: INFO: Pod pod-subpath-test-dynamicpv-mqhb no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mqhb
Sep  4 14:58:29.081: INFO: Deleting pod "pod-subpath-test-dynamicpv-mqhb" in namespace "provisioning-3501"
... 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":1,"skipped":68,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:58:34.430: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 188 lines ...
Sep  4 14:58:10.494: INFO: PersistentVolumeClaim test.csi.azure.com2rb2x found but phase is Pending instead of Bound.
Sep  4 14:58:12.527: INFO: PersistentVolumeClaim test.csi.azure.com2rb2x found but phase is Pending instead of Bound.
Sep  4 14:58:14.563: INFO: PersistentVolumeClaim test.csi.azure.com2rb2x found but phase is Pending instead of Bound.
Sep  4 14:58:16.597: INFO: PersistentVolumeClaim test.csi.azure.com2rb2x found and phase=Bound (54.950279275s)
STEP: Creating pod exec-volume-test-dynamicpv-nkn8
STEP: Creating a pod to test exec-volume-test
Sep  4 14:58:16.701: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-nkn8" in namespace "volume-4795" to be "Succeeded or Failed"
Sep  4 14:58:16.734: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 32.915589ms
Sep  4 14:58:18.768: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066371471s
Sep  4 14:58:20.802: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100423652s
Sep  4 14:58:22.839: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137969977s
Sep  4 14:58:24.874: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.172365294s
Sep  4 14:58:26.907: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206232295s
Sep  4 14:58:28.941: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.23931112s
Sep  4 14:58:30.974: INFO: Pod "exec-volume-test-dynamicpv-nkn8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.272459862s
STEP: Saw pod success
Sep  4 14:58:30.974: INFO: Pod "exec-volume-test-dynamicpv-nkn8" satisfied condition "Succeeded or Failed"
Sep  4 14:58:31.007: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000000 pod exec-volume-test-dynamicpv-nkn8 container exec-container-dynamicpv-nkn8: <nil>
STEP: delete the pod
Sep  4 14:58:31.081: INFO: Waiting for pod exec-volume-test-dynamicpv-nkn8 to disappear
Sep  4 14:58:31.117: INFO: Pod exec-volume-test-dynamicpv-nkn8 no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-nkn8
Sep  4 14:58:31.117: INFO: Deleting pod "exec-volume-test-dynamicpv-nkn8" in namespace "volume-4795"
... 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":33,"completed":1,"skipped":247,"failed":0}

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:58:47.143: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 3 lines ...

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

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

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 71 lines ...
Sep  4 14:58:10.105: INFO: PersistentVolumeClaim test.csi.azure.com4lsqx found but phase is Pending instead of Bound.
Sep  4 14:58:12.138: INFO: PersistentVolumeClaim test.csi.azure.com4lsqx found but phase is Pending instead of Bound.
Sep  4 14:58:14.173: INFO: PersistentVolumeClaim test.csi.azure.com4lsqx found but phase is Pending instead of Bound.
Sep  4 14:58:16.208: INFO: PersistentVolumeClaim test.csi.azure.com4lsqx found and phase=Bound (54.977797747s)
STEP: Creating pod pod-subpath-test-dynamicpv-zszt
STEP: Creating a pod to test subpath
Sep  4 14:58:16.311: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zszt" in namespace "provisioning-2736" to be "Succeeded or Failed"
Sep  4 14:58:16.345: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 33.567012ms
Sep  4 14:58:18.380: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068500102s
Sep  4 14:58:20.416: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104071802s
Sep  4 14:58:22.451: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.139650001s
Sep  4 14:58:24.486: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.174069279s
Sep  4 14:58:26.521: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209570784s
Sep  4 14:58:28.555: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.243368214s
Sep  4 14:58:30.589: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.277388794s
Sep  4 14:58:32.623: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.311483082s
Sep  4 14:58:34.657: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.345980726s
STEP: Saw pod success
Sep  4 14:58:34.657: INFO: Pod "pod-subpath-test-dynamicpv-zszt" satisfied condition "Succeeded or Failed"
Sep  4 14:58:34.690: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000000 pod pod-subpath-test-dynamicpv-zszt container test-container-subpath-dynamicpv-zszt: <nil>
STEP: delete the pod
Sep  4 14:58:34.767: INFO: Waiting for pod pod-subpath-test-dynamicpv-zszt to disappear
Sep  4 14:58:34.800: INFO: Pod pod-subpath-test-dynamicpv-zszt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zszt
Sep  4 14:58:34.800: INFO: Deleting pod "pod-subpath-test-dynamicpv-zszt" in namespace "provisioning-2736"
STEP: Creating pod pod-subpath-test-dynamicpv-zszt
STEP: Creating a pod to test subpath
Sep  4 14:58:34.868: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-zszt" in namespace "provisioning-2736" to be "Succeeded or Failed"
Sep  4 14:58:34.902: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 33.137188ms
Sep  4 14:58:36.936: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067420046s
Sep  4 14:58:38.971: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102437382s
Sep  4 14:58:41.005: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136048267s
Sep  4 14:58:43.038: INFO: Pod "pod-subpath-test-dynamicpv-zszt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.169509377s
STEP: Saw pod success
Sep  4 14:58:43.038: INFO: Pod "pod-subpath-test-dynamicpv-zszt" satisfied condition "Succeeded or Failed"
Sep  4 14:58:43.072: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000000 pod pod-subpath-test-dynamicpv-zszt container test-container-subpath-dynamicpv-zszt: <nil>
STEP: delete the pod
Sep  4 14:58:43.180: INFO: Waiting for pod pod-subpath-test-dynamicpv-zszt to disappear
Sep  4 14:58:43.212: INFO: Pod pod-subpath-test-dynamicpv-zszt no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-zszt
Sep  4 14:58:43.213: INFO: Deleting pod "pod-subpath-test-dynamicpv-zszt" in namespace "provisioning-2736"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing directories when readOnly specified in the volumeSource
    test/e2e/storage/testsuites/subpath.go:397
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":33,"completed":1,"skipped":37,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:58:48.532: INFO: Driver "test.csi.azure.com" does not support volume type "CSIInlineVolume" - skipping
... skipping 24 lines ...

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

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

    test/e2e/storage/testsuites/topology.go:93
------------------------------
... skipping 168 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":39,"completed":1,"skipped":15,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:58:50.650: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 226 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":27,"completed":1,"skipped":87,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
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  4 14:58:34.849: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:58:34.884: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comphrtx] to have phase Bound
Sep  4 14:58:34.917: INFO: PersistentVolumeClaim test.csi.azure.comphrtx found but phase is Pending instead of Bound.
Sep  4 14:58:36.950: INFO: PersistentVolumeClaim test.csi.azure.comphrtx found and phase=Bound (2.065604522s)
STEP: Creating pod pod-subpath-test-dynamicpv-fz45
STEP: Creating a pod to test subpath
Sep  4 14:58:37.051: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fz45" in namespace "provisioning-333" to be "Succeeded or Failed"
Sep  4 14:58:37.084: INFO: Pod "pod-subpath-test-dynamicpv-fz45": Phase="Pending", Reason="", readiness=false. Elapsed: 32.830951ms
Sep  4 14:58:39.118: INFO: Pod "pod-subpath-test-dynamicpv-fz45": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066934451s
Sep  4 14:58:41.161: INFO: Pod "pod-subpath-test-dynamicpv-fz45": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10957424s
Sep  4 14:58:43.194: INFO: Pod "pod-subpath-test-dynamicpv-fz45": Phase="Pending", Reason="", readiness=false. Elapsed: 6.142486234s
Sep  4 14:58:45.227: INFO: Pod "pod-subpath-test-dynamicpv-fz45": Phase="Pending", Reason="", readiness=false. Elapsed: 8.176030379s
Sep  4 14:58:47.260: INFO: Pod "pod-subpath-test-dynamicpv-fz45": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.209357021s
STEP: Saw pod success
Sep  4 14:58:47.260: INFO: Pod "pod-subpath-test-dynamicpv-fz45" satisfied condition "Succeeded or Failed"
Sep  4 14:58:47.294: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000000 pod pod-subpath-test-dynamicpv-fz45 container test-container-subpath-dynamicpv-fz45: <nil>
STEP: delete the pod
Sep  4 14:58:47.368: INFO: Waiting for pod pod-subpath-test-dynamicpv-fz45 to disappear
Sep  4 14:58:47.401: INFO: Pod pod-subpath-test-dynamicpv-fz45 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fz45
Sep  4 14:58:47.401: INFO: Deleting pod "pod-subpath-test-dynamicpv-fz45" in namespace "provisioning-333"
... 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":36,"completed":2,"skipped":237,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 12 lines ...
Sep  4 14:58:48.974: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:58:49.012: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxsfnx] to have phase Bound
Sep  4 14:58:49.045: INFO: PersistentVolumeClaim test.csi.azure.comxsfnx found but phase is Pending instead of Bound.
Sep  4 14:58:51.079: INFO: PersistentVolumeClaim test.csi.azure.comxsfnx found and phase=Bound (2.066929553s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  4 14:58:51.213: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-kdr9f" in namespace "snapshotting-8863" to be "Succeeded or Failed"
Sep  4 14:58:51.246: INFO: Pod "pvc-snapshottable-tester-kdr9f": Phase="Pending", Reason="", readiness=false. Elapsed: 33.345603ms
Sep  4 14:58:53.281: INFO: Pod "pvc-snapshottable-tester-kdr9f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067839558s
Sep  4 14:58:55.315: INFO: Pod "pvc-snapshottable-tester-kdr9f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.102547481s
STEP: Saw pod success
Sep  4 14:58:55.316: INFO: Pod "pvc-snapshottable-tester-kdr9f" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  4 14:58:55.349: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxsfnx] to have phase Bound
Sep  4 14:58:55.388: INFO: PersistentVolumeClaim test.csi.azure.comxsfnx found and phase=Bound (38.76703ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  4 14:58:55.495: INFO: Pod pvc-snapshottable-tester-kdr9f has the following logs: 
... skipping 192 lines ...
Sep  4 14:58:51.429: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:58:51.465: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comcmtqx] to have phase Bound
Sep  4 14:58:51.498: INFO: PersistentVolumeClaim test.csi.azure.comcmtqx found but phase is Pending instead of Bound.
Sep  4 14:58:53.538: INFO: PersistentVolumeClaim test.csi.azure.comcmtqx found and phase=Bound (2.07306087s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  4 14:58:53.674: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-lbg6s" in namespace "snapshotting-2652" to be "Succeeded or Failed"
Sep  4 14:58:53.708: INFO: Pod "pvc-snapshottable-tester-lbg6s": Phase="Pending", Reason="", readiness=false. Elapsed: 33.351535ms
Sep  4 14:58:55.745: INFO: Pod "pvc-snapshottable-tester-lbg6s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070576523s
Sep  4 14:58:57.781: INFO: Pod "pvc-snapshottable-tester-lbg6s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.106430156s
STEP: Saw pod success
Sep  4 14:58:57.781: INFO: Pod "pvc-snapshottable-tester-lbg6s" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  4 14:58:57.817: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comcmtqx] to have phase Bound
Sep  4 14:58:57.850: INFO: PersistentVolumeClaim test.csi.azure.comcmtqx found and phase=Bound (33.26583ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  4 14:58:57.969: INFO: Pod pvc-snapshottable-tester-lbg6s has the following logs: 
... skipping 55 lines ...
Sep  4 14:58:52.997: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:58:53.032: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comzlrmr] to have phase Bound
Sep  4 14:58:53.068: INFO: PersistentVolumeClaim test.csi.azure.comzlrmr found but phase is Pending instead of Bound.
Sep  4 14:58:55.101: INFO: PersistentVolumeClaim test.csi.azure.comzlrmr found and phase=Bound (2.069104173s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  4 14:58:55.234: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-9cg9k" in namespace "snapshotting-6319" to be "Succeeded or Failed"
Sep  4 14:58:55.266: INFO: Pod "pvc-snapshottable-tester-9cg9k": Phase="Pending", Reason="", readiness=false. Elapsed: 32.425039ms
Sep  4 14:58:57.300: INFO: Pod "pvc-snapshottable-tester-9cg9k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066440029s
Sep  4 14:58:59.334: INFO: Pod "pvc-snapshottable-tester-9cg9k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100690333s
Sep  4 14:59:01.368: INFO: Pod "pvc-snapshottable-tester-9cg9k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.134468561s
STEP: Saw pod success
Sep  4 14:59:01.368: INFO: Pod "pvc-snapshottable-tester-9cg9k" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  4 14:59:01.401: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comzlrmr] to have phase Bound
Sep  4 14:59:01.434: INFO: PersistentVolumeClaim test.csi.azure.comzlrmr found and phase=Bound (32.272707ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  4 14:59:01.533: INFO: Pod pvc-snapshottable-tester-9cg9k has the following logs: 
... skipping 81 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":35,"completed":1,"skipped":284,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:08.427: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 37 lines ...
Sep  4 14:58:52.686: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:58:52.722: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comfwbv7] to have phase Bound
Sep  4 14:58:52.755: INFO: PersistentVolumeClaim test.csi.azure.comfwbv7 found but phase is Pending instead of Bound.
Sep  4 14:58:54.789: INFO: PersistentVolumeClaim test.csi.azure.comfwbv7 found and phase=Bound (2.066439007s)
STEP: Creating pod pod-subpath-test-dynamicpv-79jk
STEP: Creating a pod to test subpath
Sep  4 14:58:54.890: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-79jk" in namespace "provisioning-9282" to be "Succeeded or Failed"
Sep  4 14:58:54.923: INFO: Pod "pod-subpath-test-dynamicpv-79jk": Phase="Pending", Reason="", readiness=false. Elapsed: 32.930617ms
Sep  4 14:58:56.956: INFO: Pod "pod-subpath-test-dynamicpv-79jk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066458536s
Sep  4 14:58:58.990: INFO: Pod "pod-subpath-test-dynamicpv-79jk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100655769s
Sep  4 14:59:01.038: INFO: Pod "pod-subpath-test-dynamicpv-79jk": Phase="Running", Reason="", readiness=false. Elapsed: 6.148563319s
Sep  4 14:59:03.072: INFO: Pod "pod-subpath-test-dynamicpv-79jk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.182678369s
STEP: Saw pod success
Sep  4 14:59:03.072: INFO: Pod "pod-subpath-test-dynamicpv-79jk" satisfied condition "Succeeded or Failed"
Sep  4 14:59:03.106: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000000 pod pod-subpath-test-dynamicpv-79jk container test-container-volume-dynamicpv-79jk: <nil>
STEP: delete the pod
Sep  4 14:59:03.193: INFO: Waiting for pod pod-subpath-test-dynamicpv-79jk to disappear
Sep  4 14:59:03.225: INFO: Pod pod-subpath-test-dynamicpv-79jk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-79jk
Sep  4 14:59:03.225: INFO: Deleting pod "pod-subpath-test-dynamicpv-79jk" in namespace "provisioning-9282"
... 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":27,"completed":2,"skipped":103,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 184 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents","total":38,"completed":2,"skipped":142,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:09.907: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 58 lines ...
Sep  4 14:58:36.725: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:58:36.761: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comh955d] to have phase Bound
Sep  4 14:58:36.793: INFO: PersistentVolumeClaim test.csi.azure.comh955d found but phase is Pending instead of Bound.
Sep  4 14:58:38.828: INFO: PersistentVolumeClaim test.csi.azure.comh955d found and phase=Bound (2.066633432s)
STEP: Creating pod pod-subpath-test-dynamicpv-xkf7
STEP: Creating a pod to test atomic-volume-subpath
Sep  4 14:58:38.928: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xkf7" in namespace "provisioning-4252" to be "Succeeded or Failed"
Sep  4 14:58:38.961: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.654686ms
Sep  4 14:58:40.995: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066845738s
Sep  4 14:58:43.029: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100705007s
Sep  4 14:58:45.063: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=true. Elapsed: 6.134464256s
Sep  4 14:58:47.096: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=true. Elapsed: 8.168166211s
Sep  4 14:58:49.130: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=true. Elapsed: 10.201459811s
... skipping 3 lines ...
Sep  4 14:58:57.281: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=true. Elapsed: 18.353010621s
Sep  4 14:58:59.316: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=true. Elapsed: 20.387717525s
Sep  4 14:59:01.349: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=true. Elapsed: 22.42092749s
Sep  4 14:59:03.382: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Running", Reason="", readiness=false. Elapsed: 24.453989887s
Sep  4 14:59:05.416: INFO: Pod "pod-subpath-test-dynamicpv-xkf7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.487529791s
STEP: Saw pod success
Sep  4 14:59:05.416: INFO: Pod "pod-subpath-test-dynamicpv-xkf7" satisfied condition "Succeeded or Failed"
Sep  4 14:59:05.448: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000001 pod pod-subpath-test-dynamicpv-xkf7 container test-container-subpath-dynamicpv-xkf7: <nil>
STEP: delete the pod
Sep  4 14:59:05.521: INFO: Waiting for pod pod-subpath-test-dynamicpv-xkf7 to disappear
Sep  4 14:59:05.554: INFO: Pod pod-subpath-test-dynamicpv-xkf7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xkf7
Sep  4 14:59:05.554: INFO: Deleting pod "pod-subpath-test-dynamicpv-xkf7" in namespace "provisioning-4252"
... 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":33,"completed":2,"skipped":308,"failed":0}

SSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:10.863: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 223 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
S
------------------------------
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  4 14:59:08.863: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 14:59:09.091: INFO: Creating resource for dynamic PV
Sep  4 14:59:09.091: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-141-e2e-sc9th4z
STEP: creating a claim
Sep  4 14:59:09.125: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:59:09.162: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comsjm2l] to have phase Bound
Sep  4 14:59:09.195: INFO: PersistentVolumeClaim test.csi.azure.comsjm2l found but phase is Pending instead of Bound.
Sep  4 14:59:11.228: INFO: PersistentVolumeClaim test.csi.azure.comsjm2l found and phase=Bound (2.065807871s)
STEP: Creating pod pod-subpath-test-dynamicpv-7qdf
STEP: Checking for subpath error in container status
Sep  4 14:59:15.396: INFO: Deleting pod "pod-subpath-test-dynamicpv-7qdf" in namespace "provisioning-141"
Sep  4 14:59:15.431: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-7qdf" to be fully deleted
STEP: Deleting pod
Sep  4 14:59:17.498: INFO: Deleting pod "pod-subpath-test-dynamicpv-7qdf" in namespace "provisioning-141"
STEP: Deleting pvc
Sep  4 14:59:17.532: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comsjm2l"
... skipping 9 lines ...

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

SSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:22.776: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 3 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 26 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  4 14:59:22.844: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 14:59:23.075: 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  4 14:59:23.075: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-2152" for this suite.


S [SKIPPING] [0.299 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 97 lines ...

    test/e2e/storage/external/external.go:262
------------------------------
SSSSSS
------------------------------
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  4 14:59:09.994: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 14:59:10.225: INFO: Creating resource for dynamic PV
Sep  4 14:59:10.225: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5065-e2e-scvtdq6
STEP: creating a claim
Sep  4 14:59:10.259: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:59:10.294: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comrjsnb] to have phase Bound
Sep  4 14:59:10.327: INFO: PersistentVolumeClaim test.csi.azure.comrjsnb found but phase is Pending instead of Bound.
Sep  4 14:59:12.360: INFO: PersistentVolumeClaim test.csi.azure.comrjsnb found and phase=Bound (2.065286789s)
STEP: Creating pod pod-subpath-test-dynamicpv-42r7
STEP: Checking for subpath error in container status
Sep  4 14:59:18.528: INFO: Deleting pod "pod-subpath-test-dynamicpv-42r7" in namespace "provisioning-5065"
Sep  4 14:59:18.564: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-42r7" to be fully deleted
STEP: Deleting pod
Sep  4 14:59:20.630: INFO: Deleting pod "pod-subpath-test-dynamicpv-42r7" in namespace "provisioning-5065"
STEP: Deleting pvc
Sep  4 14:59:20.663: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comrjsnb"
... skipping 9 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:25.952: 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)] 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":134,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes 
  should store data
  test/e2e/storage/testsuites/volumes.go:161
... skipping 90 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":36,"completed":3,"skipped":328,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 77 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if 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 113 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 18 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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  4 14:59:26.328: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 14:59:26.557: INFO: Creating resource for dynamic PV
Sep  4 14:59:26.557: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5716-e2e-sc659sm
STEP: creating a claim
Sep  4 14:59:26.590: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:59:26.626: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comsqvql] to have phase Bound
Sep  4 14:59:26.658: INFO: PersistentVolumeClaim test.csi.azure.comsqvql found but phase is Pending instead of Bound.
Sep  4 14:59:28.693: INFO: PersistentVolumeClaim test.csi.azure.comsqvql found and phase=Bound (2.06681057s)
STEP: Creating pod pod-subpath-test-dynamicpv-rrqg
STEP: Checking for subpath error in container status
Sep  4 14:59:32.861: INFO: Deleting pod "pod-subpath-test-dynamicpv-rrqg" in namespace "provisioning-5716"
Sep  4 14:59:32.895: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-rrqg" to be fully deleted
STEP: Deleting pod
Sep  4 14:59:34.961: INFO: Deleting pod "pod-subpath-test-dynamicpv-rrqg" in namespace "provisioning-5716"
STEP: Deleting pvc
Sep  4 14:59:34.993: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comsqvql"
... skipping 9 lines ...

• [SLOW TEST:13.911 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":38,"completed":4,"skipped":328,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  4 14:59:40.315: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 14:59:40.549: 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  4 14:59:40.550: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5037" for this suite.


S [SKIPPING] [0.303 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 148 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":33,"completed":2,"skipped":481,"failed":0}

SSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits
... skipping 90 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":39,"completed":2,"skipped":189,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:42.711: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 90 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  4 14:59:41.629: INFO: Creating resource for dynamic PV
Sep  4 14:59:41.629: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-180-e2e-scbh67b
STEP: [init] starting a pod to use the claim
Sep  4 14:59:41.705: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-hbv7f" in namespace "snapshotting-180" to be "Succeeded or Failed"
Sep  4 14:59:41.739: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Pending", Reason="", readiness=false. Elapsed: 33.218283ms
Sep  4 14:59:43.774: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068462521s
Sep  4 14:59:45.809: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103733831s
Sep  4 14:59:47.845: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.139121047s
Sep  4 14:59:49.879: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173713453s
Sep  4 14:59:51.914: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208346438s
Sep  4 14:59:53.949: INFO: Pod "pvc-snapshottable-tester-hbv7f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.243839318s
STEP: Saw pod success
Sep  4 14:59:53.949: INFO: Pod "pvc-snapshottable-tester-hbv7f" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  4 14:59:53.991: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  4 14:59:53.992: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-hbv7f-my-volume] to have phase Bound
Sep  4 14:59:54.025: INFO: PersistentVolumeClaim pvc-snapshottable-tester-hbv7f-my-volume found and phase=Bound (33.108118ms)
STEP: [init] checking the PV
... skipping 39 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  4 14:59:43.038: INFO: Creating resource for dynamic PV
Sep  4 14:59:43.038: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6570-e2e-sc9stst
STEP: [init] starting a pod to use the claim
Sep  4 14:59:43.110: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-8nxm4" in namespace "snapshotting-6570" to be "Succeeded or Failed"
Sep  4 14:59:43.143: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Pending", Reason="", readiness=false. Elapsed: 33.200486ms
Sep  4 14:59:45.177: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066934044s
Sep  4 14:59:47.211: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100975877s
Sep  4 14:59:49.245: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135413843s
Sep  4 14:59:51.279: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169361367s
Sep  4 14:59:53.314: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204610415s
Sep  4 14:59:55.349: INFO: Pod "pvc-snapshottable-tester-8nxm4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.239469848s
STEP: Saw pod success
Sep  4 14:59:55.349: INFO: Pod "pvc-snapshottable-tester-8nxm4" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  4 14:59:55.382: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  4 14:59:55.383: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-8nxm4-my-volume] to have phase Bound
Sep  4 14:59:55.417: INFO: PersistentVolumeClaim pvc-snapshottable-tester-8nxm4-my-volume found and phase=Bound (33.599923ms)
STEP: [init] checking the PV
... skipping 69 lines ...
STEP: creating a claim
Sep  4 14:59:36.348: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 14:59:36.383: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comrjtf8] to have phase Bound
Sep  4 14:59:36.415: INFO: PersistentVolumeClaim test.csi.azure.comrjtf8 found but phase is Pending instead of Bound.
Sep  4 14:59:38.449: INFO: PersistentVolumeClaim test.csi.azure.comrjtf8 found and phase=Bound (2.065510628s)
STEP: Creating pod to format volume volume-prep-provisioning-8539
Sep  4 14:59:38.548: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-8539" in namespace "provisioning-8539" to be "Succeeded or Failed"
Sep  4 14:59:38.580: INFO: Pod "volume-prep-provisioning-8539": Phase="Pending", Reason="", readiness=false. Elapsed: 32.59799ms
Sep  4 14:59:40.615: INFO: Pod "volume-prep-provisioning-8539": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067445633s
Sep  4 14:59:42.650: INFO: Pod "volume-prep-provisioning-8539": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.102508962s
STEP: Saw pod success
Sep  4 14:59:42.650: INFO: Pod "volume-prep-provisioning-8539" satisfied condition "Succeeded or Failed"
Sep  4 14:59:42.650: INFO: Deleting pod "volume-prep-provisioning-8539" in namespace "provisioning-8539"
Sep  4 14:59:42.689: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-8539" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-ds42
STEP: Checking for subpath error in container status
Sep  4 14:59:48.827: INFO: Deleting pod "pod-subpath-test-dynamicpv-ds42" in namespace "provisioning-8539"
Sep  4 14:59:48.874: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-ds42" to be fully deleted
STEP: Deleting pod
Sep  4 14:59:50.945: INFO: Deleting pod "pod-subpath-test-dynamicpv-ds42" in namespace "provisioning-8539"
STEP: Deleting pvc
Sep  4 14:59:50.978: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comrjtf8"
... skipping 12 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should verify container cannot write to subpath readonly volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:425
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]","total":36,"completed":4,"skipped":741,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  4 14:59:56.279: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 106 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should resize volume when PVC is edited while pod is using it
    test/e2e/storage/testsuites/volume_expand.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":38,"completed":5,"skipped":571,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:02.936: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 86 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":33,"completed":3,"skipped":790,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
... skipping 44 lines ...
Sep  4 15:00:03.261: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 15:00:03.298: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.compd4q6] to have phase Bound
Sep  4 15:00:03.332: INFO: PersistentVolumeClaim test.csi.azure.compd4q6 found but phase is Pending instead of Bound.
Sep  4 15:00:05.365: INFO: PersistentVolumeClaim test.csi.azure.compd4q6 found and phase=Bound (2.066612201s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  4 15:00:05.499: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-cftqg" in namespace "snapshotting-1740" to be "Succeeded or Failed"
Sep  4 15:00:05.532: INFO: Pod "pvc-snapshottable-tester-cftqg": Phase="Pending", Reason="", readiness=false. Elapsed: 33.049259ms
Sep  4 15:00:07.565: INFO: Pod "pvc-snapshottable-tester-cftqg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066434355s
Sep  4 15:00:09.600: INFO: Pod "pvc-snapshottable-tester-cftqg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101562076s
Sep  4 15:00:11.635: INFO: Pod "pvc-snapshottable-tester-cftqg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.136284115s
STEP: Saw pod success
Sep  4 15:00:11.635: INFO: Pod "pvc-snapshottable-tester-cftqg" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  4 15:00:11.668: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.compd4q6] to have phase Bound
Sep  4 15:00:11.700: INFO: PersistentVolumeClaim test.csi.azure.compd4q6 found and phase=Bound (32.504979ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  4 15:00:11.800: INFO: Pod pvc-snapshottable-tester-cftqg has the following logs: 
... skipping 67 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:26.722: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 lines ...

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

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

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

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:26.836: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 370 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single volume from pods on different node
    test/e2e/storage/testsuites/multivolume.go:451
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node","total":39,"completed":3,"skipped":447,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:28.716: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 118 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSS
------------------------------
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  4 15:00:17.396: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 15:00:17.631: INFO: Creating resource for dynamic PV
Sep  4 15:00:17.631: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6437-e2e-sckqmvr
STEP: creating a claim
Sep  4 15:00:17.666: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 15:00:17.707: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com4z6hg] to have phase Bound
Sep  4 15:00:17.739: INFO: PersistentVolumeClaim test.csi.azure.com4z6hg found but phase is Pending instead of Bound.
Sep  4 15:00:19.773: INFO: PersistentVolumeClaim test.csi.azure.com4z6hg found and phase=Bound (2.066358656s)
STEP: Creating pod pod-subpath-test-dynamicpv-bvrg
STEP: Checking for subpath error in container status
Sep  4 15:00:23.940: INFO: Deleting pod "pod-subpath-test-dynamicpv-bvrg" in namespace "provisioning-6437"
Sep  4 15:00:23.976: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-bvrg" to be fully deleted
STEP: Deleting pod
Sep  4 15:00:26.044: INFO: Deleting pod "pod-subpath-test-dynamicpv-bvrg" in namespace "provisioning-6437"
STEP: Deleting pvc
Sep  4 15:00:26.077: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com4z6hg"
... skipping 9 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:31.390: INFO: Driver test.csi.azure.com doesn't support xfs -- 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 8 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath 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 48 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should be able to unmount after the subpath directory is deleted [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:447
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":36,"completed":6,"skipped":1027,"failed":0}
Sep  4 15:00:43.945: INFO: Running AfterSuite actions on all nodes
Sep  4 15:00:43.945: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Sep  4 15:00:43.945: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
Sep  4 15:00:43.945: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func8.2
Sep  4 15:00:43.945: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func17.3
Sep  4 15:00:43.945: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func9.2
... skipping 45 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read-only inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:175
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read-only inline ephemeral volume","total":33,"completed":4,"skipped":841,"failed":0}

SSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:51.820: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 87 lines ...

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

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

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

SSSS
------------------------------
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  4 15:00:51.991: INFO: >>> kubeConfig: /root/tmp828759347/kubeconfig/kubeconfig.canadacentral.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  4 15:00:52.402: INFO: Deleting PersistentVolumeClaim "pvc-kwlgm"
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  4 15:00:52.472: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8895" for this suite.

•S
------------------------------
{"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":33,"completed":5,"skipped":999,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:00:52.560: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 294 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":39,"completed":4,"skipped":504,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:01:10.292: INFO: Driver "test.csi.azure.com" does not support volume type "CSIInlineVolume" - skipping
... skipping 66 lines ...

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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 185 lines ...
  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
------------------------------
SS
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node","total":38,"completed":7,"skipped":904,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:01:10.648: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 185 lines ...

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

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

    test/e2e/storage/framework/testsuite.go:121
------------------------------
... skipping 135 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":27,"completed":4,"skipped":168,"failed":0}

SSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:01:18.474: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 37 lines ...
Sep  4 15:01:10.950: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 15:01:10.985: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comwttdq] to have phase Bound
Sep  4 15:01:11.018: INFO: PersistentVolumeClaim test.csi.azure.comwttdq found but phase is Pending instead of Bound.
Sep  4 15:01:13.052: INFO: PersistentVolumeClaim test.csi.azure.comwttdq found and phase=Bound (2.066769835s)
STEP: Creating pod pod-subpath-test-dynamicpv-v857
STEP: Creating a pod to test subpath
Sep  4 15:01:13.153: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-v857" in namespace "provisioning-6450" to be "Succeeded or Failed"
Sep  4 15:01:13.186: INFO: Pod "pod-subpath-test-dynamicpv-v857": Phase="Pending", Reason="", readiness=false. Elapsed: 32.9145ms
Sep  4 15:01:15.220: INFO: Pod "pod-subpath-test-dynamicpv-v857": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067077094s
Sep  4 15:01:17.255: INFO: Pod "pod-subpath-test-dynamicpv-v857": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101431035s
Sep  4 15:01:19.289: INFO: Pod "pod-subpath-test-dynamicpv-v857": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.135839222s
STEP: Saw pod success
Sep  4 15:01:19.289: INFO: Pod "pod-subpath-test-dynamicpv-v857" satisfied condition "Succeeded or Failed"
Sep  4 15:01:19.322: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000001 pod pod-subpath-test-dynamicpv-v857 container test-container-volume-dynamicpv-v857: <nil>
STEP: delete the pod
Sep  4 15:01:19.397: INFO: Waiting for pod pod-subpath-test-dynamicpv-v857 to disappear
Sep  4 15:01:19.430: INFO: Pod pod-subpath-test-dynamicpv-v857 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-v857
Sep  4 15:01:19.430: INFO: Deleting pod "pod-subpath-test-dynamicpv-v857" in namespace "provisioning-6450"
... 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":38,"completed":8,"skipped":951,"failed":0}

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

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:01:32.117: INFO: Driver test.csi.azure.com doesn't support xfs -- 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 8 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath 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 210 lines ...
Sep  4 15:01:18.865: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 15:01:18.901: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5p2st] to have phase Bound
Sep  4 15:01:18.933: INFO: PersistentVolumeClaim test.csi.azure.com5p2st found but phase is Pending instead of Bound.
Sep  4 15:01:20.968: INFO: PersistentVolumeClaim test.csi.azure.com5p2st found and phase=Bound (2.066904442s)
STEP: Creating pod pod-subpath-test-dynamicpv-qdz2
STEP: Creating a pod to test subpath
Sep  4 15:01:21.068: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qdz2" in namespace "provisioning-6406" to be "Succeeded or Failed"
Sep  4 15:01:21.101: INFO: Pod "pod-subpath-test-dynamicpv-qdz2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.885402ms
Sep  4 15:01:23.136: INFO: Pod "pod-subpath-test-dynamicpv-qdz2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067913322s
Sep  4 15:01:25.169: INFO: Pod "pod-subpath-test-dynamicpv-qdz2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100966842s
Sep  4 15:01:27.204: INFO: Pod "pod-subpath-test-dynamicpv-qdz2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.13611444s
STEP: Saw pod success
Sep  4 15:01:27.204: INFO: Pod "pod-subpath-test-dynamicpv-qdz2" satisfied condition "Succeeded or Failed"
Sep  4 15:01:27.237: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000001 pod pod-subpath-test-dynamicpv-qdz2 container test-container-subpath-dynamicpv-qdz2: <nil>
STEP: delete the pod
Sep  4 15:01:27.316: INFO: Waiting for pod pod-subpath-test-dynamicpv-qdz2 to disappear
Sep  4 15:01:27.349: INFO: Pod pod-subpath-test-dynamicpv-qdz2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-qdz2
Sep  4 15:01:27.349: INFO: Deleting pod "pod-subpath-test-dynamicpv-qdz2" in namespace "provisioning-6406"
... 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":273,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[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 262 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 130 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition","total":33,"completed":4,"skipped":806,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:01:53.380: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 210 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":27,"completed":6,"skipped":982,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:01:58.794: INFO: Driver "test.csi.azure.com" does not support topology - skipping
... skipping 3 lines ...

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

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

    test/e2e/storage/testsuites/topology.go:93
------------------------------
... skipping 129 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":33,"completed":5,"skipped":971,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:02:08.791: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 58 lines ...
Sep  4 15:01:33.095: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 15:01:33.130: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.commzw9m] to have phase Bound
Sep  4 15:01:33.169: INFO: PersistentVolumeClaim test.csi.azure.commzw9m found but phase is Pending instead of Bound.
Sep  4 15:01:35.203: INFO: PersistentVolumeClaim test.csi.azure.commzw9m found and phase=Bound (2.072227348s)
STEP: Expanding non-expandable pvc
Sep  4 15:01:35.268: INFO: currentPvcSize {{5368709120 0} {<nil>} 5Gi BinarySI}, newSize {{6442450944 0} {<nil>}  BinarySI}
Sep  4 15:01:35.334: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:37.402: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:39.403: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:41.403: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:43.402: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:45.405: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:47.403: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:49.403: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:51.403: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:53.401: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:55.404: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:57.403: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:01:59.402: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:02:01.404: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:02:03.406: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:02:05.402: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  4 15:02:05.468: INFO: Error updating pvc test.csi.azure.commzw9m: persistentvolumeclaims "test.csi.azure.commzw9m" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Sep  4 15:02:05.468: INFO: Deleting PersistentVolumeClaim "test.csi.azure.commzw9m"
Sep  4 15:02:05.503: INFO: Waiting up to 5m0s for PersistentVolume pvc-08839c5d-0ff3-45ef-96ae-40177bb1a2a2 to get deleted
Sep  4 15:02:05.535: INFO: PersistentVolume pvc-08839c5d-0ff3-45ef-96ae-40177bb1a2a2 found and phase=Released (32.497979ms)
Sep  4 15:02:10.572: INFO: PersistentVolume pvc-08839c5d-0ff3-45ef-96ae-40177bb1a2a2 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":35,"completed":5,"skipped":994,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
Sep  4 15:02:10.762: INFO: Running AfterSuite actions on all nodes
Sep  4 15:02:10.762: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Sep  4 15:02:10.762: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
... skipping 59 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":38,"completed":9,"skipped":958,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  4 15:02:40.853: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 35 lines ...
Sep  4 15:02:41.115: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  4 15:02:41.149: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxpjkj] to have phase Bound
Sep  4 15:02:41.182: INFO: PersistentVolumeClaim test.csi.azure.comxpjkj found but phase is Pending instead of Bound.
Sep  4 15:02:43.215: INFO: PersistentVolumeClaim test.csi.azure.comxpjkj found and phase=Bound (2.065570692s)
STEP: Creating pod pod-subpath-test-dynamicpv-9g4v
STEP: Creating a pod to test multi_subpath
Sep  4 15:02:43.315: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-9g4v" in namespace "provisioning-7522" to be "Succeeded or Failed"
Sep  4 15:02:43.348: INFO: Pod "pod-subpath-test-dynamicpv-9g4v": Phase="Pending", Reason="", readiness=false. Elapsed: 32.933628ms
Sep  4 15:02:45.382: INFO: Pod "pod-subpath-test-dynamicpv-9g4v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06674819s
Sep  4 15:02:47.416: INFO: Pod "pod-subpath-test-dynamicpv-9g4v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100668962s
Sep  4 15:02:49.451: INFO: Pod "pod-subpath-test-dynamicpv-9g4v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.135473697s
STEP: Saw pod success
Sep  4 15:02:49.451: INFO: Pod "pod-subpath-test-dynamicpv-9g4v" satisfied condition "Succeeded or Failed"
Sep  4 15:02:49.484: INFO: Trying to get logs from node k8s-agentpool1-39847525-vmss000000 pod pod-subpath-test-dynamicpv-9g4v container test-container-subpath-dynamicpv-9g4v: <nil>
STEP: delete the pod
Sep  4 15:02:49.558: INFO: Waiting for pod pod-subpath-test-dynamicpv-9g4v to disappear
Sep  4 15:02:49.590: INFO: Pod pod-subpath-test-dynamicpv-9g4v no longer exists
STEP: Deleting pod
Sep  4 15:02:49.590: INFO: Deleting pod "pod-subpath-test-dynamicpv-9g4v" in namespace "provisioning-7522"
... skipping 14 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support creating multiple subpath from same volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:296
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]","total":38,"completed":10,"skipped":977,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
Sep  4 15:02:54.924: INFO: Running AfterSuite actions on all nodes
Sep  4 15:02:54.924: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Sep  4 15:02:54.924: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
... skipping 13 lines ...
Sep  4 15:02:08.853: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep  4 15:02:08.853: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3
Sep  4 15:02:54.971: INFO: Running AfterSuite actions on node 1


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

Ginkgo ran 1 suite in 5m38.692078357s
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:
I0904 14:57:13.279062       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 e2e-test
I0904 14:57:13.279370       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:13.300282       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
I0904 14:57:13.300301       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:13.300307       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0904 14:57:13.300327       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0904 14:57:13.300971       1 azure_auth.go:245] Using AzurePublicCloud environment
I0904 14:57:13.301029       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0904 14:57:13.301052       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 122 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0904 14:57:13.841043       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 e2e-test
I0904 14:57:13.841375       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:13.858787       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
I0904 14:57:13.858803       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:13.858809       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0904 14:57:13.858848       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0904 14:57:13.859591       1 azure_auth.go:245] Using AzurePublicCloud environment
I0904 14:57:13.859636       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0904 14:57:13.859660       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 706 lines ...
I0904 15:00:51.048771       1 azure_storage.go:66] share pvcn-d1d83ea8-6034-45e0-af91-a7fd03c40a13 deleted
I0904 15:00:51.048805       1 controllerserver.go:603] azure file(pvcn-d1d83ea8-6034-45e0-af91-a7fd03c40a13) under rg(kubetest-w5lhizz4) account(f8cdac3fd9a16407eaa4f87) volume(kubetest-w5lhizz4#f8cdac3fd9a16407eaa4f87#pvcn-d1d83ea8-6034-45e0-af91-a7fd03c40a13###ephemeral-5967) is deleted successfully
I0904 15:00:51.048839       1 azure_metrics.go:115] "Observed Request Latency" latency_seconds=0.579578801 request="azurefile_csi_driver_controller_delete_volume" resource_group="kubetest-w5lhizz4" subscription_id="0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e" source="test.csi.azure.com" volumeid="kubetest-w5lhizz4#f8cdac3fd9a16407eaa4f87#pvcn-d1d83ea8-6034-45e0-af91-a7fd03c40a13###ephemeral-5967" result_code="succeeded"
I0904 15:00:51.048865       1 utils.go:83] GRPC response: {}
I0904 15:00:52.291747       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0904 15:00:52.291775       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-b64003c0-7ac5-42c8-8832-315bb8e5aaad","parameters":{"csi.storage.k8s.io/pv/name":"pvc-b64003c0-7ac5-42c8-8832-315bb8e5aaad","csi.storage.k8s.io/pvc/name":"pvc-kwlgm","csi.storage.k8s.io/pvc/namespace":"volumemode-8895","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0904 15:00:52.292112       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0904 15:00:52.421702       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0904 15:00:52.421727       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-b64003c0-7ac5-42c8-8832-315bb8e5aaad","parameters":{"csi.storage.k8s.io/pv/name":"pvc-b64003c0-7ac5-42c8-8832-315bb8e5aaad","csi.storage.k8s.io/pvc/name":"pvc-kwlgm","csi.storage.k8s.io/pvc/namespace":"volumemode-8895","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0904 15:00:52.421922       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0904 15:00:54.252297       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0904 15:00:54.252317       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-2a11bca0-0423-4897-9a97-a5b764b5cc2d","parameters":{"csi.storage.k8s.io/pv/name":"pvc-2a11bca0-0423-4897-9a97-a5b764b5cc2d","csi.storage.k8s.io/pvc/name":"inline-volume-tester-zw2qj-my-volume-0","csi.storage.k8s.io/pvc/namespace":"ephemeral-9906","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Mount":{}},"access_mode":{"mode":7}}]}
I0904 15:00:54.252832       1 controllerserver.go:297] set vnetResourceID(/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-w5lhizz4/providers/Microsoft.Network/virtualNetworks/k8s-vnet-39847525/subnets/k8s-subnet) for NFS protocol
I0904 15:00:54.252841       1 azure.go:180] updateSubnetServiceEndpoints on vnetName: k8s-vnet-39847525, subnetName: k8s-subnet, location: canadacentral
I0904 15:00:54.299482       1 azure.go:209] serviceEndpoint(Microsoft.Storage) is already in subnet(k8s-subnet)
I0904 15:00:54.391673       1 controllerserver.go:452] begin to create file share(pvcn-2a11bca0-0423-4897-9a97-a5b764b5cc2d) on account(f8cdac3fd9a16407eaa4f87) type(Premium_LRS) rg(kubetest-w5lhizz4) location() size(100) protocol(NFS)
... skipping 215 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0904 14:57:05.078943       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 e2e-test
I0904 14:57:05.079269       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:05.103858       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
I0904 14:57:05.103878       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:05.103899       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0904 14:57:05.103915       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0904 14:57:05.104903       1 azure_auth.go:245] Using AzurePublicCloud environment
I0904 14:57:05.105094       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0904 14:57:05.105651       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:
I0904 14:57:10.918013       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 e2e-test
I0904 14:57:10.919209       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:10.939238       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
I0904 14:57:10.939256       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:10.939262       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0904 14:57:10.939279       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0904 14:57:10.940460       1 azure_auth.go:245] Using AzurePublicCloud environment
I0904 14:57:10.940502       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0904 14:57:10.940521       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1447 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0904 14:57:11.477134       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-adb6b2ef9d8177a08b1ddff13cca0b2692389eb7 e2e-test
I0904 14:57:11.478458       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:11.503151       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
I0904 14:57:11.503169       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0904 14:57:11.503174       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0904 14:57:11.503191       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0904 14:57:11.504297       1 azure_auth.go:245] Using AzurePublicCloud environment
I0904 14:57:11.504344       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0904 14:57:11.504451       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1191 lines ...