This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: chart index file
Resultsuccess
Tests 0 failed / 14 succeeded
Started2022-09-07 05:59
Elapsed37m30s
Revision
Refs 1081
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   175k      0 --:--:-- --:--:-- --:--:--  175k
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-aea62949fedc3da035043dbcbf84c45d56bff77a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-aea62949fedc3da035043dbcbf84c45d56bff77a not found: manifest unknown: manifest tagged by "e2e-aea62949fedc3da035043dbcbf84c45d56bff77a" 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-aea62949fedc3da035043dbcbf84c45d56bff77a -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=aea62949fedc3da035043dbcbf84c45d56bff77a -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-09-07T06:07:53Z -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 1847 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 332 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 18 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 510 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 50 lines ...
STEP: Building a namespace api object, basename volumemode
W0907 06:20:42.099369   36227 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep  7 06:20:42.100: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled
Sep  7 06:20:42.219: INFO: No PSP annotation exists on dry run pod; assuming PodSecurityPolicy is disabled
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  test/e2e/storage/testsuites/volumemode.go:299
Sep  7 06:20:42.687: 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  7 06:20:42.687: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-262" for this suite.


S [SKIPPING] [1.419 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 165 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  7 06:20:43.948: INFO: Creating resource for dynamic PV
Sep  7 06:20:43.948: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-7357-e2e-scvq44z
STEP: [init] starting a pod to use the claim
Sep  7 06:20:44.190: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-gjn88" in namespace "snapshotting-7357" to be "Succeeded or Failed"
Sep  7 06:20:44.308: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 117.720297ms
Sep  7 06:20:46.427: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237507082s
Sep  7 06:20:48.546: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 4.35600718s
Sep  7 06:20:50.666: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 6.475798619s
Sep  7 06:20:52.786: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 8.596392545s
Sep  7 06:20:54.906: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 10.715751715s
... skipping 23 lines ...
Sep  7 06:21:45.767: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.576655113s
Sep  7 06:21:47.885: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.695526538s
Sep  7 06:21:50.004: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.813902082s
Sep  7 06:21:52.124: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.934304187s
Sep  7 06:21:54.245: INFO: Pod "pvc-snapshottable-tester-gjn88": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m10.054664284s
STEP: Saw pod success
Sep  7 06:21:54.245: INFO: Pod "pvc-snapshottable-tester-gjn88" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  7 06:21:54.362: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  7 06:21:54.363: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-gjn88-my-volume] to have phase Bound
Sep  7 06:21:54.482: INFO: PersistentVolumeClaim pvc-snapshottable-tester-gjn88-my-volume found and phase=Bound (118.303861ms)
STEP: [init] checking the PV
... skipping 25 lines ...

        test/e2e/storage/external/external.go:357
