This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: delete volume failure when management api is throttled
Resultsuccess
Tests 0 failed / 14 succeeded
Started2022-09-08 11:47
Elapsed27m22s
Revision
Refs 1082
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-9388c85a9851ac68a89b3e978ebff88c92a23c0a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a not found: manifest unknown: manifest tagged by "e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a" 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-9388c85a9851ac68a89b3e978ebff88c92a23c0a -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=9388c85a9851ac68a89b3e978ebff88c92a23c0a -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-09-08T11:51:12Z -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 1805 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 315 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 365 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 111 lines ...
Sep  8 12:01:52.750: INFO: PersistentVolumeClaim test.csi.azure.com9gpqd found but phase is Pending instead of Bound.
Sep  8 12:01:54.781: INFO: PersistentVolumeClaim test.csi.azure.com9gpqd found but phase is Pending instead of Bound.
Sep  8 12:01:56.808: INFO: PersistentVolumeClaim test.csi.azure.com9gpqd found but phase is Pending instead of Bound.
Sep  8 12:01:58.837: INFO: PersistentVolumeClaim test.csi.azure.com9gpqd found and phase=Bound (58.909703803s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 12:01:58.948: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-l547l" in namespace "snapshotting-9589" to be "Succeeded or Failed"
Sep  8 12:01:58.976: INFO: Pod "pvc-snapshottable-tester-l547l": Phase="Pending", Reason="", readiness=false. Elapsed: 27.967904ms
Sep  8 12:02:01.005: INFO: Pod "pvc-snapshottable-tester-l547l": Phase="Running", Reason="", readiness=true. Elapsed: 2.05627064s
Sep  8 12:02:03.034: INFO: Pod "pvc-snapshottable-tester-l547l": Phase="Running", Reason="", readiness=false. Elapsed: 4.086006694s
Sep  8 12:02:05.063: INFO: Pod "pvc-snapshottable-tester-l547l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.11508903s
STEP: Saw pod success
Sep  8 12:02:05.063: INFO: Pod "pvc-snapshottable-tester-l547l" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 12:02:05.092: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com9gpqd] to have phase Bound
Sep  8 12:02:05.119: INFO: PersistentVolumeClaim test.csi.azure.com9gpqd found and phase=Bound (27.715551ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 12:02:05.238: INFO: Pod pvc-snapshottable-tester-l547l has the following logs: 
... skipping 220 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSSSSSSS
------------------------------
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
... skipping 2 lines ...
STEP: Building a namespace api object, basename provisioning
W0908 12:00:59.990609   36072 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
Sep  8 12:00:59.990: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled
Sep  8 12:01:00.024: INFO: No PSP annotation exists on dry run pod; assuming PodSecurityPolicy is disabled
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:258
Sep  8 12:01:00.153: INFO: Creating resource for dynamic PV
Sep  8 12:01:00.153: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-2888-e2e-scjqnh5
STEP: creating a claim
Sep  8 12:01:00.187: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
... skipping 25 lines ...
Sep  8 12:01:49.072: INFO: PersistentVolumeClaim test.csi.azure.comsrnwp found but phase is Pending instead of Bound.
Sep  8 12:01:51.106: INFO: PersistentVolumeClaim test.csi.azure.comsrnwp found but phase is Pending instead of Bound.
Sep  8 12:01:53.140: INFO: PersistentVolumeClaim test.csi.azure.comsrnwp found but phase is Pending instead of Bound.
Sep  8 12:01:55.174: INFO: PersistentVolumeClaim test.csi.azure.comsrnwp found but phase is Pending instead of Bound.
Sep  8 12:01:57.210: INFO: PersistentVolumeClaim test.csi.azure.comsrnwp found and phase=Bound (56.987245167s)
STEP: Creating pod pod-subpath-test-dynamicpv-26xb
STEP: Checking for subpath error in container status
Sep  8 12:02:05.383: INFO: Deleting pod "pod-subpath-test-dynamicpv-26xb" in namespace "provisioning-2888"
Sep  8 12:02:05.417: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-26xb" to be fully deleted
STEP: Deleting pod
Sep  8 12:02:07.484: INFO: Deleting pod "pod-subpath-test-dynamicpv-26xb" in namespace "provisioning-2888"
STEP: Deleting pvc
Sep  8 12:02:07.517: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comsrnwp"
... skipping 9 lines ...

• [SLOW TEST:72.895 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":29,"completed":1,"skipped":302,"failed":0}

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

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

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

    test/e2e/storage/external/external.go:262
------------------------------
SSSS
------------------------------
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  8 12:01:00.203: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.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  8 12:01:00.417: INFO: Creating resource for dynamic PV
Sep  8 12:01:00.417: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-483-e2e-scjqpt8
STEP: creating a claim
Sep  8 12:01:00.449: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
... skipping 25 lines ...
Sep  8 12:01:49.254: INFO: PersistentVolumeClaim test.csi.azure.com844zn found but phase is Pending instead of Bound.
Sep  8 12:01:51.282: INFO: PersistentVolumeClaim test.csi.azure.com844zn found but phase is Pending instead of Bound.
Sep  8 12:01:53.312: INFO: PersistentVolumeClaim test.csi.azure.com844zn found but phase is Pending instead of Bound.
Sep  8 12:01:55.340: INFO: PersistentVolumeClaim test.csi.azure.com844zn found but phase is Pending instead of Bound.
Sep  8 12:01:57.368: INFO: PersistentVolumeClaim test.csi.azure.com844zn found and phase=Bound (56.886884531s)
STEP: Creating pod pod-subpath-test-dynamicpv-wvtk
STEP: Checking for subpath error in container status
Sep  8 12:02:05.511: INFO: Deleting pod "pod-subpath-test-dynamicpv-wvtk" in namespace "provisioning-483"
Sep  8 12:02:05.541: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-wvtk" to be fully deleted
STEP: Deleting pod
Sep  8 12:02:09.599: INFO: Deleting pod "pod-subpath-test-dynamicpv-wvtk" in namespace "provisioning-483"
STEP: Deleting pvc
Sep  8 12:02:09.626: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com844zn"
... skipping 9 lines ...

• [SLOW TEST:74.624 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":36,"completed":1,"skipped":325,"failed":0}

SSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should be able to unmount after the subpath directory is deleted [LinuxOnly]
  test/e2e/storage/testsuites/subpath.go:447
... skipping 74 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should be able to unmount after the subpath directory is deleted [LinuxOnly]
    test/e2e/storage/testsuites/subpath.go:447
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]","total":36,"completed":1,"skipped":151,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:02:15.130: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 263 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":37,"completed":1,"skipped":35,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:02:17.785: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 24 lines ...

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

SSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:02:25.125: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 45 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: 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 17 lines ...
Sep  8 12:02:15.073: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:02:15.102: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com58rpt] to have phase Bound
Sep  8 12:02:15.130: INFO: PersistentVolumeClaim test.csi.azure.com58rpt found but phase is Pending instead of Bound.
Sep  8 12:02:17.159: INFO: PersistentVolumeClaim test.csi.azure.com58rpt found and phase=Bound (2.056887659s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 12:02:17.272: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-wpc5g" in namespace "snapshotting-7863" to be "Succeeded or Failed"
Sep  8 12:02:17.300: INFO: Pod "pvc-snapshottable-tester-wpc5g": Phase="Pending", Reason="", readiness=false. Elapsed: 28.033945ms
Sep  8 12:02:19.330: INFO: Pod "pvc-snapshottable-tester-wpc5g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058675676s
Sep  8 12:02:21.360: INFO: Pod "pvc-snapshottable-tester-wpc5g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.088032574s
STEP: Saw pod success
Sep  8 12:02:21.360: INFO: Pod "pvc-snapshottable-tester-wpc5g" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 12:02:21.388: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com58rpt] to have phase Bound
Sep  8 12:02:21.416: INFO: PersistentVolumeClaim test.csi.azure.com58rpt found and phase=Bound (27.996834ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 12:02:21.656: INFO: Pod pvc-snapshottable-tester-wpc5g has the following logs: 
... skipping 131 lines ...
Sep  8 12:01:50.664: INFO: PersistentVolumeClaim test.csi.azure.coml2pkl found but phase is Pending instead of Bound.
Sep  8 12:01:52.692: INFO: PersistentVolumeClaim test.csi.azure.coml2pkl found but phase is Pending instead of Bound.
Sep  8 12:01:54.721: INFO: PersistentVolumeClaim test.csi.azure.coml2pkl found but phase is Pending instead of Bound.
Sep  8 12:01:56.749: INFO: PersistentVolumeClaim test.csi.azure.coml2pkl found and phase=Bound (56.840973985s)
STEP: Creating pod pod-subpath-test-dynamicpv-xrzw
STEP: Creating a pod to test atomic-volume-subpath
Sep  8 12:01:56.838: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-xrzw" in namespace "provisioning-7245" to be "Succeeded or Failed"
Sep  8 12:01:56.869: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Pending", Reason="", readiness=false. Elapsed: 31.47824ms
Sep  8 12:01:58.898: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059619231s
Sep  8 12:02:00.927: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088655238s
Sep  8 12:02:02.956: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118305375s
Sep  8 12:02:04.985: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Running", Reason="", readiness=true. Elapsed: 8.146949555s
Sep  8 12:02:07.014: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Running", Reason="", readiness=true. Elapsed: 10.176285563s
... skipping 4 lines ...
Sep  8 12:02:17.179: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Running", Reason="", readiness=true. Elapsed: 20.340705809s
Sep  8 12:02:19.208: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Running", Reason="", readiness=true. Elapsed: 22.369749901s
Sep  8 12:02:21.238: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Running", Reason="", readiness=true. Elapsed: 24.39970281s
Sep  8 12:02:23.267: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Running", Reason="", readiness=true. Elapsed: 26.429136645s
Sep  8 12:02:25.296: INFO: Pod "pod-subpath-test-dynamicpv-xrzw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.457775466s
STEP: Saw pod success
Sep  8 12:02:25.296: INFO: Pod "pod-subpath-test-dynamicpv-xrzw" satisfied condition "Succeeded or Failed"
Sep  8 12:02:25.324: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-xrzw container test-container-subpath-dynamicpv-xrzw: <nil>
STEP: delete the pod
Sep  8 12:02:25.396: INFO: Waiting for pod pod-subpath-test-dynamicpv-xrzw to disappear
Sep  8 12:02:25.434: INFO: Pod pod-subpath-test-dynamicpv-xrzw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-xrzw
Sep  8 12:02:25.434: INFO: Deleting pod "pod-subpath-test-dynamicpv-xrzw" in namespace "provisioning-7245"
... 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":34,"completed":1,"skipped":34,"failed":0}

SSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:02:30.705: INFO: Driver test.csi.azure.com doesn't specify snapshot stress test options -- skipping
... skipping 132 lines ...
Sep  8 12:02:18.376: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:02:18.407: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2gk42] to have phase Bound
Sep  8 12:02:18.434: INFO: PersistentVolumeClaim test.csi.azure.com2gk42 found but phase is Pending instead of Bound.
Sep  8 12:02:20.481: INFO: PersistentVolumeClaim test.csi.azure.com2gk42 found and phase=Bound (2.073986583s)
STEP: Creating pod pod-subpath-test-dynamicpv-spn2
STEP: Creating a pod to test subpath
Sep  8 12:02:20.565: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-spn2" in namespace "provisioning-5311" to be "Succeeded or Failed"
Sep  8 12:02:20.592: INFO: Pod "pod-subpath-test-dynamicpv-spn2": Phase="Pending", Reason="", readiness=false. Elapsed: 27.050971ms
Sep  8 12:02:22.621: INFO: Pod "pod-subpath-test-dynamicpv-spn2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055840027s
Sep  8 12:02:24.649: INFO: Pod "pod-subpath-test-dynamicpv-spn2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.084318589s
Sep  8 12:02:26.676: INFO: Pod "pod-subpath-test-dynamicpv-spn2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.11162724s
STEP: Saw pod success
Sep  8 12:02:26.677: INFO: Pod "pod-subpath-test-dynamicpv-spn2" satisfied condition "Succeeded or Failed"
Sep  8 12:02:26.703: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000001 pod pod-subpath-test-dynamicpv-spn2 container test-container-subpath-dynamicpv-spn2: <nil>
STEP: delete the pod
Sep  8 12:02:26.772: INFO: Waiting for pod pod-subpath-test-dynamicpv-spn2 to disappear
Sep  8 12:02:26.799: INFO: Pod pod-subpath-test-dynamicpv-spn2 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-spn2
Sep  8 12:02:26.799: INFO: Deleting pod "pod-subpath-test-dynamicpv-spn2" in namespace "provisioning-5311"
... 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":37,"completed":2,"skipped":183,"failed":0}

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
... skipping 158 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSSSSS
------------------------------
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  8 12:02:27.023: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.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  8 12:02:27.223: INFO: Creating resource for dynamic PV
Sep  8 12:02:27.224: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8668-e2e-scblcps
STEP: creating a claim
Sep  8 12:02:27.252: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:02:27.287: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.combgc6x] to have phase Bound
Sep  8 12:02:27.315: INFO: PersistentVolumeClaim test.csi.azure.combgc6x found but phase is Pending instead of Bound.
Sep  8 12:02:29.344: INFO: PersistentVolumeClaim test.csi.azure.combgc6x found and phase=Bound (2.056474494s)
STEP: Creating pod pod-subpath-test-dynamicpv-2bq8
STEP: Checking for subpath error in container status
Sep  8 12:02:33.489: INFO: Deleting pod "pod-subpath-test-dynamicpv-2bq8" in namespace "provisioning-8668"
Sep  8 12:02:33.518: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2bq8" to be fully deleted
STEP: Deleting pod
Sep  8 12:02:35.576: INFO: Deleting pod "pod-subpath-test-dynamicpv-2bq8" in namespace "provisioning-8668"
STEP: Deleting pvc
Sep  8 12:02:35.604: INFO: Deleting PersistentVolumeClaim "test.csi.azure.combgc6x"
... skipping 9 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:02:40.831: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 48 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  8 12:02:32.909: INFO: Creating resource for dynamic PV
Sep  8 12:02:32.909: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-228-e2e-scn2l8t
STEP: [init] starting a pod to use the claim
Sep  8 12:02:32.967: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-b7vcs" in namespace "snapshotting-228" to be "Succeeded or Failed"
Sep  8 12:02:32.994: INFO: Pod "pvc-snapshottable-tester-b7vcs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.87608ms
Sep  8 12:02:35.023: INFO: Pod "pvc-snapshottable-tester-b7vcs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056072545s
Sep  8 12:02:37.052: INFO: Pod "pvc-snapshottable-tester-b7vcs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.084390937s
Sep  8 12:02:39.080: INFO: Pod "pvc-snapshottable-tester-b7vcs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.11305475s
Sep  8 12:02:41.108: INFO: Pod "pvc-snapshottable-tester-b7vcs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.140900432s
STEP: Saw pod success
Sep  8 12:02:41.108: INFO: Pod "pvc-snapshottable-tester-b7vcs" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  8 12:02:41.135: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  8 12:02:41.136: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-b7vcs-my-volume] to have phase Bound
Sep  8 12:02:41.163: INFO: PersistentVolumeClaim pvc-snapshottable-tester-b7vcs-my-volume found and phase=Bound (27.057531ms)
STEP: [init] checking the PV
... skipping 211 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":29,"completed":2,"skipped":551,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:02:57.879: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 159 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 245 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":36,"completed":2,"skipped":469,"failed":0}

SSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:04.998: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 37 lines ...
Sep  8 12:02:31.288: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:02:31.321: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comtthmz] to have phase Bound
Sep  8 12:02:31.348: INFO: PersistentVolumeClaim test.csi.azure.comtthmz found but phase is Pending instead of Bound.
Sep  8 12:02:33.377: INFO: PersistentVolumeClaim test.csi.azure.comtthmz found and phase=Bound (2.055621501s)
STEP: Expanding non-expandable pvc
Sep  8 12:02:33.433: INFO: currentPvcSize {{5368709120 0} {<nil>} 5Gi BinarySI}, newSize {{6442450944 0} {<nil>}  BinarySI}
Sep  8 12:02:33.489: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:35.548: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:37.548: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:39.547: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:41.550: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:43.549: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:45.547: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:47.547: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:49.546: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:51.546: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:53.546: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:55.548: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:57.546: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:02:59.548: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:03:01.547: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:03:03.559: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
Sep  8 12:03:03.616: INFO: Error updating pvc test.csi.azure.comtthmz: persistentvolumeclaims "test.csi.azure.comtthmz" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
STEP: Deleting pvc
Sep  8 12:03:03.616: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comtthmz"
Sep  8 12:03:03.646: INFO: Waiting up to 5m0s for PersistentVolume pvc-718bd81c-8fab-4e76-a4a7-9741c2249e05 to get deleted
Sep  8 12:03:03.674: INFO: PersistentVolume pvc-718bd81c-8fab-4e76-a4a7-9741c2249e05 found and phase=Released (27.678218ms)
Sep  8 12:03:08.702: INFO: PersistentVolume pvc-718bd81c-8fab-4e76-a4a7-9741c2249e05 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":2,"skipped":175,"failed":0}

SSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:08.830: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 lines ...

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
External Storage [Driver: test.csi.azure.com]
test/e2e/storage/external/external.go:174
  [Testpattern: Pre-provisioned PV (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 144 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:50
    should concurrently access the single volume from pods on different node
    test/e2e/storage/testsuites/multivolume.go:451
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node","total":32,"completed":2,"skipped":484,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:11.365: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 94 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 20 lines ...
STEP: creating a claim
Sep  8 12:02:59.091: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:02:59.126: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comkw5p9] to have phase Bound
Sep  8 12:02:59.159: INFO: PersistentVolumeClaim test.csi.azure.comkw5p9 found but phase is Pending instead of Bound.
Sep  8 12:03:01.193: INFO: PersistentVolumeClaim test.csi.azure.comkw5p9 found and phase=Bound (2.066557524s)
STEP: Creating pod to format volume volume-prep-provisioning-6948
Sep  8 12:03:01.295: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-6948" in namespace "provisioning-6948" to be "Succeeded or Failed"
Sep  8 12:03:01.328: INFO: Pod "volume-prep-provisioning-6948": Phase="Pending", Reason="", readiness=false. Elapsed: 33.16429ms
Sep  8 12:03:03.363: INFO: Pod "volume-prep-provisioning-6948": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068031441s
Sep  8 12:03:05.397: INFO: Pod "volume-prep-provisioning-6948": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102013657s
Sep  8 12:03:07.431: INFO: Pod "volume-prep-provisioning-6948": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.135573821s
STEP: Saw pod success
Sep  8 12:03:07.431: INFO: Pod "volume-prep-provisioning-6948" satisfied condition "Succeeded or Failed"
Sep  8 12:03:07.431: INFO: Deleting pod "volume-prep-provisioning-6948" in namespace "provisioning-6948"
Sep  8 12:03:07.474: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-6948" to be fully deleted
STEP: Creating pod pod-subpath-test-dynamicpv-l8wf
STEP: Checking for subpath error in container status
Sep  8 12:03:11.609: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8wf" in namespace "provisioning-6948"
Sep  8 12:03:11.643: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l8wf" to be fully deleted
STEP: Deleting pod
Sep  8 12:03:13.714: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8wf" in namespace "provisioning-6948"
STEP: Deleting pvc
Sep  8 12:03:13.747: INFO: Deleting PersistentVolumeClaim "test.csi.azure.comkw5p9"
... 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":29,"completed":3,"skipped":986,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
Sep  8 12:03:19.022: INFO: Running AfterSuite actions on all nodes
Sep  8 12:03:19.022: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func19.2
Sep  8 12:03:19.022: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage.glob..func9.2
... skipping 26 lines ...
Sep  8 12:03:09.084: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:03:09.114: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comvc8zw] to have phase Bound
Sep  8 12:03:09.142: INFO: PersistentVolumeClaim test.csi.azure.comvc8zw found but phase is Pending instead of Bound.
Sep  8 12:03:11.171: INFO: PersistentVolumeClaim test.csi.azure.comvc8zw found and phase=Bound (2.05654726s)
STEP: Creating pod pod-subpath-test-dynamicpv-cxcs
STEP: Creating a pod to test subpath
Sep  8 12:03:11.257: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-cxcs" in namespace "provisioning-4077" to be "Succeeded or Failed"
Sep  8 12:03:11.287: INFO: Pod "pod-subpath-test-dynamicpv-cxcs": Phase="Pending", Reason="", readiness=false. Elapsed: 29.647161ms
Sep  8 12:03:13.315: INFO: Pod "pod-subpath-test-dynamicpv-cxcs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058347428s
Sep  8 12:03:15.345: INFO: Pod "pod-subpath-test-dynamicpv-cxcs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.087654836s
Sep  8 12:03:17.374: INFO: Pod "pod-subpath-test-dynamicpv-cxcs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.116689964s
STEP: Saw pod success
Sep  8 12:03:17.374: INFO: Pod "pod-subpath-test-dynamicpv-cxcs" satisfied condition "Succeeded or Failed"
Sep  8 12:03:17.402: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000001 pod pod-subpath-test-dynamicpv-cxcs container test-container-volume-dynamicpv-cxcs: <nil>
STEP: delete the pod
Sep  8 12:03:17.467: INFO: Waiting for pod pod-subpath-test-dynamicpv-cxcs to disappear
Sep  8 12:03:17.495: INFO: Pod pod-subpath-test-dynamicpv-cxcs no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-cxcs
Sep  8 12:03:17.495: INFO: Deleting pod "pod-subpath-test-dynamicpv-cxcs" in namespace "provisioning-4077"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support non-existent path
    test/e2e/storage/testsuites/subpath.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path","total":34,"completed":3,"skipped":230,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:22.768: 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 174 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 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":36,"completed":3,"skipped":549,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:23.897: INFO: Driver test.csi.azure.com doesn't support xfs -- skipping
