### Test report for 4865.0.0+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 (2); Failed: azure (1)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 1</summary>

  ```
      L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4865.0.0-n-b3f89de5c7__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: __starting__, stderr: ____, err: Process exited with status 1, systemctl list-jobs returned stdout: __JOB  UNIT                TYPE  STATE_n858  multi-user.target?   start waiting_n1024 etcd-member.service start running_n_n2 jobs listed.__, stderr: ____, err: <nil_"
      L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4865.0.0-n-78544babe5 console_"
      L3: " "
  ```


</details>


🟢 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 (2); Failed: azure (1)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_"
      L2: " "
  ```


</details>


🟢 ok **kubeadm.v1.37.0.cilium.base**; Succeeded: azure (1)

🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: azure (2); Failed: azure (1)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_"
      L2: " "
  ```


</details>


🟢 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)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 5</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-cbf7456729): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/5c1d1292-a7ef-4e75-b70c-4afbbfac8418"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OperationPreempted"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T07:01:25.9869484+00:00__,"
      L8: "__endTime__: __2026-10-30T07:02:11.5089682+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__: __5c1d1292-a7ef-4e75-b70c-4afbbfac8418__"
      L15: "}"
      L16: "--------------------------------------------------------------------------------_"
      L17: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 4</summary>

  ```
      L1: " Error: _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"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T06:36:20.9167193+00:00__,"
      L8: "__endTime__: __2026-10-30T06:56:32.4143118+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__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, 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__: __15653f8b-ef4f-46c6-a990-d70b26b0ab5f__"
      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-4865.0.0-n-5099983f8c 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-4865.0.0-n-5099983f8c console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 3</summary>

  ```
      L1: " Error: _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"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T06:11:11.9820451+00:00__,"
      L8: "__endTime__: __2026-10-30T06:31:24.0960925+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__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, 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__: __6509a6fb-e550-4a9a-94c8-f02d68e92c07__"
      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-4865.0.0-n-8226487179 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-4865.0.0-n-8226487179 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 2</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-4549bddca7): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/e532331c-f7e4-4b32-b7b2-f92ecf01f634"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T05:46:11.4499346+00:00__,"
      L8: "__endTime__: __2026-10-30T06:06:23.2513958+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__message__: __OS Provisioning for VM _ci-4865.0.0-n-4549bddca7_ 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__: __e532331c-f7e4-4b32-b7b2-f92ecf01f634__"
      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-4865.0.0-n-4549bddca7 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-4865.0.0-n-4549bddca7 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 1</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-e697abf492): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/0083451b-b950-41e7-a63c-b3c0903c23f9"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T05:10:46.5314487+00:00__,"
      L8: "__endTime__: __2026-10-30T05:30:57.2222308+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__message__: __OS Provisioning for VM _ci-4865.0.0-n-e697abf492_ 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__: __0083451b-b950-41e7-a63c-b3c0903c23f9__"
      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-4865.0.0-n-e697abf492 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-4865.0.0-n-e697abf492 console_"
      L19: " "
  ```


</details>


❌ not ok **sysext.zfs.nfs**; Failed: azure (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 5</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-03b39ca7fe): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/8f370622-01b8-4a2a-a658-f1f8ca0d3227"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OperationPreempted"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T07:01:26.7628981+00:00__,"
      L8: "__endTime__: __2026-10-30T07:02:12.0715475+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__: __8f370622-01b8-4a2a-a658-f1f8ca0d3227__"
      L15: "}"
      L16: "--------------------------------------------------------------------------------_"
      L17: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 4</summary>

  ```
      L1: " Error: _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"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T06:36:21.0733596+00:00__,"
      L8: "__endTime__: __2026-10-30T06:56:34.0007738+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__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, 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__: __b369cc2c-fb6f-47b4-b4c3-9d35d9b5d014__"
      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-4865.0.0-n-2d22167679 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-4865.0.0-n-2d22167679 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 3</summary>

  ```
      L1: " Error: _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"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T06:11:11.6146923+00:00__,"
      L8: "__endTime__: __2026-10-30T06:31:23.067627+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__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, 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__: __63f41d84-2c73-4a31-9d3f-98de4aa3cfdc__"
      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-4865.0.0-n-6c455fa03d 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-4865.0.0-n-6c455fa03d console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 2</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-ef8ca6e3f5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/7fbe3239-6288-432e-a742-59cbdf91ab32"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T05:46:11.6609844+00:00__,"
      L8: "__endTime__: __2026-10-30T06:06:23.2410562+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__message__: __OS Provisioning for VM _ci-4865.0.0-n-ef8ca6e3f5_ 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__: __7fbe3239-6288-432e-a742-59cbdf91ab32__"
      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-4865.0.0-n-ef8ca6e3f5 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-4865.0.0-n-ef8ca6e3f5 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 1</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-70593e549b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/344832d6-fd45-4ba7-aaf4-65d42b0bb355"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T05:21:06.1110448+00:00__,"
      L8: "__endTime__: __2026-10-30T05:41:18.060545+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__message__: __OS Provisioning for VM _ci-4865.0.0-n-70593e549b_ 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__: __344832d6-fd45-4ba7-aaf4-65d42b0bb355__"
      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-4865.0.0-n-70593e549b 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-4865.0.0-n-70593e549b console_"
      L19: " "
  ```


