{"tests":[{"name":"sysext.zfs.docker","result":"FAIL","duration":1243529597549,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4820.1.1-n-cd41b170c8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/fd0e8189-3818-47a9-a713-7ed246d3a8ec\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T02:29:57.1987543+00:00\",\n  \"endTime\": \"2026-10-30T02:50:08.7378744+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4820.1.1-n-cd41b170c8' 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\": \"fd0e8189-3818-47a9-a713-7ed246d3a8ec\"\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-4820.1.1-n-cd41b170c8 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-4820.1.1-n-cd41b170c8 console\n"},{"name":"sysext.zfs.nfs","result":"FAIL","duration":1243533570622,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4820.1.1-n-d59735e5a5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/2b793c68-d1fe-46cf-a1f2-bcf9a81278e2\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T02:29:57.6574999+00:00\",\n  \"endTime\": \"2026-10-30T02:50:08.7378744+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4820.1.1-n-d59735e5a5' 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\": \"2b793c68-d1fe-46cf-a1f2-bcf9a81278e2\"\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-4820.1.1-n-d59735e5a5 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-4820.1.1-n-d59735e5a5 console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1246223082486,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4820.1.1-n-e1eebe00b5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/e53d7be8-7612-4e12-964e-91fa9750b74c\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T02:29:56.8534403+00:00\",\n  \"endTime\": \"2026-10-30T02:50:09.6936667+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4820.1.1-n-e1eebe00b5' 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\": \"e53d7be8-7612-4e12-964e-91fa9750b74c\"\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-4820.1.1-n-e1eebe00b5 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-4820.1.1-n-e1eebe00b5 console\n"}],"result":"FAIL","platform":"azure","version":"4820.1.1"}