### Test report for 4757.2.3 / amd64 **Platforms tested** : azure ❌ not ok **cl.etcd-member.discovery**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.3-a-3ecbe8f710): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/northeurope/operations/ed51a087-95b3-434a-8ea9-7334b858b624" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-28T10:00:23.3671729+00:00__," L8: "__endTime__: __2026-10-28T10:01:35.6720088+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__: __ed51a087-95b3-434a-8ea9-7334b858b624__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 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.3-a-d68b27bb6b 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.3-a-b770c1d7c7 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.3-a-1fdeda11f4 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-a-7e35b3e496 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.3-a-71915fafaf 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.3-a-c076d051c5 console_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _discovery.go:89: discovery failed cluster-health check: health polling failed: Process exited with status 1: " L2: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-a-8bbb5bbc8c 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.3-a-778af7e3d9 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.3-a-7cbc4cb84d 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.3-a-d9356b7069 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.3-a-e12a7786a3 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.3-a-5c868fb116 console_" L5: " " ```
❌ not ok **cl.etcd-member.v2-backup-restore**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _discovery.go:104: failed cluster-health check: health polling failed: dial tcp 20.123.5.66:22: i/o timeout:_" 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: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e28?123e6a/providers/Microsoft.Network/publicIPAddresses/ip-bc0a51e9bd" 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-6e28123e6a_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.3-a-53af88b431__ 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: machine __ci-4757.2.3-a-3cea933f80__ 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.3-a-e79b984a7f 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.3-a-e79b984a7f console_" L7: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.3-a-ad05f23d49__ 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.3-a-ad05f23d49 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.3-a-ad05f23d49 console_" L7: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.3-a-1f37011dbc__ 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.3-a-d8c8c2f378 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.3-a-d8c8c2f378 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.3-a-228e24e89c 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.3-a-228e24e89c console_" L9: " " ```
❌ 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: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e28?123e6a/providers/Microsoft.Network/publicIPAddresses/ip-56648685f2" 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-6e28123e6a_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.3-a-d6d8d641d3__ 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: machine __ci-4757.2.3-a-2ddeb93efb__ 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.3-a-842dc4a745 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.3-a-842dc4a745 console_" L7: " " ```                 Diagnostic output for azure, run 2 ``` 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-749a?5586d5/providers/Microsoft.Network/publicIPAddresses/ip-fb5e071142" 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-749a5586d5_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4757.2.3-a-cbd12bd14e__ 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.3-a-cbd12bd14e 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.3-a-cbd12bd14e console_" L7: " " ```
❌ not ok **cl.locksmith.cluster**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.3-a-f5f742aa73): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/northeurope/operations/fc09e2ef-6e8a-4996-acad-379faf07bce6" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-28T10:00:33.1640408+00:00__," L8: "__endTime__: __2026-10-28T10:01:35.5305708+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__: __fc09e2ef-6e8a-4996-acad-379faf07bce6__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 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.3-a-89d932f3e8 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.3-a-5a65fff986 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.3-a-2b605ea648 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:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-a-dfc149ca53 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.3-a-b48ed661fa 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.3-a-962e5a4a75 console_" L5: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _locksmith.go:151: cluster health: health polling failed: Process exited with status 1: " L2: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4757.2.3-a-eb8b2d2d07 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.3-a-b3b77cafb3 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.3-a-de774192d6 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.3-a-417b5e7419 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.3-a-f7e4bb7e00 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.3-a-4c727ad70c console_" L5: " " ```
❌ 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 create etcd node: PollUntilDone(ci-4757.2.3-a-9f903de411): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/northeurope/operations/ac2491c8-25a3-4d5a-9182-bd57351056fc" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-28T10:00:22.9999795+00:00__," L8: "__endTime__: __2026-10-28T10:01:37.9232217+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__: __ac2491c8-25a3-4d5a-9182-bd57351056fc__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 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-4757.2.3-a-3f2ba6647d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/northeurope/operations/ed9b7154-8913-4037-8f07-f3b1930d8f13" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-28T09:00:41.2083767+00:00__," L8: "__endTime__: __2026-10-28T09:03:06.2366899+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__: __ed9b7154-8913-4037-8f07-f3b1930d8f13__" 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.35.1.cilium.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: dial tcp 132.164.250.65:22: i/o timeout:_" 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-6e28123e6a/providers/Microsoft.Network/publicIPAddresses/ip-33cb0bc597" 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-6e28123e6a_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.36.1.calico.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-6e28123e6a/providers/Microsoft.Network/publicIPAddresses/ip-4e3f7ac3de" 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-6e28123e6a_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.36.1.cilium.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-6e28123e6a/providers/Microsoft.Network/publicIPAddresses/ip-dd6634cd4c" 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-6e28123e6a_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: dial tcp 20.234.23.114:22: i/o timeout:_" 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 create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-6e28123e6a/providers/Microsoft.Network/publicIPAddresses/ip-8ceb5655d8" 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-6e28123e6a_ is in deprovisioning state and cannot perform this operation.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.37.0.calico.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.3-a-8568d12c06): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/northeurope/operations/247c1a9e-6a5d-48c3-a259-528ccf234c3c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-28T10:00:22.8953086+00:00__," L8: "__endTime__: __2026-10-28T10:01:35.3910832+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__: __247c1a9e-6a5d-48c3-a259-528ccf234c3c__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.37.0.cilium.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```
❌ not ok **kubeadm.v1.37.0.flannel.base**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_" L2: " " ```