</details>


❌ not ok **sysext.zfs.reboot**; Failed: azure (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 5</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-af5307557a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/c2cd6243-c4d9-42dc-9af2-698642573f80"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OperationPreempted"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T07:01:25.8316219+00:00__,"
      L8: "__endTime__: __2026-10-30T07:02:11.5089682+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__: __c2cd6243-c4d9-42dc-9af2-698642573f80__"
      L15: "}"
      L16: "--------------------------------------------------------------------------------_"
      L17: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 4</summary>

  ```
      L1: " Error: _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"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T06:36:20.8331606+00:00__,"
      L8: "__endTime__: __2026-10-30T06:56:32.4312024+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__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, 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__: __bef0e4a0-e304-4976-87fb-3b66300820c8__"
      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-4865.0.0-n-55fb5c08d6 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-4865.0.0-n-55fb5c08d6 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 3</summary>

  ```
      L1: " Error: _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"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T06:11:12.1495998+00:00__,"
      L8: "__endTime__: __2026-10-30T06:31:24.1012963+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__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, 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__: __17d95f64-50ad-418c-9f8d-ce2423685de6__"
      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-4865.0.0-n-0d92ce4df6 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-4865.0.0-n-0d92ce4df6 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 2</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-a46b13d5a5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/cdb874e2-2e11-42c5-80dd-e261e6e2be08"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T05:46:10.6337886+00:00__,"
      L8: "__endTime__: __2026-10-30T06:06:22.9798284+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__message__: __OS Provisioning for VM _ci-4865.0.0-n-a46b13d5a5_ 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__: __cdb874e2-2e11-42c5-80dd-e261e6e2be08__"
      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-4865.0.0-n-a46b13d5a5 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-4865.0.0-n-a46b13d5a5 console_"
      L19: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for azure, run 1</summary>

  ```
      L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4865.0.0-n-43a6c71054): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/031a76ff-8e93-4f73-9178-6a563aa2bd19"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OSProvisioningTimedOut"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-30T05:13:07.2191772+00:00__,"
      L8: "__endTime__: __2026-10-30T05:33:21.2446427+00:00__,"
      L9: "__status__: __Failed__,"
      L10: "__error__: {"
      L11: "__code__: __OSProvisioningTimedOut__,"
      L12: "__message__: __OS Provisioning for VM _ci-4865.0.0-n-43a6c71054_ 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__: __031a76ff-8e93-4f73-9178-6a563aa2bd19__"
      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-4865.0.0-n-43a6c71054 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-4865.0.0-n-43a6c71054 console_"
      L19: " "
  ```


</details>


🟢 ok **systemd.journal.user**; Succeeded: azure (1)

🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)
