### Test report for 4757.2.3+nightly-20261029-2100 / arm64
**Platforms tested** : azure
🟢 ok **azure.nvme-friendly-naming # SKIP**; Succeeded: azure (1)
🟢 ok **bpf.ig**; Succeeded: azure (1)
🟢 ok **cl.basic**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.basic**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.multipart-mime**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.script**; Succeeded: azure (1)
🟢 ok **cl.etcd-member.discovery**; Succeeded: azure (1)
🟢 ok **cl.etcd-member.etcdctlv3**; Succeeded: azure (1)
🟢 ok **cl.etcd-member.v2-backup-restore**; Succeeded: azure (1)
🟢 ok **cl.flannel.vxlan**; Succeeded: azure (1)
🟢 ok **cl.ignition.kargs**; Succeeded: azure (1)
🟢 ok **cl.ignition.luks**; Succeeded: azure (1)
🟢 ok **cl.ignition.misc.empty**; Succeeded: azure (1)
🟢 ok **cl.ignition.symlink**; Succeeded: azure (1)
🟢 ok **cl.ignition.translation**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.btrfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.ext4root**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.groups**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.once**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.ext4root**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.ext4checkexisting**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.swap**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.vfat**; Succeeded: azure (1)
🟢 ok **cl.internet**; Succeeded: azure (1)
🟢 ok **cl.locksmith.cluster**; Succeeded: azure (1)
🟢 ok **cl.metadata.azure**; Succeeded: azure (1)
🟢 ok **cl.network.initramfs.second-boot**; Succeeded: azure (1)
🟢 ok **cl.network.iptables**; Succeeded: azure (1)
🟢 ok **cl.network.nftables**; Succeeded: azure (1)
🟢 ok **cl.network.wireguard**; Succeeded: azure (1)
🟢 ok **cl.osreset.ignition-rerun**; Succeeded: azure (1)
🟢 ok **cl.overlay.cleanup**; Succeeded: azure (1)
🟢 ok **cl.swap_activation**; Succeeded: azure (1)
🟢 ok **cl.toolbox.dnf-install**; Succeeded: azure (1)
🟢 ok **cl.update.badverity**; Succeeded: azure (1)
🟢 ok **cl.update.reboot**; Succeeded: azure (1)
🟢 ok **cl.users.shells**; Succeeded: azure (1)
🟢 ok **cl.verity**; Succeeded: azure (1)
🟢 ok **coreos.auth.verify**; Succeeded: azure (1)
🟢 ok **coreos.ignition.groups**; Succeeded: azure (1)
🟢 ok **coreos.ignition.once**; Succeeded: azure (1)
🟢 ok **coreos.ignition.resource.local**; Succeeded: azure (1)
🟢 ok **coreos.ignition.resource.remote**; Succeeded: azure (1)
🟢 ok **coreos.ignition.security.tls**; Succeeded: azure (1)
🟢 ok **coreos.ignition.ssh.key**; Succeeded: azure (1)
🟢 ok **coreos.ignition.systemd.enable-service**; Succeeded: azure (1)
🟢 ok **coreos.locksmith.reboot**; Succeeded: azure (1)
🟢 ok **coreos.locksmith.tls**; Succeeded: azure (1)
🟢 ok **coreos.selinux.boolean**; Succeeded: azure (1)
🟢 ok **coreos.selinux.enforce**; Succeeded: azure (1)
🟢 ok **coreos.tls.fetch-urls**; Succeeded: azure (1)
🟢 ok **coreos.update.badusr**; Succeeded: azure (1)
🟢 ok **docker.base**; Succeeded: azure (1)
🟢 ok **docker.btrfs-storage**; Succeeded: azure (1)
🟢 ok **docker.containerd-restart**; Succeeded: azure (1)
🟢 ok **docker.enable-service.sysext**; Succeeded: azure (1)
🟢 ok **docker.lib-coreos-dockerd-compat**; Succeeded: azure (1)
🟢 ok **docker.network-openbsd-nc**; Succeeded: azure (1)
🟢 ok **docker.selinux**; Succeeded: azure (1)
🟢 ok **docker.userns**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.37.0.calico.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.37.0.cilium.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: azure (1)
🟢 ok **podman.base**; Succeeded: azure (1)
🟢 ok **podman.network-single**; Succeeded: azure (1)
🟢 ok **podman.workflow**; Succeeded: azure (1)
🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (1)
🟢 ok **sysext.disable-containerd**; Succeeded: azure (1)
🟢 ok **sysext.disable-docker**; Succeeded: azure (1)
🟢 ok **sysext.simple**; Succeeded: azure (1)
❌ not ok **sysext.zfs.docker**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-914b8f0bf5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/4da25a64-c4b7-4f3b-8e4e-84db1e91543b"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:56:55.0879314+00:00__,"
L8: "__endTime__: __2026-10-30T05:02:20.5714156+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __4da25a64-c4b7-4f3b-8e4e-84db1e91543b__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 4
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-0723d41df3): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/bf7302d3-b0d9-4098-869d-6d3ca62996fe"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:31:35.1214318+00:00__,"
L8: "__endTime__: __2026-10-30T04:51:46.21522+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-0723d41df3_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __bf7302d3-b0d9-4098-869d-6d3ca62996fe__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-0723d41df3 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-0723d41df3 console_"
L19: " "
```
Diagnostic output for azure, run 3
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-7f5ced68e6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/3b6c7b79-04c2-4f01-a216-f8eef2da7c2e"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:06:29.6827345+00:00__,"
L8: "__endTime__: __2026-10-30T04:26:41.4426478+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-7f5ced68e6_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __3b6c7b79-04c2-4f01-a216-f8eef2da7c2e__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-7f5ced68e6 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-7f5ced68e6 console_"
L19: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _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"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T03:41:15.81024+00:00__,"
L8: "__endTime__: __2026-10-30T04:01:28.0403383+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__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, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __1a6b2cc6-83f0-4580-9994-6bf1b7c92084__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-d4de4970b4 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4757.2.3-n-d4de4970b4 console_"
L19: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-af6a64eb36): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/0aa68ad9-9e90-451a-8567-99451997377a"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T03:10:50.3348044+00:00__,"
L8: "__endTime__: __2026-10-30T03:31:03.3214528+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-af6a64eb36_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __0aa68ad9-9e90-451a-8567-99451997377a__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-af6a64eb36 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-af6a64eb36 console_"
L19: " "
```
❌ not ok **sysext.zfs.nfs**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-c90443855e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/dc8f7d32-2893-4415-8708-edc89808a1db"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:56:55.1420767+00:00__,"
L8: "__endTime__: __2026-10-30T05:02:13.8722767+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __dc8f7d32-2893-4415-8708-edc89808a1db__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 4
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-ed4bb4dfb4): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/0fc6f073-aca5-4c58-9215-608c6af33d5c"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:31:35.5345939+00:00__,"
L8: "__endTime__: __2026-10-30T04:51:47.8753647+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-ed4bb4dfb4_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __0fc6f073-aca5-4c58-9215-608c6af33d5c__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-ed4bb4dfb4 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-ed4bb4dfb4 console_"
L19: " "
```
Diagnostic output for azure, run 3
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-225fa35447): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/e9718b58-3767-4a81-84bc-2d17c42f6081"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:06:30.5185593+00:00__,"
L8: "__endTime__: __2026-10-30T04:26:42.4600292+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-225fa35447_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __e9718b58-3767-4a81-84bc-2d17c42f6081__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-225fa35447 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-225fa35447 console_"
L19: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _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"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T03:41:16.0079857+00:00__,"
L8: "__endTime__: __2026-10-30T04:01:27.3229164+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__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, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __b4f7cb73-38ef-4263-8f2a-806d9a2a63e6__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-103cc581f1 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4757.2.3-n-103cc581f1 console_"
L19: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-0aa6a2c256): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/0190abac-2c37-42a9-bfa4-ea10f6e327fb"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T03:15:55.9518316+00:00__,"
L8: "__endTime__: __2026-10-30T03:36:08.3891965+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-0aa6a2c256_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __0190abac-2c37-42a9-bfa4-ea10f6e327fb__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-0aa6a2c256 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-0aa6a2c256 console_"
L19: " "
```
❌ not ok **sysext.zfs.reboot**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-5c553d9959): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/afd0f7f1-b5f2-4d0e-85ee-c186b90e577b"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:56:55.2035704+00:00__,"
L8: "__endTime__: __2026-10-30T05:02:13.7294694+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __afd0f7f1-b5f2-4d0e-85ee-c186b90e577b__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 4
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-24e1c28ba6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/07a59b82-f7c5-4a00-b7f8-37361f516166"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:31:38.5420807+00:00__,"
L8: "__endTime__: __2026-10-30T04:51:49.158374+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-24e1c28ba6_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __07a59b82-f7c5-4a00-b7f8-37361f516166__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-24e1c28ba6 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-24e1c28ba6 console_"
L19: " "
```
Diagnostic output for azure, run 3
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-c114d84a44): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/8a81237f-fe27-4296-9951-dbcb911b45c4"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T04:06:30.0505191+00:00__,"
L8: "__endTime__: __2026-10-30T04:26:44.5004665+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-c114d84a44_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __8a81237f-fe27-4296-9951-dbcb911b45c4__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-c114d84a44 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4757.2.3-n-c114d84a44 console_"
L19: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _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"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T03:41:15.7890541+00:00__,"
L8: "__endTime__: __2026-10-30T04:01:27.3020586+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__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, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __82fbfeb9-a1d5-4534-90cd-3a6e8a55d62b__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-136baa2435 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-136baa2435 console_"
L19: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-143c4ac1b7): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/d234eb14-7db8-4cc9-bd28-e54118e3b2ef"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T03:11:23.4561996+00:00__,"
L8: "__endTime__: __2026-10-30T03:31:35.5785974+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-143c4ac1b7_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke 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 f?or 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 sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __d234eb14-7db8-4cc9-bd28-e54118e3b2ef__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4757.2.3-n-143c4ac1b7 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4757.2.3-n-143c4ac1b7 console_"
L19: " "
```
🟢 ok **systemd.journal.user**; Succeeded: azure (1)
🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)