------------------------------
SSSSSSSSSSSSS
------------------------------
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  7 06:20:43.248: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.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  7 06:20:44.066: INFO: Creating resource for dynamic PV
Sep  7 06:20:44.066: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-9858-e2e-sctxrnl
STEP: creating a claim
Sep  7 06:20:44.185: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
... skipping 25 lines ...
Sep  7 06:21:35.275: INFO: PersistentVolumeClaim test.csi.azure.comx2jrk found but phase is Pending instead of Bound.
Sep  7 06:21:37.394: INFO: PersistentVolumeClaim test.csi.azure.comx2jrk found but phase is Pending instead of Bound.
Sep  7 06:21:39.512: INFO: PersistentVolumeClaim test.csi.azure.comx2jrk found but phase is Pending instead of Bound.
Sep  7 06:21:41.632: INFO: PersistentVolumeClaim test.csi.azure.comx2jrk found but phase is Pending instead of Bound.
Sep  7 06:21:43.755: INFO: PersistentVolumeClaim test.csi.azure.comx2jrk found and phase=Bound (59.44341972s)
STEP: Creating pod pod-subpath-test-dynamicpv-dl9b
STEP: Checking for subpath error in container status
Sep  7 06:21:52.349: INFO: Deleting pod "pod-subpath-test-dynamicpv-dl9b" in namespace "provisioning-9858"
Sep  7 06:21:52.469: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dl9b" to be fully deleted
STEP: Deleting pod
Sep  7 06:21:54.705: INFO: Deleting pod "pod-subpath-test-dynamicpv-dl9b" in namespace "provisioning-9858"
STEP: Deleting pvc
Sep  7 06:21:54.822: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comx2jrk"
... skipping 9 lines ...

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

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:00.669: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 172 lines ...
Sep  7 06:21:35.963: INFO: PersistentVolumeClaim test.csi.azure.comcgj65 found but phase is Pending instead of Bound.
Sep  7 06:21:38.081: INFO: PersistentVolumeClaim test.csi.azure.comcgj65 found but phase is Pending instead of Bound.
Sep  7 06:21:40.199: INFO: PersistentVolumeClaim test.csi.azure.comcgj65 found but phase is Pending instead of Bound.
Sep  7 06:21:42.316: INFO: PersistentVolumeClaim test.csi.azure.comcgj65 found and phase=Bound (59.435027917s)
STEP: Creating pod pod-subpath-test-dynamicpv-mb76
STEP: Creating a pod to test subpath
Sep  7 06:21:42.669: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mb76" in namespace "provisioning-6631" to be "Succeeded or Failed"
Sep  7 06:21:42.787: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Pending", Reason="", readiness=false. Elapsed: 117.165854ms
Sep  7 06:21:44.905: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Pending", Reason="", readiness=false. Elapsed: 2.235548616s
Sep  7 06:21:47.024: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Pending", Reason="", readiness=false. Elapsed: 4.354322042s
Sep  7 06:21:49.141: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Pending", Reason="", readiness=false. Elapsed: 6.472041761s
Sep  7 06:21:51.260: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Pending", Reason="", readiness=false. Elapsed: 8.590787212s
Sep  7 06:21:53.379: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Pending", Reason="", readiness=false. Elapsed: 10.709918831s
Sep  7 06:21:55.502: INFO: Pod "pod-subpath-test-dynamicpv-mb76": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.832724975s
STEP: Saw pod success
Sep  7 06:21:55.502: INFO: Pod "pod-subpath-test-dynamicpv-mb76" satisfied condition "Succeeded or Failed"
Sep  7 06:21:55.619: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000001 pod pod-subpath-test-dynamicpv-mb76 container test-container-subpath-dynamicpv-mb76: <nil>
STEP: delete the pod
Sep  7 06:21:55.890: INFO: Waiting for pod pod-subpath-test-dynamicpv-mb76 to disappear
Sep  7 06:21:56.007: INFO: Pod pod-subpath-test-dynamicpv-mb76 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mb76
Sep  7 06:21:56.008: INFO: Deleting pod "pod-subpath-test-dynamicpv-mb76" in namespace "provisioning-6631"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly file specified in the volumeMount [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:382
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]","total":34,"completed":1,"skipped":39,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:02.137: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 64 lines ...
Sep  7 06:21:37.518: INFO: PersistentVolumeClaim test.csi.azure.comxb58r found but phase is Pending instead of Bound.
Sep  7 06:21:39.637: INFO: PersistentVolumeClaim test.csi.azure.comxb58r found but phase is Pending instead of Bound.
Sep  7 06:21:41.755: INFO: PersistentVolumeClaim test.csi.azure.comxb58r found but phase is Pending instead of Bound.
Sep  7 06:21:43.883: INFO: PersistentVolumeClaim test.csi.azure.comxb58r found and phase=Bound (59.458480113s)
STEP: Creating pod pod-subpath-test-dynamicpv-pn6f
STEP: Creating a pod to test subpath
Sep  7 06:21:44.245: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pn6f" in namespace "provisioning-2070" to be "Succeeded or Failed"
Sep  7 06:21:44.363: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 117.462813ms
Sep  7 06:21:46.480: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.234772871s
Sep  7 06:21:48.599: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.353273011s
Sep  7 06:21:50.717: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.471414596s
Sep  7 06:21:52.836: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.590603133s
Sep  7 06:21:54.961: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.715452147s
Sep  7 06:21:57.080: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.834444312s
STEP: Saw pod success
Sep  7 06:21:57.080: INFO: Pod "pod-subpath-test-dynamicpv-pn6f" satisfied condition "Succeeded or Failed"
Sep  7 06:21:57.197: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000001 pod pod-subpath-test-dynamicpv-pn6f container test-container-subpath-dynamicpv-pn6f: <nil>
STEP: delete the pod
Sep  7 06:21:57.443: INFO: Waiting for pod pod-subpath-test-dynamicpv-pn6f to disappear
Sep  7 06:21:57.560: INFO: Pod pod-subpath-test-dynamicpv-pn6f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pn6f
Sep  7 06:21:57.560: INFO: Deleting pod "pod-subpath-test-dynamicpv-pn6f" in namespace "provisioning-2070"
STEP: Creating pod pod-subpath-test-dynamicpv-pn6f
STEP: Creating a pod to test subpath
Sep  7 06:21:57.798: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-pn6f" in namespace "provisioning-2070" to be "Succeeded or Failed"
Sep  7 06:21:57.915: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 116.651391ms
Sep  7 06:22:00.037: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.238940788s
Sep  7 06:22:02.155: INFO: Pod "pod-subpath-test-dynamicpv-pn6f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.356819544s
STEP: Saw pod success
Sep  7 06:22:02.155: INFO: Pod "pod-subpath-test-dynamicpv-pn6f" satisfied condition "Succeeded or Failed"
Sep  7 06:22:02.272: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000001 pod pod-subpath-test-dynamicpv-pn6f container test-container-subpath-dynamicpv-pn6f: <nil>
STEP: delete the pod
Sep  7 06:22:02.529: INFO: Waiting for pod pod-subpath-test-dynamicpv-pn6f to disappear
Sep  7 06:22:02.650: INFO: Pod pod-subpath-test-dynamicpv-pn6f no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-pn6f
Sep  7 06:22:02.650: INFO: Deleting pod "pod-subpath-test-dynamicpv-pn6f" in namespace "provisioning-2070"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support existing directories when readOnly specified in the volumeSource
    test/e2e/storage/testsuites/subpath.go:397
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource","total":34,"completed":1,"skipped":313,"failed":0}

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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 67 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should resize volume when PVC is edited while pod is using it
    test/e2e/storage/testsuites/volume_expand.go:248
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it","total":34,"completed":1,"skipped":181,"failed":0}

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 56 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 17 lines ...
Sep  7 06:22:03.154: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:22:03.277: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxmj95] to have phase Bound
Sep  7 06:22:03.395: INFO: PersistentVolumeClaim test.csi.azure.comxmj95 found but phase is Pending instead of Bound.
Sep  7 06:22:05.512: INFO: PersistentVolumeClaim test.csi.azure.comxmj95 found and phase=Bound (2.234760328s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  7 06:22:05.986: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-4kv2m" in namespace "snapshotting-2116" to be "Succeeded or Failed"
Sep  7 06:22:06.105: INFO: Pod "pvc-snapshottable-tester-4kv2m": Phase="Pending", Reason="", readiness=false. Elapsed: 118.986478ms
Sep  7 06:22:08.223: INFO: Pod "pvc-snapshottable-tester-4kv2m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.236941413s
Sep  7 06:22:10.341: INFO: Pod "pvc-snapshottable-tester-4kv2m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.355214294s
STEP: Saw pod success
Sep  7 06:22:10.342: INFO: Pod "pvc-snapshottable-tester-4kv2m" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  7 06:22:10.459: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comxmj95] to have phase Bound
Sep  7 06:22:10.577: INFO: PersistentVolumeClaim test.csi.azure.comxmj95 found and phase=Bound (117.290758ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  7 06:22:10.953: INFO: Pod pvc-snapshottable-tester-4kv2m has the following logs: 
... skipping 130 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 50 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.000 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 51 lines ...
Sep  7 06:21:35.742: INFO: PersistentVolumeClaim test.csi.azure.comxdxmn found but phase is Pending instead of Bound.
Sep  7 06:21:37.860: INFO: PersistentVolumeClaim test.csi.azure.comxdxmn found but phase is Pending instead of Bound.
Sep  7 06:21:39.979: INFO: PersistentVolumeClaim test.csi.azure.comxdxmn found but phase is Pending instead of Bound.
Sep  7 06:21:42.097: INFO: PersistentVolumeClaim test.csi.azure.comxdxmn found and phase=Bound (59.437955201s)
STEP: Creating pod pod-subpath-test-dynamicpv-8bv9
STEP: Creating a pod to test atomic-volume-subpath
Sep  7 06:21:42.452: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8bv9" in namespace "provisioning-9812" to be "Succeeded or Failed"
Sep  7 06:21:42.570: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Pending", Reason="", readiness=false. Elapsed: 117.451577ms
Sep  7 06:21:44.688: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.235861497s
Sep  7 06:21:46.806: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.354193564s
Sep  7 06:21:48.927: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=true. Elapsed: 6.474509601s
Sep  7 06:21:51.045: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=true. Elapsed: 8.592723535s
Sep  7 06:21:53.163: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=true. Elapsed: 10.711156385s
... skipping 4 lines ...
Sep  7 06:22:03.757: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=true. Elapsed: 21.305192036s
Sep  7 06:22:05.879: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=true. Elapsed: 23.426411488s
Sep  7 06:22:07.999: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=true. Elapsed: 25.546430933s
Sep  7 06:22:10.116: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Running", Reason="", readiness=false. Elapsed: 27.664072188s
Sep  7 06:22:12.236: INFO: Pod "pod-subpath-test-dynamicpv-8bv9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.783400997s
STEP: Saw pod success
Sep  7 06:22:12.236: INFO: Pod "pod-subpath-test-dynamicpv-8bv9" satisfied condition "Succeeded or Failed"
Sep  7 06:22:12.353: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000000 pod pod-subpath-test-dynamicpv-8bv9 container test-container-subpath-dynamicpv-8bv9: <nil>
STEP: delete the pod
Sep  7 06:22:12.595: INFO: Waiting for pod pod-subpath-test-dynamicpv-8bv9 to disappear
Sep  7 06:22:12.711: INFO: Pod pod-subpath-test-dynamicpv-8bv9 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-8bv9
Sep  7 06:22:12.711: INFO: Deleting pod "pod-subpath-test-dynamicpv-8bv9" in namespace "provisioning-9812"
... 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":32,"completed":1,"skipped":159,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:18.831: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 37 lines ...
Sep  7 06:22:09.949: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:22:10.069: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comb9mdj] to have phase Bound
Sep  7 06:22:10.186: INFO: PersistentVolumeClaim test.csi.azure.comb9mdj found but phase is Pending instead of Bound.
Sep  7 06:22:12.305: INFO: PersistentVolumeClaim test.csi.azure.comb9mdj found and phase=Bound (2.23547718s)
STEP: Creating pod pod-subpath-test-dynamicpv-hz26
STEP: Creating a pod to test subpath
Sep  7 06:22:12.658: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-hz26" in namespace "provisioning-8925" to be "Succeeded or Failed"
Sep  7 06:22:12.784: INFO: Pod "pod-subpath-test-dynamicpv-hz26": Phase="Pending", Reason="", readiness=false. Elapsed: 126.192275ms
Sep  7 06:22:14.905: INFO: Pod "pod-subpath-test-dynamicpv-hz26": Phase="Pending", Reason="", readiness=false. Elapsed: 2.246665615s
Sep  7 06:22:17.022: INFO: Pod "pod-subpath-test-dynamicpv-hz26": Phase="Pending", Reason="", readiness=false. Elapsed: 4.364445147s
Sep  7 06:22:19.141: INFO: Pod "pod-subpath-test-dynamicpv-hz26": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.482810467s
STEP: Saw pod success
Sep  7 06:22:19.141: INFO: Pod "pod-subpath-test-dynamicpv-hz26" satisfied condition "Succeeded or Failed"
Sep  7 06:22:19.258: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000000 pod pod-subpath-test-dynamicpv-hz26 container test-container-subpath-dynamicpv-hz26: <nil>
STEP: delete the pod
Sep  7 06:22:19.506: INFO: Waiting for pod pod-subpath-test-dynamicpv-hz26 to disappear
Sep  7 06:22:19.622: INFO: Pod pod-subpath-test-dynamicpv-hz26 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-hz26
Sep  7 06:22:19.622: INFO: Deleting pod "pod-subpath-test-dynamicpv-hz26" in namespace "provisioning-8925"
... 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":34,"completed":2,"skipped":624,"failed":0}

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

SSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:26.209: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 66 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (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 24 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  7 06:22:25.708: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.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  7 06:22:26.528: 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  7 06:22:26.529: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-4515" for this suite.


S [SKIPPING] [1.068 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 20 lines ...
STEP: creating a claim
Sep  7 06:22:12.254: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:22:12.374: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comppj8x] to have phase Bound
Sep  7 06:22:12.490: INFO: PersistentVolumeClaim test.csi.azure.comppj8x found but phase is Pending instead of Bound.
Sep  7 06:22:14.607: INFO: PersistentVolumeClaim test.csi.azure.comppj8x found and phase=Bound (2.232953927s)
STEP: Creating pod to format volume volume-prep-provisioning-9398
Sep  7 06:22:14.961: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-9398" in namespace "provisioning-9398" to be "Succeeded or Failed"
Sep  7 06:22:15.078: INFO: Pod "volume-prep-provisioning-9398": Phase="Pending", Reason="", readiness=false. Elapsed: 117.37489ms
Sep  7 06:22:17.197: INFO: Pod "volume-prep-provisioning-9398": Phase="Pending", Reason="", readiness=false. Elapsed: 2.235978756s
Sep  7 06:22:19.315: INFO: Pod "volume-prep-provisioning-9398": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.353865072s
STEP: Saw pod success
Sep  7 06:22:19.315: INFO: Pod "volume-prep-provisioning-9398" satisfied condition "Succeeded or Failed"
Sep  7 06:22:19.315: INFO: Deleting pod "volume-prep-provisioning-9398" in namespace "provisioning-9398"
Sep  7 06:22:19.436: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-9398" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-9zbs
STEP: Checking for subpath error in container status
Sep  7 06:22:23.907: INFO: Deleting pod "pod-subpath-test-dynamicpv-9zbs" in namespace "provisioning-9398"
Sep  7 06:22:24.031: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-9zbs" to be fully deleted
STEP: Deleting pod
Sep  7 06:22:24.149: INFO: Deleting pod "pod-subpath-test-dynamicpv-9zbs" in namespace "provisioning-9398"
STEP: Deleting pvc
Sep  7 06:22:24.266: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comppj8x"
... skipping 12 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should verify container cannot write to subpath readonly volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:425
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]","total":35,"completed":2,"skipped":503,"failed":0}

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

    test/e2e/storage/external/external.go:262