... skipping 34 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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  8 12:03:23.475: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.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  8 12:03:23.819: INFO: Deleting PersistentVolumeClaim "pvc-47bbb"
STEP: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  test/e2e/framework/framework.go:188
Sep  8 12:03:23.885: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-5146" for this suite.

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

SSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:23.945: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 305 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":36,"completed":3,"skipped":520,"failed":0}

SSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:28.666: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 72 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":32,"completed":3,"skipped":641,"failed":0}
[BeforeEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:34.231: INFO: Driver "test.csi.azure.com" does not support volume type "CSIInlineVolume" - skipping
[AfterEach] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral
  test/e2e/framework/framework.go:188

... skipping 146 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":37,"completed":1,"skipped":7,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
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 105 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":32,"completed":4,"skipped":764,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:57.778: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 42 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 12:03:57.840: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.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  8 12:03:58.034: 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  8 12:03:58.035: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-8861" for this suite.


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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:03:59.094: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 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 (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 128 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":37,"completed":3,"skipped":347,"failed":0}

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

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:04:05.521: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 79 lines ...
Sep  8 12:03:49.602: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:03:49.632: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.coml8h8f] to have phase Bound
Sep  8 12:03:49.659: INFO: PersistentVolumeClaim test.csi.azure.coml8h8f found but phase is Pending instead of Bound.
Sep  8 12:03:51.689: INFO: PersistentVolumeClaim test.csi.azure.coml8h8f found and phase=Bound (2.057024245s)
STEP: Creating pod pod-subpath-test-dynamicpv-kx5p
STEP: Creating a pod to test subpath
Sep  8 12:03:51.775: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kx5p" in namespace "provisioning-9741" to be "Succeeded or Failed"
Sep  8 12:03:51.804: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Pending", Reason="", readiness=false. Elapsed: 29.385136ms
Sep  8 12:03:53.833: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058024639s
Sep  8 12:03:55.862: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086946716s
Sep  8 12:03:57.890: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.114723088s
Sep  8 12:03:59.918: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.143674568s
STEP: Saw pod success
Sep  8 12:03:59.919: INFO: Pod "pod-subpath-test-dynamicpv-kx5p" satisfied condition "Succeeded or Failed"
Sep  8 12:03:59.946: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-kx5p container test-container-subpath-dynamicpv-kx5p: <nil>
STEP: delete the pod
Sep  8 12:04:00.011: INFO: Waiting for pod pod-subpath-test-dynamicpv-kx5p to disappear
Sep  8 12:04:00.038: INFO: Pod pod-subpath-test-dynamicpv-kx5p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kx5p
Sep  8 12:04:00.038: INFO: Deleting pod "pod-subpath-test-dynamicpv-kx5p" in namespace "provisioning-9741"
STEP: Creating pod pod-subpath-test-dynamicpv-kx5p
STEP: Creating a pod to test subpath
Sep  8 12:04:00.096: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kx5p" in namespace "provisioning-9741" to be "Succeeded or Failed"
Sep  8 12:04:00.123: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Pending", Reason="", readiness=false. Elapsed: 26.932897ms
Sep  8 12:04:02.152: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056143947s
Sep  8 12:04:04.181: INFO: Pod "pod-subpath-test-dynamicpv-kx5p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.084716613s
STEP: Saw pod success
Sep  8 12:04:04.181: INFO: Pod "pod-subpath-test-dynamicpv-kx5p" satisfied condition "Succeeded or Failed"
Sep  8 12:04:04.208: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-kx5p container test-container-subpath-dynamicpv-kx5p: <nil>
STEP: delete the pod
Sep  8 12:04:04.282: INFO: Waiting for pod pod-subpath-test-dynamicpv-kx5p to disappear
Sep  8 12:04:04.310: INFO: Pod pod-subpath-test-dynamicpv-kx5p no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-kx5p
Sep  8 12:04:04.310: INFO: Deleting pod "pod-subpath-test-dynamicpv-kx5p" in namespace "provisioning-9741"
... 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":37,"completed":2,"skipped":37,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] volumeIO
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:04:09.600: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 37 lines ...
Sep  8 12:03:59.675: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:03:59.706: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comjxwfb] to have phase Bound
Sep  8 12:03:59.734: INFO: PersistentVolumeClaim test.csi.azure.comjxwfb found but phase is Pending instead of Bound.
Sep  8 12:04:01.764: INFO: PersistentVolumeClaim test.csi.azure.comjxwfb found and phase=Bound (2.057653299s)
STEP: Creating pod pod-subpath-test-dynamicpv-98m7
STEP: Creating a pod to test subpath
Sep  8 12:04:01.851: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-98m7" in namespace "provisioning-6022" to be "Succeeded or Failed"
Sep  8 12:04:01.879: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Pending", Reason="", readiness=false. Elapsed: 28.071893ms
Sep  8 12:04:03.908: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056543263s
Sep  8 12:04:05.937: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.085720638s
Sep  8 12:04:07.967: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.115537779s
Sep  8 12:04:09.998: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.146087088s
Sep  8 12:04:12.026: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.17447375s
Sep  8 12:04:14.055: INFO: Pod "pod-subpath-test-dynamicpv-98m7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.203772923s
STEP: Saw pod success
Sep  8 12:04:14.055: INFO: Pod "pod-subpath-test-dynamicpv-98m7" satisfied condition "Succeeded or Failed"
Sep  8 12:04:14.083: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-98m7 container test-container-subpath-dynamicpv-98m7: <nil>
STEP: delete the pod
Sep  8 12:04:14.154: INFO: Waiting for pod pod-subpath-test-dynamicpv-98m7 to disappear
Sep  8 12:04:14.182: INFO: Pod pod-subpath-test-dynamicpv-98m7 no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-98m7
Sep  8 12:04:14.182: INFO: Deleting pod "pod-subpath-test-dynamicpv-98m7" in namespace "provisioning-6022"
... 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":6,"skipped":915,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes 
  should allow exec of files on the volume
  test/e2e/storage/testsuites/volumes.go:198
