PR #113262 pull-kubernetes-e2e-capz-azure-disk-vmss #1587823067474694144
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | jsafrane: Rework volume reconstruction |
| Result | ABORTED |
| Tests | 0 failed / 12 succeeded |
| Started | |
| Elapsed | 1h7m |
| Revision | 5d2a018ad2601a5dc4a17845bfb0640db45c5ede |
| Refs |
113262 |
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should create a pod with multiple volumes [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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 Dynamic Provisioning [single-az] should detach disk after pod deleted [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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 Dynamic Provisioning [multi-az] Should test pod failover with cordoning a node
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] Should test pod failover with cordoning a node using ZRS
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should clone a volume from an existing volume and read from it [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should create a pod with multiple volumes [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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 Dynamic Provisioning [multi-az] should create a volume azuredisk with tag [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should create a volume on demand and resize it [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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 Dynamic Provisioning [multi-az] should detach disk after pod deleted [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [multi-az] should retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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 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 Dynamic Provisioning [single-az] Should test pod failover with cordoning a node
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] Should test pod failover with cordoning a node using ZRS
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should clone a volume from an existing volume and read from it [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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 Dynamic Provisioning [single-az] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests 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]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should create a volume azuredisk with tag [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests 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 Dynamic Provisioning [single-az] should create a volume on demand and resize it [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests Dynamic Provisioning [single-az] should retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests 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 Pre-Provisioned [single-az] should create an inline volume by in-tree driver [kubernetes.io/azure-disk]
AzureDisk CSI Driver End-to-End Tests Pre-Provisioned [single-az] should fail when maxShares is invalid [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests 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 Pre-Provisioned [single-az] should succeed when creating a PremiumV2_LRS disk [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests Pre-Provisioned [single-az] should succeed when creating a shared disk [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests Pre-Provisioned [single-az] should succeed when reattaching a disk to a new node on DanglingAttachError [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests Pre-Provisioned [single-az] should use a pre-provisioned volume and mount it as readOnly in a pod [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests Pre-Provisioned [single-az] should use a pre-provisioned volume and retain PV with reclaimPolicy "Retain" [disk.csi.azure.com][windows]
... skipping 126 lines ... /home/prow/go/src/k8s.io/kubernetes /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 138 100 138 0 0 4451 0 --:--:-- --:--:-- --:--:-- 4451 100 33 100 33 0 0 434 0 --:--:-- --:--:-- --:--:-- 434 Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.26.0-alpha.3.58_6a6635c48422b9 not found: manifest unknown: manifest tagged by "v1.26.0-alpha.3.58_6a6635c48422b9" is not found Building Kubernetes make: Entering directory '/home/prow/go/src/k8s.io/kubernetes' +++ [1102 15:07:58] Verifying Prerequisites.... +++ [1102 15:07:59] Building Docker image kube-build:build-7624de3211-5-v1.25.0-go1.19.2-bullseye.0 +++ [1102 15:10:23] Creating data container kube-build-data-7624de3211-5-v1.25.0-go1.19.2-bullseye.0 +++ [1102 15:10:38] Syncing sources to container ... skipping 771 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 134 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-z3i3kp-kubeconfig; do sleep 1; done" capz-z3i3kp-kubeconfig cluster.x-k8s.io/secret 1 1s # 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-z3i3kp-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-z3i3kp-control-plane-p7ssx NotReady control-plane 1s v1.26.0-alpha.3.58+6a6635c48422b9 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' Waiting for 1 control plane machine(s), 2 worker machine(s), and windows machine(s) to become Ready node/capz-z3i3kp-control-plane-p7ssx condition met node/capz-z3i3kp-mp-0000000 condition met ... skipping 62 lines ... [0mDynamic Provisioning[0m [90m[single-az][0m [1mshould create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows][0m [37m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:101[0m [1mSTEP[0m: Creating a kubernetes client Nov 2 15:41:44.208: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP[0m: Building a namespace api object, basename azuredisk Nov 2 15:41:44.472: INFO: Error listing PodSecurityPolicies; assuming PodSecurityPolicy is disabled: the server could not find the requested resource [1mSTEP[0m: Waiting for a default service account to be provisioned in namespace [1mSTEP[0m: Waiting for kube-root-ca.crt to be provisioned in namespace 2022/11/02 15:41:44 Check driver pods if restarts ... check the driver pods if restarts ... ====================================================================================== 2022/11/02 15:41:44 Check successfully Nov 2 15:41:44.841: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP[0m: setting up the StorageClass [1mSTEP[0m: creating a StorageClass [1mSTEP[0m: setting up the PVC and PV [1mSTEP[0m: creating a PVC [1mSTEP[0m: setting up the pod [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod's command exits with no error Nov 2 15:41:44.963: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vhbv2" in namespace "azuredisk-8081" to be "Succeeded or Failed" Nov 2 15:41:45.021: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 58.049929ms Nov 2 15:41:47.052: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089656118s Nov 2 15:41:49.084: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.121539234s Nov 2 15:41:51.117: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.154262752s Nov 2 15:41:53.150: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.187189239s Nov 2 15:41:55.184: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.220764888s ... skipping 9 lines ... Nov 2 15:42:15.510: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.547523763s Nov 2 15:42:17.543: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.580649621s Nov 2 15:42:19.577: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.61452807s Nov 2 15:42:21.612: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.649433306s Nov 2 15:42:23.647: INFO: Pod "azuredisk-volume-tester-vhbv2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.683906742s [1mSTEP[0m: Saw pod success Nov 2 15:42:23.647: INFO: Pod "azuredisk-volume-tester-vhbv2" satisfied condition "Succeeded or Failed" Nov 2 15:42:23.647: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-vhbv2" Nov 2 15:42:23.695: INFO: Pod azuredisk-volume-tester-vhbv2 has the following logs: hello world [1mSTEP[0m: Deleting pod azuredisk-volume-tester-vhbv2 in namespace azuredisk-8081 [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV ... skipping 104 lines ... [1mSTEP[0m: setting up the PVC and PV [1mSTEP[0m: creating a PVC [1mSTEP[0m: setting up the pod [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod has 'FailedMount' event Nov 2 15:44:10.358: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-58hkm" Nov 2 15:44:10.404: INFO: Error getting logs for pod azuredisk-volume-tester-58hkm: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-58hkm) [1mSTEP[0m: Deleting pod azuredisk-volume-tester-58hkm in namespace azuredisk-5466 [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV Nov 2 15:44:10.507: INFO: deleting PVC "azuredisk-5466"/"pvc-xzs4r" Nov 2 15:44:10.507: INFO: Deleting PersistentVolumeClaim "pvc-xzs4r" [1mSTEP[0m: waiting for claim's PV "pvc-6b284846-e5a8-46aa-bdeb-dde22d2e6b96" to be deleted ... skipping 62 lines ... [1mSTEP[0m: setting up the StorageClass [1mSTEP[0m: creating a StorageClass [1mSTEP[0m: setting up the PVC and PV [1mSTEP[0m: creating a PVC [1mSTEP[0m: setting up the pod [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod's command exits with no error Nov 2 15:46:57.509: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bfn45" in namespace "azuredisk-2790" to be "Succeeded or Failed" Nov 2 15:46:57.540: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 31.100054ms Nov 2 15:46:59.573: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063787487s Nov 2 15:47:01.605: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096607483s Nov 2 15:47:03.638: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128876446s Nov 2 15:47:05.670: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160921967s Nov 2 15:47:07.702: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 10.193573381s ... skipping 9 lines ... Nov 2 15:47:28.034: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 30.524894482s Nov 2 15:47:30.067: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 32.557735918s Nov 2 15:47:32.100: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Pending", Reason="", readiness=false. Elapsed: 34.591629204s Nov 2 15:47:34.134: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Running", Reason="", readiness=false. Elapsed: 36.6255522s Nov 2 15:47:36.169: INFO: Pod "azuredisk-volume-tester-bfn45": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.660035912s [1mSTEP[0m: Saw pod success Nov 2 15:47:36.169: INFO: Pod "azuredisk-volume-tester-bfn45" satisfied condition "Succeeded or Failed" Nov 2 15:47:36.169: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-bfn45" Nov 2 15:47:36.218: INFO: Pod azuredisk-volume-tester-bfn45 has the following logs: e2e-test [1mSTEP[0m: Deleting pod azuredisk-volume-tester-bfn45 in namespace azuredisk-2790 [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV ... skipping 46 lines ... [1mSTEP[0m: setting up the StorageClass [1mSTEP[0m: creating a StorageClass [1mSTEP[0m: setting up the PVC and PV [1mSTEP[0m: creating a PVC [1mSTEP[0m: setting up the pod [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod's command exits with an error Nov 2 15:48:47.627: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pspbd" in namespace "azuredisk-5356" to be "Error status code" Nov 2 15:48:47.658: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 31.186894ms Nov 2 15:48:49.691: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064249645s Nov 2 15:48:51.724: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096906537s Nov 2 15:48:53.756: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.12871604s Nov 2 15:48:55.787: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.160643094s Nov 2 15:48:57.820: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.19338927s Nov 2 15:48:59.852: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.22555849s Nov 2 15:49:01.884: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.257307722s Nov 2 15:49:03.917: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.290607073s Nov 2 15:49:05.949: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.322619719s Nov 2 15:49:07.982: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 20.355024644s Nov 2 15:49:10.015: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 22.38802758s Nov 2 15:49:12.050: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Pending", Reason="", readiness=false. Elapsed: 24.422886635s Nov 2 15:49:14.083: INFO: Pod "azuredisk-volume-tester-pspbd": Phase="Failed", Reason="", readiness=false. Elapsed: 26.456224466s [1mSTEP[0m: Saw pod failure Nov 2 15:49:14.083: INFO: Pod "azuredisk-volume-tester-pspbd" satisfied condition "Error status code" [1mSTEP[0m: checking that pod logs contain expected message Nov 2 15:49:14.128: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-pspbd" Nov 2 15:49:14.162: INFO: Pod azuredisk-volume-tester-pspbd has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP[0m: Deleting pod azuredisk-volume-tester-pspbd in namespace azuredisk-5356 [1mSTEP[0m: validating provisioned PV ... skipping 408 lines ... [1mSTEP[0m: setting up the StorageClass [1mSTEP[0m: creating a StorageClass [1mSTEP[0m: setting up the PVC and PV [1mSTEP[0m: creating a PVC [1mSTEP[0m: setting up the pod [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod's command exits with no error Nov 2 16:00:14.397: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-94zph" in namespace "azuredisk-59" to be "Succeeded or Failed" Nov 2 16:00:14.433: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 36.793185ms Nov 2 16:00:16.465: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068784206s Nov 2 16:00:18.499: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10241907s Nov 2 16:00:20.533: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136834245s Nov 2 16:00:22.567: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170352128s Nov 2 16:00:24.603: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206173145s ... skipping 46 lines ... Nov 2 16:02:00.221: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 1m45.824041904s Nov 2 16:02:02.255: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 1m47.858062924s Nov 2 16:02:04.288: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 1m49.891456061s Nov 2 16:02:06.321: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 1m51.924828373s Nov 2 16:02:08.355: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 1m53.958448561s Nov 2 16:02:10.389: INFO: Pod "azuredisk-volume-tester-94zph": Phase="Pending", Reason="", readiness=false. Elapsed: 1m55.992253665s {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:168","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-11-02T16:02:12Z"} ++ early_exit_handler ++ '[' -n 162 ']' ++ kill -TERM 162 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 4 lines ...