------------------------------
SSSSS
------------------------------
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  7 06:22:32.476: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.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  7 06:22:33.885: INFO: Deleting PersistentVolumeClaim "pvc-2xzzc"
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  7 06:22:34.122: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8886" for this suite.

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

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:34.370: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 156 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":34,"completed":2,"skipped":352,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:35.520: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 37 lines ...
Sep  7 06:22:19.788: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:22:19.907: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com6dc8k] to have phase Bound
Sep  7 06:22:20.025: INFO: PersistentVolumeClaim test.csi.azure.com6dc8k found but phase is Pending instead of Bound.
Sep  7 06:22:22.143: INFO: PersistentVolumeClaim test.csi.azure.com6dc8k found and phase=Bound (2.235350855s)
STEP: Creating pod pod-subpath-test-dynamicpv-fsck
STEP: Creating a pod to test subpath
Sep  7 06:22:22.504: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fsck" in namespace "provisioning-937" to be "Succeeded or Failed"
Sep  7 06:22:22.622: INFO: Pod "pod-subpath-test-dynamicpv-fsck": Phase="Pending", Reason="", readiness=false. Elapsed: 117.780839ms
Sep  7 06:22:24.747: INFO: Pod "pod-subpath-test-dynamicpv-fsck": Phase="Pending", Reason="", readiness=false. Elapsed: 2.242626535s
Sep  7 06:22:26.872: INFO: Pod "pod-subpath-test-dynamicpv-fsck": Phase="Pending", Reason="", readiness=false. Elapsed: 4.367904611s
Sep  7 06:22:28.990: INFO: Pod "pod-subpath-test-dynamicpv-fsck": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.486176573s
STEP: Saw pod success
Sep  7 06:22:28.990: INFO: Pod "pod-subpath-test-dynamicpv-fsck" satisfied condition "Succeeded or Failed"
Sep  7 06:22:29.109: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000001 pod pod-subpath-test-dynamicpv-fsck container test-container-volume-dynamicpv-fsck: <nil>
STEP: delete the pod
Sep  7 06:22:29.356: INFO: Waiting for pod pod-subpath-test-dynamicpv-fsck to disappear
Sep  7 06:22:29.474: INFO: Pod pod-subpath-test-dynamicpv-fsck no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fsck
Sep  7 06:22:29.474: INFO: Deleting pod "pod-subpath-test-dynamicpv-fsck" in namespace "provisioning-937"
... skipping 37 lines ...
    Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping

    test/e2e/storage/external/external.go:262
------------------------------
SS
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path","total":32,"completed":2,"skipped":232,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:35.545: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 3 lines ...

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

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

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

S [SKIPPING] in Spec Setup (BeforeEach) [0.002 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should fail if subpath 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 71 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 63 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support multiple inline ephemeral volumes
    test/e2e/storage/testsuites/ephemeral.go:254
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support multiple inline ephemeral volumes","total":30,"completed":2,"skipped":477,"failed":0}

SSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:42.578: 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 file is outside the volume [Slow][LinuxOnly] [BeforeEach]
    test/e2e/storage/testsuites/subpath.go:258

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

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

    test/e2e/storage/external/external.go:262
------------------------------
SSS
------------------------------
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  7 06:22:34.464: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.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  7 06:22:35.289: INFO: Creating resource for dynamic PV
Sep  7 06:22:35.289: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-5218-e2e-scqxjlc
STEP: creating a claim
Sep  7 06:22:35.415: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:22:35.535: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combrd6r] to have phase Bound
Sep  7 06:22:35.652: INFO: PersistentVolumeClaim test.csi.azure.combrd6r found but phase is Pending instead of Bound.
Sep  7 06:22:37.771: INFO: PersistentVolumeClaim test.csi.azure.combrd6r found and phase=Bound (2.23600643s)
STEP: Creating pod pod-subpath-test-dynamicpv-qlx5
STEP: Checking for subpath error in container status
Sep  7 06:22:42.370: INFO: Deleting pod "pod-subpath-test-dynamicpv-qlx5" in namespace "provisioning-5218"
Sep  7 06:22:42.489: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-qlx5" to be fully deleted
STEP: Deleting pod
Sep  7 06:22:44.726: INFO: Deleting pod "pod-subpath-test-dynamicpv-qlx5" in namespace "provisioning-5218"
STEP: Deleting pvc
Sep  7 06:22:44.844: INFO: Deleting PersistentVolumeClaim "test.csi.azure.combrd6r"
... skipping 9 lines ...

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

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:50.686: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 125 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":42,"completed":2,"skipped":266,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:51.426: INFO: Driver "test.csi.azure.com" does not support topology - skipping
[AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology
  test/e2e/framework/framework.go:188

... skipping 366 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":34,"completed":2,"skipped":382,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:22:57.704: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 115 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (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 88 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents","total":34,"completed":3,"skipped":624,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning
... skipping 48 lines ...
Sep  7 06:22:59.799: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:22:59.918: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8nmlt] to have phase Bound
Sep  7 06:23:00.037: INFO: PersistentVolumeClaim test.csi.azure.com8nmlt found but phase is Pending instead of Bound.
Sep  7 06:23:02.155: INFO: PersistentVolumeClaim test.csi.azure.com8nmlt found and phase=Bound (2.236937814s)
STEP: Creating pod pod-subpath-test-dynamicpv-qnmp
STEP: Creating a pod to test multi_subpath
Sep  7 06:23:02.509: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-qnmp" in namespace "provisioning-8721" to be "Succeeded or Failed"
Sep  7 06:23:02.626: INFO: Pod "pod-subpath-test-dynamicpv-qnmp": Phase="Pending", Reason="", readiness=false. Elapsed: 117.032085ms
Sep  7 06:23:04.746: INFO: Pod "pod-subpath-test-dynamicpv-qnmp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.236501304s
Sep  7 06:23:06.864: INFO: Pod "pod-subpath-test-dynamicpv-qnmp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.355033567s
Sep  7 06:23:08.982: INFO: Pod "pod-subpath-test-dynamicpv-qnmp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.473160118s
STEP: Saw pod success
Sep  7 06:23:08.982: INFO: Pod "pod-subpath-test-dynamicpv-qnmp" satisfied condition "Succeeded or Failed"
Sep  7 06:23:09.100: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000000 pod pod-subpath-test-dynamicpv-qnmp container test-container-subpath-dynamicpv-qnmp: <nil>
STEP: delete the pod
Sep  7 06:23:09.352: INFO: Waiting for pod pod-subpath-test-dynamicpv-qnmp to disappear
Sep  7 06:23:09.469: INFO: Pod pod-subpath-test-dynamicpv-qnmp no longer exists
STEP: Deleting pod
Sep  7 06:23:09.469: INFO: Deleting pod "pod-subpath-test-dynamicpv-qnmp" in namespace "provisioning-8721"
... 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":34,"completed":3,"skipped":520,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:23:15.449: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 168 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (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":35,"completed":5,"skipped":1001,"failed":0}