... skipping 16 lines ...
Sep  8 12:04:01.446: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:04:01.476: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comrvn4w] to have phase Bound
Sep  8 12:04:01.504: INFO: PersistentVolumeClaim test.csi.azure.comrvn4w found but phase is Pending instead of Bound.
Sep  8 12:04:03.533: INFO: PersistentVolumeClaim test.csi.azure.comrvn4w found and phase=Bound (2.057516235s)
STEP: Creating pod exec-volume-test-dynamicpv-gssg
STEP: Creating a pod to test exec-volume-test
Sep  8 12:04:03.621: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-gssg" in namespace "volume-2364" to be "Succeeded or Failed"
Sep  8 12:04:03.648: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Pending", Reason="", readiness=false. Elapsed: 27.178768ms
Sep  8 12:04:05.676: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055440086s
Sep  8 12:04:07.706: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.084643403s
Sep  8 12:04:09.738: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116739743s
Sep  8 12:04:11.766: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.145046268s
Sep  8 12:04:13.795: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.174109347s
Sep  8 12:04:15.824: INFO: Pod "exec-volume-test-dynamicpv-gssg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.202640487s
STEP: Saw pod success
Sep  8 12:04:15.824: INFO: Pod "exec-volume-test-dynamicpv-gssg" satisfied condition "Succeeded or Failed"
Sep  8 12:04:15.851: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod exec-volume-test-dynamicpv-gssg container exec-container-dynamicpv-gssg: <nil>
STEP: delete the pod
Sep  8 12:04:15.916: INFO: Waiting for pod exec-volume-test-dynamicpv-gssg to disappear
Sep  8 12:04:15.944: INFO: Pod exec-volume-test-dynamicpv-gssg no longer exists
STEP: Deleting pod exec-volume-test-dynamicpv-gssg
Sep  8 12:04:15.944: INFO: Deleting pod "exec-volume-test-dynamicpv-gssg" in namespace "volume-2364"
... 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":37,"completed":4,"skipped":404,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:04:21.210: 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 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 215 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
  test/e2e/storage/framework/testsuite.go:50
    (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
    test/e2e/storage/testsuites/fsgroupchangepolicy.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents","total":32,"completed":5,"skipped":862,"failed":0}

SS
------------------------------
[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  8 12:04:21.600: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:04:21.630: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2tw4h] to have phase Bound
Sep  8 12:04:21.658: INFO: PersistentVolumeClaim test.csi.azure.com2tw4h found but phase is Pending instead of Bound.
Sep  8 12:04:23.687: INFO: PersistentVolumeClaim test.csi.azure.com2tw4h found and phase=Bound (2.056944135s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 12:04:23.802: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-zzm6w" in namespace "snapshotting-2982" to be "Succeeded or Failed"
Sep  8 12:04:23.829: INFO: Pod "pvc-snapshottable-tester-zzm6w": Phase="Pending", Reason="", readiness=false. Elapsed: 27.480786ms
Sep  8 12:04:25.858: INFO: Pod "pvc-snapshottable-tester-zzm6w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055951474s
Sep  8 12:04:27.886: INFO: Pod "pvc-snapshottable-tester-zzm6w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.084249897s
Sep  8 12:04:29.914: INFO: Pod "pvc-snapshottable-tester-zzm6w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.112678688s
STEP: Saw pod success
Sep  8 12:04:29.914: INFO: Pod "pvc-snapshottable-tester-zzm6w" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 12:04:29.942: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2tw4h] to have phase Bound
Sep  8 12:04:29.969: INFO: PersistentVolumeClaim test.csi.azure.com2tw4h found and phase=Bound (27.292753ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 12:04:30.054: INFO: Pod pvc-snapshottable-tester-zzm6w has the following logs: 
... skipping 101 lines ...
Sep  8 12:04:19.690: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:04:19.720: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comrjq4h] to have phase Bound
Sep  8 12:04:19.748: INFO: PersistentVolumeClaim test.csi.azure.comrjq4h found but phase is Pending instead of Bound.
Sep  8 12:04:21.776: INFO: PersistentVolumeClaim test.csi.azure.comrjq4h found and phase=Bound (2.056515915s)
STEP: Creating pod pod-subpath-test-dynamicpv-gbgl
STEP: Creating a pod to test multi_subpath
Sep  8 12:04:21.863: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-gbgl" in namespace "provisioning-3228" to be "Succeeded or Failed"
Sep  8 12:04:21.891: INFO: Pod "pod-subpath-test-dynamicpv-gbgl": Phase="Pending", Reason="", readiness=false. Elapsed: 28.209006ms
Sep  8 12:04:23.921: INFO: Pod "pod-subpath-test-dynamicpv-gbgl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.05801628s
Sep  8 12:04:25.950: INFO: Pod "pod-subpath-test-dynamicpv-gbgl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086962582s
Sep  8 12:04:27.988: INFO: Pod "pod-subpath-test-dynamicpv-gbgl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124696594s
Sep  8 12:04:30.016: INFO: Pod "pod-subpath-test-dynamicpv-gbgl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.153239882s
STEP: Saw pod success
Sep  8 12:04:30.016: INFO: Pod "pod-subpath-test-dynamicpv-gbgl" satisfied condition "Succeeded or Failed"
Sep  8 12:04:30.044: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-gbgl container test-container-subpath-dynamicpv-gbgl: <nil>
STEP: delete the pod
Sep  8 12:04:30.111: INFO: Waiting for pod pod-subpath-test-dynamicpv-gbgl to disappear
Sep  8 12:04:30.138: INFO: Pod pod-subpath-test-dynamicpv-gbgl no longer exists
STEP: Deleting pod
Sep  8 12:04:30.139: INFO: Deleting pod "pod-subpath-test-dynamicpv-gbgl" in namespace "provisioning-3228"
... skipping 16 lines ...
  test/e2e/storage/framework/testsuite.go:50
    should support creating multiple subpath from same volumes [Slow]
    test/e2e/storage/testsuites/subpath.go:296
------------------------------
S
------------------------------
{"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":7,"skipped":944,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:04:35.441: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 44 lines ...
Sep  8 12:04:30.523: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:04:30.552: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comdlt8g] to have phase Bound
Sep  8 12:04:30.580: INFO: PersistentVolumeClaim test.csi.azure.comdlt8g found but phase is Pending instead of Bound.
Sep  8 12:04:32.609: INFO: PersistentVolumeClaim test.csi.azure.comdlt8g found and phase=Bound (2.056511s)
STEP: [init] starting a pod to use the claim
STEP: [init] check pod success
Sep  8 12:04:32.737: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-w2dc7" in namespace "snapshotting-9512" to be "Succeeded or Failed"
Sep  8 12:04:32.765: INFO: Pod "pvc-snapshottable-tester-w2dc7": Phase="Pending", Reason="", readiness=false. Elapsed: 27.976672ms
Sep  8 12:04:34.794: INFO: Pod "pvc-snapshottable-tester-w2dc7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056878121s
Sep  8 12:04:36.823: INFO: Pod "pvc-snapshottable-tester-w2dc7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.085793976s
STEP: Saw pod success
Sep  8 12:04:36.823: INFO: Pod "pvc-snapshottable-tester-w2dc7" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
Sep  8 12:04:36.851: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comdlt8g] to have phase Bound
Sep  8 12:04:36.878: INFO: PersistentVolumeClaim test.csi.azure.comdlt8g found and phase=Bound (27.430327ms)
STEP: [init] checking the PV
STEP: [init] deleting the pod
Sep  8 12:04:36.967: INFO: Pod pvc-snapshottable-tester-w2dc7 has the following logs: 
... skipping 257 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":36,"completed":5,"skipped":806,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath 
  should support existing directory
  test/e2e/storage/testsuites/subpath.go:207
