{"tests":[{"name":"sysext.zfs.nfs","result":"FAIL","duration":1245326408997,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-6c455fa03d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/63f41d84-2c73-4a31-9d3f-98de4aa3cfdc\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T06:11:11.6146923+00:00\",\n  \"endTime\": \"2026-10-30T06:31:23.067627+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4865.0.0-n-6c455fa03d' 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\": \"63f41d84-2c73-4a31-9d3f-98de4aa3cfdc\"\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-6c455fa03d 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-6c455fa03d console\n"},{"name":"sysext.zfs.reboot","result":"FAIL","duration":1245588612293,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-0d92ce4df6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/17d95f64-50ad-418c-9f8d-ce2423685de6\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T06:11:12.1495998+00:00\",\n  \"endTime\": \"2026-10-30T06:31:24.1012963+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4865.0.0-n-0d92ce4df6' 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\": \"17d95f64-50ad-418c-9f8d-ce2423685de6\"\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-0d92ce4df6 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-0d92ce4df6 console\n"},{"name":"sysext.zfs.docker","result":"FAIL","duration":1245782244678,"output":"        zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-8226487179): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/6509a6fb-e550-4a9a-94c8-f02d68e92c07\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OSProvisioningTimedOut\n--------------------------------------------------------------------------------\n{\n  \"startTime\": \"2026-10-30T06:11:11.9820451+00:00\",\n  \"endTime\": \"2026-10-30T06:31:24.0960925+00:00\",\n  \"status\": \"Failed\",\n  \"error\": {\n    \"code\": \"OSProvisioningTimedOut\",\n    \"message\": \"OS Provisioning for VM 'ci-4865.0.0-n-8226487179' 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\": \"6509a6fb-e550-4a9a-94c8-f02d68e92c07\"\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-8226487179 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-8226487179 console\n"}],"result":"FAIL","platform":"azure","version":"4865.0.0"}