SSSSSSSSSSSSSSSSSS
------------------------------
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  7 06:23:04.197: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.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  7 06:23:05.022: INFO: Creating resource for dynamic PV
Sep  7 06:23:05.022: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-4952-e2e-sc9nczh
STEP: creating a claim
Sep  7 06:23:05.140: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:23:05.263: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com8zh29] to have phase Bound
Sep  7 06:23:05.381: INFO: PersistentVolumeClaim test.csi.azure.com8zh29 found but phase is Pending instead of Bound.
Sep  7 06:23:07.501: INFO: PersistentVolumeClaim test.csi.azure.com8zh29 found and phase=Bound (2.237651009s)
STEP: Creating pod pod-subpath-test-dynamicpv-z5xc
STEP: Checking for subpath error in container status
Sep  7 06:23:12.095: INFO: Deleting pod "pod-subpath-test-dynamicpv-z5xc" in namespace "provisioning-4952"
Sep  7 06:23:12.216: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-z5xc" to be fully deleted
STEP: Deleting pod
Sep  7 06:23:14.452: INFO: Deleting pod "pod-subpath-test-dynamicpv-z5xc" in namespace "provisioning-4952"
STEP: Deleting pvc
Sep  7 06:23:14.570: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com8zh29"
... skipping 10 lines ...

