{"tests":[{"name":"cl.flannel.vxlan","result":"FAIL","duration":146699354104,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4869.0.0-n-dc0c9d3651\" 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        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-4869.0.0-n-dc0c9d3651 console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39mflannel-dock…\u001b[0mers (System Application Container).\r\r) on machine ci-4869.0.0-n-dc0c9d3651 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-4869.0.0-n-3100c4d69d console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39mflannel-dock…\u001b[0mers (System Application Container).\r\r) on machine ci-4869.0.0-n-3100c4d69d 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-4869.0.0-n-edd0a903ab console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39mflannel-dock…\u001b[0mers (System Application Container).\r\r) on machine ci-4869.0.0-n-edd0a903ab console\n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":372819919388,"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":372925036934,"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":373069995515,"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":373460230689,"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":382108605639,"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":382297517280,"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":384110818331,"output":"        discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1: \n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":385844283361,"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-4869.0.0-n-9582e47b1a 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-4869.0.0-n-6820e91e20 console\n"},{"name":"cl.locksmith.cluster","result":"FAIL","duration":386424135929,"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-4869.0.0-n-c8e9ba688f 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-4869.0.0-n-34f87ffe4e 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-4869.0.0-n-383bc12edc console\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":395180055194,"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":397205226893,"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":397818594376,"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.nfs","result":"FAIL","duration":1221986500123,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-2d2bc8c95d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/bbfffff8-b767-4dc3-b6b1-e3ff831446e1\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-31T09:06:54.2641956+00:00\",\n  \"endTime\": \"2026-10-31T09:27:05.3735414+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4869.0.0-n-2d2bc8c95d' 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\": \"bbfffff8-b767-4dc3-b6b1-e3ff831446e1\"\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-4869.0.0-n-2d2bc8c95d 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-4869.0.0-n-2d2bc8c95d console\n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1222799215192,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-5216cb6822): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/dde91353-d744-4fec-bf20-cd1511a85f66\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-31T09:06:54.0819356+00:00\",\n  \"endTime\": \"2026-10-31T09:27:05.8591784+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4869.0.0-n-5216cb6822' 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\": \"dde91353-d744-4fec-bf20-cd1511a85f66\"\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-4869.0.0-n-5216cb6822 console\n        harness.go:669: Found systemd dependency unit failed to start (\u001b[0;1;39mserial-getty….service\u001b[0m - Serial Getty on ttyAMA0.\r\r) on machine ci-4869.0.0-n-5216cb6822 console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1243314729356,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-f1cf1ec453): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/655a5557-99d1-436e-825c-b066e6fe4454\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-31T09:06:54.7243135+00:00\",\n  \"endTime\": \"2026-10-31T09:27:05.7539921+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4869.0.0-n-f1cf1ec453' 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\": \"655a5557-99d1-436e-825c-b066e6fe4454\"\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-4869.0.0-n-f1cf1ec453 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-4869.0.0-n-f1cf1ec453 console\n"}],"result":"FAIL","platform":"azure","version":"4869.0.0"}