### Test report for 4757.2.3+nightly-20261029-2100 / amd64 **Platforms tested** : azure 🟢 ok **azure.nvme-friendly-naming**; 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 (2); Failed: azure (1) ❌ not ok **cl.etcd-member.discovery**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-ce8871637b console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-01fd8cd062 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-51b44d2077 console_" L5: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-933c703005 console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-450b3453ee console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-c371123e8a console_" L5: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-6f904af47b console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-d4b8165f06 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-6adc6e1db2 console_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-056faebc0c console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-c6b267b5a3 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-eef2d09960 console_" L5: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-300c32808f console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-b6d32c3cb5 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-a96d4a213e console_" L5: " " ```
🟢 ok **cl.etcd-member.etcdctlv3**; Succeeded: azure (1) ❌ not ok **cl.etcd-member.v2-backup-restore**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **cl.flannel.udp**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-7220c651d9__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-ff8e678965__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-73c0536980__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-bc4701f42f__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-02ad97ddf5__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```
❌ not ok **cl.flannel.vxlan**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-3ac4e1fed8__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-7945bc1718__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-a9c69f5d23__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-762d526dc4__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4757.2.3-n-1588c732d9__ failed basic checks: some systemd units failed:" L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)" L3: "status: " L4: "journal:-- No entries --_" L5: " " ```
🟢 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) ❌ not ok **cl.locksmith.cluster**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-4cc4d8f671 console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-2167cfcbf5 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-83f6cfd48a console_" L5: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-cb2cc59f20 console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-71a8e6d6bb console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-ed632db18f console_" L5: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-b424b86b2c console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-01eaa24a53 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-25d8e6a1d0 console_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-29ae2a67b8 console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-455d79c6be console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-5f55f7cf34 console_" L5: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-122fdb491f console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-1b352e38ee console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-n-3fc2d051da console_" L5: " " ```
🟢 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 **extra-test.[V1].cl.internet**; Succeeded: azure (1) ❌ not ok **kubeadm.v1.35.1.calico.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.35.1.cilium.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.35.1.flannel.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.36.1.calico.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.36.1.cilium.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.36.1.flannel.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.37.0.calico.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.37.0.cilium.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.37.0.flannel.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
🟢 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-50d00700bb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/9d383d11-77b5-41ba-bcab-e08a46f61c44" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T03:06:53.1557211+00:00__," L8: "__endTime__: __2026-10-30T03:27:04.2394378+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-50d00700bb_ 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__: __9d383d11-77b5-41ba-bcab-e08a46f61c44__" 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-50d00700bb 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-50d00700bb console_" L19: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-3cb56cc3dd): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/a8c44f8d-4dfe-4932-82d1-49dce9eac0ed" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T02:46:38.872102+00:00__," L8: "__endTime__: __2026-10-30T03:02:14.0821267+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__: __a8c44f8d-4dfe-4932-82d1-49dce9eac0ed__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-50fe56cb49): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/57c3ab07-bca8-45ef-a045-be295f1c0c6e" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T02:21:37.1249379+00:00__," L8: "__endTime__: __2026-10-30T02:41:47.08716+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-50fe56cb49_ 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__: __57c3ab07-bca8-45ef-a045-be295f1c0c6e__" 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-50fe56cb49 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-50fe56cb49 console_" L19: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-de08a7bac6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/1374b30e-6f41-4dae-960b-46786bf0efe3" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T01:56:15.5059099+00:00__," L8: "__endTime__: __2026-10-30T02:16:26.7078702+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-de08a7bac6_ 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__: __1374b30e-6f41-4dae-960b-46786bf0efe3__" 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-de08a7bac6 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-de08a7bac6 console_" L19: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-bed7519534): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/5c9f460b-d197-44ab-bdd4-fae4ae473ac8" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T01:30:07.3087051+00:00__," L8: "__endTime__: __2026-10-30T01:50:16.9783138+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-bed7519534_ 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__: __5c9f460b-d197-44ab-bdd4-fae4ae473ac8__" 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-bed7519534 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-bed7519534 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-926e0cc513): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/ddf62530-937d-4093-b223-6c50d4b11222" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T03:06:53.189719+00:00__," L8: "__endTime__: __2026-10-30T03:27:04.1006296+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-926e0cc513_ 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__: __ddf62530-937d-4093-b223-6c50d4b11222__" 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-926e0cc513 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-926e0cc513 console_" L19: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-746b66138c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/53d1ec1f-4a3a-452a-900e-7ec11f39888d" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T02:46:38.7996459+00:00__," L8: "__endTime__: __2026-10-30T03:01:58.7833519+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__: __53d1ec1f-4a3a-452a-900e-7ec11f39888d__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-d2d33d957e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/26a1a35b-d025-498f-bc47-876682b18e10" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T02:21:34.7649419+00:00__," L8: "__endTime__: __2026-10-30T02:41:44.3916414+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-d2d33d957e_ 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__: __26a1a35b-d025-498f-bc47-876682b18e10__" 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-d2d33d957e 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-d2d33d957e console_" L19: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-b6da04bf45): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/0b056c74-c769-44c6-b83e-7883839a1e78" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T01:56:14.7337154+00:00__," L8: "__endTime__: __2026-10-30T02:16:23.7905566+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-b6da04bf45_ 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__: __0b056c74-c769-44c6-b83e-7883839a1e78__" 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-b6da04bf45 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-b6da04bf45 console_" L19: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-6a8059c715): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/fcda1b00-430c-458d-855b-fd74e4ee2af3" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T01:26:13.4600383+00:00__," L8: "__endTime__: __2026-10-30T01:46:22.0867075+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-6a8059c715_ 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__: __fcda1b00-430c-458d-855b-fd74e4ee2af3__" 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-6a8059c715 console" L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???S0.service?[0m - Serial Getty on ttyS0. ) on machine ci-4757.2.3-n-6a8059c715 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-58f2c5be50): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/8b33bc8b-bf01-433c-92d4-62ecf9d0185d" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T03:06:53.1713631+00:00__," L8: "__endTime__: __2026-10-30T03:27:02.7797791+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-58f2c5be50_ 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__: __8b33bc8b-bf01-433c-92d4-62ecf9d0185d__" 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-58f2c5be50 console" L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???S0.service?[0m - Serial Getty on ttyS0. ) on machine ci-4757.2.3-n-58f2c5be50 console_" L19: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-8c4f96f65e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/a954f45b-f085-43c4-b042-9605e408dd6e" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T02:46:39.7662714+00:00__," L8: "__endTime__: __2026-10-30T03:01:59.3156651+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__: __a954f45b-f085-43c4-b042-9605e408dd6e__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-a76df6c35f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/60e37b7f-50f2-4f72-8c8a-6a874cd9a4d0" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T02:21:35.0326517+00:00__," L8: "__endTime__: __2026-10-30T02:41:46.298008+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-a76df6c35f_ 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__: __60e37b7f-50f2-4f72-8c8a-6a874cd9a4d0__" 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-a76df6c35f 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-a76df6c35f console_" L19: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-9b0ba3f81a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/594728e1-0ce8-4a0c-b591-cbf077705fc2" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T01:56:15.4133327+00:00__," L8: "__endTime__: __2026-10-30T02:16:23.6253177+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-9b0ba3f81a_ 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__: __594728e1-0ce8-4a0c-b591-cbf077705fc2__" 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-9b0ba3f81a console" L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???S0.service?[0m - Serial Getty on ttyS0. ) on machine ci-4757.2.3-n-9b0ba3f81a console_" L19: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4757.2.3-n-b5c899fbca): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/northeurope/operations/bf3da081-3450-4d5b-8187-fd634c0c6ef9" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-30T01:31:26.3130821+00:00__," L8: "__endTime__: __2026-10-30T01:51:33.5598727+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4757.2.3-n-b5c899fbca_ 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__: __bf3da081-3450-4d5b-8187-fd634c0c6ef9__" 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-b5c899fbca 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-b5c899fbca console_" L19: " " ```
🟢 ok **systemd.journal.user**; Succeeded: azure (1) 🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)