• [SLOW TEST:21.329 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":34,"completed":4,"skipped":673,"failed":0}

S
------------------------------
[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 6 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  7 06:23:16.424: INFO: Creating resource for dynamic PV
Sep  7 06:23:16.424: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-5055-e2e-sch6cgb
STEP: [init] starting a pod to use the claim
Sep  7 06:23:16.662: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-f5t5j" in namespace "snapshotting-5055" to be "Succeeded or Failed"
Sep  7 06:23:16.779: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Pending", Reason="", readiness=false. Elapsed: 116.503123ms
Sep  7 06:23:18.897: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.234324855s
Sep  7 06:23:21.015: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.353128319s
Sep  7 06:23:23.134: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.471855895s
Sep  7 06:23:25.252: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.589782324s
Sep  7 06:23:27.370: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.707721356s
Sep  7 06:23:29.488: INFO: Pod "pvc-snapshottable-tester-f5t5j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.826081789s
STEP: Saw pod success
Sep  7 06:23:29.488: INFO: Pod "pvc-snapshottable-tester-f5t5j" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  7 06:23:29.608: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  7 06:23:29.609: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-f5t5j-my-volume] to have phase Bound
Sep  7 06:23:29.726: INFO: PersistentVolumeClaim pvc-snapshottable-tester-f5t5j-my-volume found and phase=Bound (117.213341ms)
STEP: [init] checking the PV
... skipping 71 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read/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":42,"completed":3,"skipped":476,"failed":0}

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource]
... skipping 155 lines ...
Sep  7 06:23:26.474: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:23:26.594: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com565kw] to have phase Bound
Sep  7 06:23:26.715: INFO: PersistentVolumeClaim test.csi.azure.com565kw found but phase is Pending instead of Bound.
Sep  7 06:23:28.836: INFO: PersistentVolumeClaim test.csi.azure.com565kw found and phase=Bound (2.242483026s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  7 06:23:29.312: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-pd8lv" in namespace "snapshotting-9887" to be "Succeeded or Failed"
Sep  7 06:23:29.430: INFO: Pod "pvc-snapshottable-tester-pd8lv": Phase="Pending", Reason="", readiness=false. Elapsed: 117.386049ms
Sep  7 06:23:31.548: INFO: Pod "pvc-snapshottable-tester-pd8lv": Phase="Running", Reason="", readiness=false. Elapsed: 2.23590586s
Sep  7 06:23:33.667: INFO: Pod "pvc-snapshottable-tester-pd8lv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.354315363s
STEP: Saw pod success
Sep  7 06:23:33.667: INFO: Pod "pvc-snapshottable-tester-pd8lv" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  7 06:23:33.785: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com565kw] to have phase Bound
Sep  7 06:23:33.903: INFO: PersistentVolumeClaim test.csi.azure.com565kw found and phase=Bound (117.710612ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  7 06:23:34.265: INFO: Pod pvc-snapshottable-tester-pd8lv has the following logs: 
... skipping 109 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 75 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition","total":34,"completed":3,"skipped":744,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:23:45.477: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 97 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":34,"completed":4,"skipped":757,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:23:50.039: INFO: Driver "test.csi.azure.com" does not support block volume mode - skipping
... skipping 37 lines ...
Sep  7 06:23:51.065: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:23:51.185: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.commgtsz] to have phase Bound
Sep  7 06:23:51.302: INFO: PersistentVolumeClaim test.csi.azure.commgtsz found but phase is Pending instead of Bound.
Sep  7 06:23:53.422: INFO: PersistentVolumeClaim test.csi.azure.commgtsz found and phase=Bound (2.237288203s)
STEP: Creating pod exec-volume-test-dynamicpv-xmkf
STEP: Creating a pod to test exec-volume-test
Sep  7 06:23:53.778: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-xmkf" in namespace "volume-1548" to be "Succeeded or Failed"
Sep  7 06:23:53.896: INFO: Pod "exec-volume-test-dynamicpv-xmkf": Phase="Pending", Reason="", readiness=false. Elapsed: 118.150963ms
Sep  7 06:23:56.014: INFO: Pod "exec-volume-test-dynamicpv-xmkf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.236302811s
Sep  7 06:23:58.132: INFO: Pod "exec-volume-test-dynamicpv-xmkf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.353936681s
Sep  7 06:24:00.250: INFO: Pod "exec-volume-test-dynamicpv-xmkf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.472391862s
STEP: Saw pod success
Sep  7 06:24:00.250: INFO: Pod "exec-volume-test-dynamicpv-xmkf" satisfied condition "Succeeded or Failed"
Sep  7 06:24:00.367: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000001 pod exec-volume-test-dynamicpv-xmkf container exec-container-dynamicpv-xmkf: <nil>
STEP: delete the pod
Sep  7 06:24:00.610: INFO: Waiting for pod exec-volume-test-dynamicpv-xmkf to disappear
Sep  7 06:24:00.727: INFO: Pod exec-volume-test-dynamicpv-xmkf no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-xmkf
Sep  7 06:24:00.727: INFO: Deleting pod "exec-volume-test-dynamicpv-xmkf" in namespace "volume-1548"
... 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":34,"completed":5,"skipped":841,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:24:06.708: 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 126 lines ...
Sep  7 06:23:46.438: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:23:46.563: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5xsbj] to have phase Bound
Sep  7 06:23:46.680: INFO: PersistentVolumeClaim test.csi.azure.com5xsbj found but phase is Pending instead of Bound.
Sep  7 06:23:48.798: INFO: PersistentVolumeClaim test.csi.azure.com5xsbj found and phase=Bound (2.234949636s)
STEP: Expanding non-expandable pvc
Sep  7 06:23:49.032: INFO: currentPvcSize {{5368709120 0} {<nil>} 5Gi BinarySI}, newSize {{6442450944 0} {<nil>}  BinarySI}
Sep  7 06:23:49.268: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:23:51.509: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:23:53.508: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:23:55.507: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:23:57.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:23:59.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:01.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:03.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:05.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:07.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:09.503: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:11.504: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:13.506: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:15.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:17.505: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:19.503: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  7 06:24:19.737: INFO: Error updating pvc test.csi.azure.com5xsbj: persistentvolumeclaims "test.csi.azure.com5xsbj" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Sep  7 06:24:19.738: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com5xsbj"
Sep  7 06:24:19.856: INFO: Waiting up to 5m0s for PersistentVolume pvc-49a43998-9450-4bc8-b76a-6b5e196a80ff to get deleted
Sep  7 06:24:19.973: INFO: PersistentVolume pvc-49a43998-9450-4bc8-b76a-6b5e196a80ff found and phase=Released (117.228954ms)
Sep  7 06:24:25.090: INFO: PersistentVolume pvc-49a43998-9450-4bc8-b76a-6b5e196a80ff was removed
STEP: Deleting sc
... skipping 8 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] volume-expand
  test/e2e/storage/framework/testsuite.go:50
    should not allow expansion of pvcs without AllowVolumeExpansion property
    test/e2e/storage/testsuites/volume_expand.go:159
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property","total":34,"completed":4,"skipped":797,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:24:25.627: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 78 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":32,"completed":3,"skipped":647,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[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 136 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 225 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with the same volume mode and retain data across pod recreation on the same node
    test/e2e/storage/testsuites/multivolume.go:138
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node","total":34,"completed":5,"skipped":894,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:24:32.232: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 37 lines ...
Sep  7 06:24:26.584: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:24:26.707: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comjddrk] to have phase Bound
Sep  7 06:24:26.824: INFO: PersistentVolumeClaim test.csi.azure.comjddrk found but phase is Pending instead of Bound.
Sep  7 06:24:28.941: INFO: PersistentVolumeClaim test.csi.azure.comjddrk found and phase=Bound (2.234459873s)
STEP: Creating pod pod-subpath-test-dynamicpv-28hk
STEP: Creating a pod to test subpath
Sep  7 06:24:29.296: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-28hk" in namespace "provisioning-9613" to be "Succeeded or Failed"
Sep  7 06:24:29.413: INFO: Pod "pod-subpath-test-dynamicpv-28hk": Phase="Pending", Reason="", readiness=false. Elapsed: 117.263873ms
Sep  7 06:24:31.532: INFO: Pod "pod-subpath-test-dynamicpv-28hk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.236681665s
Sep  7 06:24:33.650: INFO: Pod "pod-subpath-test-dynamicpv-28hk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.354472182s
Sep  7 06:24:35.768: INFO: Pod "pod-subpath-test-dynamicpv-28hk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.47203656s
STEP: Saw pod success
Sep  7 06:24:35.768: INFO: Pod "pod-subpath-test-dynamicpv-28hk" satisfied condition "Succeeded or Failed"
Sep  7 06:24:35.885: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000001 pod pod-subpath-test-dynamicpv-28hk container test-container-subpath-dynamicpv-28hk: <nil>
STEP: delete the pod
Sep  7 06:24:36.132: INFO: Waiting for pod pod-subpath-test-dynamicpv-28hk to disappear
Sep  7 06:24:36.249: INFO: Pod pod-subpath-test-dynamicpv-28hk no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-28hk
Sep  7 06:24:36.249: INFO: Deleting pod "pod-subpath-test-dynamicpv-28hk" in namespace "provisioning-9613"
... 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":34,"completed":5,"skipped":889,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:24:42.315: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 123 lines ...
Sep  7 06:24:31.242: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:24:31.361: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combsfjt] to have phase Bound
Sep  7 06:24:31.479: INFO: PersistentVolumeClaim test.csi.azure.combsfjt found but phase is Pending instead of Bound.
Sep  7 06:24:33.598: INFO: PersistentVolumeClaim test.csi.azure.combsfjt found and phase=Bound (2.236162818s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  7 06:24:34.071: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-j6npn" in namespace "snapshotting-5376" to be "Succeeded or Failed"
Sep  7 06:24:34.190: INFO: Pod "pvc-snapshottable-tester-j6npn": Phase="Pending", Reason="", readiness=false. Elapsed: 119.380135ms
Sep  7 06:24:36.308: INFO: Pod "pvc-snapshottable-tester-j6npn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237259733s
Sep  7 06:24:38.430: INFO: Pod "pvc-snapshottable-tester-j6npn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.358691512s
STEP: Saw pod success
Sep  7 06:24:38.430: INFO: Pod "pvc-snapshottable-tester-j6npn" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  7 06:24:38.547: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combsfjt] to have phase Bound
Sep  7 06:24:38.665: INFO: PersistentVolumeClaim test.csi.azure.combsfjt found and phase=Bound (117.171241ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  7 06:24:39.022: INFO: Pod pvc-snapshottable-tester-j6npn has the following logs: 
... skipping 92 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":42,"completed":4,"skipped":490,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] 
  should concurrently access the single volume from pods on different node
  test/e2e/storage/testsuites/multivolume.go:451
... skipping 139 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":34,"completed":6,"skipped":948,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[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 12 lines ...
Sep  7 06:24:46.252: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:24:46.373: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comggkhc] to have phase Bound
Sep  7 06:24:46.490: INFO: PersistentVolumeClaim test.csi.azure.comggkhc found but phase is Pending instead of Bound.
Sep  7 06:24:48.609: INFO: PersistentVolumeClaim test.csi.azure.comggkhc found and phase=Bound (2.235742362s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  7 06:24:49.085: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-xgjwx" in namespace "snapshotting-1541" to be "Succeeded or Failed"
Sep  7 06:24:49.203: INFO: Pod "pvc-snapshottable-tester-xgjwx": Phase="Pending", Reason="", readiness=false. Elapsed: 117.837262ms
Sep  7 06:24:51.322: INFO: Pod "pvc-snapshottable-tester-xgjwx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.237051365s
Sep  7 06:24:53.442: INFO: Pod "pvc-snapshottable-tester-xgjwx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.357047306s
STEP: Saw pod success
Sep  7 06:24:53.443: INFO: Pod "pvc-snapshottable-tester-xgjwx" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  7 06:24:53.559: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comggkhc] to have phase Bound
Sep  7 06:24:53.677: INFO: PersistentVolumeClaim test.csi.azure.comggkhc found and phase=Bound (117.390314ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  7 06:24:54.050: INFO: Pod pvc-snapshottable-tester-xgjwx has the following logs: 
... skipping 116 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":34,"completed":6,"skipped":939,"failed":0}

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

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

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

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

SSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:25:07.877: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 47 lines ...
Sep  7 06:25:01.195: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:25:01.323: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com5k7r8] to have phase Bound
Sep  7 06:25:01.441: INFO: PersistentVolumeClaim test.csi.azure.com5k7r8 found but phase is Pending instead of Bound.
Sep  7 06:25:03.560: INFO: PersistentVolumeClaim test.csi.azure.com5k7r8 found and phase=Bound (2.236453717s)
STEP: Creating pod pod-subpath-test-dynamicpv-fl7t
STEP: Creating a pod to test subpath
Sep  7 06:25:03.914: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fl7t" in namespace "provisioning-6515" to be "Succeeded or Failed"
Sep  7 06:25:04.031: INFO: Pod "pod-subpath-test-dynamicpv-fl7t": Phase="Pending", Reason="", readiness=false. Elapsed: 117.018781ms
Sep  7 06:25:06.150: INFO: Pod "pod-subpath-test-dynamicpv-fl7t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.236249579s
Sep  7 06:25:08.268: INFO: Pod "pod-subpath-test-dynamicpv-fl7t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.353756996s
Sep  7 06:25:10.386: INFO: Pod "pod-subpath-test-dynamicpv-fl7t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.472518803s
STEP: Saw pod success
Sep  7 06:25:10.386: INFO: Pod "pod-subpath-test-dynamicpv-fl7t" satisfied condition "Succeeded or Failed"
Sep  7 06:25:10.504: INFO: Trying to get logs from node k8s-agentpool1-42778123-vmss000000 pod pod-subpath-test-dynamicpv-fl7t container test-container-volume-dynamicpv-fl7t: <nil>
STEP: delete the pod
Sep  7 06:25:10.748: INFO: Waiting for pod pod-subpath-test-dynamicpv-fl7t to disappear
Sep  7 06:25:10.866: INFO: Pod pod-subpath-test-dynamicpv-fl7t no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-fl7t
Sep  7 06:25:10.866: INFO: Deleting pod "pod-subpath-test-dynamicpv-fl7t" in namespace "provisioning-6515"
... 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":32,"completed":4,"skipped":1020,"failed":0}

SSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] 
  should concurrently access the single volume from pods on the same node
  test/e2e/storage/testsuites/multivolume.go:298
... skipping 139 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":42,"completed":5,"skipped":505,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:25:35.859: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 80 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read-only inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:175
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume","total":34,"completed":7,"skipped":989,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:25:41.462: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... 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":42,"completed":6,"skipped":524,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:26:16.322: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 55 lines ...

    test/e2e/storage/testsuites/multivolume.go:84
------------------------------
SSSSSSSSSSSS
------------------------------
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  7 06:26:16.371: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.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  7 06:26:17.197: INFO: Creating resource for dynamic PV
Sep  7 06:26:17.197: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-6623-e2e-scl266m
STEP: creating a claim
Sep  7 06:26:17.316: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  7 06:26:17.436: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com7gprw] to have phase Bound
Sep  7 06:26:17.554: INFO: PersistentVolumeClaim test.csi.azure.com7gprw found but phase is Pending instead of Bound.
Sep  7 06:26:19.674: INFO: PersistentVolumeClaim test.csi.azure.com7gprw found and phase=Bound (2.237523325s)
STEP: Creating pod pod-subpath-test-dynamicpv-tqwk
STEP: Checking for subpath error in container status
Sep  7 06:26:24.267: INFO: Deleting pod "pod-subpath-test-dynamicpv-tqwk" in namespace "provisioning-6623"
Sep  7 06:26:24.388: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tqwk" to be fully deleted
STEP: Deleting pod
Sep  7 06:26:26.626: INFO: Deleting pod "pod-subpath-test-dynamicpv-tqwk" in namespace "provisioning-6623"
STEP: Deleting pvc
Sep  7 06:26:26.746: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com7gprw"
... skipping 9 lines ...

• [SLOW TEST:16.214 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":42,"completed":7,"skipped":698,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:26:32.600: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 214 lines ...
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] 
  should access to two volumes with the same volume mode and retain data across pod recreation on different node
  test/e2e/storage/testsuites/multivolume.go:168