... skipping 16 lines ...
Sep  8 12:04:45.198: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:04:45.230: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com9frh4] to have phase Bound
Sep  8 12:04:45.258: INFO: PersistentVolumeClaim test.csi.azure.com9frh4 found but phase is Pending instead of Bound.
Sep  8 12:04:47.287: INFO: PersistentVolumeClaim test.csi.azure.com9frh4 found and phase=Bound (2.056866931s)
STEP: Creating pod pod-subpath-test-dynamicpv-mnkw
STEP: Creating a pod to test subpath
Sep  8 12:04:47.372: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-mnkw" in namespace "provisioning-6241" to be "Succeeded or Failed"
Sep  8 12:04:47.404: INFO: Pod "pod-subpath-test-dynamicpv-mnkw": Phase="Pending", Reason="", readiness=false. Elapsed: 31.750678ms
Sep  8 12:04:49.433: INFO: Pod "pod-subpath-test-dynamicpv-mnkw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061087787s
Sep  8 12:04:51.462: INFO: Pod "pod-subpath-test-dynamicpv-mnkw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089936398s
Sep  8 12:04:53.490: INFO: Pod "pod-subpath-test-dynamicpv-mnkw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.118328329s
STEP: Saw pod success
Sep  8 12:04:53.490: INFO: Pod "pod-subpath-test-dynamicpv-mnkw" satisfied condition "Succeeded or Failed"
Sep  8 12:04:53.518: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-mnkw container test-container-volume-dynamicpv-mnkw: <nil>
STEP: delete the pod
Sep  8 12:04:53.587: INFO: Waiting for pod pod-subpath-test-dynamicpv-mnkw to disappear
Sep  8 12:04:53.614: INFO: Pod pod-subpath-test-dynamicpv-mnkw no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-mnkw
Sep  8 12:04:53.614: INFO: Deleting pod "pod-subpath-test-dynamicpv-mnkw" in namespace "provisioning-6241"
... 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":36,"completed":6,"skipped":878,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:04:58.950: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 3 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 32 lines ...
[It] should check snapshot fields, check restore correctly works, check deletion (ephemeral)
  test/e2e/storage/testsuites/snapshottable.go:177
Sep  8 12:04:59.184: INFO: Creating resource for dynamic PV
Sep  8 12:04:59.184: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass snapshotting-6753-e2e-scrv8b5
STEP: [init] starting a pod to use the claim
Sep  8 12:04:59.244: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-7jhkt" in namespace "snapshotting-6753" to be "Succeeded or Failed"
Sep  8 12:04:59.271: INFO: Pod "pvc-snapshottable-tester-7jhkt": Phase="Pending", Reason="", readiness=false. Elapsed: 27.833885ms
Sep  8 12:05:01.301: INFO: Pod "pvc-snapshottable-tester-7jhkt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057240362s
Sep  8 12:05:03.330: INFO: Pod "pvc-snapshottable-tester-7jhkt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086483098s
Sep  8 12:05:05.362: INFO: Pod "pvc-snapshottable-tester-7jhkt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118626599s
Sep  8 12:05:07.393: INFO: Pod "pvc-snapshottable-tester-7jhkt": Phase="Running", Reason="", readiness=false. Elapsed: 8.149194239s
Sep  8 12:05:09.422: INFO: Pod "pvc-snapshottable-tester-7jhkt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.177998883s
STEP: Saw pod success
Sep  8 12:05:09.422: INFO: Pod "pvc-snapshottable-tester-7jhkt" satisfied condition "Succeeded or Failed"
STEP: [init] checking the claim
STEP: creating a SnapshotClass
Sep  8 12:05:09.450: INFO: Driver "test.csi.azure.com" does not support snapshotting - skipping
Sep  8 12:05:09.451: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-snapshottable-tester-7jhkt-my-volume] to have phase Bound
Sep  8 12:05:09.480: INFO: PersistentVolumeClaim pvc-snapshottable-tester-7jhkt-my-volume found and phase=Bound (29.39885ms)
STEP: [init] checking the PV
... skipping 121 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":36,"completed":4,"skipped":569,"failed":0}

SSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:05:15.928: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping
... skipping 24 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext3)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:05:16.771: INFO: Driver test.csi.azure.com doesn't support ext3 -- skipping
... skipping 42 lines ...
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 12:05:16.893: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.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  8 12:05:17.084: 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  8 12:05:17.084: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "volumemode-7609" for this suite.


S [SKIPPING] [0.247 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 52 lines ...


External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral 
  should create read/write inline ephemeral volume
  test/e2e/storage/testsuites/ephemeral.go:196

{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":37,"completed":3,"skipped":146,"failed":0}
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/framework/framework.go:187
STEP: Creating a kubernetes client
Sep  8 12:04:43.973: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.json
... skipping 31 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should create read/write inline ephemeral volume
    test/e2e/storage/testsuites/ephemeral.go:196
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume","total":37,"completed":4,"skipped":146,"failed":0}

SSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:05:25.219: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - 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: 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 109 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":36,"completed":5,"skipped":667,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:05:36.877: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 149 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":37,"completed":5,"skipped":333,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:06:13.585: INFO: Driver "test.csi.azure.com" does not provide raw block - skipping
... skipping 139 lines ...

    test/e2e/storage/framework/testsuite.go:121
------------------------------
SSSSSSSSSS
------------------------------
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  8 12:06:13.738: INFO: >>> kubeConfig: /root/tmp4179949029/kubeconfig/kubeconfig.eastus.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  8 12:06:13.931: INFO: Creating resource for dynamic PV
Sep  8 12:06:13.931: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} 
STEP: creating a StorageClass provisioning-8210-e2e-scqn85b
STEP: creating a claim
Sep  8 12:06:13.961: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:06:13.995: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.coml5lrb] to have phase Bound
Sep  8 12:06:14.022: INFO: PersistentVolumeClaim test.csi.azure.coml5lrb found but phase is Pending instead of Bound.
Sep  8 12:06:16.051: INFO: PersistentVolumeClaim test.csi.azure.coml5lrb found and phase=Bound (2.056296576s)
STEP: Creating pod pod-subpath-test-dynamicpv-2wvc
STEP: Checking for subpath error in container status
Sep  8 12:06:20.196: INFO: Deleting pod "pod-subpath-test-dynamicpv-2wvc" in namespace "provisioning-8210"
Sep  8 12:06:20.226: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-2wvc" to be fully deleted
STEP: Deleting pod
Sep  8 12:06:22.282: INFO: Deleting pod "pod-subpath-test-dynamicpv-2wvc" in namespace "provisioning-8210"
STEP: Deleting pvc
Sep  8 12:06:22.310: INFO: Deleting PersistentVolumeClaim "test.csi.azure.coml5lrb"
... skipping 9 lines ...

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

SSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:06:27.534: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 66 lines ...

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

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:06:46.260: INFO: Driver test.csi.azure.com doesn't support Block -- skipping
... skipping 24 lines ...

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

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

    test/e2e/storage/external/external.go:262
