### Test report for 4757.2.2 / 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 (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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-749560d3e4 console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-a490cf5c33 console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-e873651e1b 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-a578b3966f console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-3bf68bd019 console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-922a8a4f8b console_" L5: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e96f?b84ab2/providers/Microsoft.Network/publicIPAddresses/ip-be4eff1974" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-8428ca9586 console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-325c774a6d console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-9152394b0b 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-632f6f7bba console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-fcc6979935 console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-3f009d2f5b 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: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e96f?b84ab2/providers/Microsoft.Network/publicIPAddresses/ip-d7d86541fd" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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:651: Cluster failed starting machines: machine __ci-4757.2.2-a-e34acb45a5__ 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-cb7c6c3c06 console" L6: "harness.go:621: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4757.2.2-a-cb7c6c3c06 console" L7: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-e34acb45a5 console" L8: "harness.go:621: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4757.2.2-a-e34acb45a5 console_" L9: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.2-a-28249fdc92__ 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:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e96f?b84ab2/providers/Microsoft.Network/publicIPAddresses/ip-6c0becc9e5" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.2-a-d6b0f9ffa9__ 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:651: Cluster failed starting machines: machine __ci-4757.2.2-a-33516c5360__ 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-33516c5360 console" L6: "harness.go:621: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4757.2.2-a-33516c5360 console_" L7: " " ```
❌ not ok **cl.flannel.vxlan**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.2-a-f5cffc727c__ 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-f5cffc727c console" L6: "harness.go:621: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4757.2.2-a-f5cffc727c console_" L7: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.2-a-47126168cb__ 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:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e96f?b84ab2/providers/Microsoft.Network/publicIPAddresses/ip-c559d183bc" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.2-a-5d31b7dbc0__ 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:651: Cluster failed starting machines: machine __ci-4757.2.2-a-08088930f8__ 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-e7899ab321 console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-82db73a836 console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-516ced9e55 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-5f2c372871 console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-103832dff3 console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-611d5c7d50 console_" L5: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-e96f?b84ab2/providers/Microsoft.Network/publicIPAddresses/ip-c4accddb91" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-a38538f3bf console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-912df1a6b3 console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-8fab290725 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-3863a35e14 console" L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-bc4af8edce console" L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.2-a-337c4e57ae 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-7094b7b0e9" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-4b14e31892" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-5407bef28e" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-5b53d36d3a" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-54d360504a" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-975df0fed5" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-d8c3f7b6fb" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-eeca94791e" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-e96fb84ab2/providers/Microsoft.Network/publicIPAddresses/ip-a8f2916db7" 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-e96fb84ab2_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 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 **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) 🟢 ok **systemd.journal.user**; Succeeded: azure (1) 🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)