{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (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":42,"completed":8,"skipped":787,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  7 06:27:01.482: INFO: >>> kubeConfig: /root/tmp3824419498/kubeconfig/kubeconfig.francecentral.json
... skipping 171 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should access to two volumes with the same volume mode and retain data across pod recreation on different node
    test/e2e/storage/testsuites/multivolume.go:168
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node","total":42,"completed":9,"skipped":787,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  7 06:27:52.839: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 85 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should 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":42,"completed":10,"skipped":959,"failed":0}

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
... skipping 45 lines ...
Sep  7 06:25:16.937: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep  7 06:25:16.937: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3
Sep  7 06:28:09.783: INFO: Running AfterSuite actions on node 1


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

Ginkgo ran 1 suite in 7m34.923449585s
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:
I0907 06:20:30.317553       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-aea62949fedc3da035043dbcbf84c45d56bff77a e2e-test
I0907 06:20:30.317824       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:30.341267       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
I0907 06:20:30.341284       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:30.341294       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0907 06:20:30.341313       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0907 06:20:30.342773       1 azure_auth.go:245] Using AzurePublicCloud environment
I0907 06:20:30.342895       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0907 06:20:30.342921       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 104 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0907 06:20:28.720406       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-aea62949fedc3da035043dbcbf84c45d56bff77a e2e-test
I0907 06:20:28.720694       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:28.744761       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
I0907 06:20:28.744777       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:28.744782       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0907 06:20:28.744799       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0907 06:20:28.745733       1 azure_auth.go:245] Using AzurePublicCloud environment
I0907 06:20:28.745770       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0907 06:20:28.745787       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 367 lines ...
I0907 06:22:33.041259       1 controllerserver.go:452] begin to create file share(pvcn-a037768c-bb02-4d6a-bd71-42c4c2d2083b) on account(f6bcaa7f984ef46f6ae931a) type(Premium_LRS) rg(kubetest-upt1gfyy) location() size(100) protocol(NFS)
I0907 06:22:33.200932       1 controllerserver.go:474] create file share pvcn-a037768c-bb02-4d6a-bd71-42c4c2d2083b on storage account f6bcaa7f984ef46f6ae931a successfully
I0907 06:22:33.200998       1 azure_metrics.go:115] "Observed Request Latency" latency_seconds=0.15972081 request="azurefile_csi_driver_controller_create_volume" resource_group="kubetest-upt1gfyy" subscription_id="0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e" source="test.csi.azure.com" volumeid="kubetest-upt1gfyy#f6bcaa7f984ef46f6ae931a#pvcn-a037768c-bb02-4d6a-bd71-42c4c2d2083b###ephemeral-256" result_code="succeeded"
I0907 06:22:33.201015       1 utils.go:83] GRPC response: {"volume":{"capacity_bytes":5368709120,"volume_context":{"csi.storage.k8s.io/pv/name":"pvc-a037768c-bb02-4d6a-bd71-42c4c2d2083b","csi.storage.k8s.io/pvc/name":"inline-volume-tester2-mv6px-my-volume-0","csi.storage.k8s.io/pvc/namespace":"ephemeral-256","protocol":"nfs","secretnamespace":"ephemeral-256","skuName":"Premium_LRS"},"volume_id":"kubetest-upt1gfyy#f6bcaa7f984ef46f6ae931a#pvcn-a037768c-bb02-4d6a-bd71-42c4c2d2083b###ephemeral-256"}}
I0907 06:22:33.481581       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0907 06:22:33.481694       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-77679a7a-65e8-4b48-bbce-c5cd9f9748f2","parameters":{"csi.storage.k8s.io/pv/name":"pvc-77679a7a-65e8-4b48-bbce-c5cd9f9748f2","csi.storage.k8s.io/pvc/name":"pvc-2xzzc","csi.storage.k8s.io/pvc/namespace":"volumemode-8886","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0907 06:22:33.481836       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0907 06:22:33.946884       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0907 06:22:33.946900       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-77679a7a-65e8-4b48-bbce-c5cd9f9748f2","parameters":{"csi.storage.k8s.io/pv/name":"pvc-77679a7a-65e8-4b48-bbce-c5cd9f9748f2","csi.storage.k8s.io/pvc/name":"pvc-2xzzc","csi.storage.k8s.io/pvc/namespace":"volumemode-8886","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0907 06:22:33.947036       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0907 06:22:35.483692       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0907 06:22:35.483803       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-949299ea-ad8c-49c1-aa3a-3696f2017ff5","parameters":{"csi.storage.k8s.io/pv/name":"pvc-949299ea-ad8c-49c1-aa3a-3696f2017ff5","csi.storage.k8s.io/pvc/name":"test.csi.azure.combrd6r","csi.storage.k8s.io/pvc/namespace":"provisioning-5218","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Mount":{}},"access_mode":{"mode":7}}]}
I0907 06:22:35.483988       1 controllerserver.go:297] set vnetResourceID(/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-upt1gfyy/providers/Microsoft.Network/virtualNetworks/k8s-vnet-42778123/subnets/k8s-subnet) for NFS protocol
I0907 06:22:35.484002       1 azure.go:180] updateSubnetServiceEndpoints on vnetName: k8s-vnet-42778123, subnetName: k8s-subnet, location: francecentral
I0907 06:22:35.519956       1 azure.go:209] serviceEndpoint(Microsoft.Storage) is already in subnet(k8s-subnet)
I0907 06:22:35.569735       1 controllerserver.go:452] begin to create file share(pvcn-949299ea-ad8c-49c1-aa3a-3696f2017ff5) on account(f6bcaa7f984ef46f6ae931a) type(Premium_LRS) rg(kubetest-upt1gfyy) location() size(100) protocol(NFS)
... skipping 573 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0907 06:20:22.894072       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-aea62949fedc3da035043dbcbf84c45d56bff77a e2e-test
I0907 06:20:22.894369       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:22.926972       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
I0907 06:20:22.926988       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:22.927003       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0907 06:20:22.927020       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0907 06:20:22.927818       1 azure_auth.go:245] Using AzurePublicCloud environment
I0907 06:20:22.927871       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0907 06:20:22.927889       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1052 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0907 06:20:19.098129       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-aea62949fedc3da035043dbcbf84c45d56bff77a e2e-test
I0907 06:20:19.098508       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:19.120001       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
I0907 06:20:19.120028       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:19.120034       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0907 06:20:19.120181       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0907 06:20:19.121532       1 azure_auth.go:245] Using AzurePublicCloud environment
I0907 06:20:19.121745       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0907 06:20:19.121954       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:
I0907 06:20:26.165792       1 azurefile.go:286] driver userAgent: test.csi.azure.com/e2e-aea62949fedc3da035043dbcbf84c45d56bff77a e2e-test
I0907 06:20:26.166218       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:26.192885       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
I0907 06:20:26.192902       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0907 06:20:26.192908       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0907 06:20:26.192927       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0907 06:20:26.193534       1 azure_auth.go:245] Using AzurePublicCloud environment
I0907 06:20:26.193570       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0907 06:20:26.193597       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1386 lines ...