{"tests":[{"name":"cl.flannel.udp","result":"FAIL","duration":82102592625,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4757.2.3-n-bc4701f42f\" failed basic checks: some systemd units failed:\n● flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)\nstatus: \njournal:-- No entries --\n"},{"name":"cl.cloudinit.script","result":"PASS","duration":83672055859,"output":""},{"name":"cl.flannel.vxlan","result":"FAIL","duration":84075525161,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4757.2.3-n-762d526dc4\" failed basic checks: some systemd units failed:\n● flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)\nstatus: \njournal:-- No entries --\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":302035188964,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":302453477950,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":302689133161,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":302745047182,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"cl.etcd-member.v2-backup-restore","result":"FAIL","duration":302808318395,"output":"        discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":302961019924,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.37.0.cilium.base","result":"FAIL","duration":303000083533,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":303407294722,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"cl.locksmith.cluster","result":"FAIL","duration":304070952403,"output":"        locksmith.go:151: cluster health: health polling failed: Process exited with status 1: \n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39metcd-member.servic…\u001b[0mtcd (System Application Container).\r\r) on machine ci-4757.2.3-n-29ae2a67b8 console\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39metcd-member.servic…\u001b[0mtcd (System Application Container).\r\r) on machine ci-4757.2.3-n-455d79c6be console\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39metcd-member.servic…\u001b[0mtcd (System Application Container).\r\r) on machine ci-4757.2.3-n-5f55f7cf34 console\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":305973501672,"output":"        discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: \n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39metcd-member.servic…\u001b[0mtcd (System Application Container).\r\r) on machine ci-4757.2.3-n-056faebc0c console\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39metcd-member.servic…\u001b[0mtcd (System Application Container).\r\r) on machine ci-4757.2.3-n-c6b267b5a3 console\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39metcd-member.servic…\u001b[0mtcd (System Application Container).\r\r) on machine ci-4757.2.3-n-eef2d09960 console\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":313594800391,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"FAIL","duration":323076649416,"output":"        kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1: \n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1233402897255,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-de08a7bac6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/1374b30e-6f41-4dae-960b-46786bf0efe3\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T01:56:15.5059099+00:00\",\n  \"endTime\": \"2026-10-30T02:16:26.7078702+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-de08a7bac6' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\\r\\n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image\\r\\n * Instructions for Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic\\r\\n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same.\"\n  },\n  \"name\": \"1374b30e-6f41-4dae-960b-46786bf0efe3\"\n}\n--------------------------------------------------------------------------------\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39msystemd-udev-settl…\u001b[0m To Complete Device Initialization.\r\r) on machine ci-4757.2.3-n-de08a7bac6 console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39msystemd-fsck…\u001b[0mem Check on /dev/disk/by-label/OEM.\r\r) on machine ci-4757.2.3-n-de08a7bac6 console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1234151207624,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-9b0ba3f81a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/594728e1-0ce8-4a0c-b591-cbf077705fc2\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T01:56:15.4133327+00:00\",\n  \"endTime\": \"2026-10-30T02:16:23.6253177+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-9b0ba3f81a' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\\r\\n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image\\r\\n * Instructions for Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic\\r\\n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same.\"\n  },\n  \"name\": \"594728e1-0ce8-4a0c-b591-cbf077705fc2\"\n}\n--------------------------------------------------------------------------------\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39msystemd-udev-settl…\u001b[0m To Complete Device Initialization.\r\r) on machine ci-4757.2.3-n-9b0ba3f81a console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39mserial-getty…S0.service\u001b[0m - Serial Getty on ttyS0.\r\r) on machine ci-4757.2.3-n-9b0ba3f81a console\n"},{"name":"sysext.zfs.nfs","result":"FAIL","duration":1234959564717,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-b6da04bf45): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/0b056c74-c769-44c6-b83e-7883839a1e78\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T01:56:14.7337154+00:00\",\n  \"endTime\": \"2026-10-30T02:16:23.7905566+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-b6da04bf45' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\\r\\n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image\\r\\n * Instructions for Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic\\r\\n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same.\"\n  },\n  \"name\": \"0b056c74-c769-44c6-b83e-7883839a1e78\"\n}\n--------------------------------------------------------------------------------\n        harness.go:669: Found systemd unit failed to start (\u001b[0;1;39msystemd-udev-settl…\u001b[0m To Complete Device Initialization.\r\r) on machine ci-4757.2.3-n-b6da04bf45 console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39msystemd-fsck…\u001b[0mem Check on /dev/disk/by-label/OEM.\r\r) on machine ci-4757.2.3-n-b6da04bf45 console\n"}],"result":"FAIL","platform":"azure","version":"4757.2.3"}