kubernetes-sigs/azuredisk-csi-driver PR #1595 pull-azuredisk-csi-driver-external-e2e-single-az-mainv2 #1593392132607971328
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] fix: add nodeDiskAvailabilityMap |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 43m49s |
| Revision | cc3e1c75ff170829736ae811b133078f32fd3554 |
| Refs |
1595 |
... skipping 236 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11156 100 11156 0 0 157k 0 --:--:-- --:--:-- --:--:-- 157k Downloading https://get.helm.sh/helm-v3.10.2-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/azuredisk-csi:latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781 || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781 not found: manifest unknown: manifest tagged by "latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=d6e639efe64c9b1adf40b1526b8bd59ba11f1781 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-11-18T00:01:39Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.exe ./pkg/azurediskplugin 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 701 lines ... } } ] } make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781 not found: manifest unknown: manifest tagged by "latest-v2-d6e639efe64c9b1adf40b1526b8bd59ba11f1781" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx rm container-builder || true container-builder removed docker buildx create --use --name=container-builder container-builder # enable qemu for arm64 build ... skipping 1045 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 occurs 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 occurs 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 359 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status Required properties: detail: description: Status summarizes the current attachment state of the volume attachment Nil Status indicates that the volume has not yet been attached to the node properties: ... skipping 7 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 90 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 13 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 169 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: detail: description: Current status detail of the AzVolume Nil detail indicates that the volume has not been created properties: accessible_topology: ... skipping 28 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 154 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 34 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 1063 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' - '-feature-gates=RecoverVolumeExpansionFailure=true' - "-timeout=240s" env: - name: ADDRESS value: /csi/csi.sock volumeMounts: ... skipping 324 lines ... [36m[1mS [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Inline-volume (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m [36m[1mshould fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach][0m [90mtest/e2e/storage/testsuites/subpath.go:258[0m [36mDriver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping[0m test/e2e/storage/external/external.go:262 [90m------------------------------[0m ... skipping 118 lines ... Nov 18 00:14:31.433: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comkk2nm] to have phase Bound Nov 18 00:14:31.543: INFO: PersistentVolumeClaim test.csi.azure.comkk2nm found but phase is Pending instead of Bound. Nov 18 00:14:33.651: INFO: PersistentVolumeClaim test.csi.azure.comkk2nm found but phase is Pending instead of Bound. Nov 18 00:14:35.761: INFO: PersistentVolumeClaim test.csi.azure.comkk2nm found and phase=Bound (4.328206182s) [1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-g722 [1mSTEP[0m: Creating a pod to test subpath Nov 18 00:14:36.087: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-g722" in namespace "provisioning-9685" to be "Succeeded or Failed" Nov 18 00:14:36.200: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 112.748746ms Nov 18 00:14:38.309: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222034887s Nov 18 00:14:40.417: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 4.329890905s Nov 18 00:14:42.526: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 6.439191727s Nov 18 00:14:44.635: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 8.548079703s Nov 18 00:14:46.745: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 10.657916677s ... skipping 14 lines ... Nov 18 00:15:18.406: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 42.318729645s Nov 18 00:15:20.516: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 44.428854394s Nov 18 00:15:22.625: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 46.538054066s Nov 18 00:15:24.734: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Pending", Reason="", readiness=false. Elapsed: 48.647220408s Nov 18 00:15:26.843: INFO: Pod "pod-subpath-test-dynamicpv-g722": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.75606699s [1mSTEP[0m: Saw pod success Nov 18 00:15:26.843: INFO: Pod "pod-subpath-test-dynamicpv-g722" satisfied condition "Succeeded or Failed" Nov 18 00:15:26.951: INFO: Trying to get logs from node k8s-agentpool1-81963798-vmss000001 pod pod-subpath-test-dynamicpv-g722 container test-container-subpath-dynamicpv-g722: <nil> [1mSTEP[0m: delete the pod Nov 18 00:15:27.206: INFO: Waiting for pod pod-subpath-test-dynamicpv-g722 to disappear Nov 18 00:15:27.314: INFO: Pod pod-subpath-test-dynamicpv-g722 no longer exists [1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-g722 Nov 18 00:15:27.314: INFO: Deleting pod "pod-subpath-test-dynamicpv-g722" in namespace "provisioning-9685" ... skipping 23 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m should support readOnly directory specified in the volumeMount [90mtest/e2e/storage/testsuites/subpath.go:367[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount","total":40,"completed":1,"skipped":44,"failed":0} [36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Inline-volume (default fs)] volumeIO test/e2e/storage/framework/testsuite.go:51 Nov 18 00:16:09.180: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping ... skipping 24 lines ... [36m[1mS [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Inline-volume (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m [36m[1mshould fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach][0m [90mtest/e2e/storage/testsuites/subpath.go:280[0m [36mDriver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping[0m test/e2e/storage/external/external.go:262 [90m------------------------------[0m ... skipping 8 lines ... [36m[1mS [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Pre-provisioned PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m [36m[1mshould fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach][0m [90mtest/e2e/storage/testsuites/subpath.go:242[0m [36mDriver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping[0m test/e2e/storage/external/external.go:262 [90m------------------------------[0m ... skipping 156 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should concurrently access the single volume from pods on the same node [90mtest/e2e/storage/testsuites/multivolume.go:298[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on the same node","total":34,"completed":1,"skipped":1,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Dynamic PV (block volmode)] multiVolume [Slow][0m [1mshould access to two volumes with different volume mode and retain data across pod recreation on the same node[0m [37mtest/e2e/storage/testsuites/multivolume.go:209[0m ... skipping 191 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should access to two volumes with different volume mode and retain data across pod recreation on the same node [90mtest/e2e/storage/testsuites/multivolume.go:209[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node","total":35,"completed":1,"skipped":35,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Dynamic PV (default fs)] subPath[0m [1mshould fail if subpath directory is outside the volume [Slow][LinuxOnly][0m [37mtest/e2e/storage/testsuites/subpath.go:242[0m [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 ... [1mSTEP[0m: Building a namespace api object, basename provisioning W1118 00:14:30.739580 40084 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+ Nov 18 00:14:30.739: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled Nov 18 00:14:30.852: INFO: No PSP annotation exists on dry run pod; assuming PodSecurityPolicy is disabled [1mSTEP[0m: Waiting for a default service account to be provisioned in namespace [1mSTEP[0m: 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 Nov 18 00:14:31.285: INFO: Creating resource for dynamic PV Nov 18 00:14:31.285: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} [1mSTEP[0m: creating a StorageClass provisioning-2173-e2e-scmdggp [1mSTEP[0m: creating a claim Nov 18 00:14:31.395: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil Nov 18 00:14:31.513: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com2bbsr] to have phase Bound Nov 18 00:14:31.624: INFO: PersistentVolumeClaim test.csi.azure.com2bbsr found but phase is Pending instead of Bound. Nov 18 00:14:33.735: INFO: PersistentVolumeClaim test.csi.azure.com2bbsr found but phase is Pending instead of Bound. Nov 18 00:14:35.845: INFO: PersistentVolumeClaim test.csi.azure.com2bbsr found and phase=Bound (4.331874525s) [1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-dcsf [1mSTEP[0m: Checking for subpath error in container status Nov 18 00:15:22.392: INFO: Deleting pod "pod-subpath-test-dynamicpv-dcsf" in namespace "provisioning-2173" Nov 18 00:15:22.503: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-dcsf" to be fully deleted [1mSTEP[0m: Deleting pod Nov 18 00:15:24.723: INFO: Deleting pod "pod-subpath-test-dynamicpv-dcsf" in namespace "provisioning-2173" [1mSTEP[0m: Deleting pvc Nov 18 00:15:24.832: INFO: Deleting PersistentVolumeClaim "test.csi.azure.com2bbsr" ... skipping 21 lines ... [32m• [SLOW TEST:121.786 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m should fail if subpath directory is outside the volume [Slow][LinuxOnly] [90mtest/e2e/storage/testsuites/subpath.go:242[0m [90m------------------------------[0m {"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":16,"completed":1,"skipped":145,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Inline-volume (ext3)] volumes test/e2e/storage/framework/testsuite.go:51 Nov 18 00:16:32.314: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping ... skipping 42 lines ... test/e2e/framework/framework.go:187 [1mSTEP[0m: Creating a kubernetes client Nov 18 00:16:32.450: INFO: >>> kubeConfig: /root/tmp3591491245/kubeconfig/kubeconfig.westeurope.json [1mSTEP[0m: Building a namespace api object, basename topology [1mSTEP[0m: Waiting for a default service account to be provisioned in namespace [1mSTEP[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should fail to schedule a pod which has topologies that conflict with AllowedTopologies test/e2e/storage/testsuites/topology.go:194 Nov 18 00:16:33.217: INFO: Driver didn't provide topology keys -- skipping [AfterEach] [Testpattern: Dynamic PV (immediate binding)] topology test/e2e/framework/framework.go:188 Nov 18 00:16:33.218: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [1mSTEP[0m: Destroying namespace "topology-8632" for this suite. [36m[1mS [SKIPPING] [1.096 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (immediate binding)] topology [90mtest/e2e/storage/framework/testsuite.go:50[0m [36m[1mshould fail to schedule a pod which has topologies that conflict with AllowedTopologies [Measurement][0m [90mtest/e2e/storage/testsuites/topology.go:194[0m [36mDriver didn't provide topology keys -- skipping[0m test/e2e/storage/testsuites/topology.go:126 [90m------------------------------[0m ... skipping 179 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS] [90mtest/e2e/storage/testsuites/multivolume.go:323[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]","total":39,"completed":1,"skipped":5,"failed":0} [BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath test/e2e/storage/framework/testsuite.go:51 Nov 18 00:17:31.835: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping [AfterEach] [Testpattern: Pre-provisioned PV (default fs)] subPath test/e2e/framework/framework.go:188 ... skipping 76 lines ... Nov 18 00:14:31.321: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comkv72f] to have phase Bound Nov 18 00:14:31.438: INFO: PersistentVolumeClaim test.csi.azure.comkv72f found but phase is Pending instead of Bound. Nov 18 00:14:33.548: INFO: PersistentVolumeClaim test.csi.azure.comkv72f found but phase is Pending instead of Bound. Nov 18 00:14:35.657: INFO: PersistentVolumeClaim test.csi.azure.comkv72f found and phase=Bound (4.335797952s) [1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-vm9t [1mSTEP[0m: Creating a pod to test subpath Nov 18 00:14:35.989: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-vm9t" in namespace "provisioning-3435" to be "Succeeded or Failed" Nov 18 00:14:36.100: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 110.888029ms Nov 18 00:14:38.210: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220951689s Nov 18 00:14:40.319: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330346591s Nov 18 00:14:42.429: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.440324206s Nov 18 00:14:44.539: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.550245336s Nov 18 00:14:46.649: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.660101786s ... skipping 11 lines ... Nov 18 00:15:11.970: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 35.981573818s Nov 18 00:15:14.080: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 38.091318361s Nov 18 00:15:16.190: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 40.201083285s Nov 18 00:15:18.299: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Pending", Reason="", readiness=false. Elapsed: 42.309938379s Nov 18 00:15:20.408: INFO: Pod "pod-subpath-test-dynamicpv-vm9t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.418915875s [1mSTEP[0m: Saw pod success Nov 18 00:15:20.408: INFO: Pod "pod-subpath-test-dynamicpv-vm9t" satisfied condition "Succeeded or Failed" Nov 18 00:15:20.516: INFO: Trying to get logs from node k8s-agentpool1-81963798-vmss000000 pod pod-subpath-test-dynamicpv-vm9t container test-container-subpath-dynamicpv-vm9t: <nil> [1mSTEP[0m: delete the pod Nov 18 00:15:20.769: INFO: Waiting for pod pod-subpath-test-dynamicpv-vm9t to disappear Nov 18 00:15:20.877: INFO: Pod pod-subpath-test-dynamicpv-vm9t no longer exists [1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-vm9t Nov 18 00:15:20.877: INFO: Deleting pod "pod-subpath-test-dynamicpv-vm9t" in namespace "provisioning-3435" ... skipping 41 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m should support readOnly file specified in the volumeMount [LinuxOnly] [90mtest/e2e/storage/testsuites/subpath.go:382[0m [90m------------------------------[0m {"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":32,"completed":1,"skipped":220,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning test/e2e/storage/framework/testsuite.go:51 Nov 18 00:17:34.772: INFO: Distro debian doesn't support ntfs -- skipping ... skipping 126 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (filesystem volmode)] volumeMode [90mtest/e2e/storage/framework/testsuite.go:50[0m should not mount / map unused volumes in a pod [LinuxOnly] [90mtest/e2e/storage/testsuites/volumemode.go:354[0m [90m------------------------------[0m {"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":39,"completed":2,"skipped":83,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Dynamic PV (ext4)] volumes[0m [1mshould store data[0m [37mtest/e2e/storage/testsuites/volumes.go:161[0m ... skipping 116 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (ext4)] volumes [90mtest/e2e/storage/framework/testsuite.go:50[0m should store data [90mtest/e2e/storage/testsuites/volumes.go:161[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] volumes should store data","total":34,"completed":2,"skipped":12,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] test/e2e/storage/framework/testsuite.go:51 Nov 18 00:18:59.537: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 185 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy [90mtest/e2e/storage/framework/testsuite.go:50[0m (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents [90mtest/e2e/storage/testsuites/fsgroupchangepolicy.go:216[0m [90m------------------------------[0m {"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":34,"completed":1,"skipped":7,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource][0m [0mvolume snapshot controller[0m [90m[0m [1mshould check snapshot fields, check restore correctly works, check deletion (ephemeral)[0m [37mtest/e2e/storage/testsuites/snapshottable.go:177[0m ... skipping 10 lines ... [It] should check snapshot fields, check restore correctly works, check deletion (ephemeral) test/e2e/storage/testsuites/snapshottable.go:177 Nov 18 00:16:34.399: INFO: Creating resource for dynamic PV Nov 18 00:16:34.399: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} [1mSTEP[0m: creating a StorageClass snapshotting-1207-e2e-sc96x5f [1mSTEP[0m: [init] starting a pod to use the claim Nov 18 00:16:34.621: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-457g6" in namespace "snapshotting-1207" to be "Succeeded or Failed" Nov 18 00:16:34.730: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 108.795217ms Nov 18 00:16:36.840: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219070797s Nov 18 00:16:38.952: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330232114s Nov 18 00:16:41.066: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.44450877s Nov 18 00:16:43.177: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.55566321s Nov 18 00:16:45.287: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.665527511s Nov 18 00:16:47.397: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.776145385s Nov 18 00:16:49.508: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.886664205s Nov 18 00:16:51.618: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.997028154s Nov 18 00:16:53.728: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Pending", Reason="", readiness=false. Elapsed: 19.107001744s Nov 18 00:16:55.839: INFO: Pod "pvc-snapshottable-tester-457g6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.217551921s [1mSTEP[0m: Saw pod success Nov 18 00:16:55.839: INFO: Pod "pvc-snapshottable-tester-457g6" satisfied condition "Succeeded or Failed" [1mSTEP[0m: [init] checking the claim [1mSTEP[0m: creating a SnapshotClass [1mSTEP[0m: creating a dynamic VolumeSnapshot Nov 18 00:16:56.295: INFO: Waiting up to 5m0s for VolumeSnapshot snapshot-997xx to become ready Nov 18 00:16:56.404: INFO: VolumeSnapshot snapshot-997xx found but is not ready. Nov 18 00:16:58.515: INFO: VolumeSnapshot snapshot-997xx found but is not ready. ... skipping 40 lines ... Nov 18 00:18:40.481: INFO: volumesnapshotcontents snapcontent-57fbd2e0-0215-4019-b1fc-0df6ddb096c0 has been found and is not deleted Nov 18 00:18:41.590: INFO: volumesnapshotcontents snapcontent-57fbd2e0-0215-4019-b1fc-0df6ddb096c0 has been found and is not deleted Nov 18 00:18:42.700: INFO: volumesnapshotcontents snapcontent-57fbd2e0-0215-4019-b1fc-0df6ddb096c0 has been found and is not deleted Nov 18 00:18:43.815: INFO: volumesnapshotcontents snapcontent-57fbd2e0-0215-4019-b1fc-0df6ddb096c0 has been found and is not deleted Nov 18 00:18:44.926: INFO: volumesnapshotcontents snapcontent-57fbd2e0-0215-4019-b1fc-0df6ddb096c0 has been found and is not deleted Nov 18 00:18:46.037: INFO: volumesnapshotcontents snapcontent-57fbd2e0-0215-4019-b1fc-0df6ddb096c0 has been found and is not deleted Nov 18 00:18:47.037: INFO: WaitUntil failed after reaching the timeout 30s [AfterEach] volume snapshot controller test/e2e/storage/testsuites/snapshottable.go:172 Nov 18 00:18:47.173: INFO: Pod restored-pvc-tester-hsrwc has the following logs: Nov 18 00:18:47.173: INFO: Deleting pod "restored-pvc-tester-hsrwc" in namespace "snapshotting-1207" Nov 18 00:18:47.282: INFO: Wait up to 5m0s for pod "restored-pvc-tester-hsrwc" to be fully deleted Nov 18 00:19:19.501: INFO: deleting snapshot "snapshotting-1207"/"snapshot-997xx" ... skipping 26 lines ... [90mtest/e2e/storage/testsuites/snapshottable.go:113[0m [90mtest/e2e/storage/testsuites/snapshottable.go:176[0m should check snapshot fields, check restore correctly works, check deletion (ephemeral) [90mtest/e2e/storage/testsuites/snapshottable.go:177[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)","total":16,"completed":2,"skipped":450,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Dynamic PV (default fs)] subPath[0m [1mshould support non-existent path[0m [37mtest/e2e/storage/testsuites/subpath.go:196[0m ... skipping 17 lines ... Nov 18 00:16:32.268: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comszk8t] to have phase Bound Nov 18 00:16:32.376: INFO: PersistentVolumeClaim test.csi.azure.comszk8t found but phase is Pending instead of Bound. Nov 18 00:16:34.485: INFO: PersistentVolumeClaim test.csi.azure.comszk8t found but phase is Pending instead of Bound. Nov 18 00:16:36.595: INFO: PersistentVolumeClaim test.csi.azure.comszk8t found and phase=Bound (4.326384766s) [1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-kxpt [1mSTEP[0m: Creating a pod to test subpath Nov 18 00:16:36.921: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-kxpt" in namespace "provisioning-5571" to be "Succeeded or Failed" Nov 18 00:16:37.040: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 119.205274ms Nov 18 00:16:39.150: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229442484s Nov 18 00:16:41.259: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.338003024s Nov 18 00:16:43.368: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.4475363s Nov 18 00:16:45.478: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.557569185s Nov 18 00:16:47.589: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.66795035s ... skipping 39 lines ... Nov 18 00:18:12.015: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 1m35.094340505s Nov 18 00:18:14.125: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 1m37.204002251s Nov 18 00:18:16.234: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 1m39.313525099s Nov 18 00:18:18.346: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Pending", Reason="", readiness=false. Elapsed: 1m41.42527033s Nov 18 00:18:20.457: INFO: Pod "pod-subpath-test-dynamicpv-kxpt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m43.535815091s [1mSTEP[0m: Saw pod success Nov 18 00:18:20.457: INFO: Pod "pod-subpath-test-dynamicpv-kxpt" satisfied condition "Succeeded or Failed" Nov 18 00:18:20.565: INFO: Trying to get logs from node k8s-agentpool1-81963798-vmss000000 pod pod-subpath-test-dynamicpv-kxpt container test-container-volume-dynamicpv-kxpt: <nil> [1mSTEP[0m: delete the pod Nov 18 00:18:20.850: INFO: Waiting for pod pod-subpath-test-dynamicpv-kxpt to disappear Nov 18 00:18:20.958: INFO: Pod pod-subpath-test-dynamicpv-kxpt no longer exists [1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-kxpt Nov 18 00:18:20.958: INFO: Deleting pod "pod-subpath-test-dynamicpv-kxpt" in namespace "provisioning-5571" ... skipping 29 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m should support non-existent path [90mtest/e2e/storage/testsuites/subpath.go:196[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path","total":35,"completed":2,"skipped":45,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath test/e2e/storage/framework/testsuite.go:51 Nov 18 00:19:33.517: INFO: Distro debian doesn't support ntfs -- skipping ... skipping 24 lines ... [36m[1mS [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Pre-provisioned PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m [36m[1mshould fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach][0m [90mtest/e2e/storage/testsuites/subpath.go:280[0m [36mDriver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping[0m test/e2e/storage/external/external.go:262 [90m------------------------------[0m ... skipping 159 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy [90mtest/e2e/storage/framework/testsuite.go:50[0m (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents [90mtest/e2e/storage/testsuites/fsgroupchangepolicy.go:216[0m [90m------------------------------[0m {"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":40,"completed":2,"skipped":78,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] test/e2e/storage/framework/testsuite.go:51 Nov 18 00:19:35.585: INFO: Distro debian doesn't support ntfs -- skipping ... skipping 38 lines ... Nov 18 00:19:16.688: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.comnnbzz] to have phase Bound Nov 18 00:19:16.798: INFO: PersistentVolumeClaim test.csi.azure.comnnbzz found but phase is Pending instead of Bound. Nov 18 00:19:18.909: INFO: PersistentVolumeClaim test.csi.azure.comnnbzz found but phase is Pending instead of Bound. Nov 18 00:19:21.019: INFO: PersistentVolumeClaim test.csi.azure.comnnbzz found and phase=Bound (4.331036545s) [1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-8vdd [1mSTEP[0m: Creating a pod to test subpath Nov 18 00:19:21.349: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-8vdd" in namespace "provisioning-3554" to be "Succeeded or Failed" Nov 18 00:19:21.466: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 116.774226ms Nov 18 00:19:23.576: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226878961s Nov 18 00:19:25.685: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.336562918s Nov 18 00:19:27.798: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.448850895s Nov 18 00:19:29.907: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.557769907s Nov 18 00:19:32.039: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.690032762s ... skipping 9 lines ... Nov 18 00:19:53.159: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 31.80986438s Nov 18 00:19:55.270: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 33.920761193s Nov 18 00:19:57.380: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 36.030907993s Nov 18 00:19:59.500: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Pending", Reason="", readiness=false. Elapsed: 38.151232663s Nov 18 00:20:01.611: INFO: Pod "pod-subpath-test-dynamicpv-8vdd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.262013762s [1mSTEP[0m: Saw pod success Nov 18 00:20:01.611: INFO: Pod "pod-subpath-test-dynamicpv-8vdd" satisfied condition "Succeeded or Failed" Nov 18 00:20:01.720: INFO: Trying to get logs from node k8s-agentpool1-81963798-vmss000001 pod pod-subpath-test-dynamicpv-8vdd container test-container-volume-dynamicpv-8vdd: <nil> [1mSTEP[0m: delete the pod Nov 18 00:20:01.948: INFO: Waiting for pod pod-subpath-test-dynamicpv-8vdd to disappear Nov 18 00:20:02.056: INFO: Pod pod-subpath-test-dynamicpv-8vdd no longer exists [1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-8vdd Nov 18 00:20:02.056: INFO: Deleting pod "pod-subpath-test-dynamicpv-8vdd" in namespace "provisioning-3554" ... skipping 23 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m should support existing directory [90mtest/e2e/storage/testsuites/subpath.go:207[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory","total":34,"completed":2,"skipped":29,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] test/e2e/storage/framework/testsuite.go:51 Nov 18 00:20:43.942: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 80 lines ... [90mtest/e2e/storage/framework/testsuite.go:50[0m should be able to unmount after the subpath directory is deleted [LinuxOnly] [90mtest/e2e/storage/testsuites/subpath.go:447[0m [90m------------------------------[0m [36mS[0m [90m------------------------------[0m {"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":39,"completed":3,"skipped":99,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath test/e2e/storage/framework/testsuite.go:51 Nov 18 00:20:44.097: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 181 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy [90mtest/e2e/storage/framework/testsuite.go:50[0m (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 [90mtest/e2e/storage/testsuites/fsgroupchangepolicy.go:216[0m [90m------------------------------[0m {"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":40,"completed":3,"skipped":122,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] subPath test/e2e/storage/framework/testsuite.go:51 Nov 18 00:21:40.973: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 215 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should access to two volumes with the same volume mode and retain data across pod recreation on different node [90mtest/e2e/storage/testsuites/multivolume.go:168[0m [90m------------------------------[0m {"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":32,"completed":2,"skipped":360,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource][0m [0mvolume snapshot controller[0m [90m[0m [1mshould check snapshot fields, check restore correctly works, check deletion (ephemeral)[0m [37mtest/e2e/storage/testsuites/snapshottable.go:177[0m ... skipping 10 lines ... [It] should check snapshot fields, check restore correctly works, check deletion (ephemeral) test/e2e/storage/testsuites/snapshottable.go:177 Nov 18 00:19:34.502: INFO: Creating resource for dynamic PV Nov 18 00:19:34.502: INFO: Using claimSize:5Gi, test suite supported size:{ 1Mi}, driver(test.csi.azure.com) supported size:{ 1Mi} [1mSTEP[0m: creating a StorageClass snapshotting-5655-e2e-scznd99 [1mSTEP[0m: [init] starting a pod to use the claim Nov 18 00:19:34.723: INFO: Waiting up to 15m0s for pod "pvc-snapshottable-tester-bkzw5" in namespace "snapshotting-5655" to be "Succeeded or Failed" Nov 18 00:19:34.831: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 108.359159ms Nov 18 00:19:36.943: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219702076s Nov 18 00:19:39.054: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.330785864s Nov 18 00:19:41.163: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.440099232s Nov 18 00:19:43.275: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.552288119s Nov 18 00:19:45.384: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.661449965s ... skipping 45 lines ... Nov 18 00:21:22.480: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m47.756727196s Nov 18 00:21:24.590: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m49.866558122s Nov 18 00:21:26.699: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m51.975865897s Nov 18 00:21:28.809: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Pending", Reason="", readiness=false. Elapsed: 1m54.085998652s Nov 18 00:21:30.920: INFO: Pod "pvc-snapshottable-tester-bkzw5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m56.196988038s [1mSTEP[0m: Saw pod success Nov 18 00:21:30.920: INFO: Pod "pvc-snapshottable-tester-bkzw5" satisfied condition "Succeeded or Failed" [1mSTEP[0m: [init] checking the claim [1mSTEP[0m: creating a SnapshotClass [1mSTEP[0m: creating a dynamic VolumeSnapshot Nov 18 00:21:31.363: INFO: Waiting up to 5m0s for VolumeSnapshot snapshot-588ns to become ready Nov 18 00:21:31.472: INFO: VolumeSnapshot snapshot-588ns found but is not ready. Nov 18 00:21:33.583: INFO: VolumeSnapshot snapshot-588ns found but is not ready. ... skipping 49 lines ... [90mtest/e2e/storage/testsuites/snapshottable.go:113[0m [90mtest/e2e/storage/testsuites/snapshottable.go:176[0m should check snapshot fields, check restore correctly works, check deletion (ephemeral) [90mtest/e2e/storage/testsuites/snapshottable.go:177[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)","total":35,"completed":3,"skipped":185,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning test/e2e/storage/framework/testsuite.go:51 Nov 18 00:22:43.177: INFO: Distro debian doesn't support ntfs -- skipping ... skipping 151 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should concurrently access the single read-only volume from pods on the same node [90mtest/e2e/storage/testsuites/multivolume.go:423[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":34,"completed":3,"skipped":176,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [0mExternal Storage [Driver: test.csi.azure.com][0m [90m[Testpattern: Dynamic PV (block volmode)] multiVolume [Slow][0m [1mshould access to two volumes with different volume mode and retain data across pod recreation on different node[0m [37mtest/e2e/storage/testsuites/multivolume.go:248[0m ... skipping 194 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should access to two volumes with different volume mode and retain data across pod recreation on different node [90mtest/e2e/storage/testsuites/multivolume.go:248[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node","total":16,"completed":3,"skipped":506,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (default fs)] volumeIO test/e2e/storage/framework/testsuite.go:51 Nov 18 00:23:23.103: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 203 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (ext3)] volumes [90mtest/e2e/storage/framework/testsuite.go:50[0m should store data [90mtest/e2e/storage/testsuites/volumes.go:161[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext3)] volumes should store data","total":39,"completed":4,"skipped":159,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] test/e2e/storage/framework/testsuite.go:51 Nov 18 00:23:55.066: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 24 lines ... [36m[1mS [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds][0m External Storage [Driver: test.csi.azure.com] [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath [90mtest/e2e/storage/framework/testsuite.go:50[0m [36m[1mshould fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach][0m [90mtest/e2e/storage/testsuites/subpath.go:258[0m [36mDistro debian doesn't support ntfs -- skipping[0m test/e2e/storage/framework/testsuite.go:127 [90m------------------------------[0m ... skipping 93 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] [90mtest/e2e/storage/framework/testsuite.go:50[0m should concurrently access the single read-only volume from pods on the same node [90mtest/e2e/storage/testsuites/multivolume.go:423[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node","total":40,"completed":4,"skipped":141,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath test/e2e/storage/framework/testsuite.go:51 Nov 18 00:23:56.268: INFO: Distro debian doesn't support ntfs -- skipping ... skipping 87 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral [90mtest/e2e/storage/framework/testsuite.go:50[0m should create read-only inline ephemeral volume [90mtest/e2e/storage/testsuites/ephemeral.go:175[0m [90m------------------------------[0m {"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":32,"completed":3,"skipped":387,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] test/e2e/storage/framework/testsuite.go:51 Nov 18 00:24:24.768: INFO: Driver "test.csi.azure.com" does not support volume type "PreprovisionedPV" - skipping ... skipping 66 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral [90mtest/e2e/storage/framework/testsuite.go:50[0m should create read-only inline ephemeral volume [90mtest/e2e/storage/testsuites/ephemeral.go:175[0m [90m------------------------------[0m {"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":35,"completed":4,"skipped":281,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m [90m------------------------------[0m [BeforeEach] [Testpattern: Inline-volume (default fs)] subPath test/e2e/storage/framework/testsuite.go:51 Nov 18 00:24:25.280: INFO: Driver "test.csi.azure.com" does not support volume type "InlineVolume" - skipping ... skipping 70 lines ... Nov 18 00:23:16.533: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [test.csi.azure.com25lc4] to have phase Bound Nov 18 00:23:16.641: INFO: PersistentVolumeClaim test.csi.azure.com25lc4 found but phase is Pending instead of Bound. Nov 18 00:23:18.750: INFO: PersistentVolumeClaim test.csi.azure.com25lc4 found but phase is Pending instead of Bound. Nov 18 00:23:20.860: INFO: PersistentVolumeClaim test.csi.azure.com25lc4 found and phase=Bound (4.326708915s) [1mSTEP[0m: Creating pod exec-volume-test-dynamicpv-ctgh [1mSTEP[0m: Creating a pod to test exec-volume-test Nov 18 00:23:21.191: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-ctgh" in namespace "volume-4728" to be "Succeeded or Failed" Nov 18 00:23:21.301: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 110.681644ms Nov 18 00:23:23.411: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220095326s Nov 18 00:23:25.519: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.328844789s Nov 18 00:23:27.628: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.437147368s Nov 18 00:23:29.738: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.546956884s Nov 18 00:23:31.854: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.663065713s ... skipping 6 lines ... Nov 18 00:23:46.618: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 25.427785291s Nov 18 00:23:48.726: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 27.535887651s Nov 18 00:23:50.835: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 29.644610747s Nov 18 00:23:52.949: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Pending", Reason="", readiness=false. Elapsed: 31.758087856s Nov 18 00:23:55.058: INFO: Pod "exec-volume-test-dynamicpv-ctgh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.866919372s [1mSTEP[0m: Saw pod success Nov 18 00:23:55.058: INFO: Pod "exec-volume-test-dynamicpv-ctgh" satisfied condition "Succeeded or Failed" Nov 18 00:23:55.166: INFO: Trying to get logs from node k8s-agentpool1-81963798-vmss000001 pod exec-volume-test-dynamicpv-ctgh container exec-container-dynamicpv-ctgh: <nil> [1mSTEP[0m: delete the pod Nov 18 00:23:55.392: INFO: Waiting for pod exec-volume-test-dynamicpv-ctgh to disappear Nov 18 00:23:55.499: INFO: Pod exec-volume-test-dynamicpv-ctgh no longer exists [1mSTEP[0m: Deleting pod exec-volume-test-dynamicpv-ctgh Nov 18 00:23:55.500: INFO: Deleting pod "exec-volume-test-dynamicpv-ctgh" in namespace "volume-4728" ... skipping 27 lines ... [90mtest/e2e/storage/external/external.go:174[0m [Testpattern: Dynamic PV (default fs)] volumes [90mtest/e2e/storage/framework/testsuite.go:50[0m should allow exec of files on the volume [90mtest/e2e/storage/testsuites/volumes.go:198[0m [90m------------------------------[0m {"msg":"PASSED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume","total":34,"completed":4,"skipped":202,"failed":0} [36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m[36mS[0m