kubernetes-sigs/azuredisk-csi-driver PR #1739 pull-azuredisk-csi-driver-e2e-multi-az-mainv2 #1632800070250270720
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] fix: enhance UpdateCRIWithRetry to fix the cachedClient Get not found… |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 43m6s |
| Revision | 65d9993da0e4f5288b7d01acff01b7161e794111 |
| Refs |
1739 |
... skipping 110 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 187k 0 --:--:-- --:--:-- --:--:-- 187k Downloading https://get.helm.sh/helm-v3.11.1-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-05d207ad2735cc08acb56d9d0d67c39d400fc3e6 || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-05d207ad2735cc08acb56d9d0d67c39d400fc3e6 not found: manifest unknown: manifest tagged by "latest-v2-05d207ad2735cc08acb56d9d0d67c39d400fc3e6" 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-05d207ad2735cc08acb56d9d0d67c39d400fc3e6 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=05d207ad2735cc08acb56d9d0d67c39d400fc3e6 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-03-06T17:55:34Z -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 714 lines ... } } ] } make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-05d207ad2735cc08acb56d9d0d67c39d400fc3e6 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-05d207ad2735cc08acb56d9d0d67c39d400fc3e6 not found: manifest unknown: manifest tagged by "latest-v2-05d207ad2735cc08acb56d9d0d67c39d400fc3e6" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx rm container-builder || true container-builder removed docker buildx create --use --name=container-builder container-builder # enable qemu for arm64 build ... skipping 1039 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 1069 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 294 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:04:04.212[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:04:04.212[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:04:04.245[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:04:04.245[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:04:04.282[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:04:04.282[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:04:04.316[0m Mar 6 18:04:04.316: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7hqrx" in namespace "azuredisk-5230" to be "Succeeded or Failed" Mar 6 18:04:04.354: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 37.23776ms Mar 6 18:04:06.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070528967s Mar 6 18:04:08.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.070623542s Mar 6 18:04:10.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.07074938s Mar 6 18:04:12.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.070619643s Mar 6 18:04:14.386: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.070059905s ... skipping 32 lines ... Mar 6 18:05:20.390: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m16.073194749s Mar 6 18:05:22.386: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m18.069593005s Mar 6 18:05:24.389: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m20.072825847s Mar 6 18:05:26.388: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m22.071323428s Mar 6 18:05:28.389: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m24.072845297s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:05:28.389[0m Mar 6 18:05:28.389: INFO: Pod "azuredisk-volume-tester-7hqrx" satisfied condition "Succeeded or Failed" Mar 6 18:05:28.389: INFO: deleting Pod "azuredisk-5230"/"azuredisk-volume-tester-7hqrx" Mar 6 18:05:28.482: INFO: Pod azuredisk-volume-tester-7hqrx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7hqrx in namespace azuredisk-5230 [38;5;243m03/06/23 18:05:28.482[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:05:28.553[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:05:28.584[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:04:04.212[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:04:04.212[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:04:04.245[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:04:04.245[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:04:04.282[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:04:04.282[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:04:04.316[0m Mar 6 18:04:04.316: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7hqrx" in namespace "azuredisk-5230" to be "Succeeded or Failed" Mar 6 18:04:04.354: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 37.23776ms Mar 6 18:04:06.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070528967s Mar 6 18:04:08.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.070623542s Mar 6 18:04:10.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.07074938s Mar 6 18:04:12.387: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.070619643s Mar 6 18:04:14.386: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.070059905s ... skipping 32 lines ... Mar 6 18:05:20.390: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m16.073194749s Mar 6 18:05:22.386: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m18.069593005s Mar 6 18:05:24.389: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m20.072825847s Mar 6 18:05:26.388: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Pending", Reason="", readiness=false. Elapsed: 1m22.071323428s Mar 6 18:05:28.389: INFO: Pod "azuredisk-volume-tester-7hqrx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m24.072845297s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:05:28.389[0m Mar 6 18:05:28.389: INFO: Pod "azuredisk-volume-tester-7hqrx" satisfied condition "Succeeded or Failed" Mar 6 18:05:28.389: INFO: deleting Pod "azuredisk-5230"/"azuredisk-volume-tester-7hqrx" Mar 6 18:05:28.482: INFO: Pod azuredisk-volume-tester-7hqrx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7hqrx in namespace azuredisk-5230 [38;5;243m03/06/23 18:05:28.482[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:05:28.553[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:05:28.584[0m ... skipping 39 lines ... Mar 6 18:06:11.843: INFO: PersistentVolumeClaim pvc-2llmn found but phase is Pending instead of Bound. Mar 6 18:06:13.876: INFO: PersistentVolumeClaim pvc-2llmn found and phase=Bound (4.117731695s) [1mSTEP:[0m checking the PVC [38;5;243m03/06/23 18:06:13.876[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:06:13.909[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:06:13.945[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:06:13.945[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m03/06/23 18:06:13.978[0m Mar 6 18:06:13.978: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-27jfr" in namespace "azuredisk-7551" to be "Succeeded or Failed" Mar 6 18:06:14.011: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 32.530229ms Mar 6 18:06:16.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065954403s Mar 6 18:06:18.046: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067334942s Mar 6 18:06:20.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065759311s Mar 6 18:06:22.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065834756s Mar 6 18:06:24.046: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067393457s Mar 6 18:06:26.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065506014s Mar 6 18:06:28.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.06571468s Mar 6 18:06:30.045: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066244278s Mar 6 18:06:32.043: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.065035474s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:06:32.044[0m Mar 6 18:06:32.044: INFO: Pod "azuredisk-volume-tester-27jfr" satisfied condition "Succeeded or Failed" Mar 6 18:06:32.044: INFO: deleting Pod "azuredisk-7551"/"azuredisk-volume-tester-27jfr" Mar 6 18:06:32.079: INFO: Pod azuredisk-volume-tester-27jfr has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-27jfr in namespace azuredisk-7551 [38;5;243m03/06/23 18:06:32.079[0m Mar 6 18:06:32.117: INFO: deleting PVC "azuredisk-7551"/"pvc-2llmn" Mar 6 18:06:32.117: INFO: Deleting PersistentVolumeClaim "pvc-2llmn" ... skipping 38 lines ... Mar 6 18:06:11.843: INFO: PersistentVolumeClaim pvc-2llmn found but phase is Pending instead of Bound. Mar 6 18:06:13.876: INFO: PersistentVolumeClaim pvc-2llmn found and phase=Bound (4.117731695s) [1mSTEP:[0m checking the PVC [38;5;243m03/06/23 18:06:13.876[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:06:13.909[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:06:13.945[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:06:13.945[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m03/06/23 18:06:13.978[0m Mar 6 18:06:13.978: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-27jfr" in namespace "azuredisk-7551" to be "Succeeded or Failed" Mar 6 18:06:14.011: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 32.530229ms Mar 6 18:06:16.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065954403s Mar 6 18:06:18.046: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067334942s Mar 6 18:06:20.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065759311s Mar 6 18:06:22.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065834756s Mar 6 18:06:24.046: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067393457s Mar 6 18:06:26.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065506014s Mar 6 18:06:28.044: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.06571468s Mar 6 18:06:30.045: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066244278s Mar 6 18:06:32.043: INFO: Pod "azuredisk-volume-tester-27jfr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.065035474s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:06:32.044[0m Mar 6 18:06:32.044: INFO: Pod "azuredisk-volume-tester-27jfr" satisfied condition "Succeeded or Failed" Mar 6 18:06:32.044: INFO: deleting Pod "azuredisk-7551"/"azuredisk-volume-tester-27jfr" Mar 6 18:06:32.079: INFO: Pod azuredisk-volume-tester-27jfr has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-27jfr in namespace azuredisk-7551 [38;5;243m03/06/23 18:06:32.079[0m Mar 6 18:06:32.117: INFO: deleting PVC "azuredisk-7551"/"pvc-2llmn" Mar 6 18:06:32.117: INFO: Deleting PersistentVolumeClaim "pvc-2llmn" ... skipping 30 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:07:13.176[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:07:13.176[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:07:13.21[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:07:13.211[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:07:13.246[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:07:13.246[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:07:13.278[0m Mar 6 18:07:13.279: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ldvjf" in namespace "azuredisk-1094" to be "Succeeded or Failed" Mar 6 18:07:13.311: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 32.733404ms Mar 6 18:07:15.346: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067013855s Mar 6 18:07:17.347: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06800237s Mar 6 18:07:19.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065833145s Mar 6 18:07:21.345: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066294777s Mar 6 18:07:23.347: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.068939347s ... skipping 11 lines ... Mar 6 18:07:47.345: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 34.066934362s Mar 6 18:07:49.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 36.065459416s Mar 6 18:07:51.346: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 38.067057993s Mar 6 18:07:53.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 40.065173659s Mar 6 18:07:55.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.065496825s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:07:55.344[0m Mar 6 18:07:55.344: INFO: Pod "azuredisk-volume-tester-ldvjf" satisfied condition "Succeeded or Failed" Mar 6 18:07:55.344: INFO: deleting Pod "azuredisk-1094"/"azuredisk-volume-tester-ldvjf" Mar 6 18:07:55.380: INFO: Pod azuredisk-volume-tester-ldvjf has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ldvjf in namespace azuredisk-1094 [38;5;243m03/06/23 18:07:55.38[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:07:55.45[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:07:55.483[0m ... skipping 30 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:07:13.176[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:07:13.176[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:07:13.21[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:07:13.211[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:07:13.246[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:07:13.246[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:07:13.278[0m Mar 6 18:07:13.279: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ldvjf" in namespace "azuredisk-1094" to be "Succeeded or Failed" Mar 6 18:07:13.311: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 32.733404ms Mar 6 18:07:15.346: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067013855s Mar 6 18:07:17.347: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06800237s Mar 6 18:07:19.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065833145s Mar 6 18:07:21.345: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066294777s Mar 6 18:07:23.347: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.068939347s ... skipping 11 lines ... Mar 6 18:07:47.345: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 34.066934362s Mar 6 18:07:49.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 36.065459416s Mar 6 18:07:51.346: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 38.067057993s Mar 6 18:07:53.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Pending", Reason="", readiness=false. Elapsed: 40.065173659s Mar 6 18:07:55.344: INFO: Pod "azuredisk-volume-tester-ldvjf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.065496825s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:07:55.344[0m Mar 6 18:07:55.344: INFO: Pod "azuredisk-volume-tester-ldvjf" satisfied condition "Succeeded or Failed" Mar 6 18:07:55.344: INFO: deleting Pod "azuredisk-1094"/"azuredisk-volume-tester-ldvjf" Mar 6 18:07:55.380: INFO: Pod azuredisk-volume-tester-ldvjf has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ldvjf in namespace azuredisk-1094 [38;5;243m03/06/23 18:07:55.38[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:07:55.45[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:07:55.483[0m ... skipping 29 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:08:21.408[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:08:21.408[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:08:21.441[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:08:21.441[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:08:21.478[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:08:21.478[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:08:21.512[0m Mar 6 18:08:21.512: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-66wf6" in namespace "azuredisk-1988" to be "Succeeded or Failed" Mar 6 18:08:21.548: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 36.389073ms Mar 6 18:08:23.582: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070464555s Mar 6 18:08:25.583: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071418296s Mar 6 18:08:27.582: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069766288s Mar 6 18:08:29.581: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069526707s Mar 6 18:08:31.581: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069253576s ... skipping 6 lines ... Mar 6 18:08:45.581: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 24.069445465s Mar 6 18:08:47.583: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 26.071451416s Mar 6 18:08:49.582: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 28.0700523s Mar 6 18:08:51.584: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 30.071756084s Mar 6 18:08:53.583: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.070827071s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:08:53.583[0m Mar 6 18:08:53.583: INFO: Pod "azuredisk-volume-tester-66wf6" satisfied condition "Succeeded or Failed" Mar 6 18:08:53.583: INFO: deleting Pod "azuredisk-1988"/"azuredisk-volume-tester-66wf6" Mar 6 18:08:53.622: INFO: Pod azuredisk-volume-tester-66wf6 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-66wf6 in namespace azuredisk-1988 [38;5;243m03/06/23 18:08:53.622[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:08:53.695[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:08:53.727[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:08:21.408[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:08:21.408[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:08:21.441[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:08:21.441[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:08:21.478[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:08:21.478[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:08:21.512[0m Mar 6 18:08:21.512: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-66wf6" in namespace "azuredisk-1988" to be "Succeeded or Failed" Mar 6 18:08:21.548: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 36.389073ms Mar 6 18:08:23.582: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070464555s Mar 6 18:08:25.583: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071418296s Mar 6 18:08:27.582: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069766288s Mar 6 18:08:29.581: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069526707s Mar 6 18:08:31.581: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069253576s ... skipping 6 lines ... Mar 6 18:08:45.581: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 24.069445465s Mar 6 18:08:47.583: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 26.071451416s Mar 6 18:08:49.582: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 28.0700523s Mar 6 18:08:51.584: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Pending", Reason="", readiness=false. Elapsed: 30.071756084s Mar 6 18:08:53.583: INFO: Pod "azuredisk-volume-tester-66wf6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.070827071s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:08:53.583[0m Mar 6 18:08:53.583: INFO: Pod "azuredisk-volume-tester-66wf6" satisfied condition "Succeeded or Failed" Mar 6 18:08:53.583: INFO: deleting Pod "azuredisk-1988"/"azuredisk-volume-tester-66wf6" Mar 6 18:08:53.622: INFO: Pod azuredisk-volume-tester-66wf6 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-66wf6 in namespace azuredisk-1988 [38;5;243m03/06/23 18:08:53.622[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:08:53.695[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:08:53.727[0m ... skipping 34 lines ... [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:09:34.84[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:09:34.84[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:09:34.875[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:09:34.875[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m03/06/23 18:09:34.909[0m Mar 6 18:09:52.980: INFO: deleting Pod "azuredisk-1170"/"azuredisk-volume-tester-nq2v7" Mar 6 18:09:53.014: INFO: Error getting logs for pod azuredisk-volume-tester-nq2v7: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-nq2v7) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nq2v7 in namespace azuredisk-1170 [38;5;243m03/06/23 18:09:53.014[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:09:53.079[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:09:53.111[0m Mar 6 18:09:53.111: INFO: deleting PVC "azuredisk-1170"/"pvc-k95zl" Mar 6 18:09:53.111: INFO: Deleting PersistentVolumeClaim "pvc-k95zl" [1mSTEP:[0m waiting for claim's PV "pvc-c6e4a780-ac41-4a0a-a580-e9b9eca13911" to be deleted [38;5;243m03/06/23 18:09:53.144[0m ... skipping 53 lines ... [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:09:34.84[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:09:34.84[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:09:34.875[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:09:34.875[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m03/06/23 18:09:34.909[0m Mar 6 18:09:52.980: INFO: deleting Pod "azuredisk-1170"/"azuredisk-volume-tester-nq2v7" Mar 6 18:09:53.014: INFO: Error getting logs for pod azuredisk-volume-tester-nq2v7: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-nq2v7) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nq2v7 in namespace azuredisk-1170 [38;5;243m03/06/23 18:09:53.014[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:09:53.079[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:09:53.111[0m Mar 6 18:09:53.111: INFO: deleting PVC "azuredisk-1170"/"pvc-k95zl" Mar 6 18:09:53.111: INFO: Deleting PersistentVolumeClaim "pvc-k95zl" [1mSTEP:[0m waiting for claim's PV "pvc-c6e4a780-ac41-4a0a-a580-e9b9eca13911" to be deleted [38;5;243m03/06/23 18:09:53.144[0m ... skipping 50 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:12:19.908[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:12:19.908[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:12:19.943[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:12:19.943[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:12:19.981[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:12:19.981[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:12:20.017[0m Mar 6 18:12:20.017: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-dsb7h" in namespace "azuredisk-6445" to be "Succeeded or Failed" Mar 6 18:12:20.048: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 31.594824ms Mar 6 18:12:22.083: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065731093s Mar 6 18:12:24.081: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.0639121s Mar 6 18:12:26.081: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064207628s Mar 6 18:12:28.081: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064513232s Mar 6 18:12:30.083: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065768695s Mar 6 18:12:32.082: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065693526s Mar 6 18:12:34.084: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.067146954s Mar 6 18:12:36.083: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066527762s Mar 6 18:12:38.087: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.0697698s Mar 6 18:12:40.082: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 20.065352979s Mar 6 18:12:42.084: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.0670273s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:12:42.084[0m Mar 6 18:12:42.084: INFO: Pod "azuredisk-volume-tester-dsb7h" satisfied condition "Succeeded or Failed" Mar 6 18:12:42.084: INFO: deleting Pod "azuredisk-6445"/"azuredisk-volume-tester-dsb7h" Mar 6 18:12:42.147: INFO: Pod azuredisk-volume-tester-dsb7h has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-dsb7h in namespace azuredisk-6445 [38;5;243m03/06/23 18:12:42.147[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:12:42.22[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:12:42.252[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:12:19.908[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:12:19.908[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:12:19.943[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:12:19.943[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:12:19.981[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:12:19.981[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:12:20.017[0m Mar 6 18:12:20.017: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-dsb7h" in namespace "azuredisk-6445" to be "Succeeded or Failed" Mar 6 18:12:20.048: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 31.594824ms Mar 6 18:12:22.083: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065731093s Mar 6 18:12:24.081: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.0639121s Mar 6 18:12:26.081: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064207628s Mar 6 18:12:28.081: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064513232s Mar 6 18:12:30.083: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065768695s Mar 6 18:12:32.082: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065693526s Mar 6 18:12:34.084: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 14.067146954s Mar 6 18:12:36.083: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066527762s Mar 6 18:12:38.087: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.0697698s Mar 6 18:12:40.082: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Pending", Reason="", readiness=false. Elapsed: 20.065352979s Mar 6 18:12:42.084: INFO: Pod "azuredisk-volume-tester-dsb7h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.0670273s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:12:42.084[0m Mar 6 18:12:42.084: INFO: Pod "azuredisk-volume-tester-dsb7h" satisfied condition "Succeeded or Failed" Mar 6 18:12:42.084: INFO: deleting Pod "azuredisk-6445"/"azuredisk-volume-tester-dsb7h" Mar 6 18:12:42.147: INFO: Pod azuredisk-volume-tester-dsb7h has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-dsb7h in namespace azuredisk-6445 [38;5;243m03/06/23 18:12:42.147[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:12:42.22[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:12:42.252[0m ... skipping 37 lines ... [1mSTEP:[0m creating volume in external rg azuredisk-csi-driver-test-9527663a-bc4a-11ed-8169-46c047fb67cb [38;5;243m03/06/23 18:13:24.557[0m [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:13:24.557[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:13:24.557[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:13:24.593[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:13:24.593[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:13:24.63[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:13:24.664[0m Mar 6 18:13:24.665: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vdpwx" in namespace "azuredisk-9841" to be "Succeeded or Failed" Mar 6 18:13:24.698: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.180285ms Mar 6 18:13:26.732: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067055102s Mar 6 18:13:28.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067663271s Mar 6 18:13:30.734: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069273186s Mar 6 18:13:32.732: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066796133s Mar 6 18:13:34.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067647048s ... skipping 3 lines ... Mar 6 18:13:42.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.067599782s Mar 6 18:13:44.732: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.06737179s Mar 6 18:13:46.734: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.06950051s Mar 6 18:13:48.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 24.068167838s Mar 6 18:13:50.731: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.066427474s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:13:50.731[0m Mar 6 18:13:50.733: INFO: Pod "azuredisk-volume-tester-vdpwx" satisfied condition "Succeeded or Failed" Mar 6 18:13:50.733: INFO: deleting Pod "azuredisk-9841"/"azuredisk-volume-tester-vdpwx" Mar 6 18:13:50.772: INFO: Pod azuredisk-volume-tester-vdpwx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vdpwx in namespace azuredisk-9841 [38;5;243m03/06/23 18:13:50.772[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:13:50.843[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:13:50.875[0m ... skipping 37 lines ... [1mSTEP:[0m creating volume in external rg azuredisk-csi-driver-test-9527663a-bc4a-11ed-8169-46c047fb67cb [38;5;243m03/06/23 18:13:24.557[0m [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:13:24.557[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:13:24.557[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:13:24.593[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:13:24.593[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:13:24.63[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:13:24.664[0m Mar 6 18:13:24.665: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vdpwx" in namespace "azuredisk-9841" to be "Succeeded or Failed" Mar 6 18:13:24.698: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.180285ms Mar 6 18:13:26.732: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067055102s Mar 6 18:13:28.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067663271s Mar 6 18:13:30.734: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069273186s Mar 6 18:13:32.732: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066796133s Mar 6 18:13:34.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067647048s ... skipping 3 lines ... Mar 6 18:13:42.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.067599782s Mar 6 18:13:44.732: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.06737179s Mar 6 18:13:46.734: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.06950051s Mar 6 18:13:48.733: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Pending", Reason="", readiness=false. Elapsed: 24.068167838s Mar 6 18:13:50.731: INFO: Pod "azuredisk-volume-tester-vdpwx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.066427474s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:13:50.731[0m Mar 6 18:13:50.733: INFO: Pod "azuredisk-volume-tester-vdpwx" satisfied condition "Succeeded or Failed" Mar 6 18:13:50.733: INFO: deleting Pod "azuredisk-9841"/"azuredisk-volume-tester-vdpwx" Mar 6 18:13:50.772: INFO: Pod azuredisk-volume-tester-vdpwx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vdpwx in namespace azuredisk-9841 [38;5;243m03/06/23 18:13:50.772[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:13:50.843[0m [1mSTEP:[0m checking the PV [38;5;243m03/06/23 18:13:50.875[0m ... skipping 44 lines ... [1mSTEP:[0m creating volume in external rg azuredisk-csi-driver-test-ebe082a6-bc4a-11ed-8169-46c047fb67cb [38;5;243m03/06/23 18:15:49.266[0m [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:15:49.266[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:15:49.267[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:15:49.301[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:15:49.301[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:15:49.335[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:15:49.374[0m Mar 6 18:15:49.374: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-22dgr" in namespace "azuredisk-9175" to be "Succeeded or Failed" Mar 6 18:15:49.416: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 41.922927ms Mar 6 18:15:51.452: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.078523905s Mar 6 18:15:53.450: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.075787515s Mar 6 18:15:55.452: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.077949137s Mar 6 18:15:57.457: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.083566721s Mar 6 18:15:59.448: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.074507579s Mar 6 18:16:01.450: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.076483707s Mar 6 18:16:03.449: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.074765702s Mar 6 18:16:05.451: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.077432901s Mar 6 18:16:07.451: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.076885756s Mar 6 18:16:09.450: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.076329061s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:16:09.45[0m Mar 6 18:16:09.450: INFO: Pod "azuredisk-volume-tester-22dgr" satisfied condition "Succeeded or Failed" Mar 6 18:16:09.450: INFO: deleting Pod "azuredisk-9175"/"azuredisk-volume-tester-22dgr" Mar 6 18:16:09.519: INFO: Pod azuredisk-volume-tester-22dgr has the following logs: hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-22dgr in namespace azuredisk-9175 [38;5;243m03/06/23 18:16:09.519[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:16:09.593[0m ... skipping 57 lines ... [1mSTEP:[0m creating volume in external rg azuredisk-csi-driver-test-ebe082a6-bc4a-11ed-8169-46c047fb67cb [38;5;243m03/06/23 18:15:49.266[0m [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:15:49.266[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:15:49.267[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:15:49.301[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:15:49.301[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:15:49.335[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/06/23 18:15:49.374[0m Mar 6 18:15:49.374: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-22dgr" in namespace "azuredisk-9175" to be "Succeeded or Failed" Mar 6 18:15:49.416: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 41.922927ms Mar 6 18:15:51.452: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.078523905s Mar 6 18:15:53.450: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.075787515s Mar 6 18:15:55.452: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.077949137s Mar 6 18:15:57.457: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.083566721s Mar 6 18:15:59.448: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.074507579s Mar 6 18:16:01.450: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.076483707s Mar 6 18:16:03.449: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.074765702s Mar 6 18:16:05.451: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.077432901s Mar 6 18:16:07.451: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.076885756s Mar 6 18:16:09.450: INFO: Pod "azuredisk-volume-tester-22dgr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.076329061s [1mSTEP:[0m Saw pod success [38;5;243m03/06/23 18:16:09.45[0m Mar 6 18:16:09.450: INFO: Pod "azuredisk-volume-tester-22dgr" satisfied condition "Succeeded or Failed" Mar 6 18:16:09.450: INFO: deleting Pod "azuredisk-9175"/"azuredisk-volume-tester-22dgr" Mar 6 18:16:09.519: INFO: Pod azuredisk-volume-tester-22dgr has the following logs: hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-22dgr in namespace azuredisk-9175 [38;5;243m03/06/23 18:16:09.519[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/06/23 18:16:09.593[0m ... skipping 47 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/06/23 18:17:31.995[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/06/23 18:17:31.995[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/06/23 18:17:32.028[0m [1mSTEP:[0m creating a PVC [38;5;243m03/06/23 18:17:32.028[0m [1mSTEP:[0m setting up the pod [38;5;243m03/06/23 18:17:32.062[0m [1mSTEP:[0m deploying the pod [38;5;243m03/06/23 18:17:32.062[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m03/06/23 18:17:32.095[0m Mar 6 18:17:32.095: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-kxjd9" in namespace "azuredisk-1016" to be "Error status code" Mar 6 18:17:32.130: INFO: Pod "azuredisk-volume-tester-kxjd9": Phase="Pending", Reason="", readiness=false. Elapsed: 34.978006ms Mar 6 18:17:34.164: INFO: Pod "azuredisk-volume-tester-kxjd9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068876954s Mar 6 18:17:36.165: INFO: Pod "azuredisk-volume-tester-kxjd9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069520488s Mar 6 18:17:38.163: INFO: Pod "azuredisk-volume-tester-kxjd9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067724982s Mar 6 18:17:40.163: INFO: Pod "azuredisk-volume-tester-kxjd9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.067344071s Mar 6 18:17:42.163: INFO: Pod "azuredisk-volume-tester-kxjd9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067543022s ... skipping 5 lines ...