{"tests":[{"name":"sysext.zfs.docker","result":"FAIL","duration":1243888114923,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-5099983f8c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/15653f8b-ef4f-46c6-a990-d70b26b0ab5f\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T06:36:20.9167193+00:00\",\n  \"endTime\": \"2026-10-30T06:56:32.4143118+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4865.0.0-n-5099983f8c' 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\": \"15653f8b-ef4f-46c6-a990-d70b26b0ab5f\"\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-4865.0.0-n-5099983f8c 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-4865.0.0-n-5099983f8c console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1244208810083,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-55fb5c08d6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/bef0e4a0-e304-4976-87fb-3b66300820c8\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T06:36:20.8331606+00:00\",\n  \"endTime\": \"2026-10-30T06:56:32.4312024+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4865.0.0-n-55fb5c08d6' 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\": \"bef0e4a0-e304-4976-87fb-3b66300820c8\"\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-4865.0.0-n-55fb5c08d6 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-4865.0.0-n-55fb5c08d6 console\n"},{"name":"sysext.zfs.nfs","result":"FAIL","duration":1244413066826,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-2d22167679): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/b369cc2c-fb6f-47b4-b4c3-9d35d9b5d014\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T06:36:21.0733596+00:00\",\n  \"endTime\": \"2026-10-30T06:56:34.0007738+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4865.0.0-n-2d22167679' 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\": \"b369cc2c-fb6f-47b4-b4c3-9d35d9b5d014\"\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-4865.0.0-n-2d22167679 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-4865.0.0-n-2d22167679 console\n"}],"result":"FAIL","platform":"azure","version":"4865.0.0"}