{"tests":[{"name":"cl.flannel.vxlan","result":"FAIL","duration":92740914492,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4757.2.3-n-3ac4e1fed8\" 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.flannel.udp","result":"FAIL","duration":92811818507,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4757.2.3-n-7220c651d9\" 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.36.1.flannel.base","result":"FAIL","duration":312772387409,"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":313049039241,"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":313112276483,"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.cilium.base","result":"FAIL","duration":313228827263,"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.calico.base","result":"FAIL","duration":313270189821,"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.flannel.base","result":"FAIL","duration":313290798424,"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":313330699039,"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":313356853728,"output":"        discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":313785805313,"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.discovery","result":"FAIL","duration":314363325862,"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-ce8871637b 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-01fd8cd062 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-51b44d2077 console\n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"FAIL","duration":315232529806,"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":324398559197,"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-4cc4d8f671 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-2167cfcbf5 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-83f6cfd48a console\n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1232307334508,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-50d00700bb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/9d383d11-77b5-41ba-bcab-e08a46f61c44\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T03:06:53.1557211+00:00\",\n  \"endTime\": \"2026-10-30T03:27:04.2394378+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-50d00700bb' 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\": \"9d383d11-77b5-41ba-bcab-e08a46f61c44\"\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-50d00700bb 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-50d00700bb console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1232352162283,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-58f2c5be50): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/8b33bc8b-bf01-433c-92d4-62ecf9d0185d\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T03:06:53.1713631+00:00\",\n  \"endTime\": \"2026-10-30T03:27:02.7797791+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-58f2c5be50' 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\": \"8b33bc8b-bf01-433c-92d4-62ecf9d0185d\"\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-58f2c5be50 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-58f2c5be50 console\n"},{"name":"sysext.zfs.nfs","result":"FAIL","duration":1233884119467,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-926e0cc513): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/ddf62530-937d-4093-b223-6c50d4b11222\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T03:06:53.189719+00:00\",\n  \"endTime\": \"2026-10-30T03:27:04.1006296+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-926e0cc513' 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\": \"ddf62530-937d-4093-b223-6c50d4b11222\"\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-926e0cc513 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-926e0cc513 console\n"}],"result":"FAIL","platform":"azure","version":"4757.2.3"}