------------------------------
... skipping 191 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral
  test/e2e/storage/framework/testsuite.go:50
    should support two pods which have the same volume definition
    test/e2e/storage/testsuites/ephemeral.go:216
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition","total":36,"completed":6,"skipped":912,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow]
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:06:50.971: INFO: Driver test.csi.azure.com doesn't support ext4 -- skipping
... skipping 96 lines ...
Sep  8 12:06:51.578: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Sep  8 12:06:51.611: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comszk8n] to have phase Bound
Sep  8 12:06:51.641: INFO: PersistentVolumeClaim test.csi.azure.comszk8n found but phase is Pending instead of Bound.
Sep  8 12:06:53.673: INFO: PersistentVolumeClaim test.csi.azure.comszk8n found and phase=Bound (2.062227748s)
STEP: Creating pod pod-subpath-test-dynamicpv-6w6n
STEP: Creating a pod to test subpath
Sep  8 12:06:53.780: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-6w6n" in namespace "provisioning-6161" to be "Succeeded or Failed"
Sep  8 12:06:53.816: INFO: Pod "pod-subpath-test-dynamicpv-6w6n": Phase="Pending", Reason="", readiness=false. Elapsed: 36.406021ms
Sep  8 12:06:55.850: INFO: Pod "pod-subpath-test-dynamicpv-6w6n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070194972s
Sep  8 12:06:57.882: INFO: Pod "pod-subpath-test-dynamicpv-6w6n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102533388s
Sep  8 12:06:59.918: INFO: Pod "pod-subpath-test-dynamicpv-6w6n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.137961555s
STEP: Saw pod success
Sep  8 12:06:59.918: INFO: Pod "pod-subpath-test-dynamicpv-6w6n" satisfied condition "Succeeded or Failed"
Sep  8 12:06:59.950: INFO: Trying to get logs from node k8s-agentpool1-20406825-vmss000000 pod pod-subpath-test-dynamicpv-6w6n container test-container-subpath-dynamicpv-6w6n: <nil>
STEP: delete the pod
Sep  8 12:07:00.027: INFO: Waiting for pod pod-subpath-test-dynamicpv-6w6n to disappear
Sep  8 12:07:00.059: INFO: Pod pod-subpath-test-dynamicpv-6w6n no longer exists
STEP: Deleting pod pod-subpath-test-dynamicpv-6w6n
Sep  8 12:07:00.059: INFO: Deleting pod "pod-subpath-test-dynamicpv-6w6n" in namespace "provisioning-6161"
... skipping 16 lines ...
test/e2e/storage/external/external.go:174
  [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/framework/testsuite.go:50
    should support readOnly directory specified in the volumeMount
    test/e2e/storage/testsuites/subpath.go:367
------------------------------
{"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":36,"completed":7,"skipped":949,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Inline-volume (ext4)] volumes
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:07:05.407: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping
... skipping 144 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":37,"completed":8,"skipped":944,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
  test/e2e/storage/framework/testsuite.go:51
Sep  8 12:07:15.781: INFO: Driver test.csi.azure.com doesn't support ntfs -- skipping
... skipping 83 lines ...
Sep  8 12:07:16.107: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func4.2
Sep  8 12:07:16.107: INFO: Running Cleanup Action: k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.3
Sep  8 12:07:16.108: INFO: Running AfterSuite actions on node 1


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

Ginkgo ran 1 suite in 6m20.690067928s
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:
I0908 12:00:52.547797       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a e2e-test
I0908 12:00:52.548078       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:52.569838       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
I0908 12:00:52.569855       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:52.569861       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 12:00:52.569882       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 12:00:52.570441       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 12:00:52.570468       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 12:00:52.570496       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:
I0908 12:00:52.143772       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a e2e-test
I0908 12:00:52.145660       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:52.167984       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
I0908 12:00:52.168044       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:52.168082       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 12:00:52.168128       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 12:00:52.168768       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 12:00:52.168807       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 12:00:52.168838       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 484 lines ...
I0908 12:03:23.575208       1 azure_storage.go:66] share pvcn-420c0afb-13ed-481f-abec-a0e3efd8bd6c deleted
I0908 12:03:23.575258       1 controllerserver.go:603] azure file(pvcn-420c0afb-13ed-481f-abec-a0e3efd8bd6c) under rg(kubetest-p7cotaxc) account(f7f8603a502fa4a7db09699) volume(kubetest-p7cotaxc#f7f8603a502fa4a7db09699#pvcn-420c0afb-13ed-481f-abec-a0e3efd8bd6c###fsgroupchangepolicy-587) is deleted successfully
I0908 12:03:23.575332       1 azure_metrics.go:115] "Observed Request Latency" latency_seconds=0.11977681 request="azurefile_csi_driver_controller_delete_volume" resource_group="kubetest-p7cotaxc" subscription_id="0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e" source="test.csi.azure.com" volumeid="kubetest-p7cotaxc#f7f8603a502fa4a7db09699#pvcn-420c0afb-13ed-481f-abec-a0e3efd8bd6c###fsgroupchangepolicy-587" result_code="succeeded"
I0908 12:03:23.575353       1 utils.go:83] GRPC response: {}
I0908 12:03:23.721062       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0908 12:03:23.721192       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-99239cb7-73e7-4f3b-8839-08011d7c1315","parameters":{"csi.storage.k8s.io/pv/name":"pvc-99239cb7-73e7-4f3b-8839-08011d7c1315","csi.storage.k8s.io/pvc/name":"pvc-47bbb","csi.storage.k8s.io/pvc/namespace":"volumemode-5146","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0908 12:03:23.721384       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0908 12:03:23.844848       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0908 12:03:23.845033       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-99239cb7-73e7-4f3b-8839-08011d7c1315","parameters":{"csi.storage.k8s.io/pv/name":"pvc-99239cb7-73e7-4f3b-8839-08011d7c1315","csi.storage.k8s.io/pvc/name":"pvc-47bbb","csi.storage.k8s.io/pvc/namespace":"volumemode-5146","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Block":{}},"access_mode":{"mode":7}}]}
E0908 12:03:23.845369       1 utils.go:81] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume Volume capabilities not valid: driver does not support block volumes
I0908 12:03:24.456746       1 utils.go:76] GRPC call: /csi.v1.Controller/CreateVolume
I0908 12:03:24.456771       1 utils.go:77] GRPC request: {"capacity_range":{"required_bytes":5368709120},"name":"pvc-c77d403e-bb3c-4234-8385-bbf623e36b25","parameters":{"csi.storage.k8s.io/pv/name":"pvc-c77d403e-bb3c-4234-8385-bbf623e36b25","csi.storage.k8s.io/pvc/name":"test.csi.azure.comktzkg","csi.storage.k8s.io/pvc/namespace":"multivolume-8268","protocol":"nfs","skuName":"Premium_LRS"},"volume_capabilities":[{"AccessType":{"Mount":{}},"access_mode":{"mode":7}}]}
I0908 12:03:24.456967       1 controllerserver.go:297] set vnetResourceID(/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-p7cotaxc/providers/Microsoft.Network/virtualNetworks/k8s-vnet-20406825/subnets/k8s-subnet) for NFS protocol
I0908 12:03:24.456979       1 azure.go:180] updateSubnetServiceEndpoints on vnetName: k8s-vnet-20406825, subnetName: k8s-subnet, location: eastus
I0908 12:03:24.542904       1 azure.go:209] serviceEndpoint(Microsoft.Storage) is already in subnet(k8s-subnet)
I0908 12:03:24.601998       1 controllerserver.go:452] begin to create file share(pvcn-c77d403e-bb3c-4234-8385-bbf623e36b25) on account(f7f8603a502fa4a7db09699) type(Premium_LRS) rg(kubetest-p7cotaxc) location() size(100) protocol(NFS)
... skipping 453 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 12:00:48.858817       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a e2e-test
I0908 12:00:48.861686       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:48.884616       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
I0908 12:00:48.884639       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:48.884645       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 12:00:48.884672       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 12:00:48.885409       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 12:00:48.885456       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 12:00:48.885489       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 1578 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 12:00:49.110556       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a e2e-test
I0908 12:00:49.110855       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:49.132259       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
I0908 12:00:49.132274       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:49.132279       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 12:00:49.132299       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 12:00:49.132838       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 12:00:49.132873       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 12:00:49.132895       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 668 lines ...
Go Version: go1.19
Platform: linux/amd64

Streaming logs below:
I0908 12:00:46.136222       1 azurefile.go:290] driver userAgent: test.csi.azure.com/e2e-9388c85a9851ac68a89b3e978ebff88c92a23c0a e2e-test
I0908 12:00:46.136587       1 azure.go:71] reading cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:46.162858       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
I0908 12:00:46.163359       1 azure.go:83] could not read cloud config from secret kube-system/azure-cloud-provider
I0908 12:00:46.163435       1 azure.go:93] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
I0908 12:00:46.163507       1 azure.go:101] read cloud config from file: /etc/kubernetes/azure.json successfully
I0908 12:00:46.164211       1 azure_auth.go:245] Using AzurePublicCloud environment
I0908 12:00:46.164276       1 azure_auth.go:130] azure: using client_id+client_secret to retrieve access token
I0908 12:00:46.164314       1 azure.go:774] Azure cloudprovider using try backoff: retries=6, exponent=1.500000, duration=5, jitter=1.000000
... skipping 269 lines ...