{"tests":[{"name":"cl.flannel.vxlan","result":"FAIL","duration":135361890795,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4869.0.0-n-98dd184d9f\" 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-27fa1f3e83 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-27fa1f3e83 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-98dd184d9f 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-98dd184d9f 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-6447d879cd 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-6447d879cd console\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":373940095393,"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":374025770670,"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":382619265653,"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":382704527166,"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":383007952442,"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":385015839238,"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":385432252156,"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":385870403720,"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":386146529752,"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":386663513247,"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":386757091441,"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-025c71dcab 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-ac03d9918b 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-2cd84865c4 console\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":388184191113,"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-5258460015 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-97ad676fad 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-c7def43fa8 console\n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1228837933664,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-66383e047c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/8337f984-cc12-4f35-a5d1-417c2b3f0ddc\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-31T09:32:07.9929613+00:00\",\n  \"endTime\": \"2026-10-31T09:52:19.2764806+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4869.0.0-n-66383e047c' 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\": \"8337f984-cc12-4f35-a5d1-417c2b3f0ddc\"\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-66383e047c 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-66383e047c console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1245048496023,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-c998bc2f7a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/5d72bfa6-8d91-47bd-ba3b-dd7f105c6a85\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-31T09:32:08.3748557+00:00\",\n  \"endTime\": \"2026-10-31T09:52:22.0261106+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4869.0.0-n-c998bc2f7a' 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\": \"5d72bfa6-8d91-47bd-ba3b-dd7f105c6a85\"\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-c998bc2f7a 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-c998bc2f7a console\n"},{"name":"sysext.zfs.nfs","result":"FAIL","duration":1245186991311,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-02ca0c8c89): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/10b364d4-c428-4b83-ab16-465a90356073\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-31T09:32:07.1450659+00:00\",\n  \"endTime\": \"2026-10-31T09:52:18.5130783+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4869.0.0-n-02ca0c8c89' 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\": \"10b364d4-c428-4b83-ab16-465a90356073\"\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-02ca0c8c89 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-02ca0c8c89 console\n"}],"result":"FAIL","platform":"azure","version":"4869.0.0"}