{"tests":[{"name":"sysext.zfs.nfs","result":"FAIL","duration":1244063770582,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-103cc581f1): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/b4f7cb73-38ef-4263-8f2a-806d9a2a63e6\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T03:41:16.0079857+00:00\",\n  \"endTime\": \"2026-10-30T04:01:27.3229164+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-103cc581f1' 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\": \"b4f7cb73-38ef-4263-8f2a-806d9a2a63e6\"\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-103cc581f1 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-4757.2.3-n-103cc581f1 console\n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1245024702828,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-d4de4970b4): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/1a6b2cc6-83f0-4580-9994-6bf1b7c92084\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T03:41:15.81024+00:00\",\n  \"endTime\": \"2026-10-30T04:01:28.0403383+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-d4de4970b4' 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\": \"1a6b2cc6-83f0-4580-9994-6bf1b7c92084\"\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-d4de4970b4 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-4757.2.3-n-d4de4970b4 console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1245042650719,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-136baa2435): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/82fbfeb9-a1d5-4534-90cd-3a6e8a55d62b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T03:41:15.7890541+00:00\",\n  \"endTime\": \"2026-10-30T04:01:27.3020586+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4757.2.3-n-136baa2435' 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\": \"82fbfeb9-a1d5-4534-90cd-3a6e8a55d62b\"\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-136baa2435 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-136baa2435 console\n"}],"result":"FAIL","platform":"azure","version":"4757.2.3"}