kubernetes-sigs/azuredisk-csi-driver PR #1712 pull-azuredisk-csi-driver-e2e-capz-windows-2019-mainv2 #1620551315815927808
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | edreed: [V2] build: disable provenance attestation to work around docker issue |
| Result | ABORTED |
| Tests | 0 failed / 38 succeeded |
| Started | |
| Elapsed | 2h0m |
| Revision | da7bb6ca0b2c627874174ac85b58dad975d8dfc9 |
| Refs |
1712 |
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 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 test pod failover with cordoning a node using ZRS
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 800 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 98652 0 --:--:-- --:--:-- --:--:-- 98652 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-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 not found: manifest unknown: manifest tagged by "latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9" 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-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-31T22:58:15Z -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 --driver-opt image=moby/buildkit:v0.10.6 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 241 lines ... #9 exporting to image #9 pushing layers 2.2s done #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64@sha256:92bac3970d9ffd67d3dca8ff9e299f7062cb563162f646474791dc65d69b376c #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64@sha256:92bac3970d9ffd67d3dca8ff9e299f7062cb563162f646474791dc65d69b376c 0.4s done #9 DONE 7.9s WARNING: failed to get git remote url: fatal: No remote configured to list refs from. make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-31T23:03:27Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/arm64/azurediskpluginv2 ./pkg/azurediskplugin make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx build . \ ... skipping 113 lines ... #8 exporting config sha256:889f7f9ffc58fa4f902696c177dc916ee39330338a16184363be69b7d875396c 0.0s done #8 pushing layers #8 pushing layers 2.2s done #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64@sha256:7eb149546185c129cc4eec6a1ada3dac5ba152a6feaac5b882d64117ecace183 #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64@sha256:7eb149546185c129cc4eec6a1ada3dac5ba152a6feaac5b882d64117ecace183 0.4s done #8 DONE 17.9s WARNING: failed to get git remote url: fatal: No remote configured to list refs from. make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' for osversion in 1809 20H2 ltsc2022; do \ OSVERSION=${osversion} make container-windows; \ done make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx build . \ ... skipping 68 lines ... #10 exporting config sha256:de4c840cec166f4e464251c9616f229dd5aa43723b42f80814c3bbe71c0e9716 0.0s done #10 pushing layers #10 pushing layers 1.8s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-1809-amd64@sha256:d6d0f8143c215f10b595b23ba7948d0a211400cb653b784b6a7888650bc6b563 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-1809-amd64@sha256:d6d0f8143c215f10b595b23ba7948d0a211400cb653b784b6a7888650bc6b563 0.4s done #10 DONE 11.2s WARNING: failed to get git remote url: fatal: No remote configured to list refs from. make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx build . \ --pull \ --output=type=registry \ --platform="windows/amd64" \ ... skipping 72 lines ... #10 exporting config sha256:a063044e41be6b8435d833cea4719fd377d39d48bbbec12098cc724ea9b9c432 0.0s done #10 pushing layers #10 pushing layers 1.8s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-20H2-amd64@sha256:9b667d5a1da9703b51b23901fbc9f1cfdd4098a676257b4e7ff8b825f8bb8a51 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-20H2-amd64@sha256:9b667d5a1da9703b51b23901fbc9f1cfdd4098a676257b4e7ff8b825f8bb8a51 0.4s done #10 DONE 12.2s WARNING: failed to get git remote url: fatal: No remote configured to list refs from. make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx build . \ --pull \ --output=type=registry \ --platform="windows/amd64" \ ... skipping 81 lines ... #10 exporting config sha256:f3e3e0542761dfe903f6947c52d4b1d17fdcdd091107cc21636c2de5199dd598 0.1s done #10 pushing layers #10 pushing layers 2.1s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-ltsc2022-amd64@sha256:e2269f5b93e34b720eabd46edee696ecf8a405f19933d41e03cb5d5114689c26 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-ltsc2022-amd64@sha256:e2269f5b93e34b720eabd46edee696ecf8a405f19933d41e03cb5d5114689c26 0.5s done #10 DONE 31.4s WARNING: failed to get git remote url: fatal: No remote configured to list refs from. make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker manifest create --amend capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64 capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64 capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-1809-amd64 capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-20H2-amd64 capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-ltsc2022-amd64 Created manifest list capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 # add "os.version" field to windows images (based on https://github.com/kubernetes/kubernetes/blob/master/build/pause/Makefile) set -x; \ for arch in amd64; do \ ... skipping 944 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 283 lines ... Jan 31 23:10:57.365: 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/31/23 23:10:57.368[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/31/23 23:10:57.665[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/31/23 23:10:57.739[0m I0131 23:10:57.818011 41681 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:10:57.873[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:10:57.917[0m Jan 31 23:10:57.918: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vbzfq" in namespace "azuredisk-1420" to be "Succeeded or Failed" Jan 31 23:10:57.957: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 39.626146ms Jan 31 23:10:59.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.080685555s Jan 31 23:11:01.999: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.081432665s Jan 31 23:11:03.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.079826724s Jan 31 23:11:06.001: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.083076003s Jan 31 23:11:07.996: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.078643811s ... skipping 75 lines ... Jan 31 23:13:39.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=true. Elapsed: 2m42.080342085s Jan 31 23:13:41.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=true. Elapsed: 2m44.080358235s Jan 31 23:13:43.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=true. Elapsed: 2m46.080211592s Jan 31 23:13:46.039: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.121366063s Jan 31 23:13:47.997: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2m50.079188834s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:13:47.997[0m Jan 31 23:13:47.997: INFO: Pod "azuredisk-volume-tester-vbzfq" satisfied condition "Succeeded or Failed" Jan 31 23:13:47.997: INFO: deleting Pod "azuredisk-1420"/"azuredisk-volume-tester-vbzfq" Jan 31 23:13:48.062: INFO: Pod azuredisk-volume-tester-vbzfq has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vbzfq in namespace azuredisk-1420 [38;5;243m01/31/23 23:13:48.062[0m [1mSTEP:[0m Destroying namespace "azuredisk-1420" for this suite. [38;5;243m01/31/23 23:13:48.111[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Jan 31 23:10:57.365: 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/31/23 23:10:57.368[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/31/23 23:10:57.665[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/31/23 23:10:57.739[0m I0131 23:10:57.818011 41681 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:10:57.873[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:10:57.917[0m Jan 31 23:10:57.918: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vbzfq" in namespace "azuredisk-1420" to be "Succeeded or Failed" Jan 31 23:10:57.957: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 39.626146ms Jan 31 23:10:59.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.080685555s Jan 31 23:11:01.999: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.081432665s Jan 31 23:11:03.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.079826724s Jan 31 23:11:06.001: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.083076003s Jan 31 23:11:07.996: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.078643811s ... skipping 75 lines ... Jan 31 23:13:39.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=true. Elapsed: 2m42.080342085s Jan 31 23:13:41.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=true. Elapsed: 2m44.080358235s Jan 31 23:13:43.998: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=true. Elapsed: 2m46.080211592s Jan 31 23:13:46.039: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.121366063s Jan 31 23:13:47.997: INFO: Pod "azuredisk-volume-tester-vbzfq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2m50.079188834s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:13:47.997[0m Jan 31 23:13:47.997: INFO: Pod "azuredisk-volume-tester-vbzfq" satisfied condition "Succeeded or Failed" Jan 31 23:13:47.997: INFO: deleting Pod "azuredisk-1420"/"azuredisk-volume-tester-vbzfq" Jan 31 23:13:48.062: INFO: Pod azuredisk-volume-tester-vbzfq has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vbzfq in namespace azuredisk-1420 [38;5;243m01/31/23 23:13:48.062[0m [1mSTEP:[0m Destroying namespace "azuredisk-1420" for this suite. [38;5;243m01/31/23 23:13:48.111[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 17 lines ... Jan 31 23:13:50.571: INFO: PersistentVolumeClaim pvc-5nh5n found but phase is Pending instead of Bound. Jan 31 23:13:52.608: INFO: PersistentVolumeClaim pvc-5nh5n found and phase=Bound (4.111324249s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:13:52.608[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:13:52.644[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:13:52.681[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:13:52.732[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:13:52.776[0m Jan 31 23:13:52.776: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7gnj2" in namespace "azuredisk-7548" to be "Succeeded or Failed" Jan 31 23:13:52.812: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 35.930304ms Jan 31 23:13:54.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073667788s Jan 31 23:13:56.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072775314s Jan 31 23:13:58.853: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.077225184s Jan 31 23:14:00.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.073495739s Jan 31 23:14:02.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.073477797s ... skipping 16 lines ... Jan 31 23:14:36.851: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=true. Elapsed: 44.075097796s Jan 31 23:14:38.851: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=true. Elapsed: 46.075690907s Jan 31 23:14:40.853: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=false. Elapsed: 48.076857646s Jan 31 23:14:42.852: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=false. Elapsed: 50.076263722s Jan 31 23:14:44.852: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 52.076425013s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:14:44.852[0m Jan 31 23:14:44.852: INFO: Pod "azuredisk-volume-tester-7gnj2" satisfied condition "Succeeded or Failed" Jan 31 23:14:44.852: INFO: deleting Pod "azuredisk-7548"/"azuredisk-volume-tester-7gnj2" Jan 31 23:14:44.901: INFO: Pod azuredisk-volume-tester-7gnj2 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7gnj2 in namespace azuredisk-7548 [38;5;243m01/31/23 23:14:44.901[0m Jan 31 23:14:44.953: INFO: deleting PVC "azuredisk-7548"/"pvc-5nh5n" Jan 31 23:14:44.953: INFO: Deleting PersistentVolumeClaim "pvc-5nh5n" ... skipping 38 lines ... Jan 31 23:13:50.571: INFO: PersistentVolumeClaim pvc-5nh5n found but phase is Pending instead of Bound. Jan 31 23:13:52.608: INFO: PersistentVolumeClaim pvc-5nh5n found and phase=Bound (4.111324249s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:13:52.608[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:13:52.644[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:13:52.681[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:13:52.732[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:13:52.776[0m Jan 31 23:13:52.776: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7gnj2" in namespace "azuredisk-7548" to be "Succeeded or Failed" Jan 31 23:13:52.812: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 35.930304ms Jan 31 23:13:54.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073667788s Jan 31 23:13:56.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072775314s Jan 31 23:13:58.853: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.077225184s Jan 31 23:14:00.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.073495739s Jan 31 23:14:02.849: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.073477797s ... skipping 16 lines ... Jan 31 23:14:36.851: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=true. Elapsed: 44.075097796s Jan 31 23:14:38.851: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=true. Elapsed: 46.075690907s Jan 31 23:14:40.853: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=false. Elapsed: 48.076857646s Jan 31 23:14:42.852: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Running", Reason="", readiness=false. Elapsed: 50.076263722s Jan 31 23:14:44.852: INFO: Pod "azuredisk-volume-tester-7gnj2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 52.076425013s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:14:44.852[0m Jan 31 23:14:44.852: INFO: Pod "azuredisk-volume-tester-7gnj2" satisfied condition "Succeeded or Failed" Jan 31 23:14:44.852: INFO: deleting Pod "azuredisk-7548"/"azuredisk-volume-tester-7gnj2" Jan 31 23:14:44.901: INFO: Pod azuredisk-volume-tester-7gnj2 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7gnj2 in namespace azuredisk-7548 [38;5;243m01/31/23 23:14:44.901[0m Jan 31 23:14:44.953: INFO: deleting PVC "azuredisk-7548"/"pvc-5nh5n" Jan 31 23:14:44.953: INFO: Deleting PersistentVolumeClaim "pvc-5nh5n" ... skipping 177 lines ... Jan 31 23:21:37.710: INFO: PersistentVolumeClaim pvc-g78p5 found and phase=Bound (4.100335555s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:21:37.71[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:21:37.743[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:21:37.775[0m I0131 23:21:37.775880 41681 resource_setup.go:89] adding PV (pvc-8948b156-f300-47d4-9e9a-dc5757f8c7bb) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:21:37.822[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:21:37.864[0m Jan 31 23:21:37.864: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hj8zv" in namespace "azuredisk-746" to be "Succeeded or Failed" Jan 31 23:21:37.900: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 35.583862ms Jan 31 23:21:39.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072045373s Jan 31 23:21:41.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071474722s Jan 31 23:21:43.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071936691s Jan 31 23:21:45.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072010637s Jan 31 23:21:47.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.071712852s ... skipping 19 lines ... Jan 31 23:22:27.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=true. Elapsed: 50.071528061s Jan 31 23:22:29.935: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=true. Elapsed: 52.07093991s Jan 31 23:22:31.935: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=false. Elapsed: 54.071150779s Jan 31 23:22:33.935: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=false. Elapsed: 56.070750849s Jan 31 23:22:35.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.071794384s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:22:35.936[0m Jan 31 23:22:35.936: INFO: Pod "azuredisk-volume-tester-hj8zv" satisfied condition "Succeeded or Failed" Jan 31 23:22:35.936: INFO: deleting Pod "azuredisk-746"/"azuredisk-volume-tester-hj8zv" Jan 31 23:22:35.992: INFO: Pod azuredisk-volume-tester-hj8zv has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hj8zv in namespace azuredisk-746 [38;5;243m01/31/23 23:22:35.992[0m Jan 31 23:22:36.039: INFO: deleting PVC "azuredisk-746"/"pvc-g78p5" Jan 31 23:22:36.039: INFO: Deleting PersistentVolumeClaim "pvc-g78p5" ... skipping 85 lines ... Jan 31 23:21:37.710: INFO: PersistentVolumeClaim pvc-g78p5 found and phase=Bound (4.100335555s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:21:37.71[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:21:37.743[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:21:37.775[0m I0131 23:21:37.775880 41681 resource_setup.go:89] adding PV (pvc-8948b156-f300-47d4-9e9a-dc5757f8c7bb) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:21:37.822[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:21:37.864[0m Jan 31 23:21:37.864: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hj8zv" in namespace "azuredisk-746" to be "Succeeded or Failed" Jan 31 23:21:37.900: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 35.583862ms Jan 31 23:21:39.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072045373s Jan 31 23:21:41.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071474722s Jan 31 23:21:43.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071936691s Jan 31 23:21:45.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072010637s Jan 31 23:21:47.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.071712852s ... skipping 19 lines ... Jan 31 23:22:27.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=true. Elapsed: 50.071528061s Jan 31 23:22:29.935: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=true. Elapsed: 52.07093991s Jan 31 23:22:31.935: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=false. Elapsed: 54.071150779s Jan 31 23:22:33.935: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Running", Reason="", readiness=false. Elapsed: 56.070750849s Jan 31 23:22:35.936: INFO: Pod "azuredisk-volume-tester-hj8zv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 58.071794384s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:22:35.936[0m Jan 31 23:22:35.936: INFO: Pod "azuredisk-volume-tester-hj8zv" satisfied condition "Succeeded or Failed" Jan 31 23:22:35.936: INFO: deleting Pod "azuredisk-746"/"azuredisk-volume-tester-hj8zv" Jan 31 23:22:35.992: INFO: Pod azuredisk-volume-tester-hj8zv has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hj8zv in namespace azuredisk-746 [38;5;243m01/31/23 23:22:35.992[0m Jan 31 23:22:36.039: INFO: deleting PVC "azuredisk-746"/"pvc-g78p5" Jan 31 23:22:36.039: INFO: Deleting PersistentVolumeClaim "pvc-g78p5" ... skipping 711 lines ... Jan 31 23:35:50.830: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-cp5jp] to have phase Bound Jan 31 23:35:50.865: INFO: PersistentVolumeClaim pvc-cp5jp found and phase=Bound (35.36047ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:35:50.865[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:35:50.898[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:35:50.93[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:35:50.93[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:35:50.969[0m Jan 31 23:35:50.969: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-7vfft" in namespace "azuredisk-5121" to be "Error status code" Jan 31 23:35:51.003: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 34.467523ms Jan 31 23:35:53.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069404347s Jan 31 23:35:55.037: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067986105s Jan 31 23:35:57.037: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067801499s Jan 31 23:35:59.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.068984292s Jan 31 23:36:01.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.068884101s ... skipping 10 lines ... Jan 31 23:36:23.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 32.069636893s Jan 31 23:36:25.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=true. Elapsed: 34.069279693s Jan 31 23:36:27.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=true. Elapsed: 36.070366662s Jan 31 23:36:29.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=true. Elapsed: 38.069818961s Jan 31 23:36:31.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=false. Elapsed: 40.06962729s Jan 31 23:36:33.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=false. Elapsed: 42.069699689s Jan 31 23:36:35.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Failed", Reason="", readiness=false. Elapsed: 44.069695531s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:36:35.039[0m Jan 31 23:36:35.039: INFO: Pod "azuredisk-volume-tester-7vfft" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:36:35.039[0m Jan 31 23:36:35.095: INFO: deleting Pod "azuredisk-5121"/"azuredisk-volume-tester-7vfft" Jan 31 23:36:35.131: INFO: Pod azuredisk-volume-tester-7vfft 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 54 lines ... Jan 31 23:35:50.830: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-cp5jp] to have phase Bound Jan 31 23:35:50.865: INFO: PersistentVolumeClaim pvc-cp5jp found and phase=Bound (35.36047ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:35:50.865[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:35:50.898[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:35:50.93[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:35:50.93[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:35:50.969[0m Jan 31 23:35:50.969: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-7vfft" in namespace "azuredisk-5121" to be "Error status code" Jan 31 23:35:51.003: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 34.467523ms Jan 31 23:35:53.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069404347s Jan 31 23:35:55.037: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067986105s Jan 31 23:35:57.037: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067801499s Jan 31 23:35:59.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.068984292s Jan 31 23:36:01.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.068884101s ... skipping 10 lines ... Jan 31 23:36:23.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Pending", Reason="", readiness=false. Elapsed: 32.069636893s Jan 31 23:36:25.038: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=true. Elapsed: 34.069279693s Jan 31 23:36:27.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=true. Elapsed: 36.070366662s Jan 31 23:36:29.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=true. Elapsed: 38.069818961s Jan 31 23:36:31.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=false. Elapsed: 40.06962729s Jan 31 23:36:33.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Running", Reason="", readiness=false. Elapsed: 42.069699689s Jan 31 23:36:35.039: INFO: Pod "azuredisk-volume-tester-7vfft": Phase="Failed", Reason="", readiness=false. Elapsed: 44.069695531s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:36:35.039[0m Jan 31 23:36:35.039: INFO: Pod "azuredisk-volume-tester-7vfft" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:36:35.039[0m Jan 31 23:36:35.095: INFO: deleting Pod "azuredisk-5121"/"azuredisk-volume-tester-7vfft" Jan 31 23:36:35.131: INFO: Pod azuredisk-volume-tester-7vfft 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 83 lines ... Jan 31 23:37:39.010: INFO: PersistentVolumeClaim pvc-z7496 found and phase=Bound (32.355864ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:37:39.01[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:37:39.042[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:37:39.075[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/31/23 23:37:39.116[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:37:46.676[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:37:46.713[0m Jan 31 23:37:46.714: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f7p9m" in namespace "azuredisk-174" to be "Succeeded or Failed" Jan 31 23:37:46.747: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 33.009321ms Jan 31 23:37:48.779: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06581353s Jan 31 23:37:50.779: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065846578s Jan 31 23:37:52.780: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066447152s Jan 31 23:37:54.783: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069060981s Jan 31 23:37:56.781: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067553826s ... skipping 20 lines ... Jan 31 23:38:38.781: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=true. Elapsed: 52.067056762s Jan 31 23:38:40.783: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=true. Elapsed: 54.069588451s Jan 31 23:38:42.782: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=false. Elapsed: 56.068889362s Jan 31 23:38:44.783: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=false. Elapsed: 58.069458897s Jan 31 23:38:46.782: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m0.068351074s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:38:46.782[0m Jan 31 23:38:46.782: INFO: Pod "azuredisk-volume-tester-f7p9m" satisfied condition "Succeeded or Failed" Jan 31 23:38:46.782: INFO: deleting Pod "azuredisk-174"/"azuredisk-volume-tester-f7p9m" Jan 31 23:38:46.831: INFO: Pod azuredisk-volume-tester-f7p9m has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-f7p9m in namespace azuredisk-174 [38;5;243m01/31/23 23:38:46.831[0m Jan 31 23:38:46.955: INFO: deleting PVC "azuredisk-174"/"pvc-z7496" Jan 31 23:38:46.955: INFO: Deleting PersistentVolumeClaim "pvc-z7496" ... skipping 36 lines ... Jan 31 23:37:39.010: INFO: PersistentVolumeClaim pvc-z7496 found and phase=Bound (32.355864ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:37:39.01[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:37:39.042[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:37:39.075[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/31/23 23:37:39.116[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:37:46.676[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:37:46.713[0m Jan 31 23:37:46.714: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f7p9m" in namespace "azuredisk-174" to be "Succeeded or Failed" Jan 31 23:37:46.747: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 33.009321ms Jan 31 23:37:48.779: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06581353s Jan 31 23:37:50.779: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065846578s Jan 31 23:37:52.780: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066447152s Jan 31 23:37:54.783: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069060981s Jan 31 23:37:56.781: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067553826s ... skipping 20 lines ... Jan 31 23:38:38.781: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=true. Elapsed: 52.067056762s Jan 31 23:38:40.783: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=true. Elapsed: 54.069588451s Jan 31 23:38:42.782: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=false. Elapsed: 56.068889362s Jan 31 23:38:44.783: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Running", Reason="", readiness=false. Elapsed: 58.069458897s Jan 31 23:38:46.782: INFO: Pod "azuredisk-volume-tester-f7p9m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m0.068351074s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:38:46.782[0m Jan 31 23:38:46.782: INFO: Pod "azuredisk-volume-tester-f7p9m" satisfied condition "Succeeded or Failed" Jan 31 23:38:46.782: INFO: deleting Pod "azuredisk-174"/"azuredisk-volume-tester-f7p9m" Jan 31 23:38:46.831: INFO: Pod azuredisk-volume-tester-f7p9m has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-f7p9m in namespace azuredisk-174 [38;5;243m01/31/23 23:38:46.831[0m Jan 31 23:38:46.955: INFO: deleting PVC "azuredisk-174"/"pvc-z7496" Jan 31 23:38:46.955: INFO: Deleting PersistentVolumeClaim "pvc-z7496" ... skipping 149 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 51 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:39:32.831[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:39:32.864[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:39:32.896[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:39:32.896[0m I0131 23:39:32.896617 41681 resource_setup.go:62] adding PV (pvc-8ca36a5f-d537-4521-99c0-9cd50e0ab759) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:39:32.896[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:39:32.935[0m Jan 31 23:39:32.935: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vv5nx" in namespace "azuredisk-995" to be "Succeeded or Failed" Jan 31 23:39:32.975: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 39.546621ms Jan 31 23:39:35.008: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072919852s Jan 31 23:39:37.009: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.073812522s Jan 31 23:39:39.009: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.073457585s Jan 31 23:39:41.008: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072470469s Jan 31 23:39:43.013: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.077906059s ... skipping 14 lines ... Jan 31 23:40:13.012: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=true. Elapsed: 40.07697874s Jan 31 23:40:15.010: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=true. Elapsed: 42.075237761s Jan 31 23:40:17.010: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=false. Elapsed: 44.074752622s Jan 31 23:40:19.011: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=false. Elapsed: 46.076016005s Jan 31 23:40:21.010: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.075073188s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:40:21.01[0m Jan 31 23:40:21.010: INFO: Pod "azuredisk-volume-tester-vv5nx" satisfied condition "Succeeded or Failed" Jan 31 23:40:21.010: INFO: deleting Pod "azuredisk-995"/"azuredisk-volume-tester-vv5nx" Jan 31 23:40:21.059: INFO: Pod azuredisk-volume-tester-vv5nx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vv5nx in namespace azuredisk-995 [38;5;243m01/31/23 23:40:21.06[0m Jan 31 23:40:21.105: INFO: deleting PVC "azuredisk-995"/"pvc-kwc4c" Jan 31 23:40:21.106: INFO: Deleting PersistentVolumeClaim "pvc-kwc4c" ... skipping 37 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:39:32.831[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:39:32.864[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:39:32.896[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:39:32.896[0m I0131 23:39:32.896617 41681 resource_setup.go:62] adding PV (pvc-8ca36a5f-d537-4521-99c0-9cd50e0ab759) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:39:32.896[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:39:32.935[0m Jan 31 23:39:32.935: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vv5nx" in namespace "azuredisk-995" to be "Succeeded or Failed" Jan 31 23:39:32.975: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 39.546621ms Jan 31 23:39:35.008: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072919852s Jan 31 23:39:37.009: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.073812522s Jan 31 23:39:39.009: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.073457585s Jan 31 23:39:41.008: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072470469s Jan 31 23:39:43.013: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.077906059s ... skipping 14 lines ... Jan 31 23:40:13.012: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=true. Elapsed: 40.07697874s Jan 31 23:40:15.010: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=true. Elapsed: 42.075237761s Jan 31 23:40:17.010: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=false. Elapsed: 44.074752622s Jan 31 23:40:19.011: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Running", Reason="", readiness=false. Elapsed: 46.076016005s Jan 31 23:40:21.010: INFO: Pod "azuredisk-volume-tester-vv5nx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.075073188s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:40:21.01[0m Jan 31 23:40:21.010: INFO: Pod "azuredisk-volume-tester-vv5nx" satisfied condition "Succeeded or Failed" Jan 31 23:40:21.010: INFO: deleting Pod "azuredisk-995"/"azuredisk-volume-tester-vv5nx" Jan 31 23:40:21.059: INFO: Pod azuredisk-volume-tester-vv5nx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vv5nx in namespace azuredisk-995 [38;5;243m01/31/23 23:40:21.06[0m Jan 31 23:40:21.105: INFO: deleting PVC "azuredisk-995"/"pvc-kwc4c" Jan 31 23:40:21.106: INFO: Deleting PersistentVolumeClaim "pvc-kwc4c" ... skipping 34 lines ... Jan 31 23:40:49.294: INFO: PersistentVolumeClaim pvc-7tljb found but phase is Pending instead of Bound. Jan 31 23:40:51.329: INFO: PersistentVolumeClaim pvc-7tljb found and phase=Bound (4.102070126s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:40:51.329[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:40:51.362[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:40:51.396[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:40:51.397[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/31/23 23:40:51.44[0m Jan 31 23:40:51.440: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2bnjz" in namespace "azuredisk-5185" to be "Succeeded or Failed" Jan 31 23:40:51.479: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 38.854534ms Jan 31 23:40:53.526: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086483419s Jan 31 23:40:55.512: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072459957s Jan 31 23:40:57.512: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.072201384s Jan 31 23:40:59.513: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072737064s Jan 31 23:41:01.512: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.072147547s ... skipping 14 lines ... Jan 31 23:41:31.516: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=true. Elapsed: 40.075865388s Jan 31 23:41:33.515: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=true. Elapsed: 42.074685002s Jan 31 23:41:35.516: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=false. Elapsed: 44.075630731s Jan 31 23:41:37.514: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=false. Elapsed: 46.073703387s Jan 31 23:41:39.516: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.075798494s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:41:39.516[0m Jan 31 23:41:39.516: INFO: Pod "azuredisk-volume-tester-2bnjz" satisfied condition "Succeeded or Failed" Jan 31 23:41:39.516: INFO: deleting Pod "azuredisk-5185"/"azuredisk-volume-tester-2bnjz" Jan 31 23:41:39.572: INFO: Pod azuredisk-volume-tester-2bnjz has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2bnjz in namespace azuredisk-5185 [38;5;243m01/31/23 23:41:39.573[0m Jan 31 23:41:39.626: INFO: deleting PVC "azuredisk-5185"/"pvc-7tljb" Jan 31 23:41:39.626: INFO: Deleting PersistentVolumeClaim "pvc-7tljb" ... skipping 38 lines ... Jan 31 23:40:49.294: INFO: PersistentVolumeClaim pvc-7tljb found but phase is Pending instead of Bound. Jan 31 23:40:51.329: INFO: PersistentVolumeClaim pvc-7tljb found and phase=Bound (4.102070126s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:40:51.329[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:40:51.362[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:40:51.396[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:40:51.397[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/31/23 23:40:51.44[0m Jan 31 23:40:51.440: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2bnjz" in namespace "azuredisk-5185" to be "Succeeded or Failed" Jan 31 23:40:51.479: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 38.854534ms Jan 31 23:40:53.526: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.086483419s Jan 31 23:40:55.512: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072459957s Jan 31 23:40:57.512: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.072201384s Jan 31 23:40:59.513: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072737064s Jan 31 23:41:01.512: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.072147547s ... skipping 14 lines ... Jan 31 23:41:31.516: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=true. Elapsed: 40.075865388s Jan 31 23:41:33.515: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=true. Elapsed: 42.074685002s Jan 31 23:41:35.516: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=false. Elapsed: 44.075630731s Jan 31 23:41:37.514: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Running", Reason="", readiness=false. Elapsed: 46.073703387s Jan 31 23:41:39.516: INFO: Pod "azuredisk-volume-tester-2bnjz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 48.075798494s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:41:39.516[0m Jan 31 23:41:39.516: INFO: Pod "azuredisk-volume-tester-2bnjz" satisfied condition "Succeeded or Failed" Jan 31 23:41:39.516: INFO: deleting Pod "azuredisk-5185"/"azuredisk-volume-tester-2bnjz" Jan 31 23:41:39.572: INFO: Pod azuredisk-volume-tester-2bnjz has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2bnjz in namespace azuredisk-5185 [38;5;243m01/31/23 23:41:39.573[0m Jan 31 23:41:39.626: INFO: deleting PVC "azuredisk-5185"/"pvc-7tljb" Jan 31 23:41:39.626: INFO: Deleting PersistentVolumeClaim "pvc-7tljb" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:42:24.971[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:42:25.004[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:42:25.037[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:42:25.038[0m I0131 23:42:25.038314 41681 resource_setup.go:62] adding PV (pvc-9de429d2-0c9d-49ce-b9d5-5fd002950ec4) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:42:25.038[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:42:25.076[0m Jan 31 23:42:25.076: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-t5t42" in namespace "azuredisk-2767" to be "Succeeded or Failed" Jan 31 23:42:25.115: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 39.12615ms Jan 31 23:42:27.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07407785s Jan 31 23:42:29.148: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072724312s Jan 31 23:42:31.149: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 6.073318156s Jan 31 23:42:33.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 8.07394244s Jan 31 23:42:35.151: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 10.075635522s ... skipping 17 lines ... Jan 31 23:43:11.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=true. Elapsed: 46.074317442s Jan 31 23:43:13.151: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=false. Elapsed: 48.074777212s Jan 31 23:43:15.151: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=false. Elapsed: 50.075591061s Jan 31 23:43:17.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=false. Elapsed: 52.07472483s Jan 31 23:43:19.149: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.073659876s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:43:19.149[0m Jan 31 23:43:19.150: INFO: Pod "azuredisk-volume-tester-t5t42" satisfied condition "Succeeded or Failed" Jan 31 23:43:19.150: INFO: deleting Pod "azuredisk-2767"/"azuredisk-volume-tester-t5t42" Jan 31 23:43:19.206: INFO: Pod azuredisk-volume-tester-t5t42 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-t5t42 in namespace azuredisk-2767 [38;5;243m01/31/23 23:43:19.206[0m Jan 31 23:43:19.256: INFO: deleting PVC "azuredisk-2767"/"pvc-zmwwz" Jan 31 23:43:19.256: INFO: Deleting PersistentVolumeClaim "pvc-zmwwz" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:42:24.971[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:42:25.004[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:42:25.037[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:42:25.038[0m I0131 23:42:25.038314 41681 resource_setup.go:62] adding PV (pvc-9de429d2-0c9d-49ce-b9d5-5fd002950ec4) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:42:25.038[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:42:25.076[0m Jan 31 23:42:25.076: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-t5t42" in namespace "azuredisk-2767" to be "Succeeded or Failed" Jan 31 23:42:25.115: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 39.12615ms Jan 31 23:42:27.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07407785s Jan 31 23:42:29.148: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072724312s Jan 31 23:42:31.149: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 6.073318156s Jan 31 23:42:33.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 8.07394244s Jan 31 23:42:35.151: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Pending", Reason="", readiness=false. Elapsed: 10.075635522s ... skipping 17 lines ... Jan 31 23:43:11.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=true. Elapsed: 46.074317442s Jan 31 23:43:13.151: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=false. Elapsed: 48.074777212s Jan 31 23:43:15.151: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=false. Elapsed: 50.075591061s Jan 31 23:43:17.150: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Running", Reason="", readiness=false. Elapsed: 52.07472483s Jan 31 23:43:19.149: INFO: Pod "azuredisk-volume-tester-t5t42": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.073659876s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:43:19.149[0m Jan 31 23:43:19.150: INFO: Pod "azuredisk-volume-tester-t5t42" satisfied condition "Succeeded or Failed" Jan 31 23:43:19.150: INFO: deleting Pod "azuredisk-2767"/"azuredisk-volume-tester-t5t42" Jan 31 23:43:19.206: INFO: Pod azuredisk-volume-tester-t5t42 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-t5t42 in namespace azuredisk-2767 [38;5;243m01/31/23 23:43:19.206[0m Jan 31 23:43:19.256: INFO: deleting PVC "azuredisk-2767"/"pvc-zmwwz" Jan 31 23:43:19.256: INFO: Deleting PersistentVolumeClaim "pvc-zmwwz" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:44:04.562[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:44:04.595[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:44:04.627[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:44:04.627[0m I0131 23:44:04.627735 41681 resource_setup.go:62] adding PV (pvc-ad4e40b5-144c-440b-b6db-4cbc09f29d5b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:44:04.627[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:44:04.668[0m Jan 31 23:44:04.668: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-qm6tx" in namespace "azuredisk-3866" to be "Succeeded or Failed" Jan 31 23:44:04.710: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 41.148913ms Jan 31 23:44:06.743: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074822403s Jan 31 23:44:08.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.075457734s Jan 31 23:44:10.743: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.074673129s Jan 31 23:44:12.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.075252287s Jan 31 23:44:14.743: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.074150294s ... skipping 15 lines ... Jan 31 23:44:46.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=true. Elapsed: 42.075288475s Jan 31 23:44:48.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=true. Elapsed: 44.075348716s Jan 31 23:44:50.746: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=false. Elapsed: 46.077465369s Jan 31 23:44:52.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=false. Elapsed: 48.075163505s Jan 31 23:44:54.746: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.077903096s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:44:54.746[0m Jan 31 23:44:54.747: INFO: Pod "azuredisk-volume-tester-qm6tx" satisfied condition "Succeeded or Failed" Jan 31 23:44:54.747: INFO: deleting Pod "azuredisk-3866"/"azuredisk-volume-tester-qm6tx" Jan 31 23:44:54.799: INFO: Pod azuredisk-volume-tester-qm6tx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qm6tx in namespace azuredisk-3866 [38;5;243m01/31/23 23:44:54.799[0m Jan 31 23:44:54.845: INFO: deleting PVC "azuredisk-3866"/"pvc-9jplr" Jan 31 23:44:54.845: INFO: Deleting PersistentVolumeClaim "pvc-9jplr" ... skipping 51 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:44:04.562[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:44:04.595[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:44:04.627[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:44:04.627[0m I0131 23:44:04.627735 41681 resource_setup.go:62] adding PV (pvc-ad4e40b5-144c-440b-b6db-4cbc09f29d5b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:44:04.627[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:44:04.668[0m Jan 31 23:44:04.668: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-qm6tx" in namespace "azuredisk-3866" to be "Succeeded or Failed" Jan 31 23:44:04.710: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 41.148913ms Jan 31 23:44:06.743: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074822403s Jan 31 23:44:08.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.075457734s Jan 31 23:44:10.743: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.074673129s Jan 31 23:44:12.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.075252287s Jan 31 23:44:14.743: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.074150294s ... skipping 15 lines ... Jan 31 23:44:46.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=true. Elapsed: 42.075288475s Jan 31 23:44:48.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=true. Elapsed: 44.075348716s Jan 31 23:44:50.746: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=false. Elapsed: 46.077465369s Jan 31 23:44:52.744: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Running", Reason="", readiness=false. Elapsed: 48.075163505s Jan 31 23:44:54.746: INFO: Pod "azuredisk-volume-tester-qm6tx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.077903096s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:44:54.746[0m Jan 31 23:44:54.747: INFO: Pod "azuredisk-volume-tester-qm6tx" satisfied condition "Succeeded or Failed" Jan 31 23:44:54.747: INFO: deleting Pod "azuredisk-3866"/"azuredisk-volume-tester-qm6tx" Jan 31 23:44:54.799: INFO: Pod azuredisk-volume-tester-qm6tx has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qm6tx in namespace azuredisk-3866 [38;5;243m01/31/23 23:44:54.799[0m Jan 31 23:44:54.845: INFO: deleting PVC "azuredisk-3866"/"pvc-9jplr" Jan 31 23:44:54.845: INFO: Deleting PersistentVolumeClaim "pvc-9jplr" ... skipping 122 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:46:36.774[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:46:36.806[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:46:36.84[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:46:36.84[0m I0131 23:46:36.840323 41681 resource_setup.go:62] adding PV (pvc-4d445d46-0dc9-49c0-ac6f-5952f1d47d07) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:46:36.84[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:46:36.88[0m Jan 31 23:46:36.880: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-5rgsp" in namespace "azuredisk-3854" to be "Error status code" Jan 31 23:46:36.917: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.896591ms Jan 31 23:46:38.950: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069968413s Jan 31 23:46:40.950: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069747695s Jan 31 23:46:42.952: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071465376s Jan 31 23:46:44.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.0706336s Jan 31 23:46:46.952: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.071167655s ... skipping 10 lines ... Jan 31 23:47:08.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 32.07071512s Jan 31 23:47:10.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=true. Elapsed: 34.070876018s Jan 31 23:47:12.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=true. Elapsed: 36.070769293s Jan 31 23:47:14.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=true. Elapsed: 38.071135825s Jan 31 23:47:16.953: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=false. Elapsed: 40.072887641s Jan 31 23:47:18.953: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=false. Elapsed: 42.072335259s Jan 31 23:47:20.953: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Failed", Reason="", readiness=false. Elapsed: 44.072248027s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:47:20.953[0m Jan 31 23:47:20.953: INFO: Pod "azuredisk-volume-tester-5rgsp" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:47:20.953[0m Jan 31 23:47:21.010: INFO: deleting Pod "azuredisk-3854"/"azuredisk-volume-tester-5rgsp" Jan 31 23:47:21.045: INFO: Pod azuredisk-volume-tester-5rgsp has the following logs: out-file : Access to the path 'C:\mnt\test-1\data' is denied. At line:1 char:1 + echo $null >> C:\mnt\test-1\data + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... skipping 49 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:46:36.774[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:46:36.806[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:46:36.84[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:46:36.84[0m I0131 23:46:36.840323 41681 resource_setup.go:62] adding PV (pvc-4d445d46-0dc9-49c0-ac6f-5952f1d47d07) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:46:36.84[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:46:36.88[0m Jan 31 23:46:36.880: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-5rgsp" in namespace "azuredisk-3854" to be "Error status code" Jan 31 23:46:36.917: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.896591ms Jan 31 23:46:38.950: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069968413s Jan 31 23:46:40.950: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069747695s Jan 31 23:46:42.952: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071465376s Jan 31 23:46:44.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.0706336s Jan 31 23:46:46.952: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.071167655s ... skipping 10 lines ... Jan 31 23:47:08.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Pending", Reason="", readiness=false. Elapsed: 32.07071512s Jan 31 23:47:10.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=true. Elapsed: 34.070876018s Jan 31 23:47:12.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=true. Elapsed: 36.070769293s Jan 31 23:47:14.951: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=true. Elapsed: 38.071135825s Jan 31 23:47:16.953: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=false. Elapsed: 40.072887641s Jan 31 23:47:18.953: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Running", Reason="", readiness=false. Elapsed: 42.072335259s Jan 31 23:47:20.953: INFO: Pod "azuredisk-volume-tester-5rgsp": Phase="Failed", Reason="", readiness=false. Elapsed: 44.072248027s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:47:20.953[0m Jan 31 23:47:20.953: INFO: Pod "azuredisk-volume-tester-5rgsp" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:47:20.953[0m Jan 31 23:47:21.010: INFO: deleting Pod "azuredisk-3854"/"azuredisk-volume-tester-5rgsp" Jan 31 23:47:21.045: INFO: Pod azuredisk-volume-tester-5rgsp 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 445 lines ... Jan 31 23:52:56.848: 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, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-h7p4j-5489695486\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 31 23:52:58.846: 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, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-h7p4j-5489695486\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/31/23 23:53:00.914[0m [1mSTEP:[0m check pod exec [38;5;243m01/31/23 23:53:01.013[0m Jan 31 23:53:01.013: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-8928 exec azuredisk-volume-tester-h7p4j-5489695486-tfc4p -- cmd /c type C:\mnt\test-1\data.txt' Jan 31 23:53:01.695: INFO: rc: 1 Jan 31 23:53:01.695: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-h7p4j-5489695486-tfc4p": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-8928 exec azuredisk-volume-tester-h7p4j-5489695486-tfc4p -- 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 31 23:53:03.696: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-8928 exec azuredisk-volume-tester-h7p4j-5489695486-tfc4p -- cmd /c type C:\mnt\test-1\data.txt' Jan 31 23:53:04.274: INFO: stderr: "" Jan 31 23:53:04.274: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/31/23 23:53:04.274[0m Jan 31 23:53:04.275: INFO: Deleting pod "azuredisk-volume-tester-h7p4j-5489695486-tfc4p" in namespace "azuredisk-8928" ... skipping 73 lines ... Jan 31 23:52:56.848: 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, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-h7p4j-5489695486\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 31 23:52:58.846: 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, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 31, 23, 52, 26, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"azuredisk-volume-tester-h7p4j-5489695486\" is progressing."}}, CollisionCount:(*int32)(nil)} [1mSTEP:[0m checking that the pod is running [38;5;243m01/31/23 23:53:00.914[0m [1mSTEP:[0m check pod exec [38;5;243m01/31/23 23:53:01.013[0m Jan 31 23:53:01.013: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-8928 exec azuredisk-volume-tester-h7p4j-5489695486-tfc4p -- cmd /c type C:\mnt\test-1\data.txt' Jan 31 23:53:01.695: INFO: rc: 1 Jan 31 23:53:01.695: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-h7p4j-5489695486-tfc4p": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-8928 exec azuredisk-volume-tester-h7p4j-5489695486-tfc4p -- 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 31 23:53:03.696: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-8928 exec azuredisk-volume-tester-h7p4j-5489695486-tfc4p -- cmd /c type C:\mnt\test-1\data.txt' Jan 31 23:53:04.274: INFO: stderr: "" Jan 31 23:53:04.274: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for deployment [38;5;243m01/31/23 23:53:04.274[0m Jan 31 23:53:04.275: INFO: Deleting pod "azuredisk-volume-tester-h7p4j-5489695486-tfc4p" in namespace "azuredisk-8928" ... skipping 308 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:54:47.05[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:54:47.082[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:54:47.115[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:54:47.115[0m I0131 23:54:47.115465 41681 resource_setup.go:62] adding PV (pvc-8c0b65d3-ad04-4deb-acf9-34b93b70fa80) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:54:47.115[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:54:47.157[0m Jan 31 23:54:47.157: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ts8jv" in namespace "azuredisk-5527" to be "Succeeded or Failed" Jan 31 23:54:47.199: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 42.44179ms Jan 31 23:54:49.235: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.077807947s Jan 31 23:54:51.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.076645307s Jan 31 23:54:53.236: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.078682538s Jan 31 23:54:55.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.076976327s Jan 31 23:54:57.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.077559343s ... skipping 17 lines ... Jan 31 23:55:33.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 46.077571577s Jan 31 23:55:35.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Running", Reason="", readiness=true. Elapsed: 48.077546493s Jan 31 23:55:37.237: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Running", Reason="", readiness=true. Elapsed: 50.080296846s Jan 31 23:55:39.236: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Running", Reason="", readiness=false. Elapsed: 52.07867878s Jan 31 23:55:41.235: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.077776336s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:55:41.235[0m Jan 31 23:55:41.235: INFO: Pod "azuredisk-volume-tester-ts8jv" satisfied condition "Succeeded or Failed" Jan 31 23:55:41.235: INFO: deleting Pod "azuredisk-5527"/"azuredisk-volume-tester-ts8jv" Jan 31 23:55:41.287: INFO: Pod azuredisk-volume-tester-ts8jv has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ts8jv in namespace azuredisk-5527 [38;5;243m01/31/23 23:55:41.287[0m ... skipping 90 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:54:47.05[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:54:47.082[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:54:47.115[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:54:47.115[0m I0131 23:54:47.115465 41681 resource_setup.go:62] adding PV (pvc-8c0b65d3-ad04-4deb-acf9-34b93b70fa80) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:54:47.115[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:54:47.157[0m Jan 31 23:54:47.157: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ts8jv" in namespace "azuredisk-5527" to be "Succeeded or Failed" Jan 31 23:54:47.199: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 42.44179ms Jan 31 23:54:49.235: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.077807947s Jan 31 23:54:51.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.076645307s Jan 31 23:54:53.236: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.078682538s Jan 31 23:54:55.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.076976327s Jan 31 23:54:57.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.077559343s ... skipping 17 lines ... Jan 31 23:55:33.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Pending", Reason="", readiness=false. Elapsed: 46.077571577s Jan 31 23:55:35.234: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Running", Reason="", readiness=true. Elapsed: 48.077546493s Jan 31 23:55:37.237: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Running", Reason="", readiness=true. Elapsed: 50.080296846s Jan 31 23:55:39.236: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Running", Reason="", readiness=false. Elapsed: 52.07867878s Jan 31 23:55:41.235: INFO: Pod "azuredisk-volume-tester-ts8jv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.077776336s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:55:41.235[0m Jan 31 23:55:41.235: INFO: Pod "azuredisk-volume-tester-ts8jv" satisfied condition "Succeeded or Failed" Jan 31 23:55:41.235: INFO: deleting Pod "azuredisk-5527"/"azuredisk-volume-tester-ts8jv" Jan 31 23:55:41.287: INFO: Pod azuredisk-volume-tester-ts8jv has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ts8jv in namespace azuredisk-5527 [38;5;243m01/31/23 23:55:41.287[0m ... skipping 95 lines ... Jan 31 23:56:45.662: INFO: PersistentVolumeClaim pvc-2ddkf found but phase is Pending instead of Bound. Jan 31 23:56:47.695: INFO: PersistentVolumeClaim pvc-2ddkf found and phase=Bound (4.09743507s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:56:47.695[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:56:47.728[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:56:47.76[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:56:47.76[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:56:47.799[0m Jan 31 23:56:47.799: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cxk8s" in namespace "azuredisk-3026" to be "Succeeded or Failed" Jan 31 23:56:47.831: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 32.185102ms Jan 31 23:56:49.874: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074387194s Jan 31 23:56:51.864: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065098032s Jan 31 23:56:53.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066718834s Jan 31 23:56:55.864: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065104223s Jan 31 23:56:57.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067139805s ... skipping 12 lines ... Jan 31 23:57:23.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=true. Elapsed: 36.066645372s Jan 31 23:57:25.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=true. Elapsed: 38.066966544s Jan 31 23:57:27.867: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=false. Elapsed: 40.0677582s Jan 31 23:57:29.865: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=false. Elapsed: 42.066155513s Jan 31 23:57:31.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.066518045s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:57:31.866[0m Jan 31 23:57:31.866: INFO: Pod "azuredisk-volume-tester-cxk8s" satisfied condition "Succeeded or Failed" Jan 31 23:57:31.897: INFO: deleting Pod "azuredisk-3026"/"azuredisk-volume-tester-cxk8s" Jan 31 23:57:31.945: INFO: Pod azuredisk-volume-tester-cxk8s has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cxk8s in namespace azuredisk-3026 [38;5;243m01/31/23 23:57:31.945[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:57:31.989[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/31/23 23:57:52.054[0m [1mSTEP:[0m Prow test resource group: capz-3oaokj [38;5;243m01/31/23 23:57:52.055[0m ... skipping 16 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:58:12.494[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:58:12.527[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:58:12.559[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:58:12.559[0m I0131 23:58:12.559785 41681 resource_setup.go:62] adding PV (pvc-dbd32bdd-3f2d-486e-af15-612388941558) to pod () [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/31/23 23:58:12.559[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:58:12.594[0m Jan 31 23:58:12.594: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7xdx6" in namespace "azuredisk-3026" to be "Succeeded or Failed" Jan 31 23:58:12.626: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 31.869376ms Jan 31 23:58:14.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066851477s Jan 31 23:58:16.664: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06973573s Jan 31 23:58:18.660: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065082611s Jan 31 23:58:20.660: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065398276s Jan 31 23:58:22.660: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065062028s ... skipping 9 lines ... Jan 31 23:58:42.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=true. Elapsed: 30.066556678s Jan 31 23:58:44.663: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=true. Elapsed: 32.068173956s Jan 31 23:58:46.664: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=true. Elapsed: 34.069218904s Jan 31 23:58:48.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=false. Elapsed: 36.066169867s Jan 31 23:58:50.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.06684917s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:58:50.661[0m Jan 31 23:58:50.662: INFO: Pod "azuredisk-volume-tester-7xdx6" satisfied condition "Succeeded or Failed" Jan 31 23:58:50.662: INFO: deleting Pod "azuredisk-3026"/"azuredisk-volume-tester-7xdx6" Jan 31 23:58:50.707: INFO: Pod azuredisk-volume-tester-7xdx6 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7xdx6 in namespace azuredisk-3026 [38;5;243m01/31/23 23:58:50.707[0m Jan 31 23:58:50.754: INFO: deleting PVC "azuredisk-3026"/"pvc-bwq5c" Jan 31 23:58:50.754: INFO: Deleting PersistentVolumeClaim "pvc-bwq5c" ... skipping 12 lines ... Jan 31 23:59:31.143: INFO: Claim "pvc-bwq5c" in namespace "azuredisk-3026" doesn't exist in the system Jan 31 23:59:31.143: INFO: deleting StorageClass azuredisk-3026-disk.csi.azure.com-dynamic-sc-7qk9n [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-v24ql [38;5;243m01/31/23 23:59:31.179[0m Jan 31 23:59:31.221: INFO: skip deleting VolumeSnapshotClass azuredisk-3026-disk.csi.azure.com-dynamic-sc-479gn Jan 31 23:59:31.221: INFO: Deleting resource group azuredisk-csi-driver-test-12913421-a1c3-11ed-b1ee-52ab6296bd3c Feb 1 00:00:45.081: INFO: deleting Pod "azuredisk-3026"/"azuredisk-volume-tester-cxk8s" Feb 1 00:00:45.113: INFO: Error getting logs for pod azuredisk-volume-tester-cxk8s: the server could not find the requested resource (get pods azuredisk-volume-tester-cxk8s) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cxk8s in namespace azuredisk-3026 [38;5;243m02/01/23 00:00:45.113[0m Feb 1 00:00:45.145: INFO: deleting PVC "azuredisk-3026"/"pvc-2ddkf" Feb 1 00:00:45.145: INFO: Deleting PersistentVolumeClaim "pvc-2ddkf" [1mSTEP:[0m waiting for claim's PV "pvc-3f24ab8c-8cb2-4e36-9ee5-591c07ac33fc" to be deleted [38;5;243m02/01/23 00:00:45.181[0m Feb 1 00:00:45.181: INFO: Waiting up to 10m0s for PersistentVolume pvc-3f24ab8c-8cb2-4e36-9ee5-591c07ac33fc to get deleted Feb 1 00:00:45.214: INFO: PersistentVolume pvc-3f24ab8c-8cb2-4e36-9ee5-591c07ac33fc found and phase=Released (32.684808ms) ... skipping 29 lines ... Jan 31 23:56:45.662: INFO: PersistentVolumeClaim pvc-2ddkf found but phase is Pending instead of Bound. Jan 31 23:56:47.695: INFO: PersistentVolumeClaim pvc-2ddkf found and phase=Bound (4.09743507s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:56:47.695[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:56:47.728[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:56:47.76[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:56:47.76[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:56:47.799[0m Jan 31 23:56:47.799: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cxk8s" in namespace "azuredisk-3026" to be "Succeeded or Failed" Jan 31 23:56:47.831: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 32.185102ms Jan 31 23:56:49.874: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074387194s Jan 31 23:56:51.864: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065098032s Jan 31 23:56:53.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066718834s Jan 31 23:56:55.864: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065104223s Jan 31 23:56:57.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067139805s ... skipping 12 lines ... Jan 31 23:57:23.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=true. Elapsed: 36.066645372s Jan 31 23:57:25.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=true. Elapsed: 38.066966544s Jan 31 23:57:27.867: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=false. Elapsed: 40.0677582s Jan 31 23:57:29.865: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Running", Reason="", readiness=false. Elapsed: 42.066155513s Jan 31 23:57:31.866: INFO: Pod "azuredisk-volume-tester-cxk8s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.066518045s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:57:31.866[0m Jan 31 23:57:31.866: INFO: Pod "azuredisk-volume-tester-cxk8s" satisfied condition "Succeeded or Failed" Jan 31 23:57:31.897: INFO: deleting Pod "azuredisk-3026"/"azuredisk-volume-tester-cxk8s" Jan 31 23:57:31.945: INFO: Pod azuredisk-volume-tester-cxk8s has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cxk8s in namespace azuredisk-3026 [38;5;243m01/31/23 23:57:31.945[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:57:31.989[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/31/23 23:57:52.054[0m [1mSTEP:[0m Prow test resource group: capz-3oaokj [38;5;243m01/31/23 23:57:52.055[0m ... skipping 16 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:58:12.494[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:58:12.527[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:58:12.559[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:58:12.559[0m I0131 23:58:12.559785 41681 resource_setup.go:62] adding PV (pvc-dbd32bdd-3f2d-486e-af15-612388941558) to pod () [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/31/23 23:58:12.559[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:58:12.594[0m Jan 31 23:58:12.594: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7xdx6" in namespace "azuredisk-3026" to be "Succeeded or Failed" Jan 31 23:58:12.626: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 31.869376ms Jan 31 23:58:14.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066851477s Jan 31 23:58:16.664: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06973573s Jan 31 23:58:18.660: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065082611s Jan 31 23:58:20.660: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065398276s Jan 31 23:58:22.660: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065062028s ... skipping 9 lines ... Jan 31 23:58:42.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=true. Elapsed: 30.066556678s Jan 31 23:58:44.663: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=true. Elapsed: 32.068173956s Jan 31 23:58:46.664: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=true. Elapsed: 34.069218904s Jan 31 23:58:48.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Running", Reason="", readiness=false. Elapsed: 36.066169867s Jan 31 23:58:50.661: INFO: Pod "azuredisk-volume-tester-7xdx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.06684917s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:58:50.661[0m Jan 31 23:58:50.662: INFO: Pod "azuredisk-volume-tester-7xdx6" satisfied condition "Succeeded or Failed" Jan 31 23:58:50.662: INFO: deleting Pod "azuredisk-3026"/"azuredisk-volume-tester-7xdx6" Jan 31 23:58:50.707: INFO: Pod azuredisk-volume-tester-7xdx6 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-7xdx6 in namespace azuredisk-3026 [38;5;243m01/31/23 23:58:50.707[0m Jan 31 23:58:50.754: INFO: deleting PVC "azuredisk-3026"/"pvc-bwq5c" Jan 31 23:58:50.754: INFO: Deleting PersistentVolumeClaim "pvc-bwq5c" ... skipping 12 lines ... Jan 31 23:59:31.143: INFO: Claim "pvc-bwq5c" in namespace "azuredisk-3026" doesn't exist in the system Jan 31 23:59:31.143: INFO: deleting StorageClass azuredisk-3026-disk.csi.azure.com-dynamic-sc-7qk9n [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-v24ql [38;5;243m01/31/23 23:59:31.179[0m Jan 31 23:59:31.221: INFO: skip deleting VolumeSnapshotClass azuredisk-3026-disk.csi.azure.com-dynamic-sc-479gn Jan 31 23:59:31.221: INFO: Deleting resource group azuredisk-csi-driver-test-12913421-a1c3-11ed-b1ee-52ab6296bd3c Feb 1 00:00:45.081: INFO: deleting Pod "azuredisk-3026"/"azuredisk-volume-tester-cxk8s" Feb 1 00:00:45.113: INFO: Error getting logs for pod azuredisk-volume-tester-cxk8s: the server could not find the requested resource (get pods azuredisk-volume-tester-cxk8s) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cxk8s in namespace azuredisk-3026 [38;5;243m02/01/23 00:00:45.113[0m Feb 1 00:00:45.145: INFO: deleting PVC "azuredisk-3026"/"pvc-2ddkf" Feb 1 00:00:45.145: INFO: Deleting PersistentVolumeClaim "pvc-2ddkf" [1mSTEP:[0m waiting for claim's PV "pvc-3f24ab8c-8cb2-4e36-9ee5-591c07ac33fc" to be deleted [38;5;243m02/01/23 00:00:45.181[0m Feb 1 00:00:45.181: INFO: Waiting up to 10m0s for PersistentVolume pvc-3f24ab8c-8cb2-4e36-9ee5-591c07ac33fc to get deleted Feb 1 00:00:45.214: INFO: PersistentVolume pvc-3f24ab8c-8cb2-4e36-9ee5-591c07ac33fc found and phase=Released (32.684808ms) ... skipping 28 lines ... Feb 1 00:00:58.367: INFO: PersistentVolumeClaim pvc-5fp52 found but phase is Pending instead of Bound. Feb 1 00:01:00.399: INFO: PersistentVolumeClaim pvc-5fp52 found and phase=Bound (4.098667798s) [1mSTEP:[0m checking the PVC [38;5;243m02/01/23 00:01:00.399[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:01:00.432[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:01:00.465[0m [1mSTEP:[0m deploying the pod [38;5;243m02/01/23 00:01:00.466[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:01:00.505[0m Feb 1 00:01:00.505: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-glcft" in namespace "azuredisk-7850" to be "Succeeded or Failed" Feb 1 00:01:00.538: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 33.18376ms Feb 1 00:01:02.572: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066865483s Feb 1 00:01:04.571: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065968872s Feb 1 00:01:06.572: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067392275s Feb 1 00:01:08.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.068059681s Feb 1 00:01:10.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067709089s ... skipping 13 lines ... Feb 1 00:01:38.574: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=true. Elapsed: 38.068720972s Feb 1 00:01:40.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=true. Elapsed: 40.067862482s Feb 1 00:01:42.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=false. Elapsed: 42.068353043s Feb 1 00:01:44.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=false. Elapsed: 44.068442758s Feb 1 00:01:46.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 46.067601933s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:01:46.573[0m Feb 1 00:01:46.573: INFO: Pod "azuredisk-volume-tester-glcft" satisfied condition "Succeeded or Failed" Feb 1 00:01:46.605: INFO: deleting Pod "azuredisk-7850"/"azuredisk-volume-tester-glcft" Feb 1 00:01:46.649: INFO: Pod azuredisk-volume-tester-glcft has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-glcft in namespace azuredisk-7850 [38;5;243m02/01/23 00:01:46.649[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m02/01/23 00:01:46.696[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m02/01/23 00:02:06.763[0m [1mSTEP:[0m Prow test resource group: capz-3oaokj [38;5;243m02/01/23 00:02:06.764[0m ... skipping 35 lines ... [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:02:52.924[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:02:52.957[0m [1mSTEP:[0m setting up the pod [38;5;243m02/01/23 00:02:52.957[0m I0201 00:02:52.957708 41681 resource_setup.go:62] adding PV (pvc-296e46fe-7bcd-43b4-b1ee-ee30e29ace1c) to pod () [1mSTEP:[0m Set pod anti-affinity to make sure two pods are scheduled on different nodes [38;5;243m02/01/23 00:02:52.957[0m [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m02/01/23 00:02:52.957[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:02:52.998[0m Feb 1 00:02:52.998: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c6xnm" in namespace "azuredisk-7850" to be "Succeeded or Failed" Feb 1 00:02:53.034: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 35.708105ms Feb 1 00:02:55.068: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069917674s Feb 1 00:02:57.071: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072721452s Feb 1 00:02:59.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.07071211s Feb 1 00:03:01.070: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072019378s Feb 1 00:03:03.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.070579273s ... skipping 86 lines ... Feb 1 00:05:57.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=true. Elapsed: 3m4.071050219s Feb 1 00:05:59.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.070756336s Feb 1 00:06:01.072: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.073894623s Feb 1 00:06:03.070: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.07176396s Feb 1 00:06:05.068: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 3m12.070172296s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:06:05.068[0m Feb 1 00:06:05.069: INFO: Pod "azuredisk-volume-tester-c6xnm" satisfied condition "Succeeded or Failed" Feb 1 00:06:05.069: INFO: deleting Pod "azuredisk-7850"/"azuredisk-volume-tester-c6xnm" Feb 1 00:06:05.125: INFO: Pod azuredisk-volume-tester-c6xnm has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-c6xnm in namespace azuredisk-7850 [38;5;243m02/01/23 00:06:05.125[0m Feb 1 00:06:05.169: INFO: deleting PVC "azuredisk-7850"/"pvc-b6gfb" Feb 1 00:06:05.169: INFO: Deleting PersistentVolumeClaim "pvc-b6gfb" ... skipping 15 lines ... Feb 1 00:06:45.651: INFO: Pod azuredisk-volume-tester-2nwgs has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2nwgs in namespace azuredisk-7850 [38;5;243m02/01/23 00:06:45.652[0m [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-ctqgw [38;5;243m02/01/23 00:06:45.692[0m Feb 1 00:06:45.730: INFO: skip deleting VolumeSnapshotClass azuredisk-7850-disk.csi.azure.com-dynamic-sc-66pw5 Feb 1 00:06:45.730: INFO: Deleting resource group azuredisk-csi-driver-test-aa62c01d-a1c3-11ed-b1ee-52ab6296bd3c Feb 1 00:08:02.094: INFO: deleting Pod "azuredisk-7850"/"azuredisk-volume-tester-glcft" Feb 1 00:08:02.127: INFO: Error getting logs for pod azuredisk-volume-tester-glcft: the server could not find the requested resource (get pods azuredisk-volume-tester-glcft) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-glcft in namespace azuredisk-7850 [38;5;243m02/01/23 00:08:02.127[0m Feb 1 00:08:02.159: INFO: deleting PVC "azuredisk-7850"/"pvc-5fp52" Feb 1 00:08:02.159: INFO: Deleting PersistentVolumeClaim "pvc-5fp52" [1mSTEP:[0m waiting for claim's PV "pvc-6255fa29-b198-4061-8c36-47b65427deda" to be deleted [38;5;243m02/01/23 00:08:02.195[0m Feb 1 00:08:02.195: INFO: Waiting up to 10m0s for PersistentVolume pvc-6255fa29-b198-4061-8c36-47b65427deda to get deleted Feb 1 00:08:02.233: INFO: PersistentVolume pvc-6255fa29-b198-4061-8c36-47b65427deda found and phase=Released (37.445261ms) ... skipping 29 lines ... Feb 1 00:00:58.367: INFO: PersistentVolumeClaim pvc-5fp52 found but phase is Pending instead of Bound. Feb 1 00:01:00.399: INFO: PersistentVolumeClaim pvc-5fp52 found and phase=Bound (4.098667798s) [1mSTEP:[0m checking the PVC [38;5;243m02/01/23 00:01:00.399[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:01:00.432[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:01:00.465[0m [1mSTEP:[0m deploying the pod [38;5;243m02/01/23 00:01:00.466[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:01:00.505[0m Feb 1 00:01:00.505: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-glcft" in namespace "azuredisk-7850" to be "Succeeded or Failed" Feb 1 00:01:00.538: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 33.18376ms Feb 1 00:01:02.572: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066865483s Feb 1 00:01:04.571: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065968872s Feb 1 00:01:06.572: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067392275s Feb 1 00:01:08.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.068059681s Feb 1 00:01:10.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067709089s ... skipping 13 lines ... Feb 1 00:01:38.574: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=true. Elapsed: 38.068720972s Feb 1 00:01:40.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=true. Elapsed: 40.067862482s Feb 1 00:01:42.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=false. Elapsed: 42.068353043s Feb 1 00:01:44.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Running", Reason="", readiness=false. Elapsed: 44.068442758s Feb 1 00:01:46.573: INFO: Pod "azuredisk-volume-tester-glcft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 46.067601933s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:01:46.573[0m Feb 1 00:01:46.573: INFO: Pod "azuredisk-volume-tester-glcft" satisfied condition "Succeeded or Failed" Feb 1 00:01:46.605: INFO: deleting Pod "azuredisk-7850"/"azuredisk-volume-tester-glcft" Feb 1 00:01:46.649: INFO: Pod azuredisk-volume-tester-glcft has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-glcft in namespace azuredisk-7850 [38;5;243m02/01/23 00:01:46.649[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m02/01/23 00:01:46.696[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m02/01/23 00:02:06.763[0m [1mSTEP:[0m Prow test resource group: capz-3oaokj [38;5;243m02/01/23 00:02:06.764[0m ... skipping 35 lines ... [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:02:52.924[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:02:52.957[0m [1mSTEP:[0m setting up the pod [38;5;243m02/01/23 00:02:52.957[0m I0201 00:02:52.957708 41681 resource_setup.go:62] adding PV (pvc-296e46fe-7bcd-43b4-b1ee-ee30e29ace1c) to pod () [1mSTEP:[0m Set pod anti-affinity to make sure two pods are scheduled on different nodes [38;5;243m02/01/23 00:02:52.957[0m [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m02/01/23 00:02:52.957[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:02:52.998[0m Feb 1 00:02:52.998: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c6xnm" in namespace "azuredisk-7850" to be "Succeeded or Failed" Feb 1 00:02:53.034: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 35.708105ms Feb 1 00:02:55.068: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069917674s Feb 1 00:02:57.071: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072721452s Feb 1 00:02:59.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.07071211s Feb 1 00:03:01.070: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072019378s Feb 1 00:03:03.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.070579273s ... skipping 86 lines ... Feb 1 00:05:57.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=true. Elapsed: 3m4.071050219s Feb 1 00:05:59.069: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.070756336s Feb 1 00:06:01.072: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.073894623s Feb 1 00:06:03.070: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.07176396s Feb 1 00:06:05.068: INFO: Pod "azuredisk-volume-tester-c6xnm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 3m12.070172296s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:06:05.068[0m Feb 1 00:06:05.069: INFO: Pod "azuredisk-volume-tester-c6xnm" satisfied condition "Succeeded or Failed" Feb 1 00:06:05.069: INFO: deleting Pod "azuredisk-7850"/"azuredisk-volume-tester-c6xnm" Feb 1 00:06:05.125: INFO: Pod azuredisk-volume-tester-c6xnm has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-c6xnm in namespace azuredisk-7850 [38;5;243m02/01/23 00:06:05.125[0m Feb 1 00:06:05.169: INFO: deleting PVC "azuredisk-7850"/"pvc-b6gfb" Feb 1 00:06:05.169: INFO: Deleting PersistentVolumeClaim "pvc-b6gfb" ... skipping 15 lines ... Feb 1 00:06:45.651: INFO: Pod azuredisk-volume-tester-2nwgs has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2nwgs in namespace azuredisk-7850 [38;5;243m02/01/23 00:06:45.652[0m [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-ctqgw [38;5;243m02/01/23 00:06:45.692[0m Feb 1 00:06:45.730: INFO: skip deleting VolumeSnapshotClass azuredisk-7850-disk.csi.azure.com-dynamic-sc-66pw5 Feb 1 00:06:45.730: INFO: Deleting resource group azuredisk-csi-driver-test-aa62c01d-a1c3-11ed-b1ee-52ab6296bd3c Feb 1 00:08:02.094: INFO: deleting Pod "azuredisk-7850"/"azuredisk-volume-tester-glcft" Feb 1 00:08:02.127: INFO: Error getting logs for pod azuredisk-volume-tester-glcft: the server could not find the requested resource (get pods azuredisk-volume-tester-glcft) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-glcft in namespace azuredisk-7850 [38;5;243m02/01/23 00:08:02.127[0m Feb 1 00:08:02.159: INFO: deleting PVC "azuredisk-7850"/"pvc-5fp52" Feb 1 00:08:02.159: INFO: Deleting PersistentVolumeClaim "pvc-5fp52" [1mSTEP:[0m waiting for claim's PV "pvc-6255fa29-b198-4061-8c36-47b65427deda" to be deleted [38;5;243m02/01/23 00:08:02.195[0m Feb 1 00:08:02.195: INFO: Waiting up to 10m0s for PersistentVolume pvc-6255fa29-b198-4061-8c36-47b65427deda to get deleted Feb 1 00:08:02.233: INFO: PersistentVolume pvc-6255fa29-b198-4061-8c36-47b65427deda found and phase=Released (37.445261ms) ... skipping 55 lines ... Feb 1 00:08:25.664: INFO: PersistentVolumeClaim pvc-pzjn4 found and phase=Bound (4.105030759s) [1mSTEP:[0m checking the PVC [38;5;243m02/01/23 00:08:25.665[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:08:25.697[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:08:25.729[0m I0201 00:08:25.729739 41681 resource_setup.go:89] adding PV (pvc-a2bc2521-4803-42ac-9176-ea27d3cfbe07) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/01/23 00:08:25.729[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:08:25.77[0m Feb 1 00:08:25.771: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-h9xzs" in namespace "azuredisk-2975" to be "Succeeded or Failed" Feb 1 00:08:25.808: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 37.360483ms Feb 1 00:08:27.848: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.077606592s Feb 1 00:08:29.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072563963s Feb 1 00:08:31.849: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.078395793s Feb 1 00:08:33.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072598421s Feb 1 00:08:35.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.072356761s ... skipping 18 lines ... Feb 1 00:09:13.844: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=true. Elapsed: 48.073011086s Feb 1 00:09:15.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=true. Elapsed: 50.072368566s Feb 1 00:09:17.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=false. Elapsed: 52.072502782s Feb 1 00:09:19.844: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=false. Elapsed: 54.07315415s Feb 1 00:09:21.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 56.072136789s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:09:21.843[0m Feb 1 00:09:21.843: INFO: Pod "azuredisk-volume-tester-h9xzs" satisfied condition "Succeeded or Failed" Feb 1 00:09:21.843: INFO: deleting Pod "azuredisk-2975"/"azuredisk-volume-tester-h9xzs" Feb 1 00:09:21.897: INFO: Pod azuredisk-volume-tester-h9xzs has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-h9xzs in namespace azuredisk-2975 [38;5;243m02/01/23 00:09:21.897[0m Feb 1 00:09:21.945: INFO: deleting PVC "azuredisk-2975"/"pvc-pzjn4" Feb 1 00:09:21.945: INFO: Deleting PersistentVolumeClaim "pvc-pzjn4" ... skipping 85 lines ... Feb 1 00:08:25.664: INFO: PersistentVolumeClaim pvc-pzjn4 found and phase=Bound (4.105030759s) [1mSTEP:[0m checking the PVC [38;5;243m02/01/23 00:08:25.665[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:08:25.697[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:08:25.729[0m I0201 00:08:25.729739 41681 resource_setup.go:89] adding PV (pvc-a2bc2521-4803-42ac-9176-ea27d3cfbe07) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/01/23 00:08:25.729[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:08:25.77[0m Feb 1 00:08:25.771: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-h9xzs" in namespace "azuredisk-2975" to be "Succeeded or Failed" Feb 1 00:08:25.808: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 37.360483ms Feb 1 00:08:27.848: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.077606592s Feb 1 00:08:29.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072563963s Feb 1 00:08:31.849: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.078395793s Feb 1 00:08:33.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.072598421s Feb 1 00:08:35.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.072356761s ... skipping 18 lines ... Feb 1 00:09:13.844: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=true. Elapsed: 48.073011086s Feb 1 00:09:15.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=true. Elapsed: 50.072368566s Feb 1 00:09:17.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=false. Elapsed: 52.072502782s Feb 1 00:09:19.844: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Running", Reason="", readiness=false. Elapsed: 54.07315415s Feb 1 00:09:21.843: INFO: Pod "azuredisk-volume-tester-h9xzs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 56.072136789s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:09:21.843[0m Feb 1 00:09:21.843: INFO: Pod "azuredisk-volume-tester-h9xzs" satisfied condition "Succeeded or Failed" Feb 1 00:09:21.843: INFO: deleting Pod "azuredisk-2975"/"azuredisk-volume-tester-h9xzs" Feb 1 00:09:21.897: INFO: Pod azuredisk-volume-tester-h9xzs has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-h9xzs in namespace azuredisk-2975 [38;5;243m02/01/23 00:09:21.897[0m Feb 1 00:09:21.945: INFO: deleting PVC "azuredisk-2975"/"pvc-pzjn4" Feb 1 00:09:21.945: INFO: Deleting PersistentVolumeClaim "pvc-pzjn4" ... skipping 606 lines ... [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:18:39.907[0m Feb 1 00:18:39.907: INFO: deleting Pod "azuredisk-6758"/"azuredisk-volume-tester-wc79b" Feb 1 00:18:39.953: INFO: Pod azuredisk-volume-tester-wc79b has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wc79b in namespace azuredisk-6758 [38;5;243m02/01/23 00:18:39.953[0m Feb 1 00:19:06.069: INFO: deleting Pod "azuredisk-6758"/"azuredisk-volume-tester-wc79b" Feb 1 00:19:06.105: INFO: Error getting logs for pod azuredisk-volume-tester-wc79b: the server could not find the requested resource (get pods azuredisk-volume-tester-wc79b) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wc79b in namespace azuredisk-6758 [38;5;243m02/01/23 00:19:06.105[0m Feb 1 00:19:06.139: INFO: deleting PVC "azuredisk-6758"/"pvc-znhh5" Feb 1 00:19:06.139: INFO: Deleting PersistentVolumeClaim "pvc-znhh5" [1mSTEP:[0m waiting for claim's PV "pvc-e8fdcd84-54e2-42d9-a76f-0108cd6f4c7d" to be deleted [38;5;243m02/01/23 00:19:06.181[0m Feb 1 00:19:06.181: INFO: Waiting up to 10m0s for PersistentVolume pvc-e8fdcd84-54e2-42d9-a76f-0108cd6f4c7d to get deleted Feb 1 00:19:06.217: INFO: PersistentVolume pvc-e8fdcd84-54e2-42d9-a76f-0108cd6f4c7d found and phase=Released (36.096334ms) ... skipping 63 lines ... [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:18:39.907[0m Feb 1 00:18:39.907: INFO: deleting Pod "azuredisk-6758"/"azuredisk-volume-tester-wc79b" Feb 1 00:18:39.953: INFO: Pod azuredisk-volume-tester-wc79b has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wc79b in namespace azuredisk-6758 [38;5;243m02/01/23 00:18:39.953[0m Feb 1 00:19:06.069: INFO: deleting Pod "azuredisk-6758"/"azuredisk-volume-tester-wc79b" Feb 1 00:19:06.105: INFO: Error getting logs for pod azuredisk-volume-tester-wc79b: the server could not find the requested resource (get pods azuredisk-volume-tester-wc79b) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wc79b in namespace azuredisk-6758 [38;5;243m02/01/23 00:19:06.105[0m Feb 1 00:19:06.139: INFO: deleting PVC "azuredisk-6758"/"pvc-znhh5" Feb 1 00:19:06.139: INFO: Deleting PersistentVolumeClaim "pvc-znhh5" [1mSTEP:[0m waiting for claim's PV "pvc-e8fdcd84-54e2-42d9-a76f-0108cd6f4c7d" to be deleted [38;5;243m02/01/23 00:19:06.181[0m Feb 1 00:19:06.181: INFO: Waiting up to 10m0s for PersistentVolume pvc-e8fdcd84-54e2-42d9-a76f-0108cd6f4c7d to get deleted Feb 1 00:19:06.217: INFO: PersistentVolume pvc-e8fdcd84-54e2-42d9-a76f-0108cd6f4c7d found and phase=Released (36.096334ms) ... skipping 63 lines ... [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:20:02.498[0m Feb 1 00:20:02.498: INFO: deleting Pod "azuredisk-9471"/"azuredisk-volume-tester-qb5qn" Feb 1 00:20:02.554: INFO: Pod azuredisk-volume-tester-qb5qn has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qb5qn in namespace azuredisk-9471 [38;5;243m02/01/23 00:20:02.554[0m Feb 1 00:20:12.676: INFO: deleting Pod "azuredisk-9471"/"azuredisk-volume-tester-qb5qn" Feb 1 00:20:12.711: INFO: Error getting logs for pod azuredisk-volume-tester-qb5qn: the server could not find the requested resource (get pods azuredisk-volume-tester-qb5qn) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qb5qn in namespace azuredisk-9471 [38;5;243m02/01/23 00:20:12.711[0m Feb 1 00:20:12.745: INFO: deleting PVC "azuredisk-9471"/"pvc-z6ttm" Feb 1 00:20:12.745: INFO: Deleting PersistentVolumeClaim "pvc-z6ttm" [1mSTEP:[0m waiting for claim's PV "pvc-a2c4d60c-a67c-44e2-a5b0-9484eeef810e" to be deleted [38;5;243m02/01/23 00:20:12.783[0m Feb 1 00:20:12.783: INFO: Waiting up to 10m0s for PersistentVolume pvc-a2c4d60c-a67c-44e2-a5b0-9484eeef810e to get deleted Feb 1 00:20:12.823: INFO: PersistentVolume pvc-a2c4d60c-a67c-44e2-a5b0-9484eeef810e found and phase=Released (39.551856ms) ... skipping 69 lines ... [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:20:02.498[0m Feb 1 00:20:02.498: INFO: deleting Pod "azuredisk-9471"/"azuredisk-volume-tester-qb5qn" Feb 1 00:20:02.554: INFO: Pod azuredisk-volume-tester-qb5qn has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qb5qn in namespace azuredisk-9471 [38;5;243m02/01/23 00:20:02.554[0m Feb 1 00:20:12.676: INFO: deleting Pod "azuredisk-9471"/"azuredisk-volume-tester-qb5qn" Feb 1 00:20:12.711: INFO: Error getting logs for pod azuredisk-volume-tester-qb5qn: the server could not find the requested resource (get pods azuredisk-volume-tester-qb5qn) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qb5qn in namespace azuredisk-9471 [38;5;243m02/01/23 00:20:12.711[0m Feb 1 00:20:12.745: INFO: deleting PVC "azuredisk-9471"/"pvc-z6ttm" Feb 1 00:20:12.745: INFO: Deleting PersistentVolumeClaim "pvc-z6ttm" [1mSTEP:[0m waiting for claim's PV "pvc-a2c4d60c-a67c-44e2-a5b0-9484eeef810e" to be deleted [38;5;243m02/01/23 00:20:12.783[0m Feb 1 00:20:12.783: INFO: Waiting up to 10m0s for PersistentVolume pvc-a2c4d60c-a67c-44e2-a5b0-9484eeef810e to get deleted Feb 1 00:20:12.823: INFO: PersistentVolume pvc-a2c4d60c-a67c-44e2-a5b0-9484eeef810e found and phase=Released (39.551856ms) ... skipping 52 lines ... I0201 00:21:31.066844 41681 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m checking that the pod is running [38;5;243m02/01/23 00:21:31.138[0m I0201 00:21:31.172776 41681 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m check pod exec [38;5;243m02/01/23 00:21:31.172[0m Feb 1 00:21:31.173: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-5412 exec azuredisk-volume-tester-w7gjh-0 -- cmd /c type C:\mnt\test-1\data.txt' Feb 1 00:21:31.797: INFO: rc: 1 Feb 1 00:21:31.797: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-w7gjh-0": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-5412 exec azuredisk-volume-tester-w7gjh-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. Feb 1 00:21:33.798: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-5412 exec azuredisk-volume-tester-w7gjh-0 -- cmd /c type C:\mnt\test-1\data.txt' Feb 1 00:21:34.390: INFO: stderr: "" Feb 1 00:21:34.390: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for statefulset [38;5;243m02/01/23 00:21:34.39[0m Feb 1 00:21:34.390: INFO: Deleting pod "azuredisk-volume-tester-w7gjh-0" in namespace "azuredisk-5412" ... skipping 62 lines ... I0201 00:21:31.066844 41681 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m checking that the pod is running [38;5;243m02/01/23 00:21:31.138[0m I0201 00:21:31.172776 41681 statefulset.go:175] 1/1 replicas in the StatefulSet are ready [1mSTEP:[0m check pod exec [38;5;243m02/01/23 00:21:31.172[0m Feb 1 00:21:31.173: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-5412 exec azuredisk-volume-tester-w7gjh-0 -- cmd /c type C:\mnt\test-1\data.txt' Feb 1 00:21:31.797: INFO: rc: 1 Feb 1 00:21:31.797: INFO: Error waiting for output "hello world\r\n" in pod "azuredisk-volume-tester-w7gjh-0": error running /usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-5412 exec azuredisk-volume-tester-w7gjh-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. Feb 1 00:21:33.798: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=azuredisk-5412 exec azuredisk-volume-tester-w7gjh-0 -- cmd /c type C:\mnt\test-1\data.txt' Feb 1 00:21:34.390: INFO: stderr: "" Feb 1 00:21:34.390: INFO: stdout: "hello world\r\n" [1mSTEP:[0m deleting the pod for statefulset [38;5;243m02/01/23 00:21:34.39[0m Feb 1 00:21:34.390: INFO: Deleting pod "azuredisk-volume-tester-w7gjh-0" in namespace "azuredisk-5412" ... skipping 395 lines ...