### Test report for 4869.0.0+nightly-20261030-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) ❌ 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: dial tcp 20.69.108.145:22: i/o timeout:_" L2: " " ```                 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-4869.0.0-n-5258460015 console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-97ad676fad console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-c7def43fa8 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-4869.0.0-n-9582e47b1a console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-6820e91e20 console_" L4: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd22f9bb?/providers/Microsoft.Network/networkInterfaces/nic-e10553d17d" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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-4869.0.0-n-cec26a4fbd console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-09e92c0894 console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-d9687f4b2f 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: dial tcp 20.3.102.143:22: i/o timeout:_" 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: _harness.go:699: Cluster failed starting machines: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd22f9bb?/providers/Microsoft.Network/networkInterfaces/nic-6a29165924" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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.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-4869.0.0-n-59bf36c64a__ 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-4869.0.0-n-98dd184d9f__ 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: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-27fa1f3e83 console" L6: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-27fa1f3e83 console" L7: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-98dd184d9f console" L8: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-98dd184d9f console" L9: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-6447d879cd console" L10: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-6447d879cd console_" L11: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4869.0.0-n-dc0c9d3651__ 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: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-dc0c9d3651 console" L6: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-dc0c9d3651 console" L7: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-3100c4d69d console" L8: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-3100c4d69d console" L9: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-edd0a903ab console" L10: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-edd0a903ab console_" L11: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd22f9bb?/providers/Microsoft.Network/networkInterfaces/nic-fdbaad2769" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4869.0.0-n-0e64165e72__ 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: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-f0e558d614 console" L6: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-f0e558d614 console" L7: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-a1bff1c81f console" L8: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-a1bff1c81f console" L9: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-0e64165e72 console" L10: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4869.0.0-n-0e64165e72 console_" L11: " " ```
🟢 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: dial tcp 20.9.194.32:22: i/o timeout:_" L2: " " ```                 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-4869.0.0-n-025c71dcab console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-ac03d9918b console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-2cd84865c4 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-4869.0.0-n-c8e9ba688f console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-34f87ffe4e console" L4: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-383bc12edc console_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:699: Cluster failed starting machines: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd22f9bb?/providers/Microsoft.Network/networkInterfaces/nic-a2326251b8" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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-4869.0.0-n-878a1ee5d2 console" L3: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4869.0.0-n-b5b2f9413a console_" L4: " " ```
🟢 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) ❌ 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: dial tcp 4.154.18.122:22: i/o timeout:_" 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 create etcd node: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-clust?er-image-e0cd22f9bb/providers/Microsoft.Network/networkInterfaces/nic-9c3cf1ce76" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 20.83.104.22:22: i/o timeout:_" 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 create etcd node: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-clust?er-image-e0cd22f9bb/providers/Microsoft.Network/networkInterfaces/nic-5048b39f1b" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 20.69.161.175:22: i/o timeout:_" 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 create etcd node: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-clust?er-image-e0cd22f9bb/providers/Microsoft.Network/networkInterfaces/nic-b85fb2ba53" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 20.64.201.127:22: i/o timeout:_" 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 create etcd node: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-clust?er-image-e0cd22f9bb/providers/Microsoft.Network/networkInterfaces/nic-d0887a2fbf" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 20.115.165.120:22: i/o timeout:_" 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 create etcd node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd2?2f9bb/providers/Microsoft.Compute/virtualMachines/ci-4869.0.0-n-30f5c2a9cd" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 20.94.194.47:22: i/o timeout:_" 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 create etcd node: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-clust?er-image-e0cd22f9bb/providers/Microsoft.Network/networkInterfaces/nic-4398b8debb" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 20.83.244.80:22: i/o timeout:_" 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 create etcd node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd2?2f9bb/providers/Microsoft.Compute/virtualMachines/ci-4869.0.0-n-ad6932a8cc" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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: dial tcp 13.66.157.61:22: i/o timeout:_" 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 create etcd node: PollUntilDone(ci-4869.0.0-n-e090e80cdf): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/34ce9aae-48f7-42e7-962d-aab7022fca2c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:02:13.8668781+00:00__," L8: "__endTime__: __2026-10-31T09:02:16.8453845+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __ResourceGroupBeingDeleted__," L12: "__message__: __The resource group _KOLA-CLUSTER-IMAGE-E0CD22F9BB_ is in deprovisioning state and cannot perform this operation. Target: _/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGr?oups/kola-cluster-image-e0cd22f9bb/providers/Microsoft.Compute/disks/ci-4869.0.0-n-e090e80cdf_OsDisk_1_1092563fd3774fd381740e744dea317e_.__" L13: "}," L14: "__name__: __34ce9aae-48f7-42e7-962d-aab7022fca2c__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 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: dial tcp 20.114.8.239:22: i/o timeout:_" 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 create etcd node: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-clust?er-image-e0cd22f9bb/providers/Microsoft.Network/networkInterfaces/nic-2b0c775332" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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-4869.0.0-n-c79c505dbb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/e4dd70ed-245b-406b-8783-14dc911e8fbb" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:57:24.5269286+00:00__," L8: "__endTime__: __2026-10-31T10:02:15.6734868+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__: __e4dd70ed-245b-406b-8783-14dc911e8fbb__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-66383e047c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/8337f984-cc12-4f35-a5d1-417c2b3f0ddc" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:32:07.9929613+00:00__," L8: "__endTime__: __2026-10-31T09:52:19.2764806+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-66383e047c_ 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__: __8337f984-cc12-4f35-a5d1-417c2b3f0ddc__" 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-4869.0.0-n-66383e047c 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-4869.0.0-n-66383e047c console_" L19: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-5216cb6822): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/dde91353-d744-4fec-bf20-cd1511a85f66" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:06:54.0819356+00:00__," L8: "__endTime__: __2026-10-31T09:27:05.8591784+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-5216cb6822_ 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__: __dde91353-d744-4fec-bf20-cd1511a85f66__" 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-4869.0.0-n-5216cb6822 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-4869.0.0-n-5216cb6822 console_" L19: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-c2e255c4bc): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/f8d52ad5-2198-4265-9848-41b868fbed08" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:02:13.8296619+00:00__," L8: "__endTime__: __2026-10-31T09:02:16.8349935+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __ResourceGroupBeingDeleted__," L12: "__message__: __The resource group _KOLA-CLUSTER-IMAGE-E0CD22F9BB_ is in deprovisioning state and cannot perform this operation. Target: _/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGr?oups/kola-cluster-image-e0cd22f9bb/providers/Microsoft.Compute/disks/ci-4869.0.0-n-c2e255c4bc_OsDisk_1_02c2fe9c38654bda89397d417a6e3812_.__" L13: "}," L14: "__name__: __f8d52ad5-2198-4265-9848-41b868fbed08__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-07b2609062): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/2fd029ae-9f9d-4922-b93f-8f497b309c42" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T08:28:34.1562246+00:00__," L8: "__endTime__: __2026-10-31T08:48:45.8404066+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-07b2609062_ 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__: __2fd029ae-9f9d-4922-b93f-8f497b309c42__" 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-4869.0.0-n-07b2609062 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-4869.0.0-n-07b2609062 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-4869.0.0-n-f5b327fa87): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/463c1cdb-1b48-4cb4-9bad-b58567af1189" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:57:25.1135756+00:00__," L8: "__endTime__: __2026-10-31T10:02:15.5272671+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__: __463c1cdb-1b48-4cb4-9bad-b58567af1189__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-02ca0c8c89): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/10b364d4-c428-4b83-ab16-465a90356073" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:32:07.1450659+00:00__," L8: "__endTime__: __2026-10-31T09:52:18.5130783+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-02ca0c8c89_ 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__: __10b364d4-c428-4b83-ab16-465a90356073__" 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-4869.0.0-n-02ca0c8c89 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-4869.0.0-n-02ca0c8c89 console_" L19: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-2d2bc8c95d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/bbfffff8-b767-4dc3-b6b1-e3ff831446e1" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:06:54.2641956+00:00__," L8: "__endTime__: __2026-10-31T09:27:05.3735414+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-2d2bc8c95d_ 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__: __bbfffff8-b767-4dc3-b6b1-e3ff831446e1__" 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-4869.0.0-n-2d2bc8c95d 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-4869.0.0-n-2d2bc8c95d console_" L19: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _zfs.go:172: creating a machine failed: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd22f9bb/providers/?Microsoft.Network/networkInterfaces/nic-11202f2da8" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-5b9eea9bdd): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/706c4eaa-d79b-44cb-89ca-22e3b270b2da" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T08:28:34.3393329+00:00__," L8: "__endTime__: __2026-10-31T08:48:44.7136013+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-5b9eea9bdd_ 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__: __706c4eaa-d79b-44cb-89ca-22e3b270b2da__" 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-4869.0.0-n-5b9eea9bdd 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-4869.0.0-n-5b9eea9bdd 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-4869.0.0-n-fb1ddf4c1a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/249c750c-a295-4e10-b2d0-0cf9599d68eb" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:57:24.412897+00:00__," L8: "__endTime__: __2026-10-31T10:02:15.264769+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__: __249c750c-a295-4e10-b2d0-0cf9599d68eb__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-c998bc2f7a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/5d72bfa6-8d91-47bd-ba3b-dd7f105c6a85" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:32:08.3748557+00:00__," L8: "__endTime__: __2026-10-31T09:52:22.0261106+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-c998bc2f7a_ 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__: __5d72bfa6-8d91-47bd-ba3b-dd7f105c6a85__" 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-4869.0.0-n-c998bc2f7a 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-4869.0.0-n-c998bc2f7a console_" L19: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-f1cf1ec453): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/655a5557-99d1-436e-825c-b066e6fe4454" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T09:06:54.7243135+00:00__," L8: "__endTime__: __2026-10-31T09:27:05.7539921+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-f1cf1ec453_ 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__: __655a5557-99d1-436e-825c-b066e6fe4454__" 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-4869.0.0-n-f1cf1ec453 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-4869.0.0-n-f1cf1ec453 console_" L19: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _zfs.go:172: creating a machine failed: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e0cd22f9bb/providers/?Microsoft.Network/networkInterfaces/nic-52fb71d521" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: ResourceGroupBeingDeleted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __ResourceGroupBeingDeleted__," L9: "__message__: __The resource group _kola-cluster-image-e0cd22f9bb_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4869.0.0-n-ceb657abbb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/c6172f6e-9767-4b96-a3b5-737b7a6ccaed" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OSProvisioningTimedOut" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-31T08:37:04.9635012+00:00__," L8: "__endTime__: __2026-10-31T08:57:14.0286099+00:00__," L9: "__status__: __Failed__," L10: "__error__: {" L11: "__code__: __OSProvisioningTimedOut__," L12: "__message__: __OS Provisioning for VM _ci-4869.0.0-n-ceb657abbb_ 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__: __c6172f6e-9767-4b96-a3b5-737b7a6ccaed__" 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-4869.0.0-n-ceb657abbb 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-4869.0.0-n-ceb657abbb console_" L19: " " ```
🟢 ok **systemd.journal.user**; Succeeded: azure (1) 🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)