kubernetes-sigs/azuredisk-csi-driver PR #1716 pull-azuredisk-csi-driver-e2e-windows-containerd #1622950066157260800
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | andyzhangx: feat: integrate traffic manager proxy |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 49m55s |
| Revision | eca3f8cb14b52bab0cf8e01a653549d6e6b03861 |
| Refs |
1716 |
... skipping 107 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 170k 0 --:--:-- --:--:-- --:--:-- 170k Downloading https://get.helm.sh/helm-v3.11.0-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:v1.27.0-4975dedf8f02611fe5d34a2ea303bb2b310687a3 || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.27.0-4975dedf8f02611fe5d34a2ea303bb2b310687a3 not found: manifest unknown: manifest tagged by "v1.27.0-4975dedf8f02611fe5d34a2ea303bb2b310687a3" 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=v1.27.0-4975dedf8f02611fe5d34a2ea303bb2b310687a3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=4975dedf8f02611fe5d34a2ea303bb2b310687a3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-07T13:36:12Z -extldflags "-static"" -mod vendor -o _output/amd64/azurediskplugin.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 1119 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 673 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.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 219 lines ... Feb 7 13:42:32.682: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-tzkv2] to have phase Bound Feb 7 13:42:32.741: INFO: PersistentVolumeClaim pvc-tzkv2 found and phase=Bound (58.555658ms) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:42:32.741[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:42:32.798[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:42:32.855[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:42:32.855[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/07/23 13:42:32.927[0m Feb 7 13:42:32.927: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7vdtz" in namespace "azuredisk-8081" to be "Error status code" Feb 7 13:42:32.987: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 59.319137ms Feb 7 13:42:35.048: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.12106038s Feb 7 13:42:37.045: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.118238592s Feb 7 13:42:39.045: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117310916s Feb 7 13:42:41.046: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.118880006s Feb 7 13:42:43.049: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.121691592s ... skipping 32 lines ... Feb 7 13:43:49.048: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=true. Elapsed: 1m16.121187061s Feb 7 13:43:51.045: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=true. Elapsed: 1m18.117928139s Feb 7 13:43:53.047: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=true. Elapsed: 1m20.119893659s Feb 7 13:43:55.047: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.119802057s Feb 7 13:43:57.047: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.119908938s Feb 7 13:43:59.046: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.118852455s Feb 7 13:44:01.046: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Failed", Reason="", readiness=false. Elapsed: 1m28.118280588s [1mSTEP:[0m Saw pod failure [38;5;243m02/07/23 13:44:01.046[0m Feb 7 13:44:01.046: INFO: Pod "azuredisk-volume-tester-7vdtz" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/07/23 13:44:01.046[0m Feb 7 13:44:01.137: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-7vdtz" Feb 7 13:44:01.212: INFO: Pod azuredisk-volume-tester-7vdtz has the following logs: Out-File : Access to the path 'C:\mnt\test-1\data.txt' is denied. At line:1 char:22 + ... cho 'hello world' | Out-File -FilePath C:\mnt\test-1\data.txt; Get-Co ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... skipping 81 lines ... Feb 7 13:42:32.682: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-tzkv2] to have phase Bound Feb 7 13:42:32.741: INFO: PersistentVolumeClaim pvc-tzkv2 found and phase=Bound (58.555658ms) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:42:32.741[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:42:32.798[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:42:32.855[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:42:32.855[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/07/23 13:42:32.927[0m Feb 7 13:42:32.927: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7vdtz" in namespace "azuredisk-8081" to be "Error status code" Feb 7 13:42:32.987: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 59.319137ms Feb 7 13:42:35.048: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.12106038s Feb 7 13:42:37.045: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.118238592s Feb 7 13:42:39.045: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117310916s Feb 7 13:42:41.046: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.118880006s Feb 7 13:42:43.049: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.121691592s ... skipping 32 lines ... Feb 7 13:43:49.048: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=true. Elapsed: 1m16.121187061s Feb 7 13:43:51.045: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=true. Elapsed: 1m18.117928139s Feb 7 13:43:53.047: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=true. Elapsed: 1m20.119893659s Feb 7 13:43:55.047: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.119802057s Feb 7 13:43:57.047: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.119908938s Feb 7 13:43:59.046: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.118852455s Feb 7 13:44:01.046: INFO: Pod "azuredisk-volume-tester-7vdtz": Phase="Failed", Reason="", readiness=false. Elapsed: 1m28.118280588s [1mSTEP:[0m Saw pod failure [38;5;243m02/07/23 13:44:01.046[0m Feb 7 13:44:01.046: INFO: Pod "azuredisk-volume-tester-7vdtz" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/07/23 13:44:01.046[0m Feb 7 13:44:01.137: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-7vdtz" Feb 7 13:44:01.212: INFO: Pod azuredisk-volume-tester-7vdtz has the following logs: Out-File : Access to the path 'C:\mnt\test-1\data.txt' is denied. At line:1 char:22 + ... cho 'hello world' | Out-File -FilePath C:\mnt\test-1\data.txt; Get-Co ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... skipping 139 lines ... [1mSTEP:[0m Successfully provisioned a shared disk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-afjigakn/providers/Microsoft.Compute/disks/single-shared-disk" [38;5;243m02/07/23 13:44:56.724[0m [1mSTEP:[0m Destroying namespace "azuredisk-4728" for this suite. [38;5;243m02/07/23 13:44:57.205[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould fail when maxShares is invalid [disk.csi.azure.com][windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:166[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m02/07/23 13:44:57.266[0m Feb 7 13:44:57.267: INFO: >>> kubeConfig: /root/tmp863706749/kubeconfig/kubeconfig.westus2.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m02/07/23 13:44:57.268[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m02/07/23 13:44:57.443[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m02/07/23 13:44:57.557[0m ... skipping 2 lines ... [38;5;243m------------------------------[0m [38;5;10m• [0.464 seconds][0m Pre-Provisioned [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:38[0m [single-az] [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:71[0m should fail when maxShares is invalid [disk.csi.azure.com][windows] [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:166[0m [38;5;243mBegin Captured GinkgoWriter Output >>[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m02/07/23 13:44:57.266[0m Feb 7 13:44:57.267: INFO: >>> kubeConfig: /root/tmp863706749/kubeconfig/kubeconfig.westus2.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m02/07/23 13:44:57.268[0m ... skipping 88 lines ... Feb 7 13:45:10.847: INFO: PersistentVolumeClaim pvc-gwtpr found and phase=Bound (57.845574ms) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:45:10.847[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:45:10.912[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:45:10.97[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m02/07/23 13:45:11.083[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:45:17.698[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 13:45:17.759[0m Feb 7 13:45:17.760: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-k9nqs" in namespace "azuredisk-5194" to be "Succeeded or Failed" Feb 7 13:45:17.817: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 57.786738ms Feb 7 13:45:19.876: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116749475s Feb 7 13:45:21.878: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.117883728s Feb 7 13:45:23.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119280006s Feb 7 13:45:25.877: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.11719972s Feb 7 13:45:27.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.119140331s ... skipping 43 lines ... Feb 7 13:46:55.876: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=true. Elapsed: 1m38.116456751s Feb 7 13:46:57.876: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=true. Elapsed: 1m40.116748894s Feb 7 13:46:59.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.118963253s Feb 7 13:47:01.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.11910192s Feb 7 13:47:03.877: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m46.117547678s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:47:03.877[0m Feb 7 13:47:03.877: INFO: Pod "azuredisk-volume-tester-k9nqs" satisfied condition "Succeeded or Failed" Feb 7 13:47:03.877: INFO: deleting Pod "azuredisk-5194"/"azuredisk-volume-tester-k9nqs" Feb 7 13:47:03.968: INFO: Pod azuredisk-volume-tester-k9nqs has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-k9nqs in namespace azuredisk-5194 [38;5;243m02/07/23 13:47:03.968[0m Feb 7 13:47:04.163: INFO: deleting PVC "azuredisk-5194"/"pvc-gwtpr" Feb 7 13:47:04.163: INFO: Deleting PersistentVolumeClaim "pvc-gwtpr" ... skipping 39 lines ... Feb 7 13:45:10.847: INFO: PersistentVolumeClaim pvc-gwtpr found and phase=Bound (57.845574ms) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:45:10.847[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:45:10.912[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:45:10.97[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m02/07/23 13:45:11.083[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:45:17.698[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 13:45:17.759[0m Feb 7 13:45:17.760: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-k9nqs" in namespace "azuredisk-5194" to be "Succeeded or Failed" Feb 7 13:45:17.817: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 57.786738ms Feb 7 13:45:19.876: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116749475s Feb 7 13:45:21.878: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.117883728s Feb 7 13:45:23.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119280006s Feb 7 13:45:25.877: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.11719972s Feb 7 13:45:27.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.119140331s ... skipping 43 lines ... Feb 7 13:46:55.876: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=true. Elapsed: 1m38.116456751s Feb 7 13:46:57.876: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=true. Elapsed: 1m40.116748894s Feb 7 13:46:59.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.118963253s Feb 7 13:47:01.879: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.11910192s Feb 7 13:47:03.877: INFO: Pod "azuredisk-volume-tester-k9nqs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m46.117547678s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:47:03.877[0m Feb 7 13:47:03.877: INFO: Pod "azuredisk-volume-tester-k9nqs" satisfied condition "Succeeded or Failed" Feb 7 13:47:03.877: INFO: deleting Pod "azuredisk-5194"/"azuredisk-volume-tester-k9nqs" Feb 7 13:47:03.968: INFO: Pod azuredisk-volume-tester-k9nqs has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-k9nqs in namespace azuredisk-5194 [38;5;243m02/07/23 13:47:03.968[0m Feb 7 13:47:04.163: INFO: deleting PVC "azuredisk-5194"/"pvc-gwtpr" Feb 7 13:47:04.163: INFO: Deleting PersistentVolumeClaim "pvc-gwtpr" ... skipping 71 lines ... Feb 7 13:47:51.519: INFO: PersistentVolumeClaim pvc-pzzvl found and phase=Bound (4.176366433s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:47:51.519[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:47:51.581[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:47:51.639[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 13:47:51.639[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:47:51.639[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 13:47:51.709[0m Feb 7 13:47:51.709: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-v4r2h" in namespace "azuredisk-2888" to be "Succeeded or Failed" Feb 7 13:47:51.769: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 59.943321ms Feb 7 13:47:53.832: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123188728s Feb 7 13:47:55.830: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120932136s Feb 7 13:47:57.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119024361s Feb 7 13:47:59.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.119288318s Feb 7 13:48:01.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.118685607s ... skipping 12 lines ... Feb 7 13:48:27.830: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=true. Elapsed: 36.120488929s Feb 7 13:48:29.827: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=true. Elapsed: 38.118157895s Feb 7 13:48:31.827: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=false. Elapsed: 40.118231153s Feb 7 13:48:33.827: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=false. Elapsed: 42.118286688s Feb 7 13:48:35.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.118846407s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:48:35.828[0m Feb 7 13:48:35.828: INFO: Pod "azuredisk-volume-tester-v4r2h" satisfied condition "Succeeded or Failed" Feb 7 13:48:35.828: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-v4r2h" Feb 7 13:48:35.912: INFO: Pod azuredisk-volume-tester-v4r2h has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-v4r2h in namespace azuredisk-2888 [38;5;243m02/07/23 13:48:35.912[0m Feb 7 13:48:35.981: INFO: deleting PVC "azuredisk-2888"/"pvc-pzzvl" Feb 7 13:48:35.981: INFO: Deleting PersistentVolumeClaim "pvc-pzzvl" ... skipping 39 lines ... Feb 7 13:47:51.519: INFO: PersistentVolumeClaim pvc-pzzvl found and phase=Bound (4.176366433s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:47:51.519[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:47:51.581[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:47:51.639[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 13:47:51.639[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:47:51.639[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 13:47:51.709[0m Feb 7 13:47:51.709: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-v4r2h" in namespace "azuredisk-2888" to be "Succeeded or Failed" Feb 7 13:47:51.769: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 59.943321ms Feb 7 13:47:53.832: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.123188728s Feb 7 13:47:55.830: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120932136s Feb 7 13:47:57.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119024361s Feb 7 13:47:59.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.119288318s Feb 7 13:48:01.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.118685607s ... skipping 12 lines ... Feb 7 13:48:27.830: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=true. Elapsed: 36.120488929s Feb 7 13:48:29.827: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=true. Elapsed: 38.118157895s Feb 7 13:48:31.827: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=false. Elapsed: 40.118231153s Feb 7 13:48:33.827: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Running", Reason="", readiness=false. Elapsed: 42.118286688s Feb 7 13:48:35.828: INFO: Pod "azuredisk-volume-tester-v4r2h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.118846407s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:48:35.828[0m Feb 7 13:48:35.828: INFO: Pod "azuredisk-volume-tester-v4r2h" satisfied condition "Succeeded or Failed" Feb 7 13:48:35.828: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-v4r2h" Feb 7 13:48:35.912: INFO: Pod azuredisk-volume-tester-v4r2h has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-v4r2h in namespace azuredisk-2888 [38;5;243m02/07/23 13:48:35.912[0m Feb 7 13:48:35.981: INFO: deleting PVC "azuredisk-2888"/"pvc-pzzvl" Feb 7 13:48:35.981: INFO: Deleting PersistentVolumeClaim "pvc-pzzvl" ... skipping 38 lines ... Feb 7 13:49:19.913: INFO: PersistentVolumeClaim pvc-9tb8f found but phase is Pending instead of Bound. Feb 7 13:49:21.979: INFO: PersistentVolumeClaim pvc-9tb8f found and phase=Bound (4.182272305s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:49:21.979[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:49:22.037[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:49:22.095[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:49:22.095[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m02/07/23 13:49:22.155[0m Feb 7 13:49:22.156: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-t9m2z" in namespace "azuredisk-156" to be "Succeeded or Failed" Feb 7 13:49:22.215: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 58.967328ms Feb 7 13:49:24.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118874398s Feb 7 13:49:26.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.119377806s Feb 7 13:49:28.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118632362s Feb 7 13:49:30.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.118832973s Feb 7 13:49:32.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.119290075s ... skipping 12 lines ... Feb 7 13:49:58.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 36.119019122s Feb 7 13:50:00.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Running", Reason="", readiness=true. Elapsed: 38.118565825s Feb 7 13:50:02.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Running", Reason="", readiness=true. Elapsed: 40.119142738s Feb 7 13:50:04.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Running", Reason="", readiness=false. Elapsed: 42.118992264s Feb 7 13:50:06.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.118390465s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:50:06.274[0m Feb 7 13:50:06.274: INFO: Pod "azuredisk-volume-tester-t9m2z" satisfied condition "Succeeded or Failed" Feb 7 13:50:06.274: INFO: deleting Pod "azuredisk-156"/"azuredisk-volume-tester-t9m2z" Feb 7 13:50:06.359: INFO: Pod azuredisk-volume-tester-t9m2z has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-t9m2z in namespace azuredisk-156 [38;5;243m02/07/23 13:50:06.36[0m Feb 7 13:50:06.428: INFO: deleting PVC "azuredisk-156"/"pvc-9tb8f" Feb 7 13:50:06.428: INFO: Deleting PersistentVolumeClaim "pvc-9tb8f" ... skipping 44 lines ... Feb 7 13:49:19.913: INFO: PersistentVolumeClaim pvc-9tb8f found but phase is Pending instead of Bound. Feb 7 13:49:21.979: INFO: PersistentVolumeClaim pvc-9tb8f found and phase=Bound (4.182272305s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:49:21.979[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:49:22.037[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:49:22.095[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:49:22.095[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m02/07/23 13:49:22.155[0m Feb 7 13:49:22.156: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-t9m2z" in namespace "azuredisk-156" to be "Succeeded or Failed" Feb 7 13:49:22.215: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 58.967328ms Feb 7 13:49:24.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118874398s Feb 7 13:49:26.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.119377806s Feb 7 13:49:28.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118632362s Feb 7 13:49:30.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.118832973s Feb 7 13:49:32.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.119290075s ... skipping 12 lines ... Feb 7 13:49:58.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Pending", Reason="", readiness=false. Elapsed: 36.119019122s Feb 7 13:50:00.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Running", Reason="", readiness=true. Elapsed: 38.118565825s Feb 7 13:50:02.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Running", Reason="", readiness=true. Elapsed: 40.119142738s Feb 7 13:50:04.275: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Running", Reason="", readiness=false. Elapsed: 42.118992264s Feb 7 13:50:06.274: INFO: Pod "azuredisk-volume-tester-t9m2z": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.118390465s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:50:06.274[0m Feb 7 13:50:06.274: INFO: Pod "azuredisk-volume-tester-t9m2z" satisfied condition "Succeeded or Failed" Feb 7 13:50:06.274: INFO: deleting Pod "azuredisk-156"/"azuredisk-volume-tester-t9m2z" Feb 7 13:50:06.359: INFO: Pod azuredisk-volume-tester-t9m2z has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-t9m2z in namespace azuredisk-156 [38;5;243m02/07/23 13:50:06.36[0m Feb 7 13:50:06.428: INFO: deleting PVC "azuredisk-156"/"pvc-9tb8f" Feb 7 13:50:06.428: INFO: Deleting PersistentVolumeClaim "pvc-9tb8f" ... skipping 45 lines ... Feb 7 13:51:22.951: INFO: PersistentVolumeClaim pvc-hwxgq found and phase=Bound (4.181208895s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:51:22.951[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:51:23.01[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:51:23.074[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 13:51:23.075[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:51:23.075[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 13:51:23.143[0m Feb 7 13:51:23.143: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-s742h" in namespace "azuredisk-1563" to be "Succeeded or Failed" Feb 7 13:51:23.202: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 59.444583ms Feb 7 13:51:25.264: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.121445735s Feb 7 13:51:27.265: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.122098667s Feb 7 13:51:29.266: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123187438s Feb 7 13:51:31.264: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.120807095s Feb 7 13:51:33.263: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.120286309s ... skipping 14 lines ... Feb 7 13:52:03.262: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=true. Elapsed: 40.119453672s Feb 7 13:52:05.264: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=true. Elapsed: 42.12122249s Feb 7 13:52:07.263: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=false. Elapsed: 44.11976996s Feb 7 13:52:09.268: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=false. Elapsed: 46.124599729s Feb 7 13:52:11.265: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.121845532s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:52:11.265[0m Feb 7 13:52:11.265: INFO: Pod "azuredisk-volume-tester-s742h" satisfied condition "Succeeded or Failed" Feb 7 13:52:11.265: INFO: deleting Pod "azuredisk-1563"/"azuredisk-volume-tester-s742h" Feb 7 13:52:11.363: INFO: Pod azuredisk-volume-tester-s742h has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-s742h in namespace azuredisk-1563 [38;5;243m02/07/23 13:52:11.363[0m Feb 7 13:52:11.433: INFO: deleting PVC "azuredisk-1563"/"pvc-hwxgq" Feb 7 13:52:11.433: INFO: Deleting PersistentVolumeClaim "pvc-hwxgq" ... skipping 39 lines ... Feb 7 13:51:22.951: INFO: PersistentVolumeClaim pvc-hwxgq found and phase=Bound (4.181208895s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:51:22.951[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:51:23.01[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:51:23.074[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 13:51:23.075[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:51:23.075[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 13:51:23.143[0m Feb 7 13:51:23.143: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-s742h" in namespace "azuredisk-1563" to be "Succeeded or Failed" Feb 7 13:51:23.202: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 59.444583ms Feb 7 13:51:25.264: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.121445735s Feb 7 13:51:27.265: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.122098667s Feb 7 13:51:29.266: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123187438s Feb 7 13:51:31.264: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.120807095s Feb 7 13:51:33.263: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.120286309s ... skipping 14 lines ... Feb 7 13:52:03.262: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=true. Elapsed: 40.119453672s Feb 7 13:52:05.264: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=true. Elapsed: 42.12122249s Feb 7 13:52:07.263: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=false. Elapsed: 44.11976996s Feb 7 13:52:09.268: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Running", Reason="", readiness=false. Elapsed: 46.124599729s Feb 7 13:52:11.265: INFO: Pod "azuredisk-volume-tester-s742h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.121845532s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 13:52:11.265[0m Feb 7 13:52:11.265: INFO: Pod "azuredisk-volume-tester-s742h" satisfied condition "Succeeded or Failed" Feb 7 13:52:11.265: INFO: deleting Pod "azuredisk-1563"/"azuredisk-volume-tester-s742h" Feb 7 13:52:11.363: INFO: Pod azuredisk-volume-tester-s742h has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-s742h in namespace azuredisk-1563 [38;5;243m02/07/23 13:52:11.363[0m Feb 7 13:52:11.433: INFO: deleting PVC "azuredisk-1563"/"pvc-hwxgq" Feb 7 13:52:11.433: INFO: Deleting PersistentVolumeClaim "pvc-hwxgq" ... skipping 187 lines ... Feb 7 13:53:03.280: INFO: PersistentVolumeClaim pvc-8s25m found and phase=Bound (4.18042598s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:53:03.281[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:53:03.343[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:53:03.413[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 13:53:03.413[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:53:03.413[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/07/23 13:53:03.476[0m Feb 7 13:53:03.477: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lcxcn" in namespace "azuredisk-8010" to be "Error status code" Feb 7 13:53:03.540: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 62.399653ms Feb 7 13:53:05.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124033335s Feb 7 13:53:07.606: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128331277s Feb 7 13:53:09.602: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124480919s Feb 7 13:53:11.604: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.126686881s Feb 7 13:53:13.604: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.126925386s ... skipping 22 lines ... Feb 7 13:53:59.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 56.123501378s Feb 7 13:54:01.600: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 58.122457267s Feb 7 13:54:03.600: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=true. Elapsed: 1m0.122720329s Feb 7 13:54:05.602: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=true. Elapsed: 1m2.125127426s Feb 7 13:54:07.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.124034978s Feb 7 13:54:09.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.123623533s Feb 7 13:54:11.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Failed", Reason="", readiness=false. Elapsed: 1m8.123503824s [1mSTEP:[0m Saw pod failure [38;5;243m02/07/23 13:54:11.601[0m Feb 7 13:54:11.601: INFO: Pod "azuredisk-volume-tester-lcxcn" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/07/23 13:54:11.601[0m Feb 7 13:54:11.693: INFO: deleting Pod "azuredisk-8010"/"azuredisk-volume-tester-lcxcn" Feb 7 13:54:11.756: INFO: Pod azuredisk-volume-tester-lcxcn has the following logs: out-file : Access to the path 'C:\mnt\test-1\data' is denied. At line:1 char:1 + echo $null >> C:\mnt\test-1\data + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... skipping 48 lines ... Feb 7 13:53:03.280: INFO: PersistentVolumeClaim pvc-8s25m found and phase=Bound (4.18042598s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 13:53:03.281[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 13:53:03.343[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 13:53:03.413[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 13:53:03.413[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 13:53:03.413[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/07/23 13:53:03.476[0m Feb 7 13:53:03.477: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lcxcn" in namespace "azuredisk-8010" to be "Error status code" Feb 7 13:53:03.540: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 62.399653ms Feb 7 13:53:05.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124033335s Feb 7 13:53:07.606: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128331277s Feb 7 13:53:09.602: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124480919s Feb 7 13:53:11.604: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.126686881s Feb 7 13:53:13.604: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.126925386s ... skipping 22 lines ... Feb 7 13:53:59.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 56.123501378s Feb 7 13:54:01.600: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Pending", Reason="", readiness=false. Elapsed: 58.122457267s Feb 7 13:54:03.600: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=true. Elapsed: 1m0.122720329s Feb 7 13:54:05.602: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=true. Elapsed: 1m2.125127426s Feb 7 13:54:07.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.124034978s Feb 7 13:54:09.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.123623533s Feb 7 13:54:11.601: INFO: Pod "azuredisk-volume-tester-lcxcn": Phase="Failed", Reason="", readiness=false. Elapsed: 1m8.123503824s [1mSTEP:[0m Saw pod failure [38;5;243m02/07/23 13:54:11.601[0m Feb 7 13:54:11.601: INFO: Pod "azuredisk-volume-tester-lcxcn" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/07/23 13:54:11.601[0m Feb 7 13:54:11.693: INFO: deleting Pod "azuredisk-8010"/"azuredisk-volume-tester-lcxcn" Feb 7 13:54:11.756: INFO: Pod azuredisk-volume-tester-lcxcn has the following logs: out-file : Access to the path 'C:\mnt\test-1\data' is denied. At line:1 char:1 + echo $null >> C:\mnt\test-1\data + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... skipping 884 lines ... Feb 7 14:01:44.023: INFO: PersistentVolumeClaim pvc-k6h9s found and phase=Bound (4.173289242s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 14:01:44.023[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 14:01:44.088[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 14:01:44.145[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 14:01:44.145[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 14:01:44.145[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 14:01:44.21[0m Feb 7 14:01:44.210: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z7c4p" in namespace "azuredisk-9183" to be "Succeeded or Failed" Feb 7 14:01:44.267: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 57.131402ms Feb 7 14:01:46.326: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115975999s Feb 7 14:01:48.326: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.115718791s Feb 7 14:01:50.328: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117517955s Feb 7 14:01:52.326: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.116349451s Feb 7 14:01:54.327: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.116865239s ... skipping 31 lines ... Feb 7 14:02:58.328: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=true. Elapsed: 1m14.117418831s Feb 7 14:03:00.329: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=true. Elapsed: 1m16.118614157s Feb 7 14:03:02.327: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.117228384s Feb 7 14:03:04.327: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.116956939s Feb 7 14:03:06.329: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m22.118553401s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 14:03:06.329[0m Feb 7 14:03:06.329: INFO: Pod "azuredisk-volume-tester-z7c4p" satisfied condition "Succeeded or Failed" Feb 7 14:03:06.329: INFO: deleting Pod "azuredisk-9183"/"azuredisk-volume-tester-z7c4p" Feb 7 14:03:06.437: INFO: Pod azuredisk-volume-tester-z7c4p has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-z7c4p in namespace azuredisk-9183 [38;5;243m02/07/23 14:03:06.437[0m ... skipping 87 lines ... Feb 7 14:01:44.023: INFO: PersistentVolumeClaim pvc-k6h9s found and phase=Bound (4.173289242s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 14:01:44.023[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 14:01:44.088[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 14:01:44.145[0m [1mSTEP:[0m setting up the pod [38;5;243m02/07/23 14:01:44.145[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 14:01:44.145[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 14:01:44.21[0m Feb 7 14:01:44.210: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z7c4p" in namespace "azuredisk-9183" to be "Succeeded or Failed" Feb 7 14:01:44.267: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 57.131402ms Feb 7 14:01:46.326: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115975999s Feb 7 14:01:48.326: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.115718791s Feb 7 14:01:50.328: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117517955s Feb 7 14:01:52.326: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.116349451s Feb 7 14:01:54.327: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.116865239s ... skipping 31 lines ... Feb 7 14:02:58.328: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=true. Elapsed: 1m14.117418831s Feb 7 14:03:00.329: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=true. Elapsed: 1m16.118614157s Feb 7 14:03:02.327: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.117228384s Feb 7 14:03:04.327: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.116956939s Feb 7 14:03:06.329: INFO: Pod "azuredisk-volume-tester-z7c4p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m22.118553401s [1mSTEP:[0m Saw pod success [38;5;243m02/07/23 14:03:06.329[0m Feb 7 14:03:06.329: INFO: Pod "azuredisk-volume-tester-z7c4p" satisfied condition "Succeeded or Failed" Feb 7 14:03:06.329: INFO: deleting Pod "azuredisk-9183"/"azuredisk-volume-tester-z7c4p" Feb 7 14:03:06.437: INFO: Pod azuredisk-volume-tester-z7c4p has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-z7c4p in namespace azuredisk-9183 [38;5;243m02/07/23 14:03:06.437[0m ... skipping 97 lines ... Feb 7 14:04:12.160: INFO: PersistentVolumeClaim pvc-bps7j found but phase is Pending instead of Bound. Feb 7 14:04:14.220: INFO: PersistentVolumeClaim pvc-bps7j found and phase=Bound (4.180953105s) [1mSTEP:[0m checking the PVC [38;5;243m02/07/23 14:04:14.22[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/07/23 14:04:14.279[0m [1mSTEP:[0m checking the PV [38;5;243m02/07/23 14:04:14.338[0m [1mSTEP:[0m deploying the pod [38;5;243m02/07/23 14:04:14.338[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/07/23 14:04:14.4[0m Feb 7 14:04:14.400: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z2c7v" in namespace "azuredisk-1968" to be "Succeeded or Failed"