kubernetes-sigs/azuredisk-csi-driver PR #1701 pull-azuredisk-csi-driver-e2e-capz-windows-2019-mainv2 #1618645021265760256
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] fix: delete the unnecessary increment of numRecovered in recoverAzVolume |
| Result | ABORTED |
| Tests | 0 failed / 39 succeeded |
| Started | |
| Elapsed | 2h12m |
| Revision | 67f59480f8b4e0b0e9041164949e523bc3148b87 |
| Refs |
1701 |
AzureDisk CSI Driver End-to-End Tests [AfterSuite]
AzureDisk CSI Driver End-to-End Tests [BeforeSuite]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and reschedule a pod with a persistent volume request on failover. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with a persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with multiple persistent volume requests and reschedule on failover.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with multiple persistent volume requests with replicas and reschedule on deletion.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with multiple persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with no persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Controller AzDriverNode [single-az] Should create AzDriverNode resource and report heartbeat.
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create and attach a volume with advanced perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create and attach a volume with basic perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas on node with matching pod affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas on node with matching pod node affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas on node with matching pod node selector
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should not create replicas on node with matching pod anti-affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test pod failover with cordoning a node
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test pod failover with cordoning a node using ZRS
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod with multiple volumes [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod, write and read to it, take a volume snapshot, and create another pod from the snapshot [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod, write to its pv, take a volume snapshot, overwrite data in original pv, create another pod from the snapshot, and read unaltered original data from original pv[disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a statefulset object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume azuredisk with tag [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand and mount it as readOnly in a pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand and resize it [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create multiple PV objects, bind to PVCs and attach all to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create multiple PV objects, bind to PVCs and attach all to different pods on the same node [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should delete AzVolumeAttachment after pod deleted when maxMountReplicaCount == 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should delete PV with reclaimPolicy "Delete" [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should demote AzVolumeAttachment after pod deleted when maxMountReplicaCount > 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should detach disk after pod deleted when maxMountReplicaCount = 0 [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when creating a PremiumV2_LRS disk [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when creating a shared disk [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when reattaching a disk to a new node on DanglingAttachError [disk.csi.azure.com][csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should use a pre-provisioned volume and mount it as readOnly in a pod [disk.csi.azure.com][windows][csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should use a pre-provisioned volume and retain PV with reclaimPolicy "Retain" [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and reschedule a pod with a persistent volume request on failover. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with a persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with multiple persistent volume requests and reschedule on failover.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with multiple persistent volume requests with replicas and reschedule on deletion.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with multiple persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with no persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment If a replica is deleted, should create another replica to replace the previous one
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment If failover happens, should turn replica to primary and create an additional replica for replacement
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment Should create replica azVolumeAttachment object when maxShares > 1
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment Should delete AzVolumeAttachment object properly
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment Should initialize AzVolumeAttachment object's status and append finalizer and create labels
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment number of replicas should converge to assigned maxMountReplicaCount value
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment should garbage collect replica AzVolumeAttachment if no promotion or new primary creation happens in a given period of time
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment should not delete replica AzVolumeAttachment if new primary creation happens within a given period of time after primary failure
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumes Should delete AzVolume object
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumes Should delete AzVolumeAttachment objects with deletion of AzVolume
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumes Should initialize AzVolume object
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create and attach a volume with advanced perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create and attach a volume with basic perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas on node with matching pod affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas on node with matching pod node affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas on node with matching pod node selector
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas spread across zones for zrs
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should not create replicas on node with matching pod anti-affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should not create replicas on node with non-tolerable taint
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test an increase in replicas when scaling up
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test pod failover and check for correct number of replicas
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test pod failover with cordoning a node
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test pod failover with cordoning a node using ZRS
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should check failed replica attachments are recreated after space is made from a volume detaching.
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should clone a volume from an existing volume and read from it [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should clone a volume of larger size than the source volume and make sure the filesystem is appropriately adjusted [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a block volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod with multiple volumes [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod, write and read to it, take a volume snapshot, and create another pod from the snapshot [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod, write to its pv, take a volume snapshot, overwrite data in original pv, create another pod from the snapshot, and read unaltered original data from original pv[disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a raw block volume and a filesystem volume on demand and bind to the same pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a statefulset object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume azuredisk with tag [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand and mount it as readOnly in a pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand and resize it [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create multiple PV objects, bind to PVCs and attach all to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create multiple PV objects, bind to PVCs and attach all to different pods on the same node [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should delete AzVolumeAttachment after pod deleted when maxMountReplicaCount == 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should delete PV with reclaimPolicy "Delete" [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should demote AzVolumeAttachment after pod deleted when maxMountReplicaCount > 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should detach disk after pod deleted when maxMountReplicaCount = 0 [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas spread across zones for zrs
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should not create replicas on node with non-tolerable taint
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test an increase in replicas when scaling up
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test pod failover and check for correct number of replicas
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should check failed replica attachments are recreated after space is made from a volume detaching.
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should clone a volume from an existing volume and read from it [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should clone a volume of larger size than the source volume and make sure the filesystem is appropriately adjusted [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a block volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a raw block volume and a filesystem volume on demand and bind to the same pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should create an inline volume by in-tree driver [kubernetes.io/azure-disk]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when creating a single pod and with replica attachments [disk.csi.azure.com][csi-azuredisk-scheduler-extender]
... skipping 788 lines ... certificate.cert-manager.io "selfsigned-cert" deleted # Create secret for AzureClusterIdentity ./hack/create-identity-secret.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' Error from server (NotFound): secrets "cluster-identity-secret" not found secret/cluster-identity-secret created secret/cluster-identity-secret labeled # Create customized cloud provider configs ./hack/create-custom-cloud-provider-config.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. ... skipping 228 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 194k 0 --:--:-- --:--:-- --:--:-- 194k 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 capzci.azurecr.io/azuredisk-csi:latest-v2-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9 || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9 not found: manifest unknown: manifest tagged by "latest-v2-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9" 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-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-26T16:49:48Z -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 687 lines ... } } ] } make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker pull capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9 not found: manifest unknown: manifest tagged by "latest-v2-b928b5bc739f5d5eff4b9e0ce4000398ab6a35c9" 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 1100 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 831 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" args: - "-csi-address=$(ADDRESS)" - "-v=2" - "-leader-election" - "--leader-election-namespace=kube-system" - '-handle-volume-inuse-error=false' - '-feature-gates=RecoverVolumeExpansionFailure=true' - "-timeout=240s" env: - name: ADDRESS value: /csi/csi.sock volumeMounts: ... skipping 324 lines ... Jan 26 17:02:00.008: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-qlflj] to have phase Bound Jan 26 17:02:00.116: INFO: PersistentVolumeClaim pvc-qlflj found and phase=Bound (108.225158ms) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:02:00.116[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:02:00.23[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:02:00.339[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:02:00.339[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/26/23 17:02:00.452[0m Jan 26 17:02:00.452: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-rtkxw" in namespace "azuredisk-3627" to be "Error status code" Jan 26 17:02:00.560: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 107.798412ms Jan 26 17:02:02.669: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216720538s Jan 26 17:02:04.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218167687s Jan 26 17:02:06.671: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218457406s Jan 26 17:02:08.675: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222846244s Jan 26 17:02:10.669: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.216534114s ... skipping 96 lines ... Jan 26 17:05:24.671: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 3m24.218879983s Jan 26 17:05:26.671: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=true. Elapsed: 3m26.218402074s Jan 26 17:05:28.672: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=true. Elapsed: 3m28.220001296s Jan 26 17:05:30.672: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=true. Elapsed: 3m30.2195948s Jan 26 17:05:32.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.218157606s Jan 26 17:05:34.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.217473526s Jan 26 17:05:36.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Failed", Reason="", readiness=false. Elapsed: 3m36.218218355s [1mSTEP:[0m Saw pod failure [38;5;243m01/26/23 17:05:36.671[0m Jan 26 17:05:36.671: INFO: Pod "azuredisk-volume-tester-rtkxw" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/26/23 17:05:36.671[0m Jan 26 17:05:36.809: INFO: deleting Pod "azuredisk-3627"/"azuredisk-volume-tester-rtkxw" Jan 26 17:05:36.924: INFO: Pod azuredisk-volume-tester-rtkxw 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 55 lines ... Jan 26 17:02:00.008: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-qlflj] to have phase Bound Jan 26 17:02:00.116: INFO: PersistentVolumeClaim pvc-qlflj found and phase=Bound (108.225158ms) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:02:00.116[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:02:00.23[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:02:00.339[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:02:00.339[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/26/23 17:02:00.452[0m Jan 26 17:02:00.452: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-rtkxw" in namespace "azuredisk-3627" to be "Error status code" Jan 26 17:02:00.560: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 107.798412ms Jan 26 17:02:02.669: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216720538s Jan 26 17:02:04.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218167687s Jan 26 17:02:06.671: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218457406s Jan 26 17:02:08.675: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222846244s Jan 26 17:02:10.669: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.216534114s ... skipping 96 lines ... Jan 26 17:05:24.671: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Pending", Reason="", readiness=false. Elapsed: 3m24.218879983s Jan 26 17:05:26.671: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=true. Elapsed: 3m26.218402074s Jan 26 17:05:28.672: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=true. Elapsed: 3m28.220001296s Jan 26 17:05:30.672: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=true. Elapsed: 3m30.2195948s Jan 26 17:05:32.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.218157606s Jan 26 17:05:34.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.217473526s Jan 26 17:05:36.670: INFO: Pod "azuredisk-volume-tester-rtkxw": Phase="Failed", Reason="", readiness=false. Elapsed: 3m36.218218355s [1mSTEP:[0m Saw pod failure [38;5;243m01/26/23 17:05:36.671[0m Jan 26 17:05:36.671: INFO: Pod "azuredisk-volume-tester-rtkxw" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/26/23 17:05:36.671[0m Jan 26 17:05:36.809: INFO: deleting Pod "azuredisk-3627"/"azuredisk-volume-tester-rtkxw" Jan 26 17:05:36.924: INFO: Pod azuredisk-volume-tester-rtkxw 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 84 lines ... Jan 26 17:06:20.646: INFO: PersistentVolumeClaim pvc-gtrq4 found and phase=Bound (108.011175ms) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:06:20.646[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:06:20.755[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:06:20.862[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/26/23 17:06:20.98[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:06:30.053[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:06:30.168[0m Jan 26 17:06:30.168: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xbhmx" in namespace "azuredisk-8270" to be "Succeeded or Failed" Jan 26 17:06:30.276: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 107.931861ms Jan 26 17:06:32.385: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216766832s Jan 26 17:06:34.385: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.216915434s Jan 26 17:06:36.386: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217550643s Jan 26 17:06:38.386: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217391848s Jan 26 17:06:40.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218312161s ... skipping 21 lines ... Jan 26 17:07:24.388: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=true. Elapsed: 54.219290317s Jan 26 17:07:26.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=true. Elapsed: 56.218726565s Jan 26 17:07:28.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=false. Elapsed: 58.218640305s Jan 26 17:07:30.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.218882668s Jan 26 17:07:32.388: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m2.219447753s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:07:32.388[0m Jan 26 17:07:32.388: INFO: Pod "azuredisk-volume-tester-xbhmx" satisfied condition "Succeeded or Failed" Jan 26 17:07:32.388: INFO: deleting Pod "azuredisk-8270"/"azuredisk-volume-tester-xbhmx" Jan 26 17:07:32.528: INFO: Pod azuredisk-volume-tester-xbhmx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-xbhmx in namespace azuredisk-8270 [38;5;243m01/26/23 17:07:32.528[0m Jan 26 17:07:32.875: INFO: deleting PVC "azuredisk-8270"/"pvc-gtrq4" Jan 26 17:07:32.876: INFO: Deleting PersistentVolumeClaim "pvc-gtrq4" ... skipping 37 lines ... Jan 26 17:06:20.646: INFO: PersistentVolumeClaim pvc-gtrq4 found and phase=Bound (108.011175ms) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:06:20.646[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:06:20.755[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:06:20.862[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/26/23 17:06:20.98[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:06:30.053[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:06:30.168[0m Jan 26 17:06:30.168: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xbhmx" in namespace "azuredisk-8270" to be "Succeeded or Failed" Jan 26 17:06:30.276: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 107.931861ms Jan 26 17:06:32.385: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216766832s Jan 26 17:06:34.385: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.216915434s Jan 26 17:06:36.386: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217550643s Jan 26 17:06:38.386: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217391848s Jan 26 17:06:40.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218312161s ... skipping 21 lines ... Jan 26 17:07:24.388: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=true. Elapsed: 54.219290317s Jan 26 17:07:26.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=true. Elapsed: 56.218726565s Jan 26 17:07:28.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=false. Elapsed: 58.218640305s Jan 26 17:07:30.387: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.218882668s Jan 26 17:07:32.388: INFO: Pod "azuredisk-volume-tester-xbhmx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m2.219447753s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:07:32.388[0m Jan 26 17:07:32.388: INFO: Pod "azuredisk-volume-tester-xbhmx" satisfied condition "Succeeded or Failed" Jan 26 17:07:32.388: INFO: deleting Pod "azuredisk-8270"/"azuredisk-volume-tester-xbhmx" Jan 26 17:07:32.528: INFO: Pod azuredisk-volume-tester-xbhmx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-xbhmx in namespace azuredisk-8270 [38;5;243m01/26/23 17:07:32.528[0m Jan 26 17:07:32.875: INFO: deleting PVC "azuredisk-8270"/"pvc-gtrq4" Jan 26 17:07:32.876: INFO: Deleting PersistentVolumeClaim "pvc-gtrq4" ... skipping 150 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/26/23 17:08:27.937[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:08:28.046[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:08:28.155[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:08:28.156[0m I0126 17:08:28.156336 42930 resource_setup.go:62] adding PV (pvc-a4e2c210-a9fc-4756-9ce8-75c2d286a982) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:08:28.156[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:08:28.271[0m Jan 26 17:08:28.271: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zftcf" in namespace "azuredisk-9415" to be "Succeeded or Failed" Jan 26 17:08:28.380: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 108.398329ms Jan 26 17:08:30.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219442634s Jan 26 17:08:32.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.21925848s Jan 26 17:08:34.489: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217491236s Jan 26 17:08:36.492: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220223214s Jan 26 17:08:38.490: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218204853s ... skipping 12 lines ... Jan 26 17:09:04.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=true. Elapsed: 36.219749429s Jan 26 17:09:06.492: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=true. Elapsed: 38.220515284s Jan 26 17:09:08.490: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=false. Elapsed: 40.218671655s Jan 26 17:09:10.492: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=false. Elapsed: 42.220608405s Jan 26 17:09:12.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.219393903s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:09:12.491[0m Jan 26 17:09:12.491: INFO: Pod "azuredisk-volume-tester-zftcf" satisfied condition "Succeeded or Failed" Jan 26 17:09:12.491: INFO: deleting Pod "azuredisk-9415"/"azuredisk-volume-tester-zftcf" Jan 26 17:09:12.618: INFO: Pod azuredisk-volume-tester-zftcf has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-zftcf in namespace azuredisk-9415 [38;5;243m01/26/23 17:09:12.618[0m Jan 26 17:09:12.743: INFO: deleting PVC "azuredisk-9415"/"pvc-gbfxm" Jan 26 17:09:12.743: INFO: Deleting PersistentVolumeClaim "pvc-gbfxm" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:08:27.937[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:08:28.046[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:08:28.155[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:08:28.156[0m I0126 17:08:28.156336 42930 resource_setup.go:62] adding PV (pvc-a4e2c210-a9fc-4756-9ce8-75c2d286a982) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:08:28.156[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:08:28.271[0m Jan 26 17:08:28.271: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zftcf" in namespace "azuredisk-9415" to be "Succeeded or Failed" Jan 26 17:08:28.380: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 108.398329ms Jan 26 17:08:30.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219442634s Jan 26 17:08:32.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.21925848s Jan 26 17:08:34.489: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217491236s Jan 26 17:08:36.492: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220223214s Jan 26 17:08:38.490: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218204853s ... skipping 12 lines ... Jan 26 17:09:04.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=true. Elapsed: 36.219749429s Jan 26 17:09:06.492: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=true. Elapsed: 38.220515284s Jan 26 17:09:08.490: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=false. Elapsed: 40.218671655s Jan 26 17:09:10.492: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Running", Reason="", readiness=false. Elapsed: 42.220608405s Jan 26 17:09:12.491: INFO: Pod "azuredisk-volume-tester-zftcf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.219393903s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:09:12.491[0m Jan 26 17:09:12.491: INFO: Pod "azuredisk-volume-tester-zftcf" satisfied condition "Succeeded or Failed" Jan 26 17:09:12.491: INFO: deleting Pod "azuredisk-9415"/"azuredisk-volume-tester-zftcf" Jan 26 17:09:12.618: INFO: Pod azuredisk-volume-tester-zftcf has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-zftcf in namespace azuredisk-9415 [38;5;243m01/26/23 17:09:12.618[0m Jan 26 17:09:12.743: INFO: deleting PVC "azuredisk-9415"/"pvc-gbfxm" Jan 26 17:09:12.743: INFO: Deleting PersistentVolumeClaim "pvc-gbfxm" ... skipping 37 lines ... Jan 26 17:09:58.263: INFO: PersistentVolumeClaim pvc-zzcwq found but phase is Pending instead of Bound. Jan 26 17:10:00.374: INFO: PersistentVolumeClaim pvc-zzcwq found and phase=Bound (4.328370074s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:10:00.374[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:10:00.483[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:10:00.592[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:10:00.592[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/26/23 17:10:00.705[0m Jan 26 17:10:00.705: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c7mhf" in namespace "azuredisk-3140" to be "Succeeded or Failed" Jan 26 17:10:00.824: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 118.752771ms Jan 26 17:10:02.935: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229765082s Jan 26 17:10:04.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.230523372s Jan 26 17:10:06.934: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.229065952s Jan 26 17:10:08.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.230478029s Jan 26 17:10:10.933: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.228152131s ... skipping 14 lines ... Jan 26 17:10:40.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=true. Elapsed: 40.230822211s Jan 26 17:10:42.935: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=true. Elapsed: 42.22975393s Jan 26 17:10:44.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=false. Elapsed: 44.230771932s Jan 26 17:10:46.935: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=false. Elapsed: 46.230095646s Jan 26 17:10:48.934: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.228888095s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:10:48.934[0m Jan 26 17:10:48.935: INFO: Pod "azuredisk-volume-tester-c7mhf" satisfied condition "Succeeded or Failed" Jan 26 17:10:48.935: INFO: deleting Pod "azuredisk-3140"/"azuredisk-volume-tester-c7mhf" Jan 26 17:10:49.067: INFO: Pod azuredisk-volume-tester-c7mhf has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-c7mhf in namespace azuredisk-3140 [38;5;243m01/26/23 17:10:49.067[0m Jan 26 17:10:49.190: INFO: deleting PVC "azuredisk-3140"/"pvc-zzcwq" Jan 26 17:10:49.190: INFO: Deleting PersistentVolumeClaim "pvc-zzcwq" ... skipping 38 lines ... Jan 26 17:09:58.263: INFO: PersistentVolumeClaim pvc-zzcwq found but phase is Pending instead of Bound. Jan 26 17:10:00.374: INFO: PersistentVolumeClaim pvc-zzcwq found and phase=Bound (4.328370074s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:10:00.374[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:10:00.483[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:10:00.592[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:10:00.592[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/26/23 17:10:00.705[0m Jan 26 17:10:00.705: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c7mhf" in namespace "azuredisk-3140" to be "Succeeded or Failed" Jan 26 17:10:00.824: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 118.752771ms Jan 26 17:10:02.935: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.229765082s Jan 26 17:10:04.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.230523372s Jan 26 17:10:06.934: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.229065952s Jan 26 17:10:08.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.230478029s Jan 26 17:10:10.933: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.228152131s ... skipping 14 lines ... Jan 26 17:10:40.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=true. Elapsed: 40.230822211s Jan 26 17:10:42.935: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=true. Elapsed: 42.22975393s Jan 26 17:10:44.936: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=false. Elapsed: 44.230771932s Jan 26 17:10:46.935: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Running", Reason="", readiness=false. Elapsed: 46.230095646s Jan 26 17:10:48.934: INFO: Pod "azuredisk-volume-tester-c7mhf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.228888095s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:10:48.934[0m Jan 26 17:10:48.935: INFO: Pod "azuredisk-volume-tester-c7mhf" satisfied condition "Succeeded or Failed" Jan 26 17:10:48.935: INFO: deleting Pod "azuredisk-3140"/"azuredisk-volume-tester-c7mhf" Jan 26 17:10:49.067: INFO: Pod azuredisk-volume-tester-c7mhf has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-c7mhf in namespace azuredisk-3140 [38;5;243m01/26/23 17:10:49.067[0m Jan 26 17:10:49.190: INFO: deleting PVC "azuredisk-3140"/"pvc-zzcwq" Jan 26 17:10:49.190: INFO: Deleting PersistentVolumeClaim "pvc-zzcwq" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:11:36.852[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:11:36.96[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:11:37.069[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:11:37.069[0m I0126 17:11:37.069731 42930 resource_setup.go:62] adding PV (pvc-960a9d6a-3acf-4b7a-b35a-dc685bce96cf) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:11:37.069[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:11:37.182[0m Jan 26 17:11:37.183: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-g9s85" in namespace "azuredisk-1490" to be "Succeeded or Failed" Jan 26 17:11:37.291: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 108.339077ms Jan 26 17:11:39.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219033767s Jan 26 17:11:41.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 4.217865419s Jan 26 17:11:43.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217627743s Jan 26 17:11:45.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217267501s Jan 26 17:11:47.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 10.217519651s ... skipping 15 lines ... Jan 26 17:12:19.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=true. Elapsed: 42.219354601s Jan 26 17:12:21.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=true. Elapsed: 44.219032919s Jan 26 17:12:23.403: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=false. Elapsed: 46.220048093s Jan 26 17:12:25.403: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=false. Elapsed: 48.220262409s Jan 26 17:12:27.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.219774917s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:12:27.402[0m Jan 26 17:12:27.403: INFO: Pod "azuredisk-volume-tester-g9s85" satisfied condition "Succeeded or Failed" Jan 26 17:12:27.403: INFO: deleting Pod "azuredisk-1490"/"azuredisk-volume-tester-g9s85" Jan 26 17:12:27.532: INFO: Pod azuredisk-volume-tester-g9s85 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g9s85 in namespace azuredisk-1490 [38;5;243m01/26/23 17:12:27.532[0m Jan 26 17:12:27.654: INFO: deleting PVC "azuredisk-1490"/"pvc-28qvf" Jan 26 17:12:27.654: INFO: Deleting PersistentVolumeClaim "pvc-28qvf" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:11:36.852[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:11:36.96[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:11:37.069[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:11:37.069[0m I0126 17:11:37.069731 42930 resource_setup.go:62] adding PV (pvc-960a9d6a-3acf-4b7a-b35a-dc685bce96cf) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:11:37.069[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:11:37.182[0m Jan 26 17:11:37.183: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-g9s85" in namespace "azuredisk-1490" to be "Succeeded or Failed" Jan 26 17:11:37.291: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 108.339077ms Jan 26 17:11:39.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219033767s Jan 26 17:11:41.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 4.217865419s Jan 26 17:11:43.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217627743s Jan 26 17:11:45.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217267501s Jan 26 17:11:47.400: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Pending", Reason="", readiness=false. Elapsed: 10.217519651s ... skipping 15 lines ... Jan 26 17:12:19.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=true. Elapsed: 42.219354601s Jan 26 17:12:21.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=true. Elapsed: 44.219032919s Jan 26 17:12:23.403: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=false. Elapsed: 46.220048093s Jan 26 17:12:25.403: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Running", Reason="", readiness=false. Elapsed: 48.220262409s Jan 26 17:12:27.402: INFO: Pod "azuredisk-volume-tester-g9s85": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.219774917s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:12:27.402[0m Jan 26 17:12:27.403: INFO: Pod "azuredisk-volume-tester-g9s85" satisfied condition "Succeeded or Failed" Jan 26 17:12:27.403: INFO: deleting Pod "azuredisk-1490"/"azuredisk-volume-tester-g9s85" Jan 26 17:12:27.532: INFO: Pod azuredisk-volume-tester-g9s85 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g9s85 in namespace azuredisk-1490 [38;5;243m01/26/23 17:12:27.532[0m Jan 26 17:12:27.654: INFO: deleting PVC "azuredisk-1490"/"pvc-28qvf" Jan 26 17:12:27.654: INFO: Deleting PersistentVolumeClaim "pvc-28qvf" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:13:15.381[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:13:15.49[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:13:15.598[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:13:15.598[0m I0126 17:13:15.598720 42930 resource_setup.go:62] adding PV (pvc-edf6dea7-9a67-4834-86e8-1397f2977088) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:13:15.598[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:13:15.713[0m Jan 26 17:13:15.713: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cbr78" in namespace "azuredisk-4523" to be "Succeeded or Failed" Jan 26 17:13:15.825: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 111.568507ms Jan 26 17:13:17.934: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220464451s Jan 26 17:13:19.934: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220422472s Jan 26 17:13:21.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221234524s Jan 26 17:13:23.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 8.221801952s Jan 26 17:13:25.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 10.221941142s ... skipping 14 lines ... Jan 26 17:13:55.936: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=true. Elapsed: 40.222625064s Jan 26 17:13:57.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=true. Elapsed: 42.221575604s Jan 26 17:13:59.936: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=false. Elapsed: 44.223114398s Jan 26 17:14:01.939: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=false. Elapsed: 46.22593227s Jan 26 17:14:03.934: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.220973335s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:14:03.934[0m Jan 26 17:14:03.934: INFO: Pod "azuredisk-volume-tester-cbr78" satisfied condition "Succeeded or Failed" Jan 26 17:14:03.934: INFO: deleting Pod "azuredisk-4523"/"azuredisk-volume-tester-cbr78" Jan 26 17:14:04.061: INFO: Pod azuredisk-volume-tester-cbr78 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cbr78 in namespace azuredisk-4523 [38;5;243m01/26/23 17:14:04.061[0m Jan 26 17:14:04.178: INFO: deleting PVC "azuredisk-4523"/"pvc-4tp4h" Jan 26 17:14:04.179: INFO: Deleting PersistentVolumeClaim "pvc-4tp4h" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:13:15.381[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:13:15.49[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:13:15.598[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:13:15.598[0m I0126 17:13:15.598720 42930 resource_setup.go:62] adding PV (pvc-edf6dea7-9a67-4834-86e8-1397f2977088) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:13:15.598[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:13:15.713[0m Jan 26 17:13:15.713: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cbr78" in namespace "azuredisk-4523" to be "Succeeded or Failed" Jan 26 17:13:15.825: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 111.568507ms Jan 26 17:13:17.934: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220464451s Jan 26 17:13:19.934: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220422472s Jan 26 17:13:21.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221234524s Jan 26 17:13:23.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 8.221801952s Jan 26 17:13:25.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Pending", Reason="", readiness=false. Elapsed: 10.221941142s ... skipping 14 lines ... Jan 26 17:13:55.936: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=true. Elapsed: 40.222625064s Jan 26 17:13:57.935: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=true. Elapsed: 42.221575604s Jan 26 17:13:59.936: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=false. Elapsed: 44.223114398s Jan 26 17:14:01.939: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Running", Reason="", readiness=false. Elapsed: 46.22593227s Jan 26 17:14:03.934: INFO: Pod "azuredisk-volume-tester-cbr78": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.220973335s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:14:03.934[0m Jan 26 17:14:03.934: INFO: Pod "azuredisk-volume-tester-cbr78" satisfied condition "Succeeded or Failed" Jan 26 17:14:03.934: INFO: deleting Pod "azuredisk-4523"/"azuredisk-volume-tester-cbr78" Jan 26 17:14:04.061: INFO: Pod azuredisk-volume-tester-cbr78 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cbr78 in namespace azuredisk-4523 [38;5;243m01/26/23 17:14:04.061[0m Jan 26 17:14:04.178: INFO: deleting PVC "azuredisk-4523"/"pvc-4tp4h" Jan 26 17:14:04.179: INFO: Deleting PersistentVolumeClaim "pvc-4tp4h" ... skipping 111 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:14:54.917[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:14:55.024[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:14:55.132[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:14:55.132[0m I0126 17:14:55.132694 42930 resource_setup.go:62] adding PV (pvc-c37c42cc-0889-4664-b21e-52b05c9a269c) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:14:55.132[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/26/23 17:14:55.244[0m Jan 26 17:14:55.244: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-cl2b6" in namespace "azuredisk-5836" to be "Error status code" Jan 26 17:14:55.353: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 109.006867ms Jan 26 17:14:57.462: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217475474s Jan 26 17:14:59.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218614101s Jan 26 17:15:01.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218859826s Jan 26 17:15:03.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219222019s Jan 26 17:15:05.462: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.217462415s ... skipping 28 lines ... Jan 26 17:16:03.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m8.219111311s Jan 26 17:16:05.464: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=true. Elapsed: 1m10.219595238s Jan 26 17:16:07.464: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=true. Elapsed: 1m12.220059782s Jan 26 17:16:09.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=true. Elapsed: 1m14.218965302s Jan 26 17:16:11.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.219113579s Jan 26 17:16:13.466: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.222136478s Jan 26 17:16:15.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Failed", Reason="", readiness=false. Elapsed: 1m20.218652448s [1mSTEP:[0m Saw pod failure [38;5;243m01/26/23 17:16:15.463[0m Jan 26 17:16:15.463: INFO: Pod "azuredisk-volume-tester-cl2b6" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/26/23 17:16:15.463[0m Jan 26 17:16:15.596: INFO: deleting Pod "azuredisk-5836"/"azuredisk-volume-tester-cl2b6" Jan 26 17:16:15.708: INFO: Pod azuredisk-volume-tester-cl2b6 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 52 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:14:54.917[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:14:55.024[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:14:55.132[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:14:55.132[0m I0126 17:14:55.132694 42930 resource_setup.go:62] adding PV (pvc-c37c42cc-0889-4664-b21e-52b05c9a269c) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:14:55.132[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/26/23 17:14:55.244[0m Jan 26 17:14:55.244: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-cl2b6" in namespace "azuredisk-5836" to be "Error status code" Jan 26 17:14:55.353: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 109.006867ms Jan 26 17:14:57.462: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217475474s Jan 26 17:14:59.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218614101s Jan 26 17:15:01.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218859826s Jan 26 17:15:03.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219222019s Jan 26 17:15:05.462: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.217462415s ... skipping 28 lines ... Jan 26 17:16:03.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Pending", Reason="", readiness=false. Elapsed: 1m8.219111311s Jan 26 17:16:05.464: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=true. Elapsed: 1m10.219595238s Jan 26 17:16:07.464: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=true. Elapsed: 1m12.220059782s Jan 26 17:16:09.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=true. Elapsed: 1m14.218965302s Jan 26 17:16:11.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.219113579s Jan 26 17:16:13.466: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.222136478s Jan 26 17:16:15.463: INFO: Pod "azuredisk-volume-tester-cl2b6": Phase="Failed", Reason="", readiness=false. Elapsed: 1m20.218652448s [1mSTEP:[0m Saw pod failure [38;5;243m01/26/23 17:16:15.463[0m Jan 26 17:16:15.463: INFO: Pod "azuredisk-volume-tester-cl2b6" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/26/23 17:16:15.463[0m Jan 26 17:16:15.596: INFO: deleting Pod "azuredisk-5836"/"azuredisk-volume-tester-cl2b6" Jan 26 17:16:15.708: INFO: Pod azuredisk-volume-tester-cl2b6 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 469 lines ... Jan 26 17:22:30.842: 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, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-9n28b-5659b76bf9\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 26 17:22:32.840: 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, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-9n28b-5659b76bf9\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 17:22:35.059[0m [1mSTEP:[0m check pod exec [38;5;243m01/26/23 17:22:35.386[0m Jan 26 17:22:35.386: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-4929 exec azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:22:36.616: INFO: rc: 1 Jan 26 17:22:36.616: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-4929 exec azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt -- 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 26 17:22:38.616: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-4929 exec azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:22:39.799: INFO: stderr: "" Jan 26 17:22:39.799: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/26/23 17:22:39.799[0m Jan 26 17:22:39.799: INFO: Deleting pod "azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt" in namespace "azuredisk-4929" ... skipping 79 lines ... Jan 26 17:22:30.842: 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, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-9n28b-5659b76bf9\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 26 17:22:32.840: 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, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 17, 21, 54, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-9n28b-5659b76bf9\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 17:22:35.059[0m [1mSTEP:[0m check pod exec [38;5;243m01/26/23 17:22:35.386[0m Jan 26 17:22:35.386: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-4929 exec azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:22:36.616: INFO: rc: 1 Jan 26 17:22:36.616: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-4929 exec azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt -- 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 26 17:22:38.616: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-4929 exec azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:22:39.799: INFO: stderr: "" Jan 26 17:22:39.799: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/26/23 17:22:39.799[0m Jan 26 17:22:39.799: INFO: Deleting pod "azuredisk-volume-tester-9n28b-5659b76bf9-hm4jt" in namespace "azuredisk-4929" ... skipping 309 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:24:11.758[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:24:11.866[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:24:11.975[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:24:11.975[0m I0126 17:24:11.975485 42930 resource_setup.go:62] adding PV (pvc-67f074d7-2870-42f3-8135-a58c64c5149e) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:24:11.975[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:24:12.09[0m Jan 26 17:24:12.090: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z7j6c" in namespace "azuredisk-4045" to be "Succeeded or Failed" Jan 26 17:24:12.200: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 110.153535ms Jan 26 17:24:14.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220430694s Jan 26 17:24:16.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220570821s Jan 26 17:24:18.314: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.22389455s Jan 26 17:24:20.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.22086557s Jan 26 17:24:22.312: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.221671766s ... skipping 32 lines ... Jan 26 17:25:28.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=true. Elapsed: 1m16.221048918s Jan 26 17:25:30.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.220690407s Jan 26 17:25:32.310: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.219727928s Jan 26 17:25:34.312: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.221720652s Jan 26 17:25:36.312: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m24.221969136s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:25:36.312[0m Jan 26 17:25:36.312: INFO: Pod "azuredisk-volume-tester-z7j6c" satisfied condition "Succeeded or Failed" Jan 26 17:25:36.312: INFO: deleting Pod "azuredisk-4045"/"azuredisk-volume-tester-z7j6c" Jan 26 17:25:36.444: INFO: Pod azuredisk-volume-tester-z7j6c has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-z7j6c in namespace azuredisk-4045 [38;5;243m01/26/23 17:25:36.444[0m ... skipping 90 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:24:11.758[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:24:11.866[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:24:11.975[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:24:11.975[0m I0126 17:24:11.975485 42930 resource_setup.go:62] adding PV (pvc-67f074d7-2870-42f3-8135-a58c64c5149e) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:24:11.975[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:24:12.09[0m Jan 26 17:24:12.090: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z7j6c" in namespace "azuredisk-4045" to be "Succeeded or Failed" Jan 26 17:24:12.200: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 110.153535ms Jan 26 17:24:14.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220430694s Jan 26 17:24:16.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220570821s Jan 26 17:24:18.314: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.22389455s Jan 26 17:24:20.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.22086557s Jan 26 17:24:22.312: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.221671766s ... skipping 32 lines ... Jan 26 17:25:28.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=true. Elapsed: 1m16.221048918s Jan 26 17:25:30.311: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.220690407s Jan 26 17:25:32.310: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.219727928s Jan 26 17:25:34.312: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.221720652s Jan 26 17:25:36.312: INFO: Pod "azuredisk-volume-tester-z7j6c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m24.221969136s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:25:36.312[0m Jan 26 17:25:36.312: INFO: Pod "azuredisk-volume-tester-z7j6c" satisfied condition "Succeeded or Failed" Jan 26 17:25:36.312: INFO: deleting Pod "azuredisk-4045"/"azuredisk-volume-tester-z7j6c" Jan 26 17:25:36.444: INFO: Pod azuredisk-volume-tester-z7j6c has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-z7j6c in namespace azuredisk-4045 [38;5;243m01/26/23 17:25:36.444[0m ... skipping 95 lines ... Jan 26 17:26:44.948: INFO: PersistentVolumeClaim pvc-zszxx found but phase is Pending instead of Bound. Jan 26 17:26:47.057: INFO: PersistentVolumeClaim pvc-zszxx found and phase=Bound (4.326334052s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:26:47.057[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:26:47.166[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:26:47.274[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:26:47.275[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:26:47.392[0m Jan 26 17:26:47.392: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5rbw8" in namespace "azuredisk-5602" to be "Succeeded or Failed" Jan 26 17:26:47.500: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 107.751526ms Jan 26 17:26:49.610: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217234673s Jan 26 17:26:51.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218770189s Jan 26 17:26:53.610: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217682627s Jan 26 17:26:55.610: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.21772066s Jan 26 17:26:57.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218162062s ... skipping 27 lines ... Jan 26 17:27:53.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=true. Elapsed: 1m6.218880156s Jan 26 17:27:55.613: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=true. Elapsed: 1m8.22015921s Jan 26 17:27:57.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.218768699s Jan 26 17:27:59.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.218121798s Jan 26 17:28:01.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m14.218597727s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:28:01.611[0m Jan 26 17:28:01.611: INFO: Pod "azuredisk-volume-tester-5rbw8" satisfied condition "Succeeded or Failed" Jan 26 17:28:01.719: INFO: deleting Pod "azuredisk-5602"/"azuredisk-volume-tester-5rbw8" Jan 26 17:28:01.845: INFO: Pod azuredisk-volume-tester-5rbw8 has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-5rbw8 in namespace azuredisk-5602 [38;5;243m01/26/23 17:28:01.845[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/26/23 17:28:01.966[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/26/23 17:28:22.184[0m [1mSTEP:[0m Prow test resource group: capz-kyk3l0 [38;5;243m01/26/23 17:28:22.184[0m ... skipping 16 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:28:44.47[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:28:44.578[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:28:44.687[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:28:44.687[0m I0126 17:28:44.687487 42930 resource_setup.go:62] adding PV (pvc-bc49628e-532b-4ba0-b162-985e6d799ba7) to pod () [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/26/23 17:28:44.687[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:28:44.803[0m Jan 26 17:28:44.803: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mqrth" in namespace "azuredisk-5602" to be "Succeeded or Failed" Jan 26 17:28:44.914: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 111.21653ms Jan 26 17:28:47.029: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226012772s Jan 26 17:28:49.024: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 4.221104589s Jan 26 17:28:51.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221637028s Jan 26 17:28:53.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222101441s Jan 26 17:28:55.024: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 10.220972433s ... skipping 7 lines ... Jan 26 17:29:11.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=true. Elapsed: 26.221721165s Jan 26 17:29:13.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=true. Elapsed: 28.222384379s Jan 26 17:29:15.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=false. Elapsed: 30.22206556s Jan 26 17:29:17.027: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=false. Elapsed: 32.223864308s Jan 26 17:29:19.027: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.224375775s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:29:19.028[0m Jan 26 17:29:19.028: INFO: Pod "azuredisk-volume-tester-mqrth" satisfied condition "Succeeded or Failed" Jan 26 17:29:19.028: INFO: deleting Pod "azuredisk-5602"/"azuredisk-volume-tester-mqrth" Jan 26 17:29:19.147: INFO: Pod azuredisk-volume-tester-mqrth has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-mqrth in namespace azuredisk-5602 [38;5;243m01/26/23 17:29:19.147[0m Jan 26 17:29:19.266: INFO: deleting PVC "azuredisk-5602"/"pvc-cjwcl" Jan 26 17:29:19.266: INFO: Deleting PersistentVolumeClaim "pvc-cjwcl" ... skipping 12 lines ... Jan 26 17:30:00.478: INFO: Claim "pvc-cjwcl" in namespace "azuredisk-5602" doesn't exist in the system Jan 26 17:30:00.478: INFO: deleting StorageClass azuredisk-5602-disk.csi.azure.com-dynamic-sc-qqg29 [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-wq84n [38;5;243m01/26/23 17:30:00.59[0m Jan 26 17:30:00.704: INFO: skip deleting VolumeSnapshotClass azuredisk-5602-disk.csi.azure.com-dynamic-sc-wdp64 Jan 26 17:30:00.704: INFO: Deleting resource group azuredisk-csi-driver-test-d4f94020-9d9e-11ed-b421-72101b7cf8e1 Jan 26 17:31:19.524: INFO: deleting Pod "azuredisk-5602"/"azuredisk-volume-tester-5rbw8" Jan 26 17:31:19.635: INFO: Error getting logs for pod azuredisk-volume-tester-5rbw8: the server could not find the requested resource (get pods azuredisk-volume-tester-5rbw8) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-5rbw8 in namespace azuredisk-5602 [38;5;243m01/26/23 17:31:19.635[0m Jan 26 17:31:19.743: INFO: deleting PVC "azuredisk-5602"/"pvc-zszxx" Jan 26 17:31:19.743: INFO: Deleting PersistentVolumeClaim "pvc-zszxx" [1mSTEP:[0m waiting for claim's PV "pvc-e29284bc-4ef7-4882-9828-0e36340c392e" to be deleted [38;5;243m01/26/23 17:31:19.858[0m Jan 26 17:31:19.858: INFO: Waiting up to 10m0s for PersistentVolume pvc-e29284bc-4ef7-4882-9828-0e36340c392e to get deleted Jan 26 17:31:19.967: INFO: PersistentVolume pvc-e29284bc-4ef7-4882-9828-0e36340c392e found and phase=Released (108.377964ms) ... skipping 29 lines ... Jan 26 17:26:44.948: INFO: PersistentVolumeClaim pvc-zszxx found but phase is Pending instead of Bound. Jan 26 17:26:47.057: INFO: PersistentVolumeClaim pvc-zszxx found and phase=Bound (4.326334052s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:26:47.057[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:26:47.166[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:26:47.274[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:26:47.275[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:26:47.392[0m Jan 26 17:26:47.392: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5rbw8" in namespace "azuredisk-5602" to be "Succeeded or Failed" Jan 26 17:26:47.500: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 107.751526ms Jan 26 17:26:49.610: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217234673s Jan 26 17:26:51.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218770189s Jan 26 17:26:53.610: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217682627s Jan 26 17:26:55.610: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.21772066s Jan 26 17:26:57.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218162062s ... skipping 27 lines ... Jan 26 17:27:53.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=true. Elapsed: 1m6.218880156s Jan 26 17:27:55.613: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=true. Elapsed: 1m8.22015921s Jan 26 17:27:57.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.218768699s Jan 26 17:27:59.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.218121798s Jan 26 17:28:01.611: INFO: Pod "azuredisk-volume-tester-5rbw8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m14.218597727s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:28:01.611[0m Jan 26 17:28:01.611: INFO: Pod "azuredisk-volume-tester-5rbw8" satisfied condition "Succeeded or Failed" Jan 26 17:28:01.719: INFO: deleting Pod "azuredisk-5602"/"azuredisk-volume-tester-5rbw8" Jan 26 17:28:01.845: INFO: Pod azuredisk-volume-tester-5rbw8 has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-5rbw8 in namespace azuredisk-5602 [38;5;243m01/26/23 17:28:01.845[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/26/23 17:28:01.966[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/26/23 17:28:22.184[0m [1mSTEP:[0m Prow test resource group: capz-kyk3l0 [38;5;243m01/26/23 17:28:22.184[0m ... skipping 16 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:28:44.47[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:28:44.578[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:28:44.687[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:28:44.687[0m I0126 17:28:44.687487 42930 resource_setup.go:62] adding PV (pvc-bc49628e-532b-4ba0-b162-985e6d799ba7) to pod () [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/26/23 17:28:44.687[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:28:44.803[0m Jan 26 17:28:44.803: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mqrth" in namespace "azuredisk-5602" to be "Succeeded or Failed" Jan 26 17:28:44.914: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 111.21653ms Jan 26 17:28:47.029: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 2.226012772s Jan 26 17:28:49.024: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 4.221104589s Jan 26 17:28:51.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221637028s Jan 26 17:28:53.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 8.222101441s Jan 26 17:28:55.024: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Pending", Reason="", readiness=false. Elapsed: 10.220972433s ... skipping 7 lines ... Jan 26 17:29:11.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=true. Elapsed: 26.221721165s Jan 26 17:29:13.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=true. Elapsed: 28.222384379s Jan 26 17:29:15.025: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=false. Elapsed: 30.22206556s Jan 26 17:29:17.027: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Running", Reason="", readiness=false. Elapsed: 32.223864308s Jan 26 17:29:19.027: INFO: Pod "azuredisk-volume-tester-mqrth": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.224375775s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:29:19.028[0m Jan 26 17:29:19.028: INFO: Pod "azuredisk-volume-tester-mqrth" satisfied condition "Succeeded or Failed" Jan 26 17:29:19.028: INFO: deleting Pod "azuredisk-5602"/"azuredisk-volume-tester-mqrth" Jan 26 17:29:19.147: INFO: Pod azuredisk-volume-tester-mqrth has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-mqrth in namespace azuredisk-5602 [38;5;243m01/26/23 17:29:19.147[0m Jan 26 17:29:19.266: INFO: deleting PVC "azuredisk-5602"/"pvc-cjwcl" Jan 26 17:29:19.266: INFO: Deleting PersistentVolumeClaim "pvc-cjwcl" ... skipping 12 lines ... Jan 26 17:30:00.478: INFO: Claim "pvc-cjwcl" in namespace "azuredisk-5602" doesn't exist in the system Jan 26 17:30:00.478: INFO: deleting StorageClass azuredisk-5602-disk.csi.azure.com-dynamic-sc-qqg29 [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-wq84n [38;5;243m01/26/23 17:30:00.59[0m Jan 26 17:30:00.704: INFO: skip deleting VolumeSnapshotClass azuredisk-5602-disk.csi.azure.com-dynamic-sc-wdp64 Jan 26 17:30:00.704: INFO: Deleting resource group azuredisk-csi-driver-test-d4f94020-9d9e-11ed-b421-72101b7cf8e1 Jan 26 17:31:19.524: INFO: deleting Pod "azuredisk-5602"/"azuredisk-volume-tester-5rbw8" Jan 26 17:31:19.635: INFO: Error getting logs for pod azuredisk-volume-tester-5rbw8: the server could not find the requested resource (get pods azuredisk-volume-tester-5rbw8) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-5rbw8 in namespace azuredisk-5602 [38;5;243m01/26/23 17:31:19.635[0m Jan 26 17:31:19.743: INFO: deleting PVC "azuredisk-5602"/"pvc-zszxx" Jan 26 17:31:19.743: INFO: Deleting PersistentVolumeClaim "pvc-zszxx" [1mSTEP:[0m waiting for claim's PV "pvc-e29284bc-4ef7-4882-9828-0e36340c392e" to be deleted [38;5;243m01/26/23 17:31:19.858[0m Jan 26 17:31:19.858: INFO: Waiting up to 10m0s for PersistentVolume pvc-e29284bc-4ef7-4882-9828-0e36340c392e to get deleted Jan 26 17:31:19.967: INFO: PersistentVolume pvc-e29284bc-4ef7-4882-9828-0e36340c392e found and phase=Released (108.377964ms) ... skipping 28 lines ... Jan 26 17:31:34.459: INFO: PersistentVolumeClaim pvc-6mnmb found but phase is Pending instead of Bound. Jan 26 17:31:36.568: INFO: PersistentVolumeClaim pvc-6mnmb found and phase=Bound (4.327660933s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:31:36.568[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:31:36.676[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:31:36.784[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:31:36.785[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:31:36.898[0m Jan 26 17:31:36.898: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m6jsm" in namespace "azuredisk-2751" to be "Succeeded or Failed" Jan 26 17:31:37.006: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 108.086971ms Jan 26 17:31:39.116: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217666205s Jan 26 17:31:41.116: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.217516973s Jan 26 17:31:43.118: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.219337759s Jan 26 17:31:45.115: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217052688s Jan 26 17:31:47.117: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218762784s ... skipping 15 lines ... Jan 26 17:32:19.122: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=true. Elapsed: 42.223453244s Jan 26 17:32:21.122: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=false. Elapsed: 44.223539829s Jan 26 17:32:23.118: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=false. Elapsed: 46.21947197s Jan 26 17:32:25.117: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=false. Elapsed: 48.218981113s Jan 26 17:32:27.117: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.218868964s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:32:27.117[0m Jan 26 17:32:27.117: INFO: Pod "azuredisk-volume-tester-m6jsm" satisfied condition "Succeeded or Failed" Jan 26 17:32:27.231: INFO: deleting Pod "azuredisk-2751"/"azuredisk-volume-tester-m6jsm" Jan 26 17:32:27.352: INFO: Pod azuredisk-volume-tester-m6jsm has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-m6jsm in namespace azuredisk-2751 [38;5;243m01/26/23 17:32:27.352[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/26/23 17:32:27.472[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/26/23 17:32:47.689[0m [1mSTEP:[0m Prow test resource group: capz-kyk3l0 [38;5;243m01/26/23 17:32:47.69[0m ... skipping 35 lines ... [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:33:34.752[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:33:34.861[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:33:34.861[0m I0126 17:33:34.861988 42930 resource_setup.go:62] adding PV (pvc-d8c80410-192d-4dc6-b298-fc8efe197e8a) to pod () [1mSTEP:[0m Set pod anti-affinity to make sure two pods are scheduled on different nodes [38;5;243m01/26/23 17:33:34.862[0m [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/26/23 17:33:34.862[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:33:34.978[0m Jan 26 17:33:34.978: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6xjlr" in namespace "azuredisk-2751" to be "Succeeded or Failed" Jan 26 17:33:35.087: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 109.186861ms Jan 26 17:33:37.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220532928s Jan 26 17:33:39.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220559234s Jan 26 17:33:41.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.220092805s Jan 26 17:33:43.199: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.221214208s Jan 26 17:33:45.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.22027588s ... skipping 94 lines ... Jan 26 17:36:55.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=true. Elapsed: 3m20.220243307s Jan 26 17:36:57.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=true. Elapsed: 3m22.220433901s Jan 26 17:36:59.200: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.222046831s Jan 26 17:37:01.199: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.220896763s Jan 26 17:37:03.199: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 3m28.220686371s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:37:03.199[0m Jan 26 17:37:03.199: INFO: Pod "azuredisk-volume-tester-6xjlr" satisfied condition "Succeeded or Failed" Jan 26 17:37:03.199: INFO: deleting Pod "azuredisk-2751"/"azuredisk-volume-tester-6xjlr" Jan 26 17:37:03.333: INFO: Pod azuredisk-volume-tester-6xjlr has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-6xjlr in namespace azuredisk-2751 [38;5;243m01/26/23 17:37:03.333[0m Jan 26 17:37:03.452: INFO: deleting PVC "azuredisk-2751"/"pvc-pnx9d" Jan 26 17:37:03.452: INFO: Deleting PersistentVolumeClaim "pvc-pnx9d" ... skipping 15 lines ... Jan 26 17:37:44.920: INFO: Pod azuredisk-volume-tester-ljvrf has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ljvrf in namespace azuredisk-2751 [38;5;243m01/26/23 17:37:44.92[0m [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-md777 [38;5;243m01/26/23 17:37:45.036[0m Jan 26 17:37:45.152: INFO: skip deleting VolumeSnapshotClass azuredisk-2751-disk.csi.azure.com-dynamic-sc-rjrr8 Jan 26 17:37:45.152: INFO: Deleting resource group azuredisk-csi-driver-test-733a242d-9d9f-11ed-b421-72101b7cf8e1 Jan 26 17:39:04.182: INFO: deleting Pod "azuredisk-2751"/"azuredisk-volume-tester-m6jsm" Jan 26 17:39:04.290: INFO: Error getting logs for pod azuredisk-volume-tester-m6jsm: the server could not find the requested resource (get pods azuredisk-volume-tester-m6jsm) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-m6jsm in namespace azuredisk-2751 [38;5;243m01/26/23 17:39:04.29[0m Jan 26 17:39:04.398: INFO: deleting PVC "azuredisk-2751"/"pvc-6mnmb" Jan 26 17:39:04.398: INFO: Deleting PersistentVolumeClaim "pvc-6mnmb" [1mSTEP:[0m waiting for claim's PV "pvc-49ecbb2f-93b3-4c45-93f9-dd80f7ca62eb" to be deleted [38;5;243m01/26/23 17:39:04.513[0m Jan 26 17:39:04.513: INFO: Waiting up to 10m0s for PersistentVolume pvc-49ecbb2f-93b3-4c45-93f9-dd80f7ca62eb to get deleted Jan 26 17:39:04.621: INFO: PersistentVolume pvc-49ecbb2f-93b3-4c45-93f9-dd80f7ca62eb found and phase=Released (108.029145ms) ... skipping 29 lines ... Jan 26 17:31:34.459: INFO: PersistentVolumeClaim pvc-6mnmb found but phase is Pending instead of Bound. Jan 26 17:31:36.568: INFO: PersistentVolumeClaim pvc-6mnmb found and phase=Bound (4.327660933s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:31:36.568[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:31:36.676[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:31:36.784[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:31:36.785[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:31:36.898[0m Jan 26 17:31:36.898: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m6jsm" in namespace "azuredisk-2751" to be "Succeeded or Failed" Jan 26 17:31:37.006: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 108.086971ms Jan 26 17:31:39.116: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217666205s Jan 26 17:31:41.116: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.217516973s Jan 26 17:31:43.118: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.219337759s Jan 26 17:31:45.115: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217052688s Jan 26 17:31:47.117: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218762784s ... skipping 15 lines ... Jan 26 17:32:19.122: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=true. Elapsed: 42.223453244s Jan 26 17:32:21.122: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=false. Elapsed: 44.223539829s Jan 26 17:32:23.118: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=false. Elapsed: 46.21947197s Jan 26 17:32:25.117: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Running", Reason="", readiness=false. Elapsed: 48.218981113s Jan 26 17:32:27.117: INFO: Pod "azuredisk-volume-tester-m6jsm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.218868964s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:32:27.117[0m Jan 26 17:32:27.117: INFO: Pod "azuredisk-volume-tester-m6jsm" satisfied condition "Succeeded or Failed" Jan 26 17:32:27.231: INFO: deleting Pod "azuredisk-2751"/"azuredisk-volume-tester-m6jsm" Jan 26 17:32:27.352: INFO: Pod azuredisk-volume-tester-m6jsm has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-m6jsm in namespace azuredisk-2751 [38;5;243m01/26/23 17:32:27.352[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/26/23 17:32:27.472[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/26/23 17:32:47.689[0m [1mSTEP:[0m Prow test resource group: capz-kyk3l0 [38;5;243m01/26/23 17:32:47.69[0m ... skipping 35 lines ... [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:33:34.752[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:33:34.861[0m [1mSTEP:[0m setting up the pod [38;5;243m01/26/23 17:33:34.861[0m I0126 17:33:34.861988 42930 resource_setup.go:62] adding PV (pvc-d8c80410-192d-4dc6-b298-fc8efe197e8a) to pod () [1mSTEP:[0m Set pod anti-affinity to make sure two pods are scheduled on different nodes [38;5;243m01/26/23 17:33:34.862[0m [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/26/23 17:33:34.862[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:33:34.978[0m Jan 26 17:33:34.978: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6xjlr" in namespace "azuredisk-2751" to be "Succeeded or Failed" Jan 26 17:33:35.087: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 109.186861ms Jan 26 17:33:37.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220532928s Jan 26 17:33:39.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220559234s Jan 26 17:33:41.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.220092805s Jan 26 17:33:43.199: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.221214208s Jan 26 17:33:45.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.22027588s ... skipping 94 lines ... Jan 26 17:36:55.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=true. Elapsed: 3m20.220243307s Jan 26 17:36:57.198: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=true. Elapsed: 3m22.220433901s Jan 26 17:36:59.200: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.222046831s Jan 26 17:37:01.199: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.220896763s Jan 26 17:37:03.199: INFO: Pod "azuredisk-volume-tester-6xjlr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 3m28.220686371s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:37:03.199[0m Jan 26 17:37:03.199: INFO: Pod "azuredisk-volume-tester-6xjlr" satisfied condition "Succeeded or Failed" Jan 26 17:37:03.199: INFO: deleting Pod "azuredisk-2751"/"azuredisk-volume-tester-6xjlr" Jan 26 17:37:03.333: INFO: Pod azuredisk-volume-tester-6xjlr has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-6xjlr in namespace azuredisk-2751 [38;5;243m01/26/23 17:37:03.333[0m Jan 26 17:37:03.452: INFO: deleting PVC "azuredisk-2751"/"pvc-pnx9d" Jan 26 17:37:03.452: INFO: Deleting PersistentVolumeClaim "pvc-pnx9d" ... skipping 15 lines ... Jan 26 17:37:44.920: INFO: Pod azuredisk-volume-tester-ljvrf has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ljvrf in namespace azuredisk-2751 [38;5;243m01/26/23 17:37:44.92[0m [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-md777 [38;5;243m01/26/23 17:37:45.036[0m Jan 26 17:37:45.152: INFO: skip deleting VolumeSnapshotClass azuredisk-2751-disk.csi.azure.com-dynamic-sc-rjrr8 Jan 26 17:37:45.152: INFO: Deleting resource group azuredisk-csi-driver-test-733a242d-9d9f-11ed-b421-72101b7cf8e1 Jan 26 17:39:04.182: INFO: deleting Pod "azuredisk-2751"/"azuredisk-volume-tester-m6jsm" Jan 26 17:39:04.290: INFO: Error getting logs for pod azuredisk-volume-tester-m6jsm: the server could not find the requested resource (get pods azuredisk-volume-tester-m6jsm) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-m6jsm in namespace azuredisk-2751 [38;5;243m01/26/23 17:39:04.29[0m Jan 26 17:39:04.398: INFO: deleting PVC "azuredisk-2751"/"pvc-6mnmb" Jan 26 17:39:04.398: INFO: Deleting PersistentVolumeClaim "pvc-6mnmb" [1mSTEP:[0m waiting for claim's PV "pvc-49ecbb2f-93b3-4c45-93f9-dd80f7ca62eb" to be deleted [38;5;243m01/26/23 17:39:04.513[0m Jan 26 17:39:04.513: INFO: Waiting up to 10m0s for PersistentVolume pvc-49ecbb2f-93b3-4c45-93f9-dd80f7ca62eb to get deleted Jan 26 17:39:04.621: INFO: PersistentVolume pvc-49ecbb2f-93b3-4c45-93f9-dd80f7ca62eb found and phase=Released (108.029145ms) ... skipping 55 lines ... Jan 26 17:39:30.763: INFO: PersistentVolumeClaim pvc-tj4s9 found and phase=Bound (4.325376358s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:39:30.764[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:39:30.872[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:39:30.98[0m I0126 17:39:30.980962 42930 resource_setup.go:89] adding PV (pvc-eed797b9-2cd3-4a40-8a56-b893146538c1) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:39:30.98[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:39:31.096[0m Jan 26 17:39:31.096: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cj8x5" in namespace "azuredisk-1016" to be "Succeeded or Failed" Jan 26 17:39:31.209: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 112.316823ms Jan 26 17:39:33.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222565887s Jan 26 17:39:35.321: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.224462541s Jan 26 17:39:37.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.222863006s Jan 26 17:39:39.320: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223633996s Jan 26 17:39:41.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.222338564s ... skipping 18 lines ... Jan 26 17:40:19.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=true. Elapsed: 48.222503675s Jan 26 17:40:21.320: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=true. Elapsed: 50.223630357s Jan 26 17:40:23.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=false. Elapsed: 52.222525221s Jan 26 17:40:25.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=false. Elapsed: 54.222852495s Jan 26 17:40:27.321: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 56.224602075s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:40:27.321[0m Jan 26 17:40:27.321: INFO: Pod "azuredisk-volume-tester-cj8x5" satisfied condition "Succeeded or Failed" Jan 26 17:40:27.321: INFO: deleting Pod "azuredisk-1016"/"azuredisk-volume-tester-cj8x5" Jan 26 17:40:27.451: INFO: Pod azuredisk-volume-tester-cj8x5 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cj8x5 in namespace azuredisk-1016 [38;5;243m01/26/23 17:40:27.451[0m Jan 26 17:40:27.568: INFO: deleting PVC "azuredisk-1016"/"pvc-tj4s9" Jan 26 17:40:27.568: INFO: Deleting PersistentVolumeClaim "pvc-tj4s9" ... skipping 85 lines ... Jan 26 17:39:30.763: INFO: PersistentVolumeClaim pvc-tj4s9 found and phase=Bound (4.325376358s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 17:39:30.764[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 17:39:30.872[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 17:39:30.98[0m I0126 17:39:30.980962 42930 resource_setup.go:89] adding PV (pvc-eed797b9-2cd3-4a40-8a56-b893146538c1) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 17:39:30.98[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 17:39:31.096[0m Jan 26 17:39:31.096: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cj8x5" in namespace "azuredisk-1016" to be "Succeeded or Failed" Jan 26 17:39:31.209: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 112.316823ms Jan 26 17:39:33.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.222565887s Jan 26 17:39:35.321: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.224462541s Jan 26 17:39:37.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.222863006s Jan 26 17:39:39.320: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223633996s Jan 26 17:39:41.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.222338564s ... skipping 18 lines ... Jan 26 17:40:19.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=true. Elapsed: 48.222503675s Jan 26 17:40:21.320: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=true. Elapsed: 50.223630357s Jan 26 17:40:23.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=false. Elapsed: 52.222525221s Jan 26 17:40:25.319: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Running", Reason="", readiness=false. Elapsed: 54.222852495s Jan 26 17:40:27.321: INFO: Pod "azuredisk-volume-tester-cj8x5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 56.224602075s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 17:40:27.321[0m Jan 26 17:40:27.321: INFO: Pod "azuredisk-volume-tester-cj8x5" satisfied condition "Succeeded or Failed" Jan 26 17:40:27.321: INFO: deleting Pod "azuredisk-1016"/"azuredisk-volume-tester-cj8x5" Jan 26 17:40:27.451: INFO: Pod azuredisk-volume-tester-cj8x5 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cj8x5 in namespace azuredisk-1016 [38;5;243m01/26/23 17:40:27.451[0m Jan 26 17:40:27.568: INFO: deleting PVC "azuredisk-1016"/"pvc-tj4s9" Jan 26 17:40:27.568: INFO: Deleting PersistentVolumeClaim "pvc-tj4s9" ... skipping 603 lines ... [1mSTEP:[0m begin to delete the pod [38;5;243m01/26/23 17:49:49.225[0m Jan 26 17:49:49.225: INFO: deleting Pod "azuredisk-4176"/"azuredisk-volume-tester-7gz8z" Jan 26 17:49:49.350: INFO: Pod azuredisk-volume-tester-7gz8z has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7gz8z in namespace azuredisk-4176 [38;5;243m01/26/23 17:49:49.35[0m Jan 26 17:50:13.703: INFO: deleting Pod "azuredisk-4176"/"azuredisk-volume-tester-7gz8z" Jan 26 17:50:13.813: INFO: Error getting logs for pod azuredisk-volume-tester-7gz8z: the server could not find the requested resource (get pods azuredisk-volume-tester-7gz8z) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7gz8z in namespace azuredisk-4176 [38;5;243m01/26/23 17:50:13.813[0m Jan 26 17:50:13.921: INFO: deleting PVC "azuredisk-4176"/"pvc-m84f7" Jan 26 17:50:13.921: INFO: Deleting PersistentVolumeClaim "pvc-m84f7" [1mSTEP:[0m waiting for claim's PV "pvc-2d5b344d-07ca-472f-a05c-4ca8a0451987" to be deleted [38;5;243m01/26/23 17:50:14.033[0m Jan 26 17:50:14.033: INFO: Waiting up to 10m0s for PersistentVolume pvc-2d5b344d-07ca-472f-a05c-4ca8a0451987 to get deleted Jan 26 17:50:14.143: INFO: PersistentVolume pvc-2d5b344d-07ca-472f-a05c-4ca8a0451987 found and phase=Released (109.908738ms) ... skipping 62 lines ... [1mSTEP:[0m begin to delete the pod [38;5;243m01/26/23 17:49:49.225[0m Jan 26 17:49:49.225: INFO: deleting Pod "azuredisk-4176"/"azuredisk-volume-tester-7gz8z" Jan 26 17:49:49.350: INFO: Pod azuredisk-volume-tester-7gz8z has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7gz8z in namespace azuredisk-4176 [38;5;243m01/26/23 17:49:49.35[0m Jan 26 17:50:13.703: INFO: deleting Pod "azuredisk-4176"/"azuredisk-volume-tester-7gz8z" Jan 26 17:50:13.813: INFO: Error getting logs for pod azuredisk-volume-tester-7gz8z: the server could not find the requested resource (get pods azuredisk-volume-tester-7gz8z) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7gz8z in namespace azuredisk-4176 [38;5;243m01/26/23 17:50:13.813[0m Jan 26 17:50:13.921: INFO: deleting PVC "azuredisk-4176"/"pvc-m84f7" Jan 26 17:50:13.921: INFO: Deleting PersistentVolumeClaim "pvc-m84f7" [1mSTEP:[0m waiting for claim's PV "pvc-2d5b344d-07ca-472f-a05c-4ca8a0451987" to be deleted [38;5;243m01/26/23 17:50:14.033[0m Jan 26 17:50:14.033: INFO: Waiting up to 10m0s for PersistentVolume pvc-2d5b344d-07ca-472f-a05c-4ca8a0451987 to get deleted Jan 26 17:50:14.143: INFO: PersistentVolume pvc-2d5b344d-07ca-472f-a05c-4ca8a0451987 found and phase=Released (109.908738ms) ... skipping 60 lines ... I0126 17:51:08.675165 42930 dynamically_provisioned_pod_delete.go:101] volumes: [{Name:test-volume-1 VolumeSource:{HostPath:nil EmptyDir:nil GCEPersistentDisk:nil AWSElasticBlockStore:nil GitRepo:nil Secret:nil NFS:nil ISCSI:nil Glusterfs:nil PersistentVolumeClaim:&PersistentVolumeClaimVolumeSource{ClaimName:pvc-s4hsf,ReadOnly:false,} RBD:nil FlexVolume:nil Cinder:nil CephFS:nil Flocker:nil DownwardAPI:nil FC:nil AzureFile:nil ConfigMap:nil VsphereVolume:nil Quobyte:nil AzureDisk:nil PhotonPersistentDisk:nil Projected:nil PortworxVolume:nil ScaleIO:nil StorageOS:nil CSI:nil Ephemeral:nil}}] [1mSTEP:[0m begin to delete the pod [38;5;243m01/26/23 17:51:08.675[0m Jan 26 17:51:08.675: INFO: deleting Pod "azuredisk-2419"/"azuredisk-volume-tester-wt88m" Jan 26 17:51:08.796: INFO: Pod azuredisk-volume-tester-wt88m has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wt88m in namespace azuredisk-2419 [38;5;243m01/26/23 17:51:08.796[0m Jan 26 17:51:25.165: INFO: deleting Pod "azuredisk-2419"/"azuredisk-volume-tester-wt88m" Jan 26 17:51:25.273: INFO: Error getting logs for pod azuredisk-volume-tester-wt88m: the server could not find the requested resource (get pods azuredisk-volume-tester-wt88m) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wt88m in namespace azuredisk-2419 [38;5;243m01/26/23 17:51:25.273[0m Jan 26 17:51:25.381: INFO: deleting PVC "azuredisk-2419"/"pvc-s4hsf" Jan 26 17:51:25.381: INFO: Deleting PersistentVolumeClaim "pvc-s4hsf" [1mSTEP:[0m waiting for claim's PV "pvc-f64605dc-da88-4f98-8027-e32a637eba11" to be deleted [38;5;243m01/26/23 17:51:25.492[0m Jan 26 17:51:25.492: INFO: Waiting up to 10m0s for PersistentVolume pvc-f64605dc-da88-4f98-8027-e32a637eba11 to get deleted Jan 26 17:51:25.602: INFO: PersistentVolume pvc-f64605dc-da88-4f98-8027-e32a637eba11 found and phase=Released (110.13602ms) ... skipping 64 lines ... I0126 17:51:08.675165 42930 dynamically_provisioned_pod_delete.go:101] volumes: [{Name:test-volume-1 VolumeSource:{HostPath:nil EmptyDir:nil GCEPersistentDisk:nil AWSElasticBlockStore:nil GitRepo:nil Secret:nil NFS:nil ISCSI:nil Glusterfs:nil PersistentVolumeClaim:&PersistentVolumeClaimVolumeSource{ClaimName:pvc-s4hsf,ReadOnly:false,} RBD:nil FlexVolume:nil Cinder:nil CephFS:nil Flocker:nil DownwardAPI:nil FC:nil AzureFile:nil ConfigMap:nil VsphereVolume:nil Quobyte:nil AzureDisk:nil PhotonPersistentDisk:nil Projected:nil PortworxVolume:nil ScaleIO:nil StorageOS:nil CSI:nil Ephemeral:nil}}] [1mSTEP:[0m begin to delete the pod [38;5;243m01/26/23 17:51:08.675[0m Jan 26 17:51:08.675: INFO: deleting Pod "azuredisk-2419"/"azuredisk-volume-tester-wt88m" Jan 26 17:51:08.796: INFO: Pod azuredisk-volume-tester-wt88m has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wt88m in namespace azuredisk-2419 [38;5;243m01/26/23 17:51:08.796[0m Jan 26 17:51:25.165: INFO: deleting Pod "azuredisk-2419"/"azuredisk-volume-tester-wt88m" Jan 26 17:51:25.273: INFO: Error getting logs for pod azuredisk-volume-tester-wt88m: the server could not find the requested resource (get pods azuredisk-volume-tester-wt88m) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wt88m in namespace azuredisk-2419 [38;5;243m01/26/23 17:51:25.273[0m Jan 26 17:51:25.381: INFO: deleting PVC "azuredisk-2419"/"pvc-s4hsf" Jan 26 17:51:25.381: INFO: Deleting PersistentVolumeClaim "pvc-s4hsf" [1mSTEP:[0m waiting for claim's PV "pvc-f64605dc-da88-4f98-8027-e32a637eba11" to be deleted [38;5;243m01/26/23 17:51:25.492[0m Jan 26 17:51:25.492: INFO: Waiting up to 10m0s for PersistentVolume pvc-f64605dc-da88-4f98-8027-e32a637eba11 to get deleted Jan 26 17:51:25.602: INFO: PersistentVolume pvc-f64605dc-da88-4f98-8027-e32a637eba11 found and phase=Released (110.13602ms) ... skipping 61 lines ... I0126 17:52:57.627370 42930 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 17:52:57.849[0m I0126 17:52:57.957603 42930 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m check pod exec [38;5;243m01/26/23 17:52:57.957[0m Jan 26 17:52:57.957: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-9600 exec azuredisk-volume-tester-ndzff-0 -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:52:59.141: INFO: rc: 1 Jan 26 17:52:59.141: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-ndzff-0": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-9600 exec azuredisk-volume-tester-ndzff-0 -- 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 26 17:53:01.142: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-9600 exec azuredisk-volume-tester-ndzff-0 -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:53:02.313: INFO: stderr: "" Jan 26 17:53:02.313: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for statefulset [38;5;243m01/26/23 17:53:02.313[0m Jan 26 17:53:02.313: INFO: Deleting pod "azuredisk-volume-tester-ndzff-0" in namespace "azuredisk-9600" ... skipping 72 lines ... I0126 17:52:57.627370 42930 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 17:52:57.849[0m I0126 17:52:57.957603 42930 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m check pod exec [38;5;243m01/26/23 17:52:57.957[0m Jan 26 17:52:57.957: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-9600 exec azuredisk-volume-tester-ndzff-0 -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:52:59.141: INFO: rc: 1 Jan 26 17:52:59.141: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-ndzff-0": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-9600 exec azuredisk-volume-tester-ndzff-0 -- 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 26 17:53:01.142: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-9600 exec azuredisk-volume-tester-ndzff-0 -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 17:53:02.313: INFO: stderr: "" Jan 26 17:53:02.313: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for statefulset [38;5;243m01/26/23 17:53:02.313[0m Jan 26 17:53:02.313: INFO: Deleting pod "azuredisk-volume-tester-ndzff-0" in namespace "azuredisk-9600" ... skipping 1014 lines ... Jan 26 18:04:41.277: 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, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zmddd-7664c9ff9d\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 26 18:04:43.278: 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, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zmddd-7664c9ff9d\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 18:04:45.501[0m [1mSTEP:[0m check pod exec [38;5;243m01/26/23 18:04:45.831[0m Jan 26 18:04:45.831: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-7230 exec azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:04:47.033: INFO: rc: 1 Jan 26 18:04:47.033: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-7230 exec azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk -- 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 26 18:04:49.034: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-7230 exec azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:04:50.218: INFO: stderr: "" Jan 26 18:04:50.218: INFO: stdout: "hello world\r\n" [1mSTEP:[0m cordoning node 0 [38;5;243m01/26/23 18:04:50.218[0m [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/26/23 18:04:50.463[0m ... skipping 80 lines ... Jan 26 18:04:41.277: 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, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zmddd-7664c9ff9d\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 26 18:04:43.278: 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, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 4, 5, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-zmddd-7664c9ff9d\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 18:04:45.501[0m [1mSTEP:[0m check pod exec [38;5;243m01/26/23 18:04:45.831[0m Jan 26 18:04:45.831: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-7230 exec azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:04:47.033: INFO: rc: 1 Jan 26 18:04:47.033: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-7230 exec azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk -- 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 26 18:04:49.034: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-7230 exec azuredisk-volume-tester-zmddd-7664c9ff9d-tzppk -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:04:50.218: INFO: stderr: "" Jan 26 18:04:50.218: INFO: stdout: "hello world\r\n" [1mSTEP:[0m cordoning node 0 [38;5;243m01/26/23 18:04:50.218[0m [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/26/23 18:04:50.463[0m ... skipping 76 lines ... Jan 26 18:06:20.460: 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, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-pdvjn-7bfdc6c574\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 26 18:06:22.466: 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, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-pdvjn-7bfdc6c574\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 18:06:24.682[0m [1mSTEP:[0m check pod exec [38;5;243m01/26/23 18:06:25.013[0m Jan 26 18:06:25.013: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-1065 exec azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:06:26.316: INFO: rc: 1 Jan 26 18:06:26.316: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-1065 exec azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth -- 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 26 18:06:28.318: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-1065 exec azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:06:29.515: INFO: stderr: "" Jan 26 18:06:29.515: INFO: stdout: "hello world\r\n" [1mSTEP:[0m cordoning node 0 [38;5;243m01/26/23 18:06:29.515[0m [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/26/23 18:06:29.767[0m ... skipping 107 lines ... Jan 26 18:06:20.460: 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, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-pdvjn-7bfdc6c574\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 26 18:06:22.466: 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, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 26, 18, 5, 50, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-pdvjn-7bfdc6c574\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/26/23 18:06:24.682[0m [1mSTEP:[0m check pod exec [38;5;243m01/26/23 18:06:25.013[0m Jan 26 18:06:25.013: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-1065 exec azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:06:26.316: INFO: rc: 1 Jan 26 18:06:26.316: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-1065 exec azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth -- 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 26 18:06:28.318: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-1065 exec azuredisk-volume-tester-pdvjn-7bfdc6c574-w6qth -- cmd /c type C:\mnt\test-1\data.txt' Jan 26 18:06:29.515: INFO: stderr: "" Jan 26 18:06:29.515: INFO: stdout: "hello world\r\n" [1mSTEP:[0m cordoning node 0 [38;5;243m01/26/23 18:06:29.515[0m [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/26/23 18:06:29.767[0m ... skipping 167 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 [38;5;243m------------------------------[0m [0mDynamic Provisioning [38;5;243m[single-az][0m [1mshould check failed replica attachments are recreated after space is made from a volume detaching.[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:1778[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m01/26/23 18:08:20.171[0m Jan 26 18:08:20.171: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/26/23 18:08:20.172[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/26/23 18:08:20.501[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/26/23 18:08:20.716[0m ... skipping 6 lines ... [38;5;243m------------------------------[0m [38;5;14mS [SKIPPED] [1.656 seconds][0m Dynamic Provisioning [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41[0m [single-az] [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:45[0m [38;5;14m[1m[It] should check failed replica attachments are recreated after space is made from a volume detaching.[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:1778[0m [38;5;243mBegin Captured GinkgoWriter Output >>[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m01/26/23 18:08:20.171[0m Jan 26 18:08:20.171: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/26/23 18:08:20.172[0m ... skipping 15 lines ... Jan 26 18:08:21.828: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/26/23 18:08:21.83[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/26/23 18:08:22.16[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/26/23 18:08:22.376[0m I0126 18:08:22.590223 42930 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 18:08:22.732[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 18:08:22.847[0m Jan 26 18:08:22.847: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-46ptw" in namespace "azuredisk-7772" to be "Succeeded or Failed" Jan 26 18:08:22.959: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Pending", Reason="", readiness=false. Elapsed: 112.018877ms Jan 26 18:08:25.069: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.221344651s Jan 26 18:08:27.068: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220590337s Jan 26 18:08:29.075: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Running", Reason="", readiness=true. Elapsed: 6.227688641s Jan 26 18:08:31.075: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Running", Reason="", readiness=true. Elapsed: 8.227127285s Jan 26 18:08:33.074: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Running", Reason="", readiness=false. Elapsed: 10.22626765s Jan 26 18:08:35.075: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.227182136s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 18:08:35.075[0m Jan 26 18:08:35.075: INFO: Pod "azuredisk-volume-tester-46ptw" satisfied condition "Succeeded or Failed" Jan 26 18:08:35.075: INFO: deleting Pod "azuredisk-7772"/"azuredisk-volume-tester-46ptw" Jan 26 18:08:35.192: INFO: Pod azuredisk-volume-tester-46ptw has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-46ptw in namespace azuredisk-7772 [38;5;243m01/26/23 18:08:35.192[0m [1mSTEP:[0m Destroying namespace "azuredisk-7772" for this suite. [38;5;243m01/26/23 18:08:35.315[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Jan 26 18:08:21.828: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/26/23 18:08:21.83[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/26/23 18:08:22.16[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/26/23 18:08:22.376[0m I0126 18:08:22.590223 42930 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 18:08:22.732[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 18:08:22.847[0m Jan 26 18:08:22.847: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-46ptw" in namespace "azuredisk-7772" to be "Succeeded or Failed" Jan 26 18:08:22.959: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Pending", Reason="", readiness=false. Elapsed: 112.018877ms Jan 26 18:08:25.069: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.221344651s Jan 26 18:08:27.068: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.220590337s Jan 26 18:08:29.075: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Running", Reason="", readiness=true. Elapsed: 6.227688641s Jan 26 18:08:31.075: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Running", Reason="", readiness=true. Elapsed: 8.227127285s Jan 26 18:08:33.074: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Running", Reason="", readiness=false. Elapsed: 10.22626765s Jan 26 18:08:35.075: INFO: Pod "azuredisk-volume-tester-46ptw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.227182136s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 18:08:35.075[0m Jan 26 18:08:35.075: INFO: Pod "azuredisk-volume-tester-46ptw" satisfied condition "Succeeded or Failed" Jan 26 18:08:35.075: INFO: deleting Pod "azuredisk-7772"/"azuredisk-volume-tester-46ptw" Jan 26 18:08:35.192: INFO: Pod azuredisk-volume-tester-46ptw has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-46ptw in namespace azuredisk-7772 [38;5;243m01/26/23 18:08:35.192[0m [1mSTEP:[0m Destroying namespace "azuredisk-7772" for this suite. [38;5;243m01/26/23 18:08:35.315[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 17 lines ... Jan 26 18:08:38.626: INFO: PersistentVolumeClaim pvc-rgtx5 found but phase is Pending instead of Bound. Jan 26 18:08:40.735: INFO: PersistentVolumeClaim pvc-rgtx5 found and phase=Bound (4.326977735s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 18:08:40.735[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 18:08:40.844[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 18:08:40.952[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 18:08:41.094[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 18:08:41.208[0m Jan 26 18:08:41.208: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xt79t" in namespace "azuredisk-9635" to be "Succeeded or Failed" Jan 26 18:08:41.316: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 108.482815ms Jan 26 18:08:43.425: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217366257s Jan 26 18:08:45.425: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.21727235s Jan 26 18:08:47.426: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218612352s Jan 26 18:08:49.425: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217619019s Jan 26 18:08:51.427: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218866581s ... skipping 14 lines ... Jan 26 18:09:21.431: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=true. Elapsed: 40.22285915s Jan 26 18:09:23.432: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=true. Elapsed: 42.224351211s Jan 26 18:09:25.432: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=false. Elapsed: 44.223801894s Jan 26 18:09:27.430: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=false. Elapsed: 46.222697961s Jan 26 18:09:29.430: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.222583894s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 18:09:29.431[0m Jan 26 18:09:29.431: INFO: Pod "azuredisk-volume-tester-xt79t" satisfied condition "Succeeded or Failed" Jan 26 18:09:29.431: INFO: deleting Pod "azuredisk-9635"/"azuredisk-volume-tester-xt79t" Jan 26 18:09:29.548: INFO: Pod azuredisk-volume-tester-xt79t has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-xt79t in namespace azuredisk-9635 [38;5;243m01/26/23 18:09:29.549[0m Jan 26 18:09:29.672: INFO: deleting PVC "azuredisk-9635"/"pvc-rgtx5" Jan 26 18:09:29.672: INFO: Deleting PersistentVolumeClaim "pvc-rgtx5" ... skipping 38 lines ... Jan 26 18:08:38.626: INFO: PersistentVolumeClaim pvc-rgtx5 found but phase is Pending instead of Bound. Jan 26 18:08:40.735: INFO: PersistentVolumeClaim pvc-rgtx5 found and phase=Bound (4.326977735s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 18:08:40.735[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 18:08:40.844[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 18:08:40.952[0m [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 18:08:41.094[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 18:08:41.208[0m Jan 26 18:08:41.208: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xt79t" in namespace "azuredisk-9635" to be "Succeeded or Failed" Jan 26 18:08:41.316: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 108.482815ms Jan 26 18:08:43.425: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217366257s Jan 26 18:08:45.425: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.21727235s Jan 26 18:08:47.426: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218612352s Jan 26 18:08:49.425: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217619019s Jan 26 18:08:51.427: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218866581s ... skipping 14 lines ... Jan 26 18:09:21.431: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=true. Elapsed: 40.22285915s Jan 26 18:09:23.432: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=true. Elapsed: 42.224351211s Jan 26 18:09:25.432: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=false. Elapsed: 44.223801894s Jan 26 18:09:27.430: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Running", Reason="", readiness=false. Elapsed: 46.222697961s Jan 26 18:09:29.430: INFO: Pod "azuredisk-volume-tester-xt79t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.222583894s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 18:09:29.431[0m Jan 26 18:09:29.431: INFO: Pod "azuredisk-volume-tester-xt79t" satisfied condition "Succeeded or Failed" Jan 26 18:09:29.431: INFO: deleting Pod "azuredisk-9635"/"azuredisk-volume-tester-xt79t" Jan 26 18:09:29.548: INFO: Pod azuredisk-volume-tester-xt79t has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-xt79t in namespace azuredisk-9635 [38;5;243m01/26/23 18:09:29.549[0m Jan 26 18:09:29.672: INFO: deleting PVC "azuredisk-9635"/"pvc-rgtx5" Jan 26 18:09:29.672: INFO: Deleting PersistentVolumeClaim "pvc-rgtx5" ... skipping 175 lines ... Jan 26 18:16:17.770: INFO: PersistentVolumeClaim pvc-49w4c found and phase=Bound (4.327156385s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 18:16:17.77[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 18:16:17.878[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 18:16:17.985[0m I0126 18:16:17.986036 42930 resource_setup.go:89] adding PV (pvc-f4693983-54ad-4b63-b7e7-1a5b2b8f1753) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 18:16:18.138[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 18:16:18.251[0m Jan 26 18:16:18.252: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bqwdx" in namespace "azuredisk-8256" to be "Succeeded or Failed" Jan 26 18:16:18.383: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 131.628703ms Jan 26 18:16:20.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.247719138s Jan 26 18:16:22.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.248881803s Jan 26 18:16:24.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.248306793s Jan 26 18:16:26.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.247851645s Jan 26 18:16:28.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.248506121s ... skipping 19 lines ... Jan 26 18:17:08.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=true. Elapsed: 50.247350351s Jan 26 18:17:10.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=true. Elapsed: 52.247697805s Jan 26 18:17:12.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=false. Elapsed: 54.24755612s Jan 26 18:17:14.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=false. Elapsed: 56.24880293s Jan 26 18:17:16.501: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.248936962s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 18:17:16.501[0m Jan 26 18:17:16.501: INFO: Pod "azuredisk-volume-tester-bqwdx" satisfied condition "Succeeded or Failed" Jan 26 18:17:16.501: INFO: deleting Pod "azuredisk-8256"/"azuredisk-volume-tester-bqwdx" Jan 26 18:17:16.635: INFO: Pod azuredisk-volume-tester-bqwdx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bqwdx in namespace azuredisk-8256 [38;5;243m01/26/23 18:17:16.635[0m Jan 26 18:17:16.764: INFO: deleting PVC "azuredisk-8256"/"pvc-49w4c" Jan 26 18:17:16.764: INFO: Deleting PersistentVolumeClaim "pvc-49w4c" ... skipping 85 lines ... Jan 26 18:16:17.770: INFO: PersistentVolumeClaim pvc-49w4c found and phase=Bound (4.327156385s) [1mSTEP:[0m checking the PVC [38;5;243m01/26/23 18:16:17.77[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/26/23 18:16:17.878[0m [1mSTEP:[0m checking the PV [38;5;243m01/26/23 18:16:17.985[0m I0126 18:16:17.986036 42930 resource_setup.go:89] adding PV (pvc-f4693983-54ad-4b63-b7e7-1a5b2b8f1753) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/26/23 18:16:18.138[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/26/23 18:16:18.251[0m Jan 26 18:16:18.252: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bqwdx" in namespace "azuredisk-8256" to be "Succeeded or Failed" Jan 26 18:16:18.383: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 131.628703ms Jan 26 18:16:20.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.247719138s Jan 26 18:16:22.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.248881803s Jan 26 18:16:24.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.248306793s Jan 26 18:16:26.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.247851645s Jan 26 18:16:28.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.248506121s ... skipping 19 lines ... Jan 26 18:17:08.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=true. Elapsed: 50.247350351s Jan 26 18:17:10.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=true. Elapsed: 52.247697805s Jan 26 18:17:12.499: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=false. Elapsed: 54.24755612s Jan 26 18:17:14.500: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Running", Reason="", readiness=false. Elapsed: 56.24880293s Jan 26 18:17:16.501: INFO: Pod "azuredisk-volume-tester-bqwdx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.248936962s [1mSTEP:[0m Saw pod success [38;5;243m01/26/23 18:17:16.501[0m Jan 26 18:17:16.501: INFO: Pod "azuredisk-volume-tester-bqwdx" satisfied condition "Succeeded or Failed" Jan 26 18:17:16.501: INFO: deleting Pod "azuredisk-8256"/"azuredisk-volume-tester-bqwdx" Jan 26 18:17:16.635: INFO: Pod azuredisk-volume-tester-bqwdx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bqwdx in namespace azuredisk-8256 [38;5;243m01/26/23 18:17:16.635[0m Jan 26 18:17:16.764: INFO: deleting PVC "azuredisk-8256"/"pvc-49w4c" Jan 26 18:17:16.764: INFO: Deleting PersistentVolumeClaim "pvc-49w4c" ... skipping 427 lines ...