kubernetes-sigs/azuredisk-csi-driver PR #1666 pull-azuredisk-csi-driver-e2e-windows-containerd-mainv2 #1616505848941514752
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] feat: fetch VMs to recover AzVolumeAttachment |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 56m33s |
| Revision | 3c9841e0e8a2720e25692fb457a0736f981f613b |
| Refs |
1666 |
... skipping 108 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 158k 0 --:--:-- --:--:-- --:--:-- 158k 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:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 not found: manifest unknown: manifest tagged by "latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228" 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-170b3ae022589c5c949eadbdc4736c1b28944228 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=170b3ae022589c5c949eadbdc4736c1b28944228 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-20T18:51:49Z -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 1602 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 883 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 300 lines ... Jan 20 19:05:12.086: INFO: PersistentVolumeClaim pvc-bn7rm found but phase is Pending instead of Bound. Jan 20 19:05:14.102: INFO: PersistentVolumeClaim pvc-bn7rm found and phase=Bound (10.100626229s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:05:14.102[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:05:14.118[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:05:14.133[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:05:14.133[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/20/23 19:05:14.16[0m Jan 20 19:05:14.161: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-xzbpp" in namespace "azuredisk-3134" to be "Error status code" Jan 20 19:05:14.195: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 34.254564ms Jan 20 19:05:16.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.051752123s Jan 20 19:05:18.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.051838972s Jan 20 19:05:20.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.052123843s Jan 20 19:05:22.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.051643937s Jan 20 19:05:24.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.051614098s ... skipping 27 lines ... Jan 20 19:06:20.212: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=true. Elapsed: 1m6.050979265s Jan 20 19:06:22.224: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=true. Elapsed: 1m8.063150278s Jan 20 19:06:24.212: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=true. Elapsed: 1m10.051068235s Jan 20 19:06:26.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.051869638s Jan 20 19:06:28.214: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.053118993s Jan 20 19:06:30.216: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.054677334s Jan 20 19:06:32.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Failed", Reason="", readiness=false. Elapsed: 1m18.051909169s [1mSTEP:[0m Saw pod failure [38;5;243m01/20/23 19:06:32.213[0m Jan 20 19:06:32.213: INFO: Pod "azuredisk-volume-tester-xzbpp" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/20/23 19:06:32.213[0m Jan 20 19:06:32.282: INFO: deleting Pod "azuredisk-3134"/"azuredisk-volume-tester-xzbpp" Jan 20 19:06:32.317: INFO: Pod azuredisk-volume-tester-xzbpp 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 60 lines ... Jan 20 19:05:12.086: INFO: PersistentVolumeClaim pvc-bn7rm found but phase is Pending instead of Bound. Jan 20 19:05:14.102: INFO: PersistentVolumeClaim pvc-bn7rm found and phase=Bound (10.100626229s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:05:14.102[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:05:14.118[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:05:14.133[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:05:14.133[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/20/23 19:05:14.16[0m Jan 20 19:05:14.161: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-xzbpp" in namespace "azuredisk-3134" to be "Error status code" Jan 20 19:05:14.195: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 34.254564ms Jan 20 19:05:16.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.051752123s Jan 20 19:05:18.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.051838972s Jan 20 19:05:20.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.052123843s Jan 20 19:05:22.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.051643937s Jan 20 19:05:24.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.051614098s ... skipping 27 lines ... Jan 20 19:06:20.212: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=true. Elapsed: 1m6.050979265s Jan 20 19:06:22.224: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=true. Elapsed: 1m8.063150278s Jan 20 19:06:24.212: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=true. Elapsed: 1m10.051068235s Jan 20 19:06:26.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.051869638s Jan 20 19:06:28.214: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.053118993s Jan 20 19:06:30.216: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.054677334s Jan 20 19:06:32.213: INFO: Pod "azuredisk-volume-tester-xzbpp": Phase="Failed", Reason="", readiness=false. Elapsed: 1m18.051909169s [1mSTEP:[0m Saw pod failure [38;5;243m01/20/23 19:06:32.213[0m Jan 20 19:06:32.213: INFO: Pod "azuredisk-volume-tester-xzbpp" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/20/23 19:06:32.213[0m Jan 20 19:06:32.282: INFO: deleting Pod "azuredisk-3134"/"azuredisk-volume-tester-xzbpp" Jan 20 19:06:32.317: INFO: Pod azuredisk-volume-tester-xzbpp 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 90 lines ... Jan 20 19:07:28.680: INFO: PersistentVolumeClaim pvc-68mbn found and phase=Bound (12.12759326s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:07:28.68[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:07:28.695[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:07:28.71[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/20/23 19:07:28.725[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:07:40.659[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:07:40.684[0m Jan 20 19:07:40.684: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-h4hc4" in namespace "azuredisk-2617" to be "Succeeded or Failed" Jan 20 19:07:40.733: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 48.982694ms Jan 20 19:07:42.754: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069582509s Jan 20 19:07:44.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064972124s Jan 20 19:07:46.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064935157s Jan 20 19:07:48.751: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066895882s Jan 20 19:07:50.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065088768s ... skipping 27 lines ... Jan 20 19:08:46.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=true. Elapsed: 1m6.065080075s Jan 20 19:08:48.751: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=true. Elapsed: 1m8.067312623s Jan 20 19:08:50.750: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.065907547s Jan 20 19:08:52.751: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.066863673s Jan 20 19:08:54.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m14.065482544s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:08:54.75[0m Jan 20 19:08:54.750: INFO: Pod "azuredisk-volume-tester-h4hc4" satisfied condition "Succeeded or Failed" Jan 20 19:08:54.750: INFO: deleting Pod "azuredisk-2617"/"azuredisk-volume-tester-h4hc4" Jan 20 19:08:54.804: INFO: Pod azuredisk-volume-tester-h4hc4 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-h4hc4 in namespace azuredisk-2617 [38;5;243m01/20/23 19:08:54.804[0m Jan 20 19:08:54.870: INFO: deleting PVC "azuredisk-2617"/"pvc-68mbn" Jan 20 19:08:54.870: INFO: Deleting PersistentVolumeClaim "pvc-68mbn" ... skipping 42 lines ... Jan 20 19:07:28.680: INFO: PersistentVolumeClaim pvc-68mbn found and phase=Bound (12.12759326s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:07:28.68[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:07:28.695[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:07:28.71[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/20/23 19:07:28.725[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:07:40.659[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:07:40.684[0m Jan 20 19:07:40.684: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-h4hc4" in namespace "azuredisk-2617" to be "Succeeded or Failed" Jan 20 19:07:40.733: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 48.982694ms Jan 20 19:07:42.754: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069582509s Jan 20 19:07:44.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064972124s Jan 20 19:07:46.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064935157s Jan 20 19:07:48.751: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066895882s Jan 20 19:07:50.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065088768s ... skipping 27 lines ... Jan 20 19:08:46.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=true. Elapsed: 1m6.065080075s Jan 20 19:08:48.751: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=true. Elapsed: 1m8.067312623s Jan 20 19:08:50.750: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.065907547s Jan 20 19:08:52.751: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.066863673s Jan 20 19:08:54.749: INFO: Pod "azuredisk-volume-tester-h4hc4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m14.065482544s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:08:54.75[0m Jan 20 19:08:54.750: INFO: Pod "azuredisk-volume-tester-h4hc4" satisfied condition "Succeeded or Failed" Jan 20 19:08:54.750: INFO: deleting Pod "azuredisk-2617"/"azuredisk-volume-tester-h4hc4" Jan 20 19:08:54.804: INFO: Pod azuredisk-volume-tester-h4hc4 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-h4hc4 in namespace azuredisk-2617 [38;5;243m01/20/23 19:08:54.804[0m Jan 20 19:08:54.870: INFO: deleting PVC "azuredisk-2617"/"pvc-68mbn" Jan 20 19:08:54.870: INFO: Deleting PersistentVolumeClaim "pvc-68mbn" ... skipping 153 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case not supported by Windows clusters[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/utils/testutil/env_utils.go:26[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: { "error": { "code": "NotFound", "message": "Disk single-shared-disk is not found." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 27 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case not supported by Windows clusters[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/utils/testutil/env_utils.go:26[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: { "error": { "code": "NotFound", "message": "Disk single-shared-disk is not found." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 27 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for csi driver[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:395[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: { "error": { "code": "NotFound", "message": "Disk single-shared-disk is not found." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 22 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:09:53.724[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:09:53.739[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:09:53.757[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:09:53.757[0m I0120 19:09:53.757388 15815 resource_setup.go:62] adding PV (pvc-2b897c81-a62c-4183-9eaa-f9d1e0ccaf18) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:09:53.757[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:09:53.776[0m Jan 20 19:09:53.776: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9n9l9" in namespace "azuredisk-3909" to be "Succeeded or Failed" Jan 20 19:09:53.808: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 31.793515ms Jan 20 19:09:55.828: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.051698878s Jan 20 19:09:57.826: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.049750406s Jan 20 19:09:59.824: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.047769655s Jan 20 19:10:01.841: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064847031s Jan 20 19:10:03.827: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.051084582s ... skipping 16 lines ... Jan 20 19:10:37.827: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=true. Elapsed: 44.050260257s Jan 20 19:10:39.825: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=true. Elapsed: 46.048390377s Jan 20 19:10:41.826: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=false. Elapsed: 48.050104098s Jan 20 19:10:43.838: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=false. Elapsed: 50.061480976s Jan 20 19:10:45.841: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 52.064626926s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:10:45.841[0m Jan 20 19:10:45.844: INFO: Pod "azuredisk-volume-tester-9n9l9" satisfied condition "Succeeded or Failed" Jan 20 19:10:45.844: INFO: deleting Pod "azuredisk-3909"/"azuredisk-volume-tester-9n9l9" Jan 20 19:10:45.895: INFO: Pod azuredisk-volume-tester-9n9l9 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-9n9l9 in namespace azuredisk-3909 [38;5;243m01/20/23 19:10:45.895[0m Jan 20 19:10:45.919: INFO: deleting PVC "azuredisk-3909"/"pvc-ncknn" Jan 20 19:10:45.919: INFO: Deleting PersistentVolumeClaim "pvc-ncknn" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:09:53.724[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:09:53.739[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:09:53.757[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:09:53.757[0m I0120 19:09:53.757388 15815 resource_setup.go:62] adding PV (pvc-2b897c81-a62c-4183-9eaa-f9d1e0ccaf18) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:09:53.757[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:09:53.776[0m Jan 20 19:09:53.776: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9n9l9" in namespace "azuredisk-3909" to be "Succeeded or Failed" Jan 20 19:09:53.808: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 31.793515ms Jan 20 19:09:55.828: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.051698878s Jan 20 19:09:57.826: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.049750406s Jan 20 19:09:59.824: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.047769655s Jan 20 19:10:01.841: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064847031s Jan 20 19:10:03.827: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.051084582s ... skipping 16 lines ... Jan 20 19:10:37.827: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=true. Elapsed: 44.050260257s Jan 20 19:10:39.825: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=true. Elapsed: 46.048390377s Jan 20 19:10:41.826: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=false. Elapsed: 48.050104098s Jan 20 19:10:43.838: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Running", Reason="", readiness=false. Elapsed: 50.061480976s Jan 20 19:10:45.841: INFO: Pod "azuredisk-volume-tester-9n9l9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 52.064626926s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:10:45.841[0m Jan 20 19:10:45.844: INFO: Pod "azuredisk-volume-tester-9n9l9" satisfied condition "Succeeded or Failed" Jan 20 19:10:45.844: INFO: deleting Pod "azuredisk-3909"/"azuredisk-volume-tester-9n9l9" Jan 20 19:10:45.895: INFO: Pod azuredisk-volume-tester-9n9l9 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-9n9l9 in namespace azuredisk-3909 [38;5;243m01/20/23 19:10:45.895[0m Jan 20 19:10:45.919: INFO: deleting PVC "azuredisk-3909"/"pvc-ncknn" Jan 20 19:10:45.919: INFO: Deleting PersistentVolumeClaim "pvc-ncknn" ... skipping 37 lines ... Jan 20 19:11:29.016: INFO: PersistentVolumeClaim pvc-7ng9x found but phase is Pending instead of Bound. Jan 20 19:11:31.032: INFO: PersistentVolumeClaim pvc-7ng9x found and phase=Bound (4.058914148s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:11:31.032[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:11:31.046[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:11:31.063[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:11:31.063[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/20/23 19:11:31.087[0m Jan 20 19:11:31.087: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-df84c" in namespace "azuredisk-8442" to be "Succeeded or Failed" Jan 20 19:11:31.109: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 22.560927ms Jan 20 19:11:33.124: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.037059041s Jan 20 19:11:35.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.038835595s Jan 20 19:11:37.127: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.040054052s Jan 20 19:11:39.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.039554119s Jan 20 19:11:41.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.039415894s ... skipping 19 lines ... Jan 20 19:12:21.128: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=true. Elapsed: 50.040925266s Jan 20 19:12:23.136: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=true. Elapsed: 52.049031007s Jan 20 19:12:25.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=false. Elapsed: 54.039616625s Jan 20 19:12:27.127: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=false. Elapsed: 56.03984062s Jan 20 19:12:29.125: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.038254324s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:12:29.125[0m Jan 20 19:12:29.125: INFO: Pod "azuredisk-volume-tester-df84c" satisfied condition "Succeeded or Failed" Jan 20 19:12:29.125: INFO: deleting Pod "azuredisk-8442"/"azuredisk-volume-tester-df84c" Jan 20 19:12:29.193: INFO: Pod azuredisk-volume-tester-df84c has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-df84c in namespace azuredisk-8442 [38;5;243m01/20/23 19:12:29.193[0m Jan 20 19:12:29.229: INFO: deleting PVC "azuredisk-8442"/"pvc-7ng9x" Jan 20 19:12:29.230: INFO: Deleting PersistentVolumeClaim "pvc-7ng9x" ... skipping 38 lines ... Jan 20 19:11:29.016: INFO: PersistentVolumeClaim pvc-7ng9x found but phase is Pending instead of Bound. Jan 20 19:11:31.032: INFO: PersistentVolumeClaim pvc-7ng9x found and phase=Bound (4.058914148s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:11:31.032[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:11:31.046[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:11:31.063[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:11:31.063[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/20/23 19:11:31.087[0m Jan 20 19:11:31.087: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-df84c" in namespace "azuredisk-8442" to be "Succeeded or Failed" Jan 20 19:11:31.109: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 22.560927ms Jan 20 19:11:33.124: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.037059041s Jan 20 19:11:35.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.038835595s Jan 20 19:11:37.127: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.040054052s Jan 20 19:11:39.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.039554119s Jan 20 19:11:41.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.039415894s ... skipping 19 lines ... Jan 20 19:12:21.128: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=true. Elapsed: 50.040925266s Jan 20 19:12:23.136: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=true. Elapsed: 52.049031007s Jan 20 19:12:25.126: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=false. Elapsed: 54.039616625s Jan 20 19:12:27.127: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Running", Reason="", readiness=false. Elapsed: 56.03984062s Jan 20 19:12:29.125: INFO: Pod "azuredisk-volume-tester-df84c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.038254324s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:12:29.125[0m Jan 20 19:12:29.125: INFO: Pod "azuredisk-volume-tester-df84c" satisfied condition "Succeeded or Failed" Jan 20 19:12:29.125: INFO: deleting Pod "azuredisk-8442"/"azuredisk-volume-tester-df84c" Jan 20 19:12:29.193: INFO: Pod azuredisk-volume-tester-df84c has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-df84c in namespace azuredisk-8442 [38;5;243m01/20/23 19:12:29.193[0m Jan 20 19:12:29.229: INFO: deleting PVC "azuredisk-8442"/"pvc-7ng9x" Jan 20 19:12:29.230: INFO: Deleting PersistentVolumeClaim "pvc-7ng9x" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:13:14.083[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:13:14.098[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:13:14.114[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:13:14.115[0m I0120 19:13:14.115173 15815 resource_setup.go:62] adding PV (pvc-8b9487cb-87e8-4105-b85b-568e7a09ca5b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:13:14.115[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:13:14.144[0m Jan 20 19:13:14.144: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tx98w" in namespace "azuredisk-8467" to be "Succeeded or Failed" Jan 20 19:13:14.188: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 43.401286ms Jan 20 19:13:16.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061669866s Jan 20 19:13:18.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.061469664s Jan 20 19:13:20.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.060482881s Jan 20 19:13:22.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.061118562s Jan 20 19:13:24.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.061552805s ... skipping 24 lines ... Jan 20 19:14:14.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=true. Elapsed: 1m0.061643564s Jan 20 19:14:16.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.06034861s Jan 20 19:14:18.204: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.059657938s Jan 20 19:14:20.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.061185427s Jan 20 19:14:22.207: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m8.062987422s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:14:22.207[0m Jan 20 19:14:22.208: INFO: Pod "azuredisk-volume-tester-tx98w" satisfied condition "Succeeded or Failed" Jan 20 19:14:22.208: INFO: deleting Pod "azuredisk-8467"/"azuredisk-volume-tester-tx98w" Jan 20 19:14:22.270: INFO: Pod azuredisk-volume-tester-tx98w has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-tx98w in namespace azuredisk-8467 [38;5;243m01/20/23 19:14:22.27[0m Jan 20 19:14:22.292: INFO: deleting PVC "azuredisk-8467"/"pvc-d2z65" Jan 20 19:14:22.292: INFO: Deleting PersistentVolumeClaim "pvc-d2z65" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:13:14.083[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:13:14.098[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:13:14.114[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:13:14.115[0m I0120 19:13:14.115173 15815 resource_setup.go:62] adding PV (pvc-8b9487cb-87e8-4105-b85b-568e7a09ca5b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:13:14.115[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:13:14.144[0m Jan 20 19:13:14.144: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tx98w" in namespace "azuredisk-8467" to be "Succeeded or Failed" Jan 20 19:13:14.188: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 43.401286ms Jan 20 19:13:16.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061669866s Jan 20 19:13:18.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.061469664s Jan 20 19:13:20.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.060482881s Jan 20 19:13:22.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.061118562s Jan 20 19:13:24.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.061552805s ... skipping 24 lines ... Jan 20 19:14:14.206: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=true. Elapsed: 1m0.061643564s Jan 20 19:14:16.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.06034861s Jan 20 19:14:18.204: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.059657938s Jan 20 19:14:20.205: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.061185427s Jan 20 19:14:22.207: INFO: Pod "azuredisk-volume-tester-tx98w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m8.062987422s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:14:22.207[0m Jan 20 19:14:22.208: INFO: Pod "azuredisk-volume-tester-tx98w" satisfied condition "Succeeded or Failed" Jan 20 19:14:22.208: INFO: deleting Pod "azuredisk-8467"/"azuredisk-volume-tester-tx98w" Jan 20 19:14:22.270: INFO: Pod azuredisk-volume-tester-tx98w has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-tx98w in namespace azuredisk-8467 [38;5;243m01/20/23 19:14:22.27[0m Jan 20 19:14:22.292: INFO: deleting PVC "azuredisk-8467"/"pvc-d2z65" Jan 20 19:14:22.292: INFO: Deleting PersistentVolumeClaim "pvc-d2z65" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:15:07.158[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:15:07.173[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:15:07.188[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:15:07.189[0m I0120 19:15:07.189088 15815 resource_setup.go:62] adding PV (pvc-74262400-cef5-44bd-a8d1-a900be963426) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:15:07.189[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:15:07.209[0m Jan 20 19:15:07.209: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7mf2j" in namespace "azuredisk-9597" to be "Succeeded or Failed" Jan 20 19:15:07.233: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 23.984945ms Jan 20 19:15:09.251: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.041345739s Jan 20 19:15:11.251: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.041516331s Jan 20 19:15:13.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.040201442s Jan 20 19:15:15.254: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.045155755s Jan 20 19:15:17.257: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.048061281s ... skipping 14 lines ... Jan 20 19:15:47.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=true. Elapsed: 40.039749441s Jan 20 19:15:49.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=true. Elapsed: 42.03987076s Jan 20 19:15:51.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=false. Elapsed: 44.039998848s Jan 20 19:15:53.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=false. Elapsed: 46.039607158s Jan 20 19:15:55.251: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.041717903s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:15:55.251[0m Jan 20 19:15:55.251: INFO: Pod "azuredisk-volume-tester-7mf2j" satisfied condition "Succeeded or Failed" Jan 20 19:15:55.251: INFO: deleting Pod "azuredisk-9597"/"azuredisk-volume-tester-7mf2j" Jan 20 19:15:55.298: INFO: Pod azuredisk-volume-tester-7mf2j has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7mf2j in namespace azuredisk-9597 [38;5;243m01/20/23 19:15:55.298[0m Jan 20 19:15:55.330: INFO: deleting PVC "azuredisk-9597"/"pvc-555wf" Jan 20 19:15:55.330: INFO: Deleting PersistentVolumeClaim "pvc-555wf" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:15:07.158[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:15:07.173[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:15:07.188[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:15:07.189[0m I0120 19:15:07.189088 15815 resource_setup.go:62] adding PV (pvc-74262400-cef5-44bd-a8d1-a900be963426) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:15:07.189[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:15:07.209[0m Jan 20 19:15:07.209: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7mf2j" in namespace "azuredisk-9597" to be "Succeeded or Failed" Jan 20 19:15:07.233: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 23.984945ms Jan 20 19:15:09.251: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.041345739s Jan 20 19:15:11.251: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.041516331s Jan 20 19:15:13.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.040201442s Jan 20 19:15:15.254: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.045155755s Jan 20 19:15:17.257: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.048061281s ... skipping 14 lines ... Jan 20 19:15:47.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=true. Elapsed: 40.039749441s Jan 20 19:15:49.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=true. Elapsed: 42.03987076s Jan 20 19:15:51.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=false. Elapsed: 44.039998848s Jan 20 19:15:53.249: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Running", Reason="", readiness=false. Elapsed: 46.039607158s Jan 20 19:15:55.251: INFO: Pod "azuredisk-volume-tester-7mf2j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.041717903s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:15:55.251[0m Jan 20 19:15:55.251: INFO: Pod "azuredisk-volume-tester-7mf2j" satisfied condition "Succeeded or Failed" Jan 20 19:15:55.251: INFO: deleting Pod "azuredisk-9597"/"azuredisk-volume-tester-7mf2j" Jan 20 19:15:55.298: INFO: Pod azuredisk-volume-tester-7mf2j has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7mf2j in namespace azuredisk-9597 [38;5;243m01/20/23 19:15:55.298[0m Jan 20 19:15:55.330: INFO: deleting PVC "azuredisk-9597"/"pvc-555wf" Jan 20 19:15:55.330: INFO: Deleting PersistentVolumeClaim "pvc-555wf" ... skipping 111 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:16:40.79[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:16:40.808[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:16:40.825[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:16:40.826[0m I0120 19:16:40.826187 15815 resource_setup.go:62] adding PV (pvc-f4c27c14-a0db-416d-a99c-9b450e724fee) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:16:40.826[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/20/23 19:16:40.851[0m Jan 20 19:16:40.851: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-zgnwt" in namespace "azuredisk-114" to be "Error status code" Jan 20 19:16:40.872: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 21.280249ms Jan 20 19:16:42.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.038024322s Jan 20 19:16:44.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.037743225s Jan 20 19:16:46.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.037053103s Jan 20 19:16:48.890: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.039156861s Jan 20 19:16:50.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.037748595s ... skipping 13 lines ... Jan 20 19:17:18.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 38.038058333s Jan 20 19:17:20.887: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 40.036210554s Jan 20 19:17:22.897: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 42.046157644s Jan 20 19:17:24.890: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Running", Reason="", readiness=true. Elapsed: 44.039161907s Jan 20 19:17:26.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Running", Reason="", readiness=true. Elapsed: 46.036657475s Jan 20 19:17:28.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Running", Reason="", readiness=false. Elapsed: 48.037100179s Jan 20 19:17:30.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Failed", Reason="", readiness=false. Elapsed: 50.036833255s [1mSTEP:[0m Saw pod failure [38;5;243m01/20/23 19:17:30.888[0m Jan 20 19:17:30.888: INFO: Pod "azuredisk-volume-tester-zgnwt" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/20/23 19:17:30.889[0m Jan 20 19:17:30.952: INFO: deleting Pod "azuredisk-114"/"azuredisk-volume-tester-zgnwt" Jan 20 19:17:30.976: INFO: Pod azuredisk-volume-tester-zgnwt 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 49 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:16:40.79[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:16:40.808[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:16:40.825[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:16:40.826[0m I0120 19:16:40.826187 15815 resource_setup.go:62] adding PV (pvc-f4c27c14-a0db-416d-a99c-9b450e724fee) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:16:40.826[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/20/23 19:16:40.851[0m Jan 20 19:16:40.851: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-zgnwt" in namespace "azuredisk-114" to be "Error status code" Jan 20 19:16:40.872: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 21.280249ms Jan 20 19:16:42.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.038024322s Jan 20 19:16:44.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.037743225s Jan 20 19:16:46.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.037053103s Jan 20 19:16:48.890: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.039156861s Jan 20 19:16:50.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.037748595s ... skipping 13 lines ... Jan 20 19:17:18.889: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 38.038058333s Jan 20 19:17:20.887: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 40.036210554s Jan 20 19:17:22.897: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Pending", Reason="", readiness=false. Elapsed: 42.046157644s Jan 20 19:17:24.890: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Running", Reason="", readiness=true. Elapsed: 44.039161907s Jan 20 19:17:26.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Running", Reason="", readiness=true. Elapsed: 46.036657475s Jan 20 19:17:28.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Running", Reason="", readiness=false. Elapsed: 48.037100179s Jan 20 19:17:30.888: INFO: Pod "azuredisk-volume-tester-zgnwt": Phase="Failed", Reason="", readiness=false. Elapsed: 50.036833255s [1mSTEP:[0m Saw pod failure [38;5;243m01/20/23 19:17:30.888[0m Jan 20 19:17:30.888: INFO: Pod "azuredisk-volume-tester-zgnwt" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/20/23 19:17:30.889[0m Jan 20 19:17:30.952: INFO: deleting Pod "azuredisk-114"/"azuredisk-volume-tester-zgnwt" Jan 20 19:17:30.976: INFO: Pod azuredisk-volume-tester-zgnwt 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 458 lines ... Jan 20 19:23:20.708: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zbcmr-57bcff96c9\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 20 19:23:22.712: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zbcmr-57bcff96c9\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/20/23 19:23:24.756[0m [1mSTEP:[0m check pod exec [38;5;243m01/20/23 19:23:24.812[0m Jan 20 19:23:24.812: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-1pou37c4.northcentralus.cloudapp.azure.com --kubeconfig=/root/tmp147543868/kubeconfig/kubeconfig.northcentralus.json --namespace=azuredisk-8006 exec azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv -- cmd /c type C:\mnt\test-1\data.txt' Jan 20 19:23:25.392: INFO: rc: 1 Jan 20 19:23:25.392: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv": error running /usr/local/bin/kubectl --server=https://kubetest-1pou37c4.northcentralus.cloudapp.azure.com --kubeconfig=/root/tmp147543868/kubeconfig/kubeconfig.northcentralus.json --namespace=azuredisk-8006 exec azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv -- cmd /c type C:\mnt\test-1\data.txt: Command stdout: stderr: The system cannot find the file specified. command terminated with exit code 1 error: exit status 1. Jan 20 19:23:27.393: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-1pou37c4.northcentralus.cloudapp.azure.com --kubeconfig=/root/tmp147543868/kubeconfig/kubeconfig.northcentralus.json --namespace=azuredisk-8006 exec azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv -- cmd /c type C:\mnt\test-1\data.txt' Jan 20 19:23:28.037: INFO: stderr: "" Jan 20 19:23:28.037: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/20/23 19:23:28.037[0m Jan 20 19:23:28.037: INFO: Deleting pod "azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv" in namespace "azuredisk-8006" ... skipping 80 lines ... Jan 20 19:23:20.708: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zbcmr-57bcff96c9\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 20 19:23:22.712: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 20, 19, 22, 44, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zbcmr-57bcff96c9\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/20/23 19:23:24.756[0m [1mSTEP:[0m check pod exec [38;5;243m01/20/23 19:23:24.812[0m Jan 20 19:23:24.812: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-1pou37c4.northcentralus.cloudapp.azure.com --kubeconfig=/root/tmp147543868/kubeconfig/kubeconfig.northcentralus.json --namespace=azuredisk-8006 exec azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv -- cmd /c type C:\mnt\test-1\data.txt' Jan 20 19:23:25.392: INFO: rc: 1 Jan 20 19:23:25.392: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv": error running /usr/local/bin/kubectl --server=https://kubetest-1pou37c4.northcentralus.cloudapp.azure.com --kubeconfig=/root/tmp147543868/kubeconfig/kubeconfig.northcentralus.json --namespace=azuredisk-8006 exec azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv -- cmd /c type C:\mnt\test-1\data.txt: Command stdout: stderr: The system cannot find the file specified. command terminated with exit code 1 error: exit status 1. Jan 20 19:23:27.393: INFO: Running '/usr/local/bin/kubectl --server=https://kubetest-1pou37c4.northcentralus.cloudapp.azure.com --kubeconfig=/root/tmp147543868/kubeconfig/kubeconfig.northcentralus.json --namespace=azuredisk-8006 exec azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv -- cmd /c type C:\mnt\test-1\data.txt' Jan 20 19:23:28.037: INFO: stderr: "" Jan 20 19:23:28.037: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/20/23 19:23:28.037[0m Jan 20 19:23:28.037: INFO: Deleting pod "azuredisk-volume-tester-zbcmr-57bcff96c9-lfpsv" in namespace "azuredisk-8006" ... skipping 131 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:24:41.451[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:24:41.466[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:24:41.48[0m Jan 20 19:24:41.481: INFO: deleting PVC "azuredisk-1984"/"pvc-8x2q9" Jan 20 19:24:41.481: INFO: Deleting PersistentVolumeClaim "pvc-8x2q9" Jan 20 19:24:41.498: INFO: Waiting up to 5m0s for PersistentVolumeClaim pvc-8x2q9 to be removed {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:168","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2023-01-20T19:24:41Z"} ++ early_exit_handler ++ '[' -n 166 ']' ++ kill -TERM 166 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 4 lines ...