kubernetes-sigs/azuredisk-csi-driver PR #1712 pull-azuredisk-csi-driver-e2e-capz-mainv2 #1620551316650594304
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 / 47 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 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
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 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 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 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 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 retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
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 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 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 creating a single pod and with replica attachments [disk.csi.azure.com][csi-azuredisk-scheduler-extender]
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 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 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 volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
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]
... skipping 803 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 127 lines ... # Wait for the kubeconfig to become available. timeout --foreground 300 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets | grep capz-g49wn9-kubeconfig; do sleep 1; done" capz-g49wn9-kubeconfig cluster.x-k8s.io/secret 1 0s # Get kubeconfig and store it locally. /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets capz-g49wn9-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig timeout --foreground 600 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done" error: the server doesn't have a resource type "nodes" capz-g49wn9-control-plane-f9kt7 NotReady control-plane 6s v1.24.6 run "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig ..." to work with the new target cluster make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' pod/kube-apiserver-capz-g49wn9-control-plane-f9kt7 condition met namespace/calico-system created NAME DATA AGE ... skipping 83 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 170k 0 --:--:-- --:--:-- --:--:-- 170k Downloading https://get.helm.sh/helm-v3.11.0-linux-amd64.tar.gz Verifying checksum... Done. Preparing to install helm into /usr/local/bin helm installed into /usr/local/bin/helm docker pull 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:52:31Z -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 242 lines ... #9 exporting to image #9 pushing layers 2.3s done #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64@sha256:10180a4fd3eff1fa499a39d3328b341130009afbb74c222e691fad00086b5f1f #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64@sha256:10180a4fd3eff1fa499a39d3328b341130009afbb74c222e691fad00086b5f1f 0.4s done #9 DONE 6.7s 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-31T22:55:43Z -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 116 lines ... #8 exporting config sha256:446b541c90233322f726cef400cd776f705a166e7bbdf088a98b7eae34b1944d done #8 pushing layers #8 pushing layers 1.9s done #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64@sha256:b7c0a302607c2f2edf3dd639f58901964704e2a1e424eea01f76c9be5ab22c99 #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64@sha256:b7c0a302607c2f2edf3dd639f58901964704e2a1e424eea01f76c9be5ab22c99 0.4s done #8 DONE 6.0s 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 70 lines ... #10 exporting config sha256:966a766344748d65a93f934db4a514b9dee73d99d0cf3188195a68e9c2aeed06 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:2aef461e8ba1896ce71c43e0abf60cb94e28d4d12121f51262c59df4aeaa70af #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-1809-amd64@sha256:2aef461e8ba1896ce71c43e0abf60cb94e28d4d12121f51262c59df4aeaa70af 0.4s done #10 DONE 6.1s 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 66 lines ... #10 exporting config sha256:ddcb1ec90bd727cb5d2a10d6e345dadae7b0a37e77e1d68d7e1484d2d165f24f done #10 pushing layers #10 pushing layers 1.7s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-20H2-amd64@sha256:8dac98a2c6d8605077e95886bcf7ba6757292028d6d89936c4d9a55287bb8587 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-20H2-amd64@sha256:8dac98a2c6d8605077e95886bcf7ba6757292028d6d89936c4d9a55287bb8587 0.4s done #10 DONE 5.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' docker buildx build . \ --pull \ --output=type=registry \ --platform="windows/amd64" \ ... skipping 68 lines ... #10 exporting config sha256:887065a2a52489d464deb7fdf17d0627342ccb9eb6f5a75614b5c961c989b05f done #10 pushing layers #10 pushing layers 1.7s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-ltsc2022-amd64@sha256:1a4feeebe119233a6de7e32c77e89c449b29e067468774f19244c95bd9dcc19c #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-windows-ltsc2022-amd64@sha256:1a4feeebe119233a6de7e32c77e89c449b29e067468774f19244c95bd9dcc19c 0.3s done #10 DONE 5.8s 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 74 lines ... } } ] } make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker pull capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-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' docker buildx rm container-builder || true container-builder removed docker buildx create --use --name=container-builder --driver-opt image=moby/buildkit:v0.10.6 container-builder # enable qemu for arm64 build ... skipping 152 lines ... #8 exporting to image #8 pushing layers 2.3s done #8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64@sha256:cdb8f04d414816e8060789e20d325a04bcf7155f97f0c285a018b11d35df9457 #8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64@sha256:cdb8f04d414816e8060789e20d325a04bcf7155f97f0c285a018b11d35df9457 0.4s done #8 DONE 5.5s 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.schedulerVersion=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:00:08Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName= -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/arm64/azdiskschedulerextender ./pkg/azdiskschedulerextender 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 35 lines ... #7 exporting config sha256:1d4a962aa907bdfd5aa850a2311580e754af5946cffa7f2512939ba38e11f84e 0.0s done #7 pushing layers #7 pushing layers 1.7s done #7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64@sha256:5cc8446c65c796fdf73ceb8ddc7900e5e2acdb7ed8c68795ebc635c94278435f #7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64@sha256:5cc8446c65c796fdf73ceb8ddc7900e5e2acdb7ed8c68795ebc635c94278435f 0.4s done #7 DONE 6.5s 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/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-amd64 capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9-linux-arm64 Created manifest list capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 docker manifest push --purge capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 sha256:b3b5af592336a5a204a2c0cc7ed4b4d4f66712ad70e1becf83621fbca890f127 docker manifest inspect capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-930851ca0d19682b1fa9f893a9e8fa4374a3f5f9 ... skipping 847 lines ... type: string type: object oneOf: - required: ["persistentVolumeClaimName"] - required: ["volumeSnapshotContentName"] volumeSnapshotClassName: description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.' type: string required: - source type: object status: description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object. ... skipping 2 lines ... description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.' type: string creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown. format: date-time type: string error: description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurs during the snapshot creation. Upon success, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: type: string description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$ x-kubernetes-int-or-string: true type: object required: - spec type: object ... skipping 60 lines ... type: string volumeSnapshotContentName: description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable. type: string type: object volumeSnapshotClassName: description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.' type: string required: - source type: object status: description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object. ... skipping 2 lines ... description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.' type: string creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown. format: date-time type: string error: description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurs during the snapshot creation. Upon success, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: type: string description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$ x-kubernetes-int-or-string: true type: object required: - spec type: object ... skipping 254 lines ... description: status represents the current information of a snapshot. properties: creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC. format: int64 type: integer error: description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. format: int64 minimum: 0 type: integer snapshotHandle: description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress. type: string type: object required: - spec type: object served: true ... skipping 108 lines ... description: status represents the current information of a snapshot. properties: creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC. format: int64 type: integer error: description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. format: int64 minimum: 0 type: integer snapshotHandle: description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress. type: string type: object required: - spec type: object served: true ... skipping 359 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status Required properties: detail: description: Status summarizes the current attachment state of the volume attachment Nil Status indicates that the volume has not yet been attached to the node properties: ... skipping 7 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 90 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 13 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 169 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: detail: description: Current status detail of the AzVolume Nil detail indicates that the volume has not been created properties: accessible_topology: ... skipping 28 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 154 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 34 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 1069 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" args: - "-csi-address=$(ADDRESS)" - "-v=2" - "-leader-election" - "--leader-election-namespace=kube-system" - '-handle-volume-inuse-error=false' - '-feature-gates=RecoverVolumeExpansionFailure=true' - "-timeout=240s" env: - name: ADDRESS value: /csi/csi.sock volumeMounts: ... skipping 283 lines ... Jan 31 23:04:29.944: 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:04:29.946[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/31/23 23:04:30.171[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/31/23 23:04:30.234[0m I0131 23:04:30.297775 41330 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:04:30.35[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:04:30.387[0m Jan 31 23:04:30.387: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b5dxd" in namespace "azuredisk-3817" to be "Succeeded or Failed" Jan 31 23:04:30.425: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Pending", Reason="", readiness=false. Elapsed: 38.083479ms Jan 31 23:04:32.460: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072650183s Jan 31 23:04:34.460: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Running", Reason="", readiness=false. Elapsed: 4.072353264s Jan 31 23:04:36.460: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.072951332s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:04:36.461[0m Jan 31 23:04:36.461: INFO: Pod "azuredisk-volume-tester-b5dxd" satisfied condition "Succeeded or Failed" Jan 31 23:04:36.461: INFO: deleting Pod "azuredisk-3817"/"azuredisk-volume-tester-b5dxd" Jan 31 23:04:36.515: INFO: Pod azuredisk-volume-tester-b5dxd has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-b5dxd in namespace azuredisk-3817 [38;5;243m01/31/23 23:04:36.515[0m [1mSTEP:[0m Destroying namespace "azuredisk-3817" for this suite. [38;5;243m01/31/23 23:04:36.569[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Jan 31 23:04:29.944: 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:04:29.946[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/31/23 23:04:30.171[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/31/23 23:04:30.234[0m I0131 23:04:30.297775 41330 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:04:30.35[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:04:30.387[0m Jan 31 23:04:30.387: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b5dxd" in namespace "azuredisk-3817" to be "Succeeded or Failed" Jan 31 23:04:30.425: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Pending", Reason="", readiness=false. Elapsed: 38.083479ms Jan 31 23:04:32.460: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072650183s Jan 31 23:04:34.460: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Running", Reason="", readiness=false. Elapsed: 4.072353264s Jan 31 23:04:36.460: INFO: Pod "azuredisk-volume-tester-b5dxd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.072951332s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:04:36.461[0m Jan 31 23:04:36.461: INFO: Pod "azuredisk-volume-tester-b5dxd" satisfied condition "Succeeded or Failed" Jan 31 23:04:36.461: INFO: deleting Pod "azuredisk-3817"/"azuredisk-volume-tester-b5dxd" Jan 31 23:04:36.515: INFO: Pod azuredisk-volume-tester-b5dxd has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-b5dxd in namespace azuredisk-3817 [38;5;243m01/31/23 23:04:36.515[0m [1mSTEP:[0m Destroying namespace "azuredisk-3817" for this suite. [38;5;243m01/31/23 23:04:36.569[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 17 lines ... Jan 31 23:04:38.966: INFO: PersistentVolumeClaim pvc-wllkl found but phase is Pending instead of Bound. Jan 31 23:04:41.000: INFO: PersistentVolumeClaim pvc-wllkl found and phase=Bound (4.098657459s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:04:41[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:04:41.032[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:04:41.065[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:04:41.113[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:04:41.147[0m Jan 31 23:04:41.147: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tmhmg" in namespace "azuredisk-5735" to be "Succeeded or Failed" Jan 31 23:04:41.183: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 35.771522ms Jan 31 23:04:43.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070113259s Jan 31 23:04:45.215: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.068025219s Jan 31 23:04:47.216: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069144862s Jan 31 23:04:49.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.070089438s Jan 31 23:04:51.216: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069378321s Jan 31 23:04:53.218: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.070973312s Jan 31 23:04:55.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.070180504s Jan 31 23:04:57.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Running", Reason="", readiness=true. Elapsed: 16.07042406s Jan 31 23:04:59.218: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Running", Reason="", readiness=false. Elapsed: 18.071050336s Jan 31 23:05:01.216: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.069551792s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:05:01.216[0m Jan 31 23:05:01.216: INFO: Pod "azuredisk-volume-tester-tmhmg" satisfied condition "Succeeded or Failed" Jan 31 23:05:01.217: INFO: deleting Pod "azuredisk-5735"/"azuredisk-volume-tester-tmhmg" Jan 31 23:05:01.251: INFO: Pod azuredisk-volume-tester-tmhmg has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-tmhmg in namespace azuredisk-5735 [38;5;243m01/31/23 23:05:01.251[0m Jan 31 23:05:01.305: INFO: deleting PVC "azuredisk-5735"/"pvc-wllkl" Jan 31 23:05:01.305: INFO: Deleting PersistentVolumeClaim "pvc-wllkl" ... skipping 38 lines ... Jan 31 23:04:38.966: INFO: PersistentVolumeClaim pvc-wllkl found but phase is Pending instead of Bound. Jan 31 23:04:41.000: INFO: PersistentVolumeClaim pvc-wllkl found and phase=Bound (4.098657459s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:04:41[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:04:41.032[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:04:41.065[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:04:41.113[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:04:41.147[0m Jan 31 23:04:41.147: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tmhmg" in namespace "azuredisk-5735" to be "Succeeded or Failed" Jan 31 23:04:41.183: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 35.771522ms Jan 31 23:04:43.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070113259s Jan 31 23:04:45.215: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.068025219s Jan 31 23:04:47.216: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069144862s Jan 31 23:04:49.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.070089438s Jan 31 23:04:51.216: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069378321s Jan 31 23:04:53.218: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.070973312s Jan 31 23:04:55.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.070180504s Jan 31 23:04:57.217: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Running", Reason="", readiness=true. Elapsed: 16.07042406s Jan 31 23:04:59.218: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Running", Reason="", readiness=false. Elapsed: 18.071050336s Jan 31 23:05:01.216: INFO: Pod "azuredisk-volume-tester-tmhmg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.069551792s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:05:01.216[0m Jan 31 23:05:01.216: INFO: Pod "azuredisk-volume-tester-tmhmg" satisfied condition "Succeeded or Failed" Jan 31 23:05:01.217: INFO: deleting Pod "azuredisk-5735"/"azuredisk-volume-tester-tmhmg" Jan 31 23:05:01.251: INFO: Pod azuredisk-volume-tester-tmhmg has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-tmhmg in namespace azuredisk-5735 [38;5;243m01/31/23 23:05:01.251[0m Jan 31 23:05:01.305: INFO: deleting PVC "azuredisk-5735"/"pvc-wllkl" Jan 31 23:05:01.305: INFO: Deleting PersistentVolumeClaim "pvc-wllkl" ... skipping 163 lines ... Jan 31 23:11:55.917: INFO: PersistentVolumeClaim pvc-p8gms found and phase=Bound (4.098576457s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:11:55.917[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:11:55.949[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:11:55.981[0m I0131 23:11:55.981715 41330 resource_setup.go:89] adding PV (pvc-83c3d838-9314-4385-a0b2-c861cfbeb55e) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:11:56.03[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:11:56.065[0m Jan 31 23:11:56.065: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-g2nd9" in namespace "azuredisk-3630" to be "Succeeded or Failed" Jan 31 23:11:56.098: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.021091ms Jan 31 23:11:58.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06704288s Jan 31 23:12:00.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066939955s Jan 31 23:12:02.131: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066172883s Jan 31 23:12:04.133: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.067681831s Jan 31 23:12:06.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067062967s Jan 31 23:12:08.133: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.068117633s Jan 31 23:12:10.134: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.068372266s Jan 31 23:12:12.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066410963s Jan 31 23:12:14.134: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.068525723s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:12:14.134[0m Jan 31 23:12:14.134: INFO: Pod "azuredisk-volume-tester-g2nd9" satisfied condition "Succeeded or Failed" Jan 31 23:12:14.134: INFO: deleting Pod "azuredisk-3630"/"azuredisk-volume-tester-g2nd9" Jan 31 23:12:14.179: INFO: Pod azuredisk-volume-tester-g2nd9 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g2nd9 in namespace azuredisk-3630 [38;5;243m01/31/23 23:12:14.18[0m Jan 31 23:12:14.219: INFO: deleting PVC "azuredisk-3630"/"pvc-p8gms" Jan 31 23:12:14.219: INFO: Deleting PersistentVolumeClaim "pvc-p8gms" ... skipping 85 lines ... Jan 31 23:11:55.917: INFO: PersistentVolumeClaim pvc-p8gms found and phase=Bound (4.098576457s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:11:55.917[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:11:55.949[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:11:55.981[0m I0131 23:11:55.981715 41330 resource_setup.go:89] adding PV (pvc-83c3d838-9314-4385-a0b2-c861cfbeb55e) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:11:56.03[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:11:56.065[0m Jan 31 23:11:56.065: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-g2nd9" in namespace "azuredisk-3630" to be "Succeeded or Failed" Jan 31 23:11:56.098: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.021091ms Jan 31 23:11:58.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06704288s Jan 31 23:12:00.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066939955s Jan 31 23:12:02.131: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066172883s Jan 31 23:12:04.133: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.067681831s Jan 31 23:12:06.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067062967s Jan 31 23:12:08.133: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.068117633s Jan 31 23:12:10.134: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.068372266s Jan 31 23:12:12.132: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066410963s Jan 31 23:12:14.134: INFO: Pod "azuredisk-volume-tester-g2nd9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.068525723s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:12:14.134[0m Jan 31 23:12:14.134: INFO: Pod "azuredisk-volume-tester-g2nd9" satisfied condition "Succeeded or Failed" Jan 31 23:12:14.134: INFO: deleting Pod "azuredisk-3630"/"azuredisk-volume-tester-g2nd9" Jan 31 23:12:14.179: INFO: Pod azuredisk-volume-tester-g2nd9 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g2nd9 in namespace azuredisk-3630 [38;5;243m01/31/23 23:12:14.18[0m Jan 31 23:12:14.219: INFO: deleting PVC "azuredisk-3630"/"pvc-p8gms" Jan 31 23:12:14.219: INFO: Deleting PersistentVolumeClaim "pvc-p8gms" ... skipping 599 lines ... Jan 31 23:25:39.126: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-k5hp2] to have phase Bound Jan 31 23:25:39.158: INFO: PersistentVolumeClaim pvc-k5hp2 found and phase=Bound (32.115019ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:25:39.158[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:25:39.19[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:25:39.221[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:25:39.221[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:25:39.254[0m Jan 31 23:25:39.254: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-vdlzf" in namespace "azuredisk-7660" to be "Error status code" Jan 31 23:25:39.286: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 31.818375ms Jan 31 23:25:41.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065123288s Jan 31 23:25:43.319: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064626147s Jan 31 23:25:45.319: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064768063s Jan 31 23:25:47.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065184274s Jan 31 23:25:49.318: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.063418112s Jan 31 23:25:51.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065192379s Jan 31 23:25:53.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065730614s Jan 31 23:25:55.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Running", Reason="", readiness=false. Elapsed: 16.065575491s Jan 31 23:25:57.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Failed", Reason="", readiness=false. Elapsed: 18.06607198s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:25:57.321[0m Jan 31 23:25:57.321: INFO: Pod "azuredisk-volume-tester-vdlzf" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:25:57.321[0m Jan 31 23:25:57.367: INFO: deleting Pod "azuredisk-7660"/"azuredisk-volume-tester-vdlzf" Jan 31 23:25:57.400: INFO: Pod azuredisk-volume-tester-vdlzf has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vdlzf in namespace azuredisk-7660 [38;5;243m01/31/23 23:25:57.4[0m Jan 31 23:25:57.437: INFO: deleting PVC "azuredisk-7660"/"pvc-k5hp2" ... skipping 37 lines ... Jan 31 23:25:39.126: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-k5hp2] to have phase Bound Jan 31 23:25:39.158: INFO: PersistentVolumeClaim pvc-k5hp2 found and phase=Bound (32.115019ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:25:39.158[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:25:39.19[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:25:39.221[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:25:39.221[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:25:39.254[0m Jan 31 23:25:39.254: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-vdlzf" in namespace "azuredisk-7660" to be "Error status code" Jan 31 23:25:39.286: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 31.818375ms Jan 31 23:25:41.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065123288s Jan 31 23:25:43.319: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064626147s Jan 31 23:25:45.319: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064768063s Jan 31 23:25:47.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065184274s Jan 31 23:25:49.318: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.063418112s Jan 31 23:25:51.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065192379s Jan 31 23:25:53.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065730614s Jan 31 23:25:55.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Running", Reason="", readiness=false. Elapsed: 16.065575491s Jan 31 23:25:57.320: INFO: Pod "azuredisk-volume-tester-vdlzf": Phase="Failed", Reason="", readiness=false. Elapsed: 18.06607198s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:25:57.321[0m Jan 31 23:25:57.321: INFO: Pod "azuredisk-volume-tester-vdlzf" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:25:57.321[0m Jan 31 23:25:57.367: INFO: deleting Pod "azuredisk-7660"/"azuredisk-volume-tester-vdlzf" Jan 31 23:25:57.400: INFO: Pod azuredisk-volume-tester-vdlzf has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vdlzf in namespace azuredisk-7660 [38;5;243m01/31/23 23:25:57.4[0m Jan 31 23:25:57.437: INFO: deleting PVC "azuredisk-7660"/"pvc-k5hp2" ... skipping 66 lines ... Jan 31 23:27:01.081: INFO: PersistentVolumeClaim pvc-v6q7x found and phase=Bound (32.281215ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:27:01.081[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:27:01.113[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:27:01.144[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/31/23 23:27:01.185[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:27:13.516[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:27:13.549[0m Jan 31 23:27:13.549: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wfgk7" in namespace "azuredisk-6559" to be "Succeeded or Failed" Jan 31 23:27:13.580: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 31.0889ms Jan 31 23:27:15.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064310693s Jan 31 23:27:17.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064268734s Jan 31 23:27:19.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065628944s Jan 31 23:27:21.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.063461433s Jan 31 23:27:23.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.064369224s ... skipping 12 lines ... Jan 31 23:27:49.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 36.066298814s Jan 31 23:27:51.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Running", Reason="", readiness=true. Elapsed: 38.066080198s Jan 31 23:27:53.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Running", Reason="", readiness=true. Elapsed: 40.065757514s Jan 31 23:27:55.614: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Running", Reason="", readiness=false. Elapsed: 42.06524134s Jan 31 23:27:57.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.065995082s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:27:57.615[0m Jan 31 23:27:57.615: INFO: Pod "azuredisk-volume-tester-wfgk7" satisfied condition "Succeeded or Failed" Jan 31 23:27:57.615: INFO: deleting Pod "azuredisk-6559"/"azuredisk-volume-tester-wfgk7" Jan 31 23:27:57.662: INFO: Pod azuredisk-volume-tester-wfgk7 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wfgk7 in namespace azuredisk-6559 [38;5;243m01/31/23 23:27:57.662[0m Jan 31 23:27:57.774: INFO: deleting PVC "azuredisk-6559"/"pvc-v6q7x" Jan 31 23:27:57.774: INFO: Deleting PersistentVolumeClaim "pvc-v6q7x" ... skipping 36 lines ... Jan 31 23:27:01.081: INFO: PersistentVolumeClaim pvc-v6q7x found and phase=Bound (32.281215ms) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:27:01.081[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:27:01.113[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:27:01.144[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/31/23 23:27:01.185[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:27:13.516[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:27:13.549[0m Jan 31 23:27:13.549: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wfgk7" in namespace "azuredisk-6559" to be "Succeeded or Failed" Jan 31 23:27:13.580: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 31.0889ms Jan 31 23:27:15.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064310693s Jan 31 23:27:17.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064268734s Jan 31 23:27:19.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065628944s Jan 31 23:27:21.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.063461433s Jan 31 23:27:23.613: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.064369224s ... skipping 12 lines ... Jan 31 23:27:49.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Pending", Reason="", readiness=false. Elapsed: 36.066298814s Jan 31 23:27:51.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Running", Reason="", readiness=true. Elapsed: 38.066080198s Jan 31 23:27:53.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Running", Reason="", readiness=true. Elapsed: 40.065757514s Jan 31 23:27:55.614: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Running", Reason="", readiness=false. Elapsed: 42.06524134s Jan 31 23:27:57.615: INFO: Pod "azuredisk-volume-tester-wfgk7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.065995082s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:27:57.615[0m Jan 31 23:27:57.615: INFO: Pod "azuredisk-volume-tester-wfgk7" satisfied condition "Succeeded or Failed" Jan 31 23:27:57.615: INFO: deleting Pod "azuredisk-6559"/"azuredisk-volume-tester-wfgk7" Jan 31 23:27:57.662: INFO: Pod azuredisk-volume-tester-wfgk7 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-wfgk7 in namespace azuredisk-6559 [38;5;243m01/31/23 23:27:57.662[0m Jan 31 23:27:57.774: INFO: deleting PVC "azuredisk-6559"/"pvc-v6q7x" Jan 31 23:27:57.774: INFO: Deleting PersistentVolumeClaim "pvc-v6q7x" ... skipping 389 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 shared-disk-replicas 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 23 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:31:43.753[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:31:43.785[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:31:43.817[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:31:43.817[0m I0131 23:31:43.817431 41330 resource_setup.go:62] adding PV (pvc-fae2df21-8fad-46d3-818c-2079526e793d) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:31:43.817[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:31:43.853[0m Jan 31 23:31:43.853: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bcdbl" in namespace "azuredisk-5375" to be "Succeeded or Failed" Jan 31 23:31:43.885: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 31.812331ms Jan 31 23:31:45.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066782017s Jan 31 23:31:47.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066563516s Jan 31 23:31:49.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066289177s Jan 31 23:31:51.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066376703s Jan 31 23:31:53.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.066487431s Jan 31 23:31:55.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065977204s Jan 31 23:31:57.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.066312246s Jan 31 23:31:59.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Running", Reason="", readiness=false. Elapsed: 16.065947529s Jan 31 23:32:01.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.066601083s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:32:01.92[0m Jan 31 23:32:01.920: INFO: Pod "azuredisk-volume-tester-bcdbl" satisfied condition "Succeeded or Failed" Jan 31 23:32:01.920: INFO: deleting Pod "azuredisk-5375"/"azuredisk-volume-tester-bcdbl" Jan 31 23:32:01.962: INFO: Pod azuredisk-volume-tester-bcdbl has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bcdbl in namespace azuredisk-5375 [38;5;243m01/31/23 23:32:01.962[0m Jan 31 23:32:02.003: INFO: deleting PVC "azuredisk-5375"/"pvc-8t8q7" Jan 31 23:32:02.003: INFO: Deleting PersistentVolumeClaim "pvc-8t8q7" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:31:43.753[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:31:43.785[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:31:43.817[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:31:43.817[0m I0131 23:31:43.817431 41330 resource_setup.go:62] adding PV (pvc-fae2df21-8fad-46d3-818c-2079526e793d) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:31:43.817[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:31:43.853[0m Jan 31 23:31:43.853: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bcdbl" in namespace "azuredisk-5375" to be "Succeeded or Failed" Jan 31 23:31:43.885: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 31.812331ms Jan 31 23:31:45.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066782017s Jan 31 23:31:47.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066563516s Jan 31 23:31:49.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066289177s Jan 31 23:31:51.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066376703s Jan 31 23:31:53.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.066487431s Jan 31 23:31:55.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065977204s Jan 31 23:31:57.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.066312246s Jan 31 23:31:59.919: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Running", Reason="", readiness=false. Elapsed: 16.065947529s Jan 31 23:32:01.920: INFO: Pod "azuredisk-volume-tester-bcdbl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.066601083s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:32:01.92[0m Jan 31 23:32:01.920: INFO: Pod "azuredisk-volume-tester-bcdbl" satisfied condition "Succeeded or Failed" Jan 31 23:32:01.920: INFO: deleting Pod "azuredisk-5375"/"azuredisk-volume-tester-bcdbl" Jan 31 23:32:01.962: INFO: Pod azuredisk-volume-tester-bcdbl has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bcdbl in namespace azuredisk-5375 [38;5;243m01/31/23 23:32:01.962[0m Jan 31 23:32:02.003: INFO: deleting PVC "azuredisk-5375"/"pvc-8t8q7" Jan 31 23:32:02.003: INFO: Deleting PersistentVolumeClaim "pvc-8t8q7" ... skipping 38 lines ... Jan 31 23:32:45.351: INFO: PersistentVolumeClaim pvc-sllff found but phase is Pending instead of Bound. Jan 31 23:32:47.385: INFO: PersistentVolumeClaim pvc-sllff found and phase=Bound (4.116088448s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:32:47.385[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:32:47.417[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:32:47.449[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:32:47.45[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/31/23 23:32:47.484[0m Jan 31 23:32:47.484: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nwjzv" in namespace "azuredisk-6571" to be "Succeeded or Failed" Jan 31 23:32:47.522: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 37.842016ms Jan 31 23:32:49.555: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071233963s Jan 31 23:32:51.557: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072437074s Jan 31 23:32:53.557: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.072503543s Jan 31 23:32:55.554: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.07009043s Jan 31 23:32:57.556: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.071970541s Jan 31 23:32:59.556: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.071495869s Jan 31 23:33:01.555: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.070738334s Jan 31 23:33:03.557: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.072457487s Jan 31 23:33:05.558: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.074181231s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:33:05.558[0m Jan 31 23:33:05.559: INFO: Pod "azuredisk-volume-tester-nwjzv" satisfied condition "Succeeded or Failed" Jan 31 23:33:05.559: INFO: deleting Pod "azuredisk-6571"/"azuredisk-volume-tester-nwjzv" Jan 31 23:33:05.593: INFO: Pod azuredisk-volume-tester-nwjzv has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nwjzv in namespace azuredisk-6571 [38;5;243m01/31/23 23:33:05.593[0m Jan 31 23:33:05.634: INFO: deleting PVC "azuredisk-6571"/"pvc-sllff" Jan 31 23:33:05.634: INFO: Deleting PersistentVolumeClaim "pvc-sllff" ... skipping 38 lines ... Jan 31 23:32:45.351: INFO: PersistentVolumeClaim pvc-sllff found but phase is Pending instead of Bound. Jan 31 23:32:47.385: INFO: PersistentVolumeClaim pvc-sllff found and phase=Bound (4.116088448s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:32:47.385[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:32:47.417[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:32:47.449[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:32:47.45[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/31/23 23:32:47.484[0m Jan 31 23:32:47.484: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nwjzv" in namespace "azuredisk-6571" to be "Succeeded or Failed" Jan 31 23:32:47.522: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 37.842016ms Jan 31 23:32:49.555: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071233963s Jan 31 23:32:51.557: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072437074s Jan 31 23:32:53.557: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.072503543s Jan 31 23:32:55.554: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.07009043s Jan 31 23:32:57.556: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.071970541s Jan 31 23:32:59.556: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.071495869s Jan 31 23:33:01.555: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.070738334s Jan 31 23:33:03.557: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.072457487s Jan 31 23:33:05.558: INFO: Pod "azuredisk-volume-tester-nwjzv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.074181231s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:33:05.558[0m Jan 31 23:33:05.559: INFO: Pod "azuredisk-volume-tester-nwjzv" satisfied condition "Succeeded or Failed" Jan 31 23:33:05.559: INFO: deleting Pod "azuredisk-6571"/"azuredisk-volume-tester-nwjzv" Jan 31 23:33:05.593: INFO: Pod azuredisk-volume-tester-nwjzv has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nwjzv in namespace azuredisk-6571 [38;5;243m01/31/23 23:33:05.593[0m Jan 31 23:33:05.634: INFO: deleting PVC "azuredisk-6571"/"pvc-sllff" Jan 31 23:33:05.634: INFO: Deleting PersistentVolumeClaim "pvc-sllff" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:33:50.985[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:33:51.017[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:33:51.049[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:33:51.049[0m I0131 23:33:51.050057 41330 resource_setup.go:62] adding PV (pvc-0f634a1e-37ef-404f-9e5b-3e802edf036b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:33:51.05[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:33:51.085[0m Jan 31 23:33:51.085: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-67grp" in namespace "azuredisk-851" to be "Succeeded or Failed" Jan 31 23:33:51.123: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 37.496677ms Jan 31 23:33:53.159: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07376401s Jan 31 23:33:55.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071667495s Jan 31 23:33:57.156: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.070487479s Jan 31 23:33:59.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.071238388s Jan 31 23:34:01.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.07183136s ... skipping 11 lines ... Jan 31 23:34:25.158: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 34.072465902s Jan 31 23:34:27.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.071397055s Jan 31 23:34:29.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 38.071231687s Jan 31 23:34:31.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 40.071444563s Jan 31 23:34:33.156: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.070819639s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:34:33.156[0m Jan 31 23:34:33.157: INFO: Pod "azuredisk-volume-tester-67grp" satisfied condition "Succeeded or Failed" Jan 31 23:34:33.157: INFO: deleting Pod "azuredisk-851"/"azuredisk-volume-tester-67grp" Jan 31 23:34:33.191: INFO: Pod azuredisk-volume-tester-67grp has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-67grp in namespace azuredisk-851 [38;5;243m01/31/23 23:34:33.192[0m Jan 31 23:34:33.231: INFO: deleting PVC "azuredisk-851"/"pvc-k2dlf" Jan 31 23:34:33.231: INFO: Deleting PersistentVolumeClaim "pvc-k2dlf" ... skipping 37 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:33:50.985[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:33:51.017[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:33:51.049[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:33:51.049[0m I0131 23:33:51.050057 41330 resource_setup.go:62] adding PV (pvc-0f634a1e-37ef-404f-9e5b-3e802edf036b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:33:51.05[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:33:51.085[0m Jan 31 23:33:51.085: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-67grp" in namespace "azuredisk-851" to be "Succeeded or Failed" Jan 31 23:33:51.123: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 37.496677ms Jan 31 23:33:53.159: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07376401s Jan 31 23:33:55.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071667495s Jan 31 23:33:57.156: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.070487479s Jan 31 23:33:59.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.071238388s Jan 31 23:34:01.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.07183136s ... skipping 11 lines ... Jan 31 23:34:25.158: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 34.072465902s Jan 31 23:34:27.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.071397055s Jan 31 23:34:29.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 38.071231687s Jan 31 23:34:31.157: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Pending", Reason="", readiness=false. Elapsed: 40.071444563s Jan 31 23:34:33.156: INFO: Pod "azuredisk-volume-tester-67grp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.070819639s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:34:33.156[0m Jan 31 23:34:33.157: INFO: Pod "azuredisk-volume-tester-67grp" satisfied condition "Succeeded or Failed" Jan 31 23:34:33.157: INFO: deleting Pod "azuredisk-851"/"azuredisk-volume-tester-67grp" Jan 31 23:34:33.191: INFO: Pod azuredisk-volume-tester-67grp has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-67grp in namespace azuredisk-851 [38;5;243m01/31/23 23:34:33.192[0m Jan 31 23:34:33.231: INFO: deleting PVC "azuredisk-851"/"pvc-k2dlf" Jan 31 23:34:33.231: INFO: Deleting PersistentVolumeClaim "pvc-k2dlf" ... skipping 37 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:35:03.474[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:35:03.509[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:35:03.541[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:35:03.542[0m I0131 23:35:03.542228 41330 resource_setup.go:62] adding PV (pvc-c8469628-3e91-46f3-b8a0-cb5e255b094b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:35:03.542[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:35:03.575[0m Jan 31 23:35:03.576: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hd8vs" in namespace "azuredisk-99" to be "Succeeded or Failed" Jan 31 23:35:03.611: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 35.573445ms Jan 31 23:35:05.649: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07362234s Jan 31 23:35:07.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069463834s Jan 31 23:35:09.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069591959s Jan 31 23:35:11.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069247564s Jan 31 23:35:13.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069553238s ... skipping 4 lines ... Jan 31 23:35:23.643: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 20.067301012s Jan 31 23:35:25.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 22.069413653s Jan 31 23:35:27.644: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 24.067978339s Jan 31 23:35:29.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.068862004s Jan 31 23:35:31.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.069050608s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:35:31.645[0m Jan 31 23:35:31.645: INFO: Pod "azuredisk-volume-tester-hd8vs" satisfied condition "Succeeded or Failed" Jan 31 23:35:31.645: INFO: deleting Pod "azuredisk-99"/"azuredisk-volume-tester-hd8vs" Jan 31 23:35:31.681: INFO: Pod azuredisk-volume-tester-hd8vs has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hd8vs in namespace azuredisk-99 [38;5;243m01/31/23 23:35:31.681[0m Jan 31 23:35:31.722: INFO: deleting PVC "azuredisk-99"/"pvc-6hm7k" Jan 31 23:35:31.722: INFO: Deleting PersistentVolumeClaim "pvc-6hm7k" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:35:03.474[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:35:03.509[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:35:03.541[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:35:03.542[0m I0131 23:35:03.542228 41330 resource_setup.go:62] adding PV (pvc-c8469628-3e91-46f3-b8a0-cb5e255b094b) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:35:03.542[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:35:03.575[0m Jan 31 23:35:03.576: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hd8vs" in namespace "azuredisk-99" to be "Succeeded or Failed" Jan 31 23:35:03.611: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 35.573445ms Jan 31 23:35:05.649: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07362234s Jan 31 23:35:07.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069463834s Jan 31 23:35:09.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069591959s Jan 31 23:35:11.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069247564s Jan 31 23:35:13.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069553238s ... skipping 4 lines ... Jan 31 23:35:23.643: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 20.067301012s Jan 31 23:35:25.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 22.069413653s Jan 31 23:35:27.644: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 24.067978339s Jan 31 23:35:29.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Pending", Reason="", readiness=false. Elapsed: 26.068862004s Jan 31 23:35:31.645: INFO: Pod "azuredisk-volume-tester-hd8vs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.069050608s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:35:31.645[0m Jan 31 23:35:31.645: INFO: Pod "azuredisk-volume-tester-hd8vs" satisfied condition "Succeeded or Failed" Jan 31 23:35:31.645: INFO: deleting Pod "azuredisk-99"/"azuredisk-volume-tester-hd8vs" Jan 31 23:35:31.681: INFO: Pod azuredisk-volume-tester-hd8vs has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hd8vs in namespace azuredisk-99 [38;5;243m01/31/23 23:35:31.681[0m Jan 31 23:35:31.722: INFO: deleting PVC "azuredisk-99"/"pvc-6hm7k" Jan 31 23:35:31.722: INFO: Deleting PersistentVolumeClaim "pvc-6hm7k" ... skipping 42 lines ... [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:36:17.193[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:36:17.193[0m I0131 23:36:17.193463 41330 resource_setup.go:62] adding PV (pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:36:17.193[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m01/31/23 23:36:17.228[0m Jan 31 23:36:31.299: INFO: deleting Pod "azuredisk-8224"/"azuredisk-volume-tester-9wsgx" Jan 31 23:36:31.340: INFO: Error getting logs for pod azuredisk-volume-tester-9wsgx: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-9wsgx) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-9wsgx in namespace azuredisk-8224 [38;5;243m01/31/23 23:36:31.34[0m Jan 31 23:36:31.376: INFO: deleting PVC "azuredisk-8224"/"pvc-xmfct" Jan 31 23:36:31.376: INFO: Deleting PersistentVolumeClaim "pvc-xmfct" [1mSTEP:[0m waiting for claim's PV "pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d" to be deleted [38;5;243m01/31/23 23:36:31.409[0m Jan 31 23:36:31.409: INFO: Waiting up to 10m0s for PersistentVolume pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d to get deleted Jan 31 23:36:31.441: INFO: PersistentVolume pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d found and phase=Bound (32.293183ms) ... skipping 61 lines ... [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:36:17.193[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:36:17.193[0m I0131 23:36:17.193463 41330 resource_setup.go:62] adding PV (pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:36:17.193[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m01/31/23 23:36:17.228[0m Jan 31 23:36:31.299: INFO: deleting Pod "azuredisk-8224"/"azuredisk-volume-tester-9wsgx" Jan 31 23:36:31.340: INFO: Error getting logs for pod azuredisk-volume-tester-9wsgx: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-9wsgx) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-9wsgx in namespace azuredisk-8224 [38;5;243m01/31/23 23:36:31.34[0m Jan 31 23:36:31.376: INFO: deleting PVC "azuredisk-8224"/"pvc-xmfct" Jan 31 23:36:31.376: INFO: Deleting PersistentVolumeClaim "pvc-xmfct" [1mSTEP:[0m waiting for claim's PV "pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d" to be deleted [38;5;243m01/31/23 23:36:31.409[0m Jan 31 23:36:31.409: INFO: Waiting up to 10m0s for PersistentVolume pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d to get deleted Jan 31 23:36:31.441: INFO: PersistentVolume pvc-bc1022ba-e5b0-4044-b4c4-64e68b0fc60d found and phase=Bound (32.293183ms) ... skipping 59 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:39:07.41[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:39:07.443[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:39:07.475[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:39:07.475[0m I0131 23:39:07.475977 41330 resource_setup.go:62] adding PV (pvc-c5fccecc-0a1e-4dbd-b575-15ba4e8a50af) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:39:07.475[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:39:07.509[0m Jan 31 23:39:07.510: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fh7bx" in namespace "azuredisk-6632" to be "Succeeded or Failed" Jan 31 23:39:07.541: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.542076ms Jan 31 23:39:09.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065327229s Jan 31 23:39:11.574: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064007036s Jan 31 23:39:13.573: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063712087s Jan 31 23:39:15.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065721129s Jan 31 23:39:17.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065599433s Jan 31 23:39:19.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.066487747s Jan 31 23:39:21.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.066379986s Jan 31 23:39:23.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.065666277s Jan 31 23:39:25.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Running", Reason="", readiness=false. Elapsed: 18.066420162s Jan 31 23:39:27.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.066861121s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:39:27.577[0m Jan 31 23:39:27.577: INFO: Pod "azuredisk-volume-tester-fh7bx" satisfied condition "Succeeded or Failed" Jan 31 23:39:27.577: INFO: deleting Pod "azuredisk-6632"/"azuredisk-volume-tester-fh7bx" Jan 31 23:39:27.622: INFO: Pod azuredisk-volume-tester-fh7bx has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-fh7bx in namespace azuredisk-6632 [38;5;243m01/31/23 23:39:27.622[0m Jan 31 23:39:27.661: INFO: deleting PVC "azuredisk-6632"/"pvc-mrxnm" Jan 31 23:39:27.661: INFO: Deleting PersistentVolumeClaim "pvc-mrxnm" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:39:07.41[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:39:07.443[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:39:07.475[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:39:07.475[0m I0131 23:39:07.475977 41330 resource_setup.go:62] adding PV (pvc-c5fccecc-0a1e-4dbd-b575-15ba4e8a50af) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:39:07.475[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:39:07.509[0m Jan 31 23:39:07.510: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fh7bx" in namespace "azuredisk-6632" to be "Succeeded or Failed" Jan 31 23:39:07.541: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.542076ms Jan 31 23:39:09.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065327229s Jan 31 23:39:11.574: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064007036s Jan 31 23:39:13.573: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063712087s Jan 31 23:39:15.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065721129s Jan 31 23:39:17.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065599433s Jan 31 23:39:19.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.066487747s Jan 31 23:39:21.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.066379986s Jan 31 23:39:23.575: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.065666277s Jan 31 23:39:25.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Running", Reason="", readiness=false. Elapsed: 18.066420162s Jan 31 23:39:27.576: INFO: Pod "azuredisk-volume-tester-fh7bx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.066861121s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:39:27.577[0m Jan 31 23:39:27.577: INFO: Pod "azuredisk-volume-tester-fh7bx" satisfied condition "Succeeded or Failed" Jan 31 23:39:27.577: INFO: deleting Pod "azuredisk-6632"/"azuredisk-volume-tester-fh7bx" Jan 31 23:39:27.622: INFO: Pod azuredisk-volume-tester-fh7bx has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-fh7bx in namespace azuredisk-6632 [38;5;243m01/31/23 23:39:27.622[0m Jan 31 23:39:27.661: INFO: deleting PVC "azuredisk-6632"/"pvc-mrxnm" Jan 31 23:39:27.661: INFO: Deleting PersistentVolumeClaim "pvc-mrxnm" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:40:12.867[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:40:12.898[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:40:12.93[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:40:12.93[0m I0131 23:40:12.930795 41330 resource_setup.go:62] adding PV (pvc-5cd0a48a-b0cc-45cb-954a-76f01bf16cbe) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:40:12.93[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:40:12.964[0m Jan 31 23:40:12.965: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-lqvdj" in namespace "azuredisk-5310" to be "Error status code" Jan 31 23:40:13.000: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 35.337411ms Jan 31 23:40:15.032: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067633355s Jan 31 23:40:17.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06817369s Jan 31 23:40:19.032: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067865649s Jan 31 23:40:21.034: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.068984412s Jan 31 23:40:23.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.068765739s Jan 31 23:40:25.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.06835934s Jan 31 23:40:27.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.067962089s Jan 31 23:40:29.037: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.072057237s Jan 31 23:40:31.035: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Failed", Reason="", readiness=false. Elapsed: 18.070724647s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:40:31.035[0m Jan 31 23:40:31.036: INFO: Pod "azuredisk-volume-tester-lqvdj" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:40:31.036[0m Jan 31 23:40:31.070: INFO: deleting Pod "azuredisk-5310"/"azuredisk-volume-tester-lqvdj" Jan 31 23:40:31.105: INFO: Pod azuredisk-volume-tester-lqvdj has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-lqvdj in namespace azuredisk-5310 [38;5;243m01/31/23 23:40:31.105[0m Jan 31 23:40:31.146: INFO: deleting PVC "azuredisk-5310"/"pvc-bgl2j" ... skipping 41 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:40:12.867[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:40:12.898[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:40:12.93[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:40:12.93[0m I0131 23:40:12.930795 41330 resource_setup.go:62] adding PV (pvc-5cd0a48a-b0cc-45cb-954a-76f01bf16cbe) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:40:12.93[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/31/23 23:40:12.964[0m Jan 31 23:40:12.965: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-lqvdj" in namespace "azuredisk-5310" to be "Error status code" Jan 31 23:40:13.000: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 35.337411ms Jan 31 23:40:15.032: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067633355s Jan 31 23:40:17.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06817369s Jan 31 23:40:19.032: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067865649s Jan 31 23:40:21.034: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.068984412s Jan 31 23:40:23.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.068765739s Jan 31 23:40:25.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.06835934s Jan 31 23:40:27.033: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.067962089s Jan 31 23:40:29.037: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.072057237s Jan 31 23:40:31.035: INFO: Pod "azuredisk-volume-tester-lqvdj": Phase="Failed", Reason="", readiness=false. Elapsed: 18.070724647s [1mSTEP:[0m Saw pod failure [38;5;243m01/31/23 23:40:31.035[0m Jan 31 23:40:31.036: INFO: Pod "azuredisk-volume-tester-lqvdj" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/31/23 23:40:31.036[0m Jan 31 23:40:31.070: INFO: deleting Pod "azuredisk-5310"/"azuredisk-volume-tester-lqvdj" Jan 31 23:40:31.105: INFO: Pod azuredisk-volume-tester-lqvdj has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-lqvdj in namespace azuredisk-5310 [38;5;243m01/31/23 23:40:31.105[0m Jan 31 23:40:31.146: INFO: deleting PVC "azuredisk-5310"/"pvc-bgl2j" ... skipping 687 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:48:01.908[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:48:01.939[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:48:01.972[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:48:01.972[0m I0131 23:48:01.972305 41330 resource_setup.go:62] adding PV (pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:48:01.972[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:48:02.006[0m Jan 31 23:48:02.006: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vjqwv" in namespace "azuredisk-4272" to be "Succeeded or Failed" Jan 31 23:48:02.040: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 34.493139ms Jan 31 23:48:04.074: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067644193s Jan 31 23:48:06.075: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.068616475s Jan 31 23:48:08.076: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069716463s Jan 31 23:48:10.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066623656s Jan 31 23:48:12.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.0665796s Jan 31 23:48:14.072: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.066519598s Jan 31 23:48:16.075: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.068635685s Jan 31 23:48:18.074: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Running", Reason="", readiness=true. Elapsed: 16.067805674s Jan 31 23:48:20.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Running", Reason="", readiness=false. Elapsed: 18.067470246s Jan 31 23:48:22.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.067564166s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:48:22.074[0m Jan 31 23:48:22.074: INFO: Pod "azuredisk-volume-tester-vjqwv" satisfied condition "Succeeded or Failed" Jan 31 23:48:22.105: INFO: deleting Pod "azuredisk-4272"/"azuredisk-volume-tester-vjqwv" Jan 31 23:48:22.147: INFO: Pod azuredisk-volume-tester-vjqwv has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vjqwv in namespace azuredisk-4272 [38;5;243m01/31/23 23:48:22.147[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:48:22.193[0m [1mSTEP:[0m cloning existing volume [38;5;243m01/31/23 23:48:40.258[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m01/31/23 23:48:40.321[0m ... skipping 6 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:48:44.455[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:48:44.487[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:48:44.518[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:48:44.519[0m I0131 23:48:44.519248 41330 resource_setup.go:62] adding PV (pvc-617e1375-c305-43c4-be19-61de4dc80415) to pod () [1mSTEP:[0m deploying a second pod with cloned volume [38;5;243m01/31/23 23:48:44.519[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:48:44.554[0m Jan 31 23:48:44.555: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zr6f5" in namespace "azuredisk-4272" to be "Succeeded or Failed" Jan 31 23:48:44.586: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 31.226843ms Jan 31 23:48:46.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06433951s Jan 31 23:48:48.620: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065222185s Jan 31 23:48:50.618: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063595877s Jan 31 23:48:52.618: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.063305531s Jan 31 23:48:54.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.064796396s Jan 31 23:48:56.618: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.063035134s Jan 31 23:48:58.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.064710765s Jan 31 23:49:00.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.064401602s Jan 31 23:49:02.621: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.066610312s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:49:02.621[0m Jan 31 23:49:02.621: INFO: Pod "azuredisk-volume-tester-zr6f5" satisfied condition "Succeeded or Failed" Jan 31 23:49:02.621: INFO: deleting Pod "azuredisk-4272"/"azuredisk-volume-tester-zr6f5" Jan 31 23:49:02.656: INFO: Pod azuredisk-volume-tester-zr6f5 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-zr6f5 in namespace azuredisk-4272 [38;5;243m01/31/23 23:49:02.656[0m Jan 31 23:49:02.695: INFO: deleting PVC "azuredisk-4272"/"pvc-bhfl9" Jan 31 23:49:02.695: INFO: Deleting PersistentVolumeClaim "pvc-bhfl9" ... skipping 8 lines ... Jan 31 23:49:32.959: INFO: PersistentVolume pvc-617e1375-c305-43c4-be19-61de4dc80415 found and phase=Released (30.231154363s) Jan 31 23:49:37.991: INFO: PersistentVolume pvc-617e1375-c305-43c4-be19-61de4dc80415 found and phase=Released (35.263185002s) Jan 31 23:49:43.027: INFO: PersistentVolume pvc-617e1375-c305-43c4-be19-61de4dc80415 was removed Jan 31 23:49:43.027: INFO: Waiting up to 5m0s for PersistentVolumeClaim pvc-bhfl9 to be removed Jan 31 23:49:43.058: INFO: Claim "pvc-bhfl9" in namespace "azuredisk-4272" doesn't exist in the system Jan 31 23:49:43.058: INFO: deleting Pod "azuredisk-4272"/"azuredisk-volume-tester-vjqwv" Jan 31 23:49:43.090: INFO: Error getting logs for pod azuredisk-volume-tester-vjqwv: the server could not find the requested resource (get pods azuredisk-volume-tester-vjqwv) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vjqwv in namespace azuredisk-4272 [38;5;243m01/31/23 23:49:43.09[0m Jan 31 23:49:43.122: INFO: deleting PVC "azuredisk-4272"/"pvc-hnkvl" Jan 31 23:49:43.122: INFO: Deleting PersistentVolumeClaim "pvc-hnkvl" [1mSTEP:[0m waiting for claim's PV "pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7" to be deleted [38;5;243m01/31/23 23:49:43.159[0m Jan 31 23:49:43.159: INFO: Waiting up to 10m0s for PersistentVolume pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7 to get deleted Jan 31 23:49:43.190: INFO: PersistentVolume pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7 found and phase=Released (31.182589ms) ... skipping 31 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:48:01.908[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:48:01.939[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:48:01.972[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:48:01.972[0m I0131 23:48:01.972305 41330 resource_setup.go:62] adding PV (pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:48:01.972[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:48:02.006[0m Jan 31 23:48:02.006: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vjqwv" in namespace "azuredisk-4272" to be "Succeeded or Failed" Jan 31 23:48:02.040: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 34.493139ms Jan 31 23:48:04.074: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067644193s Jan 31 23:48:06.075: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.068616475s Jan 31 23:48:08.076: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069716463s Jan 31 23:48:10.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066623656s Jan 31 23:48:12.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.0665796s Jan 31 23:48:14.072: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.066519598s Jan 31 23:48:16.075: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.068635685s Jan 31 23:48:18.074: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Running", Reason="", readiness=true. Elapsed: 16.067805674s Jan 31 23:48:20.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Running", Reason="", readiness=false. Elapsed: 18.067470246s Jan 31 23:48:22.073: INFO: Pod "azuredisk-volume-tester-vjqwv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.067564166s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:48:22.074[0m Jan 31 23:48:22.074: INFO: Pod "azuredisk-volume-tester-vjqwv" satisfied condition "Succeeded or Failed" Jan 31 23:48:22.105: INFO: deleting Pod "azuredisk-4272"/"azuredisk-volume-tester-vjqwv" Jan 31 23:48:22.147: INFO: Pod azuredisk-volume-tester-vjqwv has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vjqwv in namespace azuredisk-4272 [38;5;243m01/31/23 23:48:22.147[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:48:22.193[0m [1mSTEP:[0m cloning existing volume [38;5;243m01/31/23 23:48:40.258[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m01/31/23 23:48:40.321[0m ... skipping 6 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:48:44.455[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:48:44.487[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:48:44.518[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:48:44.519[0m I0131 23:48:44.519248 41330 resource_setup.go:62] adding PV (pvc-617e1375-c305-43c4-be19-61de4dc80415) to pod () [1mSTEP:[0m deploying a second pod with cloned volume [38;5;243m01/31/23 23:48:44.519[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:48:44.554[0m Jan 31 23:48:44.555: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zr6f5" in namespace "azuredisk-4272" to be "Succeeded or Failed" Jan 31 23:48:44.586: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 31.226843ms Jan 31 23:48:46.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06433951s Jan 31 23:48:48.620: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065222185s Jan 31 23:48:50.618: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063595877s Jan 31 23:48:52.618: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.063305531s Jan 31 23:48:54.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.064796396s Jan 31 23:48:56.618: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 12.063035134s Jan 31 23:48:58.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 14.064710765s Jan 31 23:49:00.619: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.064401602s Jan 31 23:49:02.621: INFO: Pod "azuredisk-volume-tester-zr6f5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.066610312s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:49:02.621[0m Jan 31 23:49:02.621: INFO: Pod "azuredisk-volume-tester-zr6f5" satisfied condition "Succeeded or Failed" Jan 31 23:49:02.621: INFO: deleting Pod "azuredisk-4272"/"azuredisk-volume-tester-zr6f5" Jan 31 23:49:02.656: INFO: Pod azuredisk-volume-tester-zr6f5 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-zr6f5 in namespace azuredisk-4272 [38;5;243m01/31/23 23:49:02.656[0m Jan 31 23:49:02.695: INFO: deleting PVC "azuredisk-4272"/"pvc-bhfl9" Jan 31 23:49:02.695: INFO: Deleting PersistentVolumeClaim "pvc-bhfl9" ... skipping 8 lines ... Jan 31 23:49:32.959: INFO: PersistentVolume pvc-617e1375-c305-43c4-be19-61de4dc80415 found and phase=Released (30.231154363s) Jan 31 23:49:37.991: INFO: PersistentVolume pvc-617e1375-c305-43c4-be19-61de4dc80415 found and phase=Released (35.263185002s) Jan 31 23:49:43.027: INFO: PersistentVolume pvc-617e1375-c305-43c4-be19-61de4dc80415 was removed Jan 31 23:49:43.027: INFO: Waiting up to 5m0s for PersistentVolumeClaim pvc-bhfl9 to be removed Jan 31 23:49:43.058: INFO: Claim "pvc-bhfl9" in namespace "azuredisk-4272" doesn't exist in the system Jan 31 23:49:43.058: INFO: deleting Pod "azuredisk-4272"/"azuredisk-volume-tester-vjqwv" Jan 31 23:49:43.090: INFO: Error getting logs for pod azuredisk-volume-tester-vjqwv: the server could not find the requested resource (get pods azuredisk-volume-tester-vjqwv) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-vjqwv in namespace azuredisk-4272 [38;5;243m01/31/23 23:49:43.09[0m Jan 31 23:49:43.122: INFO: deleting PVC "azuredisk-4272"/"pvc-hnkvl" Jan 31 23:49:43.122: INFO: Deleting PersistentVolumeClaim "pvc-hnkvl" [1mSTEP:[0m waiting for claim's PV "pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7" to be deleted [38;5;243m01/31/23 23:49:43.159[0m Jan 31 23:49:43.159: INFO: Waiting up to 10m0s for PersistentVolume pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7 to get deleted Jan 31 23:49:43.190: INFO: PersistentVolume pvc-956d3f8e-731d-4323-8272-ccad7aafcdb7 found and phase=Released (31.182589ms) ... skipping 31 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:49:58.134[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:49:58.166[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:49:58.197[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:49:58.197[0m I0131 23:49:58.197850 41330 resource_setup.go:62] adding PV (pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:49:58.197[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:49:58.234[0m Jan 31 23:49:58.235: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-v47z8" in namespace "azuredisk-9566" to be "Succeeded or Failed" Jan 31 23:49:58.265: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.910039ms Jan 31 23:50:00.299: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064220632s Jan 31 23:50:02.297: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.062583544s Jan 31 23:50:04.298: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063100405s Jan 31 23:50:06.299: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064055168s Jan 31 23:50:08.298: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.062923438s Jan 31 23:50:10.298: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.063819099s Jan 31 23:50:12.300: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065217465s Jan 31 23:50:14.299: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.064602205s Jan 31 23:50:16.300: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.065618771s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:50:16.3[0m Jan 31 23:50:16.300: INFO: Pod "azuredisk-volume-tester-v47z8" satisfied condition "Succeeded or Failed" Jan 31 23:50:16.332: INFO: deleting Pod "azuredisk-9566"/"azuredisk-volume-tester-v47z8" Jan 31 23:50:16.366: INFO: Pod azuredisk-volume-tester-v47z8 has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-v47z8 in namespace azuredisk-9566 [38;5;243m01/31/23 23:50:16.366[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:50:16.428[0m [1mSTEP:[0m cloning existing volume [38;5;243m01/31/23 23:50:38.493[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m01/31/23 23:50:38.556[0m ... skipping 6 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:50:42.688[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:50:42.72[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:50:42.752[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:50:42.752[0m I0131 23:50:42.752327 41330 resource_setup.go:62] adding PV (pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9) to pod () [1mSTEP:[0m deploying a second pod with cloned volume [38;5;243m01/31/23 23:50:42.752[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:50:42.786[0m Jan 31 23:50:42.786: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nb6pn" in namespace "azuredisk-9566" to be "Succeeded or Failed" Jan 31 23:50:42.821: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 34.219337ms Jan 31 23:50:44.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067375447s Jan 31 23:50:46.855: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069073781s Jan 31 23:50:48.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067324186s Jan 31 23:50:50.853: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066999611s Jan 31 23:50:52.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06782869s Jan 31 23:50:54.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.067858748s Jan 31 23:50:56.857: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.070584677s Jan 31 23:50:58.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.067627539s Jan 31 23:51:00.855: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.068516829s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:51:00.855[0m Jan 31 23:51:00.855: INFO: Pod "azuredisk-volume-tester-nb6pn" satisfied condition "Succeeded or Failed" Jan 31 23:51:00.855: INFO: deleting Pod "azuredisk-9566"/"azuredisk-volume-tester-nb6pn" Jan 31 23:51:00.890: INFO: Pod azuredisk-volume-tester-nb6pn has the following logs: 20.0G [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nb6pn in namespace azuredisk-9566 [38;5;243m01/31/23 23:51:00.89[0m Jan 31 23:51:00.933: INFO: deleting PVC "azuredisk-9566"/"pvc-jhqks" Jan 31 23:51:00.933: INFO: Deleting PersistentVolumeClaim "pvc-jhqks" ... skipping 7 lines ... Jan 31 23:51:26.166: INFO: PersistentVolume pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9 found and phase=Released (25.200065938s) Jan 31 23:51:31.200: INFO: PersistentVolume pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9 found and phase=Released (30.23390206s) Jan 31 23:51:36.236: INFO: PersistentVolume pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9 was removed Jan 31 23:51:36.236: INFO: Waiting up to 5m0s for PersistentVolumeClaim pvc-jhqks to be removed Jan 31 23:51:36.268: INFO: Claim "pvc-jhqks" in namespace "azuredisk-9566" doesn't exist in the system Jan 31 23:51:36.268: INFO: deleting Pod "azuredisk-9566"/"azuredisk-volume-tester-v47z8" Jan 31 23:51:36.298: INFO: Error getting logs for pod azuredisk-volume-tester-v47z8: the server could not find the requested resource (get pods azuredisk-volume-tester-v47z8) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-v47z8 in namespace azuredisk-9566 [38;5;243m01/31/23 23:51:36.299[0m Jan 31 23:51:36.330: INFO: deleting PVC "azuredisk-9566"/"pvc-khwxw" Jan 31 23:51:36.330: INFO: Deleting PersistentVolumeClaim "pvc-khwxw" [1mSTEP:[0m waiting for claim's PV "pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6" to be deleted [38;5;243m01/31/23 23:51:36.363[0m Jan 31 23:51:36.363: INFO: Waiting up to 10m0s for PersistentVolume pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6 to get deleted Jan 31 23:51:36.398: INFO: PersistentVolume pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6 found and phase=Released (34.058353ms) ... skipping 31 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:49:58.134[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:49:58.166[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:49:58.197[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:49:58.197[0m I0131 23:49:58.197850 41330 resource_setup.go:62] adding PV (pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:49:58.197[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:49:58.234[0m Jan 31 23:49:58.235: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-v47z8" in namespace "azuredisk-9566" to be "Succeeded or Failed" Jan 31 23:49:58.265: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 30.910039ms Jan 31 23:50:00.299: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064220632s Jan 31 23:50:02.297: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.062583544s Jan 31 23:50:04.298: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063100405s Jan 31 23:50:06.299: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064055168s Jan 31 23:50:08.298: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.062923438s Jan 31 23:50:10.298: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 12.063819099s Jan 31 23:50:12.300: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065217465s Jan 31 23:50:14.299: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Pending", Reason="", readiness=false. Elapsed: 16.064602205s Jan 31 23:50:16.300: INFO: Pod "azuredisk-volume-tester-v47z8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.065618771s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:50:16.3[0m Jan 31 23:50:16.300: INFO: Pod "azuredisk-volume-tester-v47z8" satisfied condition "Succeeded or Failed" Jan 31 23:50:16.332: INFO: deleting Pod "azuredisk-9566"/"azuredisk-volume-tester-v47z8" Jan 31 23:50:16.366: INFO: Pod azuredisk-volume-tester-v47z8 has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-v47z8 in namespace azuredisk-9566 [38;5;243m01/31/23 23:50:16.366[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:50:16.428[0m [1mSTEP:[0m cloning existing volume [38;5;243m01/31/23 23:50:38.493[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m01/31/23 23:50:38.556[0m ... skipping 6 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:50:42.688[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:50:42.72[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:50:42.752[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:50:42.752[0m I0131 23:50:42.752327 41330 resource_setup.go:62] adding PV (pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9) to pod () [1mSTEP:[0m deploying a second pod with cloned volume [38;5;243m01/31/23 23:50:42.752[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:50:42.786[0m Jan 31 23:50:42.786: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nb6pn" in namespace "azuredisk-9566" to be "Succeeded or Failed" Jan 31 23:50:42.821: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 34.219337ms Jan 31 23:50:44.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067375447s Jan 31 23:50:46.855: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.069073781s Jan 31 23:50:48.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067324186s Jan 31 23:50:50.853: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066999611s Jan 31 23:50:52.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06782869s Jan 31 23:50:54.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.067858748s Jan 31 23:50:56.857: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.070584677s Jan 31 23:50:58.854: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.067627539s Jan 31 23:51:00.855: INFO: Pod "azuredisk-volume-tester-nb6pn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.068516829s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:51:00.855[0m Jan 31 23:51:00.855: INFO: Pod "azuredisk-volume-tester-nb6pn" satisfied condition "Succeeded or Failed" Jan 31 23:51:00.855: INFO: deleting Pod "azuredisk-9566"/"azuredisk-volume-tester-nb6pn" Jan 31 23:51:00.890: INFO: Pod azuredisk-volume-tester-nb6pn has the following logs: 20.0G [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nb6pn in namespace azuredisk-9566 [38;5;243m01/31/23 23:51:00.89[0m Jan 31 23:51:00.933: INFO: deleting PVC "azuredisk-9566"/"pvc-jhqks" Jan 31 23:51:00.933: INFO: Deleting PersistentVolumeClaim "pvc-jhqks" ... skipping 7 lines ... Jan 31 23:51:26.166: INFO: PersistentVolume pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9 found and phase=Released (25.200065938s) Jan 31 23:51:31.200: INFO: PersistentVolume pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9 found and phase=Released (30.23390206s) Jan 31 23:51:36.236: INFO: PersistentVolume pvc-4fa2c494-d11b-45fe-800a-0f293e2af9c9 was removed Jan 31 23:51:36.236: INFO: Waiting up to 5m0s for PersistentVolumeClaim pvc-jhqks to be removed Jan 31 23:51:36.268: INFO: Claim "pvc-jhqks" in namespace "azuredisk-9566" doesn't exist in the system Jan 31 23:51:36.268: INFO: deleting Pod "azuredisk-9566"/"azuredisk-volume-tester-v47z8" Jan 31 23:51:36.298: INFO: Error getting logs for pod azuredisk-volume-tester-v47z8: the server could not find the requested resource (get pods azuredisk-volume-tester-v47z8) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-v47z8 in namespace azuredisk-9566 [38;5;243m01/31/23 23:51:36.299[0m Jan 31 23:51:36.330: INFO: deleting PVC "azuredisk-9566"/"pvc-khwxw" Jan 31 23:51:36.330: INFO: Deleting PersistentVolumeClaim "pvc-khwxw" [1mSTEP:[0m waiting for claim's PV "pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6" to be deleted [38;5;243m01/31/23 23:51:36.363[0m Jan 31 23:51:36.363: INFO: Waiting up to 10m0s for PersistentVolume pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6 to get deleted Jan 31 23:51:36.398: INFO: PersistentVolume pvc-e9de6aeb-931d-4cf9-909e-7ebb87e883f6 found and phase=Released (34.058353ms) ... skipping 59 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:51:59.827[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:51:59.859[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:51:59.891[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:51:59.891[0m I0131 23:51:59.891340 41330 resource_setup.go:62] adding PV (pvc-2ba05841-27d3-432a-92ce-faedb0be1a7f) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:51:59.891[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:51:59.926[0m Jan 31 23:51:59.926: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c46df" in namespace "azuredisk-2805" to be "Succeeded or Failed" Jan 31 23:51:59.965: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 39.226456ms Jan 31 23:52:02.000: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07351985s Jan 31 23:52:03.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 4.073461649s Jan 31 23:52:06.000: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 6.07368447s Jan 31 23:52:07.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 8.073187924s Jan 31 23:52:10.000: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 10.074020326s Jan 31 23:52:11.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 12.072629481s Jan 31 23:52:13.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 14.073064012s Jan 31 23:52:15.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 16.072850912s Jan 31 23:52:18.001: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.075415433s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:52:18.001[0m Jan 31 23:52:18.002: INFO: Pod "azuredisk-volume-tester-c46df" satisfied condition "Succeeded or Failed" Jan 31 23:52:18.002: INFO: deleting Pod "azuredisk-2805"/"azuredisk-volume-tester-c46df" Jan 31 23:52:18.046: INFO: Pod azuredisk-volume-tester-c46df has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-c46df in namespace azuredisk-2805 [38;5;243m01/31/23 23:52:18.046[0m ... skipping 90 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:51:59.827[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:51:59.859[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:51:59.891[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:51:59.891[0m I0131 23:51:59.891340 41330 resource_setup.go:62] adding PV (pvc-2ba05841-27d3-432a-92ce-faedb0be1a7f) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:51:59.891[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:51:59.926[0m Jan 31 23:51:59.926: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c46df" in namespace "azuredisk-2805" to be "Succeeded or Failed" Jan 31 23:51:59.965: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 39.226456ms Jan 31 23:52:02.000: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07351985s Jan 31 23:52:03.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 4.073461649s Jan 31 23:52:06.000: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 6.07368447s Jan 31 23:52:07.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 8.073187924s Jan 31 23:52:10.000: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 10.074020326s Jan 31 23:52:11.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 12.072629481s Jan 31 23:52:13.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 14.073064012s Jan 31 23:52:15.999: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Pending", Reason="", readiness=false. Elapsed: 16.072850912s Jan 31 23:52:18.001: INFO: Pod "azuredisk-volume-tester-c46df": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.075415433s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:52:18.001[0m Jan 31 23:52:18.002: INFO: Pod "azuredisk-volume-tester-c46df" satisfied condition "Succeeded or Failed" Jan 31 23:52:18.002: INFO: deleting Pod "azuredisk-2805"/"azuredisk-volume-tester-c46df" Jan 31 23:52:18.046: INFO: Pod azuredisk-volume-tester-c46df has the following logs: hello world hello world hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-c46df in namespace azuredisk-2805 [38;5;243m01/31/23 23:52:18.046[0m ... skipping 76 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:53:27.94[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:53:27.971[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:53:28.002[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:53:28.002[0m I0131 23:53:28.003029 41330 resource_setup.go:62] adding PV (pvc-40e1ef0e-7017-4f8b-9c00-1ddec2a8a988) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:53:28.003[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:53:28.035[0m Jan 31 23:53:28.036: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lmlpd" in namespace "azuredisk-1697" to be "Succeeded or Failed" Jan 31 23:53:28.069: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 33.888952ms Jan 31 23:53:30.104: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0680021s Jan 31 23:53:32.103: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067031699s Jan 31 23:53:34.104: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.06800704s Jan 31 23:53:36.102: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066397257s Jan 31 23:53:38.105: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069547718s Jan 31 23:53:40.104: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.06827793s Jan 31 23:53:42.102: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Running", Reason="", readiness=true. Elapsed: 14.0667036s Jan 31 23:53:44.103: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Running", Reason="", readiness=false. Elapsed: 16.06796089s Jan 31 23:53:46.103: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.067193943s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:53:46.103[0m Jan 31 23:53:46.103: INFO: Pod "azuredisk-volume-tester-lmlpd" satisfied condition "Succeeded or Failed" Jan 31 23:53:46.103: INFO: deleting Pod "azuredisk-1697"/"azuredisk-volume-tester-lmlpd" Jan 31 23:53:46.139: INFO: Pod azuredisk-volume-tester-lmlpd has the following logs: 100+0 records in 100+0 records out 104857600 bytes (100.0MB) copied, 0.067846 seconds, 1.4GB/s hello world ... skipping 67 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:53:27.94[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:53:27.971[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:53:28.002[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:53:28.002[0m I0131 23:53:28.003029 41330 resource_setup.go:62] adding PV (pvc-40e1ef0e-7017-4f8b-9c00-1ddec2a8a988) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:53:28.003[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:53:28.035[0m Jan 31 23:53:28.036: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lmlpd" in namespace "azuredisk-1697" to be "Succeeded or Failed" Jan 31 23:53:28.069: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 33.888952ms Jan 31 23:53:30.104: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0680021s Jan 31 23:53:32.103: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067031699s Jan 31 23:53:34.104: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.06800704s Jan 31 23:53:36.102: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066397257s Jan 31 23:53:38.105: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069547718s Jan 31 23:53:40.104: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.06827793s Jan 31 23:53:42.102: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Running", Reason="", readiness=true. Elapsed: 14.0667036s Jan 31 23:53:44.103: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Running", Reason="", readiness=false. Elapsed: 16.06796089s Jan 31 23:53:46.103: INFO: Pod "azuredisk-volume-tester-lmlpd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.067193943s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:53:46.103[0m Jan 31 23:53:46.103: INFO: Pod "azuredisk-volume-tester-lmlpd" satisfied condition "Succeeded or Failed" Jan 31 23:53:46.103: INFO: deleting Pod "azuredisk-1697"/"azuredisk-volume-tester-lmlpd" Jan 31 23:53:46.139: INFO: Pod azuredisk-volume-tester-lmlpd has the following logs: 100+0 records in 100+0 records out 104857600 bytes (100.0MB) copied, 0.067846 seconds, 1.4GB/s hello world ... skipping 51 lines ... Jan 31 23:54:39.552: INFO: PersistentVolumeClaim pvc-2jf7g found but phase is Pending instead of Bound. Jan 31 23:54:41.585: INFO: PersistentVolumeClaim pvc-2jf7g found and phase=Bound (4.102042009s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:54:41.585[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:54:41.616[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:54:41.651[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:54:41.651[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:54:41.684[0m Jan 31 23:54:41.684: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-g6zhj" in namespace "azuredisk-5295" to be "Succeeded or Failed" Jan 31 23:54:41.715: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.888635ms Jan 31 23:54:43.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063884889s Jan 31 23:54:45.747: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.063535367s Jan 31 23:54:47.749: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064782904s Jan 31 23:54:49.747: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.062769561s Jan 31 23:54:51.747: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.062914715s Jan 31 23:54:53.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.064128242s Jan 31 23:54:55.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.063740063s Jan 31 23:54:57.750: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.065802968s Jan 31 23:54:59.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.064091511s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:54:59.748[0m Jan 31 23:54:59.748: INFO: Pod "azuredisk-volume-tester-g6zhj" satisfied condition "Succeeded or Failed" Jan 31 23:54:59.780: INFO: deleting Pod "azuredisk-5295"/"azuredisk-volume-tester-g6zhj" Jan 31 23:54:59.814: INFO: Pod azuredisk-volume-tester-g6zhj has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g6zhj in namespace azuredisk-5295 [38;5;243m01/31/23 23:54:59.814[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:54:59.852[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/31/23 23:55:13.916[0m [1mSTEP:[0m Prow test resource group: capz-g49wn9 [38;5;243m01/31/23 23:55:13.917[0m ... skipping 16 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:55:34.5[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:55:34.532[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:55:34.564[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:55:34.564[0m I0131 23:55:34.564430 41330 resource_setup.go:62] adding PV (pvc-9e50e41b-5d50-4f9b-aefa-754d225cc45a) to pod () [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/31/23 23:55:34.564[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:55:34.6[0m Jan 31 23:55:34.600: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zxbbl" in namespace "azuredisk-5295" to be "Succeeded or Failed" Jan 31 23:55:34.654: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 54.008942ms Jan 31 23:55:36.687: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.087158225s Jan 31 23:55:38.688: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088491855s Jan 31 23:55:40.687: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.087342663s Jan 31 23:55:42.686: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.086178587s Jan 31 23:55:44.686: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.08589368s Jan 31 23:55:46.687: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.086615886s Jan 31 23:55:48.688: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.087646855s Jan 31 23:55:50.696: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.095815955s Jan 31 23:55:52.688: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.088339325s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:55:52.688[0m Jan 31 23:55:52.689: INFO: Pod "azuredisk-volume-tester-zxbbl" satisfied condition "Succeeded or Failed" Jan 31 23:55:52.689: INFO: deleting Pod "azuredisk-5295"/"azuredisk-volume-tester-zxbbl" Jan 31 23:55:52.722: INFO: Pod azuredisk-volume-tester-zxbbl has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-zxbbl in namespace azuredisk-5295 [38;5;243m01/31/23 23:55:52.723[0m Jan 31 23:55:52.762: INFO: deleting PVC "azuredisk-5295"/"pvc-ctw5m" Jan 31 23:55:52.762: INFO: Deleting PersistentVolumeClaim "pvc-ctw5m" ... skipping 12 lines ... Jan 31 23:56:33.143: INFO: Claim "pvc-ctw5m" in namespace "azuredisk-5295" doesn't exist in the system Jan 31 23:56:33.143: INFO: deleting StorageClass azuredisk-5295-disk.csi.azure.com-dynamic-sc-8dx6s [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-8sd6z [38;5;243m01/31/23 23:56:33.175[0m Jan 31 23:56:33.214: INFO: skip deleting VolumeSnapshotClass azuredisk-5295-disk.csi.azure.com-dynamic-sc-vk9n4 Jan 31 23:56:33.214: INFO: Deleting resource group azuredisk-csi-driver-test-b44f4c6c-a1c2-11ed-91a3-b60e75ebbac2 Jan 31 23:57:49.494: INFO: deleting Pod "azuredisk-5295"/"azuredisk-volume-tester-g6zhj" Jan 31 23:57:49.526: INFO: Error getting logs for pod azuredisk-volume-tester-g6zhj: the server could not find the requested resource (get pods azuredisk-volume-tester-g6zhj) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g6zhj in namespace azuredisk-5295 [38;5;243m01/31/23 23:57:49.526[0m Jan 31 23:57:49.557: INFO: deleting PVC "azuredisk-5295"/"pvc-2jf7g" Jan 31 23:57:49.557: INFO: Deleting PersistentVolumeClaim "pvc-2jf7g" [1mSTEP:[0m waiting for claim's PV "pvc-a74fb34c-5729-44e1-9895-3e964522e75c" to be deleted [38;5;243m01/31/23 23:57:49.589[0m Jan 31 23:57:49.589: INFO: Waiting up to 10m0s for PersistentVolume pvc-a74fb34c-5729-44e1-9895-3e964522e75c to get deleted Jan 31 23:57:49.621: INFO: PersistentVolume pvc-a74fb34c-5729-44e1-9895-3e964522e75c found and phase=Released (31.94904ms) ... skipping 29 lines ... Jan 31 23:54:39.552: INFO: PersistentVolumeClaim pvc-2jf7g found but phase is Pending instead of Bound. Jan 31 23:54:41.585: INFO: PersistentVolumeClaim pvc-2jf7g found and phase=Bound (4.102042009s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:54:41.585[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:54:41.616[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:54:41.651[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:54:41.651[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:54:41.684[0m Jan 31 23:54:41.684: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-g6zhj" in namespace "azuredisk-5295" to be "Succeeded or Failed" Jan 31 23:54:41.715: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.888635ms Jan 31 23:54:43.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063884889s Jan 31 23:54:45.747: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.063535367s Jan 31 23:54:47.749: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064782904s Jan 31 23:54:49.747: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.062769561s Jan 31 23:54:51.747: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.062914715s Jan 31 23:54:53.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.064128242s Jan 31 23:54:55.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.063740063s Jan 31 23:54:57.750: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.065802968s Jan 31 23:54:59.748: INFO: Pod "azuredisk-volume-tester-g6zhj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.064091511s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:54:59.748[0m Jan 31 23:54:59.748: INFO: Pod "azuredisk-volume-tester-g6zhj" satisfied condition "Succeeded or Failed" Jan 31 23:54:59.780: INFO: deleting Pod "azuredisk-5295"/"azuredisk-volume-tester-g6zhj" Jan 31 23:54:59.814: INFO: Pod azuredisk-volume-tester-g6zhj has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g6zhj in namespace azuredisk-5295 [38;5;243m01/31/23 23:54:59.814[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:54:59.852[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/31/23 23:55:13.916[0m [1mSTEP:[0m Prow test resource group: capz-g49wn9 [38;5;243m01/31/23 23:55:13.917[0m ... skipping 16 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:55:34.5[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:55:34.532[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:55:34.564[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:55:34.564[0m I0131 23:55:34.564430 41330 resource_setup.go:62] adding PV (pvc-9e50e41b-5d50-4f9b-aefa-754d225cc45a) to pod () [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/31/23 23:55:34.564[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:55:34.6[0m Jan 31 23:55:34.600: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zxbbl" in namespace "azuredisk-5295" to be "Succeeded or Failed" Jan 31 23:55:34.654: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 54.008942ms Jan 31 23:55:36.687: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.087158225s Jan 31 23:55:38.688: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088491855s Jan 31 23:55:40.687: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.087342663s Jan 31 23:55:42.686: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.086178587s Jan 31 23:55:44.686: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.08589368s Jan 31 23:55:46.687: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.086615886s Jan 31 23:55:48.688: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.087646855s Jan 31 23:55:50.696: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.095815955s Jan 31 23:55:52.688: INFO: Pod "azuredisk-volume-tester-zxbbl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.088339325s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:55:52.688[0m Jan 31 23:55:52.689: INFO: Pod "azuredisk-volume-tester-zxbbl" satisfied condition "Succeeded or Failed" Jan 31 23:55:52.689: INFO: deleting Pod "azuredisk-5295"/"azuredisk-volume-tester-zxbbl" Jan 31 23:55:52.722: INFO: Pod azuredisk-volume-tester-zxbbl has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-zxbbl in namespace azuredisk-5295 [38;5;243m01/31/23 23:55:52.723[0m Jan 31 23:55:52.762: INFO: deleting PVC "azuredisk-5295"/"pvc-ctw5m" Jan 31 23:55:52.762: INFO: Deleting PersistentVolumeClaim "pvc-ctw5m" ... skipping 12 lines ... Jan 31 23:56:33.143: INFO: Claim "pvc-ctw5m" in namespace "azuredisk-5295" doesn't exist in the system Jan 31 23:56:33.143: INFO: deleting StorageClass azuredisk-5295-disk.csi.azure.com-dynamic-sc-8dx6s [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-8sd6z [38;5;243m01/31/23 23:56:33.175[0m Jan 31 23:56:33.214: INFO: skip deleting VolumeSnapshotClass azuredisk-5295-disk.csi.azure.com-dynamic-sc-vk9n4 Jan 31 23:56:33.214: INFO: Deleting resource group azuredisk-csi-driver-test-b44f4c6c-a1c2-11ed-91a3-b60e75ebbac2 Jan 31 23:57:49.494: INFO: deleting Pod "azuredisk-5295"/"azuredisk-volume-tester-g6zhj" Jan 31 23:57:49.526: INFO: Error getting logs for pod azuredisk-volume-tester-g6zhj: the server could not find the requested resource (get pods azuredisk-volume-tester-g6zhj) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-g6zhj in namespace azuredisk-5295 [38;5;243m01/31/23 23:57:49.526[0m Jan 31 23:57:49.557: INFO: deleting PVC "azuredisk-5295"/"pvc-2jf7g" Jan 31 23:57:49.557: INFO: Deleting PersistentVolumeClaim "pvc-2jf7g" [1mSTEP:[0m waiting for claim's PV "pvc-a74fb34c-5729-44e1-9895-3e964522e75c" to be deleted [38;5;243m01/31/23 23:57:49.589[0m Jan 31 23:57:49.589: INFO: Waiting up to 10m0s for PersistentVolume pvc-a74fb34c-5729-44e1-9895-3e964522e75c to get deleted Jan 31 23:57:49.621: INFO: PersistentVolume pvc-a74fb34c-5729-44e1-9895-3e964522e75c found and phase=Released (31.94904ms) ... skipping 29 lines ... Jan 31 23:58:02.520: INFO: PersistentVolumeClaim pvc-zxb5s found but phase is Pending instead of Bound. Jan 31 23:58:04.553: INFO: PersistentVolumeClaim pvc-zxb5s found and phase=Bound (4.095175186s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:58:04.553[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:58:04.584[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:58:04.616[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:58:04.616[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:58:04.649[0m Jan 31 23:58:04.649: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2hdtv" in namespace "azuredisk-9817" to be "Succeeded or Failed" Jan 31 23:58:04.685: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 36.126118ms Jan 31 23:58:06.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069440153s Jan 31 23:58:08.722: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072437722s Jan 31 23:58:10.720: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071028147s Jan 31 23:58:12.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069836268s Jan 31 23:58:14.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069456978s Jan 31 23:58:16.718: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.068456585s Jan 31 23:58:18.718: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.068453973s Jan 31 23:58:20.723: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Running", Reason="", readiness=false. Elapsed: 16.073521604s Jan 31 23:58:22.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.069865456s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:58:22.719[0m Jan 31 23:58:22.719: INFO: Pod "azuredisk-volume-tester-2hdtv" satisfied condition "Succeeded or Failed" Jan 31 23:58:22.752: INFO: deleting Pod "azuredisk-9817"/"azuredisk-volume-tester-2hdtv" Jan 31 23:58:22.796: INFO: Pod azuredisk-volume-tester-2hdtv has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2hdtv in namespace azuredisk-9817 [38;5;243m01/31/23 23:58:22.796[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:58:22.837[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/31/23 23:58:42.902[0m [1mSTEP:[0m Prow test resource group: capz-g49wn9 [38;5;243m01/31/23 23:58:42.902[0m ... skipping 28 lines ... [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:59:15.096[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:59:15.127[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:59:15.127[0m I0131 23:59:15.127848 41330 resource_setup.go:62] adding PV (pvc-6ac82188-d4c9-4919-941a-40068e297b56) to pod () [1mSTEP:[0m Set pod anti-affinity to make sure two pods are scheduled on different nodes [38;5;243m01/31/23 23:59:15.127[0m [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/31/23 23:59:15.127[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:59:15.164[0m Jan 31 23:59:15.164: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-rf577" in namespace "azuredisk-9817" to be "Succeeded or Failed" Jan 31 23:59:15.195: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 31.033134ms Jan 31 23:59:17.231: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066784839s Jan 31 23:59:19.227: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 4.063683165s Jan 31 23:59:21.230: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065973862s Jan 31 23:59:23.228: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064194428s Jan 31 23:59:25.229: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065325905s Jan 31 23:59:27.228: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.064106587s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:59:27.228[0m Jan 31 23:59:27.228: INFO: Pod "azuredisk-volume-tester-rf577" satisfied condition "Succeeded or Failed" Jan 31 23:59:27.228: INFO: deleting Pod "azuredisk-9817"/"azuredisk-volume-tester-rf577" Jan 31 23:59:27.271: INFO: Pod azuredisk-volume-tester-rf577 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-rf577 in namespace azuredisk-9817 [38;5;243m01/31/23 23:59:27.271[0m Jan 31 23:59:27.309: INFO: deleting PVC "azuredisk-9817"/"pvc-z4fnm" Jan 31 23:59:27.309: INFO: Deleting PersistentVolumeClaim "pvc-z4fnm" ... skipping 15 lines ... Feb 1 00:00:07.757: INFO: Pod azuredisk-volume-tester-87xkf has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-87xkf in namespace azuredisk-9817 [38;5;243m02/01/23 00:00:07.757[0m [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-chxsz [38;5;243m02/01/23 00:00:07.791[0m Feb 1 00:00:07.825: INFO: skip deleting VolumeSnapshotClass azuredisk-9817-disk.csi.azure.com-dynamic-sc-jtmb8 Feb 1 00:00:07.825: INFO: Deleting resource group azuredisk-csi-driver-test-30dfe585-a1c3-11ed-91a3-b60e75ebbac2 Feb 1 00:02:36.742: INFO: deleting Pod "azuredisk-9817"/"azuredisk-volume-tester-2hdtv" Feb 1 00:02:36.915: INFO: Error getting logs for pod azuredisk-volume-tester-2hdtv: the server could not find the requested resource (get pods azuredisk-volume-tester-2hdtv) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2hdtv in namespace azuredisk-9817 [38;5;243m02/01/23 00:02:36.915[0m Feb 1 00:02:36.946: INFO: deleting PVC "azuredisk-9817"/"pvc-zxb5s" Feb 1 00:02:36.946: INFO: Deleting PersistentVolumeClaim "pvc-zxb5s" [1mSTEP:[0m waiting for claim's PV "pvc-62487ab6-150f-4e28-8021-4d45128aeaf7" to be deleted [38;5;243m02/01/23 00:02:36.98[0m Feb 1 00:02:36.981: INFO: Waiting up to 10m0s for PersistentVolume pvc-62487ab6-150f-4e28-8021-4d45128aeaf7 to get deleted Feb 1 00:02:37.013: INFO: PersistentVolume pvc-62487ab6-150f-4e28-8021-4d45128aeaf7 found and phase=Released (32.231037ms) ... skipping 29 lines ... Jan 31 23:58:02.520: INFO: PersistentVolumeClaim pvc-zxb5s found but phase is Pending instead of Bound. Jan 31 23:58:04.553: INFO: PersistentVolumeClaim pvc-zxb5s found and phase=Bound (4.095175186s) [1mSTEP:[0m checking the PVC [38;5;243m01/31/23 23:58:04.553[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:58:04.584[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:58:04.616[0m [1mSTEP:[0m deploying the pod [38;5;243m01/31/23 23:58:04.616[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:58:04.649[0m Jan 31 23:58:04.649: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2hdtv" in namespace "azuredisk-9817" to be "Succeeded or Failed" Jan 31 23:58:04.685: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 36.126118ms Jan 31 23:58:06.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069440153s Jan 31 23:58:08.722: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072437722s Jan 31 23:58:10.720: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071028147s Jan 31 23:58:12.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.069836268s Jan 31 23:58:14.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069456978s Jan 31 23:58:16.718: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.068456585s Jan 31 23:58:18.718: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.068453973s Jan 31 23:58:20.723: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Running", Reason="", readiness=false. Elapsed: 16.073521604s Jan 31 23:58:22.719: INFO: Pod "azuredisk-volume-tester-2hdtv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.069865456s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:58:22.719[0m Jan 31 23:58:22.719: INFO: Pod "azuredisk-volume-tester-2hdtv" satisfied condition "Succeeded or Failed" Jan 31 23:58:22.752: INFO: deleting Pod "azuredisk-9817"/"azuredisk-volume-tester-2hdtv" Jan 31 23:58:22.796: INFO: Pod azuredisk-volume-tester-2hdtv has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2hdtv in namespace azuredisk-9817 [38;5;243m01/31/23 23:58:22.796[0m [1mSTEP:[0m waiting for disk to detach from node [38;5;243m01/31/23 23:58:22.837[0m [1mSTEP:[0m Checking Prow test resource group [38;5;243m01/31/23 23:58:42.902[0m [1mSTEP:[0m Prow test resource group: capz-g49wn9 [38;5;243m01/31/23 23:58:42.902[0m ... skipping 28 lines ... [1mSTEP:[0m validating provisioned PV [38;5;243m01/31/23 23:59:15.096[0m [1mSTEP:[0m checking the PV [38;5;243m01/31/23 23:59:15.127[0m [1mSTEP:[0m setting up the pod [38;5;243m01/31/23 23:59:15.127[0m I0131 23:59:15.127848 41330 resource_setup.go:62] adding PV (pvc-6ac82188-d4c9-4919-941a-40068e297b56) to pod () [1mSTEP:[0m Set pod anti-affinity to make sure two pods are scheduled on different nodes [38;5;243m01/31/23 23:59:15.127[0m [1mSTEP:[0m deploying a pod with a volume restored from the snapshot [38;5;243m01/31/23 23:59:15.127[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/31/23 23:59:15.164[0m Jan 31 23:59:15.164: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-rf577" in namespace "azuredisk-9817" to be "Succeeded or Failed" Jan 31 23:59:15.195: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 31.033134ms Jan 31 23:59:17.231: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066784839s Jan 31 23:59:19.227: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 4.063683165s Jan 31 23:59:21.230: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065973862s Jan 31 23:59:23.228: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064194428s Jan 31 23:59:25.229: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065325905s Jan 31 23:59:27.228: INFO: Pod "azuredisk-volume-tester-rf577": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.064106587s [1mSTEP:[0m Saw pod success [38;5;243m01/31/23 23:59:27.228[0m Jan 31 23:59:27.228: INFO: Pod "azuredisk-volume-tester-rf577" satisfied condition "Succeeded or Failed" Jan 31 23:59:27.228: INFO: deleting Pod "azuredisk-9817"/"azuredisk-volume-tester-rf577" Jan 31 23:59:27.271: INFO: Pod azuredisk-volume-tester-rf577 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-rf577 in namespace azuredisk-9817 [38;5;243m01/31/23 23:59:27.271[0m Jan 31 23:59:27.309: INFO: deleting PVC "azuredisk-9817"/"pvc-z4fnm" Jan 31 23:59:27.309: INFO: Deleting PersistentVolumeClaim "pvc-z4fnm" ... skipping 15 lines ... Feb 1 00:00:07.757: INFO: Pod azuredisk-volume-tester-87xkf has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-87xkf in namespace azuredisk-9817 [38;5;243m02/01/23 00:00:07.757[0m [1mSTEP:[0m deleting a VolumeSnapshot volume-snapshot-chxsz [38;5;243m02/01/23 00:00:07.791[0m Feb 1 00:00:07.825: INFO: skip deleting VolumeSnapshotClass azuredisk-9817-disk.csi.azure.com-dynamic-sc-jtmb8 Feb 1 00:00:07.825: INFO: Deleting resource group azuredisk-csi-driver-test-30dfe585-a1c3-11ed-91a3-b60e75ebbac2 Feb 1 00:02:36.742: INFO: deleting Pod "azuredisk-9817"/"azuredisk-volume-tester-2hdtv" Feb 1 00:02:36.915: INFO: Error getting logs for pod azuredisk-volume-tester-2hdtv: the server could not find the requested resource (get pods azuredisk-volume-tester-2hdtv) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-2hdtv in namespace azuredisk-9817 [38;5;243m02/01/23 00:02:36.915[0m Feb 1 00:02:36.946: INFO: deleting PVC "azuredisk-9817"/"pvc-zxb5s" Feb 1 00:02:36.946: INFO: Deleting PersistentVolumeClaim "pvc-zxb5s" [1mSTEP:[0m waiting for claim's PV "pvc-62487ab6-150f-4e28-8021-4d45128aeaf7" to be deleted [38;5;243m02/01/23 00:02:36.98[0m Feb 1 00:02:36.981: INFO: Waiting up to 10m0s for PersistentVolume pvc-62487ab6-150f-4e28-8021-4d45128aeaf7 to get deleted Feb 1 00:02:37.013: INFO: PersistentVolume pvc-62487ab6-150f-4e28-8021-4d45128aeaf7 found and phase=Released (32.231037ms) ... skipping 56 lines ... Feb 1 00:03:00.409: INFO: PersistentVolumeClaim pvc-bdrlw found and phase=Bound (4.095987076s) [1mSTEP:[0m checking the PVC [38;5;243m02/01/23 00:03:00.409[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:03:00.441[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:03:00.473[0m I0201 00:03:00.473979 41330 resource_setup.go:89] adding PV (pvc-c8f304ef-9ee3-4ebc-b234-416c129cc08d) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/01/23 00:03:00.474[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:03:00.507[0m Feb 1 00:03:00.507: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nggh4" in namespace "azuredisk-8741" to be "Succeeded or Failed" Feb 1 00:03:00.540: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.652109ms Feb 1 00:03:02.576: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068530349s Feb 1 00:03:04.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06715251s Feb 1 00:03:06.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067027103s Feb 1 00:03:08.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.067796251s Feb 1 00:03:10.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06623606s Feb 1 00:03:12.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.06747895s Feb 1 00:03:14.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.066786211s Feb 1 00:03:16.578: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.070294863s Feb 1 00:03:18.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.067959628s Feb 1 00:03:20.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.066774692s Feb 1 00:03:22.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.067068885s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:03:22.575[0m Feb 1 00:03:22.575: INFO: Pod "azuredisk-volume-tester-nggh4" satisfied condition "Succeeded or Failed" Feb 1 00:03:22.575: INFO: deleting Pod "azuredisk-8741"/"azuredisk-volume-tester-nggh4" Feb 1 00:03:22.616: INFO: Pod azuredisk-volume-tester-nggh4 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nggh4 in namespace azuredisk-8741 [38;5;243m02/01/23 00:03:22.616[0m Feb 1 00:03:22.655: INFO: deleting PVC "azuredisk-8741"/"pvc-bdrlw" Feb 1 00:03:22.655: INFO: Deleting PersistentVolumeClaim "pvc-bdrlw" ... skipping 84 lines ... Feb 1 00:03:00.409: INFO: PersistentVolumeClaim pvc-bdrlw found and phase=Bound (4.095987076s) [1mSTEP:[0m checking the PVC [38;5;243m02/01/23 00:03:00.409[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/01/23 00:03:00.441[0m [1mSTEP:[0m checking the PV [38;5;243m02/01/23 00:03:00.473[0m I0201 00:03:00.473979 41330 resource_setup.go:89] adding PV (pvc-c8f304ef-9ee3-4ebc-b234-416c129cc08d) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/01/23 00:03:00.474[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/01/23 00:03:00.507[0m Feb 1 00:03:00.507: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nggh4" in namespace "azuredisk-8741" to be "Succeeded or Failed" Feb 1 00:03:00.540: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.652109ms Feb 1 00:03:02.576: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068530349s Feb 1 00:03:04.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.06715251s Feb 1 00:03:06.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067027103s Feb 1 00:03:08.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.067796251s Feb 1 00:03:10.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06623606s Feb 1 00:03:12.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.06747895s Feb 1 00:03:14.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.066786211s Feb 1 00:03:16.578: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.070294863s Feb 1 00:03:18.575: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.067959628s Feb 1 00:03:20.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.066774692s Feb 1 00:03:22.574: INFO: Pod "azuredisk-volume-tester-nggh4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.067068885s [1mSTEP:[0m Saw pod success [38;5;243m02/01/23 00:03:22.575[0m Feb 1 00:03:22.575: INFO: Pod "azuredisk-volume-tester-nggh4" satisfied condition "Succeeded or Failed" Feb 1 00:03:22.575: INFO: deleting Pod "azuredisk-8741"/"azuredisk-volume-tester-nggh4" Feb 1 00:03:22.616: INFO: Pod azuredisk-volume-tester-nggh4 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-nggh4 in namespace azuredisk-8741 [38;5;243m02/01/23 00:03:22.616[0m Feb 1 00:03:22.655: INFO: deleting PVC "azuredisk-8741"/"pvc-bdrlw" Feb 1 00:03:22.655: INFO: Deleting PersistentVolumeClaim "pvc-bdrlw" ... skipping 548 lines ... I0201 00:12:05.113516 41330 dynamically_provisioned_pod_delete.go:101] volumes: [{Name:test-volume-1 VolumeSource:{HostPath:nil EmptyDir:nil GCEPersistentDisk:nil AWSElasticBlockStore:nil GitRepo:nil Secret:nil NFS:nil ISCSI:nil Glusterfs:nil PersistentVolumeClaim:&PersistentVolumeClaimVolumeSource{ClaimName:pvc-pkg6d,ReadOnly:false,} RBD:nil FlexVolume:nil Cinder:nil CephFS:nil Flocker:nil DownwardAPI:nil FC:nil AzureFile:nil ConfigMap:nil VsphereVolume:nil Quobyte:nil AzureDisk:nil PhotonPersistentDisk:nil Projected:nil PortworxVolume:nil ScaleIO:nil StorageOS:nil CSI:nil Ephemeral:nil}}] [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:12:05.113[0m Feb 1 00:12:05.113: INFO: deleting Pod "azuredisk-1494"/"azuredisk-volume-tester-mcfbl" Feb 1 00:12:05.148: INFO: Pod azuredisk-volume-tester-mcfbl has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-mcfbl in namespace azuredisk-1494 [38;5;243m02/01/23 00:12:05.148[0m Feb 1 00:13:01.261: INFO: deleting Pod "azuredisk-1494"/"azuredisk-volume-tester-mcfbl" Feb 1 00:13:01.293: INFO: Error getting logs for pod azuredisk-volume-tester-mcfbl: the server could not find the requested resource (get pods azuredisk-volume-tester-mcfbl) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-mcfbl in namespace azuredisk-1494 [38;5;243m02/01/23 00:13:01.293[0m Feb 1 00:13:01.327: INFO: deleting PVC "azuredisk-1494"/"pvc-pkg6d" Feb 1 00:13:01.327: INFO: Deleting PersistentVolumeClaim "pvc-pkg6d" [1mSTEP:[0m waiting for claim's PV "pvc-34756bf3-3630-41be-94ff-4fd26a49acb2" to be deleted [38;5;243m02/01/23 00:13:01.36[0m Feb 1 00:13:01.360: INFO: Waiting up to 10m0s for PersistentVolume pvc-34756bf3-3630-41be-94ff-4fd26a49acb2 to get deleted Feb 1 00:13:01.395: INFO: PersistentVolume pvc-34756bf3-3630-41be-94ff-4fd26a49acb2 found and phase=Released (34.832154ms) ... skipping 51 lines ... I0201 00:12:05.113516 41330 dynamically_provisioned_pod_delete.go:101] volumes: [{Name:test-volume-1 VolumeSource:{HostPath:nil EmptyDir:nil GCEPersistentDisk:nil AWSElasticBlockStore:nil GitRepo:nil Secret:nil NFS:nil ISCSI:nil Glusterfs:nil PersistentVolumeClaim:&PersistentVolumeClaimVolumeSource{ClaimName:pvc-pkg6d,ReadOnly:false,} RBD:nil FlexVolume:nil Cinder:nil CephFS:nil Flocker:nil DownwardAPI:nil FC:nil AzureFile:nil ConfigMap:nil VsphereVolume:nil Quobyte:nil AzureDisk:nil PhotonPersistentDisk:nil Projected:nil PortworxVolume:nil ScaleIO:nil StorageOS:nil CSI:nil Ephemeral:nil}}] [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:12:05.113[0m Feb 1 00:12:05.113: INFO: deleting Pod "azuredisk-1494"/"azuredisk-volume-tester-mcfbl" Feb 1 00:12:05.148: INFO: Pod azuredisk-volume-tester-mcfbl has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-mcfbl in namespace azuredisk-1494 [38;5;243m02/01/23 00:12:05.148[0m Feb 1 00:13:01.261: INFO: deleting Pod "azuredisk-1494"/"azuredisk-volume-tester-mcfbl" Feb 1 00:13:01.293: INFO: Error getting logs for pod azuredisk-volume-tester-mcfbl: the server could not find the requested resource (get pods azuredisk-volume-tester-mcfbl) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-mcfbl in namespace azuredisk-1494 [38;5;243m02/01/23 00:13:01.293[0m Feb 1 00:13:01.327: INFO: deleting PVC "azuredisk-1494"/"pvc-pkg6d" Feb 1 00:13:01.327: INFO: Deleting PersistentVolumeClaim "pvc-pkg6d" [1mSTEP:[0m waiting for claim's PV "pvc-34756bf3-3630-41be-94ff-4fd26a49acb2" to be deleted [38;5;243m02/01/23 00:13:01.36[0m Feb 1 00:13:01.360: INFO: Waiting up to 10m0s for PersistentVolume pvc-34756bf3-3630-41be-94ff-4fd26a49acb2 to get deleted Feb 1 00:13:01.395: INFO: PersistentVolume pvc-34756bf3-3630-41be-94ff-4fd26a49acb2 found and phase=Released (34.832154ms) ... skipping 52 lines ... I0201 00:13:32.592381 41330 dynamically_provisioned_pod_delete.go:101] volumes: [{Name:test-volume-1 VolumeSource:{HostPath:nil EmptyDir:nil GCEPersistentDisk:nil AWSElasticBlockStore:nil GitRepo:nil Secret:nil NFS:nil ISCSI:nil Glusterfs:nil PersistentVolumeClaim:&PersistentVolumeClaimVolumeSource{ClaimName:pvc-58jnw,ReadOnly:false,} RBD:nil FlexVolume:nil Cinder:nil CephFS:nil Flocker:nil DownwardAPI:nil FC:nil AzureFile:nil ConfigMap:nil VsphereVolume:nil Quobyte:nil AzureDisk:nil PhotonPersistentDisk:nil Projected:nil PortworxVolume:nil ScaleIO:nil StorageOS:nil CSI:nil Ephemeral:nil}}] [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:13:32.592[0m Feb 1 00:13:32.592: INFO: deleting Pod "azuredisk-8999"/"azuredisk-volume-tester-4dr7r" Feb 1 00:13:32.627: INFO: Pod azuredisk-volume-tester-4dr7r has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-4dr7r in namespace azuredisk-8999 [38;5;243m02/01/23 00:13:32.627[0m Feb 1 00:14:06.737: INFO: deleting Pod "azuredisk-8999"/"azuredisk-volume-tester-4dr7r" Feb 1 00:14:06.769: INFO: Error getting logs for pod azuredisk-volume-tester-4dr7r: the server could not find the requested resource (get pods azuredisk-volume-tester-4dr7r) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-4dr7r in namespace azuredisk-8999 [38;5;243m02/01/23 00:14:06.769[0m Feb 1 00:14:06.801: INFO: deleting PVC "azuredisk-8999"/"pvc-58jnw" Feb 1 00:14:06.801: INFO: Deleting PersistentVolumeClaim "pvc-58jnw" [1mSTEP:[0m waiting for claim's PV "pvc-9f065bfe-1938-4a1f-87c5-68d4cbd593c3" to be deleted [38;5;243m02/01/23 00:14:06.835[0m Feb 1 00:14:06.835: INFO: Waiting up to 10m0s for PersistentVolume pvc-9f065bfe-1938-4a1f-87c5-68d4cbd593c3 to get deleted Feb 1 00:14:06.888: INFO: PersistentVolume pvc-9f065bfe-1938-4a1f-87c5-68d4cbd593c3 found and phase=Released (52.910032ms) ... skipping 58 lines ... I0201 00:13:32.592381 41330 dynamically_provisioned_pod_delete.go:101] volumes: [{Name:test-volume-1 VolumeSource:{HostPath:nil EmptyDir:nil GCEPersistentDisk:nil AWSElasticBlockStore:nil GitRepo:nil Secret:nil NFS:nil ISCSI:nil Glusterfs:nil PersistentVolumeClaim:&PersistentVolumeClaimVolumeSource{ClaimName:pvc-58jnw,ReadOnly:false,} RBD:nil FlexVolume:nil Cinder:nil CephFS:nil Flocker:nil DownwardAPI:nil FC:nil AzureFile:nil ConfigMap:nil VsphereVolume:nil Quobyte:nil AzureDisk:nil PhotonPersistentDisk:nil Projected:nil PortworxVolume:nil ScaleIO:nil StorageOS:nil CSI:nil Ephemeral:nil}}] [1mSTEP:[0m begin to delete the pod [38;5;243m02/01/23 00:13:32.592[0m Feb 1 00:13:32.592: INFO: deleting Pod "azuredisk-8999"/"azuredisk-volume-tester-4dr7r" Feb 1 00:13:32.627: INFO: Pod azuredisk-volume-tester-4dr7r has the following logs: [1mSTEP:[0m Deleting pod azuredisk-volume-tester-4dr7r in namespace azuredisk-8999 [38;5;243m02/01/23 00:13:32.627[0m Feb 1 00:14:06.737: INFO: deleting Pod "azuredisk-8999"/"azuredisk-volume-tester-4dr7r" Feb 1 00:14:06.769: INFO: Error getting logs for pod azuredisk-volume-tester-4dr7r: the server could not find the requested resource (get pods azuredisk-volume-tester-4dr7r) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-4dr7r in namespace azuredisk-8999 [38;5;243m02/01/23 00:14:06.769[0m Feb 1 00:14:06.801: INFO: deleting PVC "azuredisk-8999"/"pvc-58jnw" Feb 1 00:14:06.801: INFO: Deleting PersistentVolumeClaim "pvc-58jnw" [1mSTEP:[0m waiting for claim's PV "pvc-9f065bfe-1938-4a1f-87c5-68d4cbd593c3" to be deleted [38;5;243m02/01/23 00:14:06.835[0m Feb 1 00:14:06.835: INFO: Waiting up to 10m0s for PersistentVolume pvc-9f065bfe-1938-4a1f-87c5-68d4cbd593c3 to get deleted Feb 1 00:14:06.888: INFO: PersistentVolume pvc-9f065bfe-1938-4a1f-87c5-68d4cbd593c3 found and phase=Released (52.910032ms) ... skipping 1032 lines ...