{"tests":[{"name":"cl.flannel.udp","result":"FAIL","duration":82117664468,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4757.2.3-n-73c0536980\" 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.vxlan","result":"FAIL","duration":82883304659,"output":"        harness.go:699: Cluster failed starting machines: machine \"ci-4757.2.3-n-a9c69f5d23\" 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":301695972505,"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":301698243242,"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":301752095602,"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":301967601608,"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":302088281356,"output":"        discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1: \n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":302329497432,"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":302471663528,"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":302651302400,"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":303024770099,"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":303099592905,"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":303226434490,"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-6f904af47b 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-d4b8165f06 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-6adc6e1db2 console\n"},{"name":"cl.locksmith.cluster","result":"FAIL","duration":307446751852,"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-b424b86b2c 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-01eaa24a53 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-25d8e6a1d0 console\n"},{"name":"sysext.zfs.nfs","result":"FAIL","duration":1234186702924,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-d2d33d957e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/26a1a35b-d025-498f-bc47-876682b18e10\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T02:21:34.7649419+00:00\",\n  \"endTime\": \"2026-10-30T02:41:44.3916414+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-d2d33d957e' 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\": \"26a1a35b-d025-498f-bc47-876682b18e10\"\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-d2d33d957e 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-d2d33d957e console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1236285521723,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-a76df6c35f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/60e37b7f-50f2-4f72-8c8a-6a874cd9a4d0\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T02:21:35.0326517+00:00\",\n  \"endTime\": \"2026-10-30T02:41:46.298008+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-a76df6c35f' 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\": \"60e37b7f-50f2-4f72-8c8a-6a874cd9a4d0\"\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-a76df6c35f 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-a76df6c35f console\n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1238155344315,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-50fe56cb49): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/57c3ab07-bca8-45ef-a045-be295f1c0c6e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T02:21:37.1249379+00:00\",\n  \"endTime\": \"2026-10-30T02:41:47.08716+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-50fe56cb49' 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\": \"57c3ab07-bca8-45ef-a045-be295f1c0c6e\"\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-50fe56cb49 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-50fe56cb49 console\n"}],"result":"FAIL","platform":"azure","version":"4757.2.3"}