### Test report for 4790.1.1+nightly-20261021-2100 / amd64

**Platforms tested** : azure 

🟢 ok **azure.nvme-friendly-naming**; Succeeded: azure (1)

🟢 ok **bpf.ig**; Succeeded: azure (1)

🟢 ok **cl.basic**; Succeeded: azure (1)

🟢 ok **cl.cloudinit.basic**; Succeeded: azure (1)

🟢 ok **cl.cloudinit.multipart-mime**; Succeeded: azure (1)

🟢 ok **cl.cloudinit.script**; Succeeded: azure (1)

❌ not ok **cl.etcd-member.discovery**; Failed: azure (1, 2, 3, 4, 5)

<details>

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-c65fc4af5a__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: ____, stderr: ____, err: dial tcp 40.115.121.66:22: i/o timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 40.115.121.66:22: i/o time?out_"
      L2: " "
  ```

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

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

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-89eec79d98__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: __starting__, stderr: ____, err: Process exited with status 1, systemctl list-jobs returned stdout: __JOB  UNIT                TYPE  STATE_n1086 etcd-member.servi?ce start running_n900  multi-user.target   start waiting_n_n2 jobs listed.__, stderr: ____, err: <nil_"
      L2: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-f28c2972d6 console"
      L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-233ca85395 console_"
      L4: " "
  ```

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

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

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-13d337ee51__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: __starting__, stderr: ____, err: Process exited with status 1, systemctl list-jobs returned stdout: __JOB  UNIT                TYPE  STATE_n1053 etcd-member.servi?ce start running_n887  multi-user.target   start waiting_n_n2 jobs listed.__, stderr: ____, err: <nil__"
      L2: " "
  ```


</details>


🟢 ok **cl.etcd-member.etcdctlv3**; Succeeded: azure (1)

🟢 ok **cl.etcd-member.v2-backup-restore**; Succeeded: azure (1)

❌ not ok **cl.flannel.udp**; Failed: azure (1, 2, 3, 4, 5)

<details>

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-7a19b080ca__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-d07cfc6194__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-0be7feec0e__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-0f571486d3__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-8720b4aaf3__ 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: " "
  ```


</details>


❌ not ok **cl.flannel.vxlan**; Failed: azure (1, 2, 3, 4, 5)

<details>

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-6c54c156b3__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-4a854ca68d__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-572f4f02cc__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-8f37516c2a__ 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: " "
  ```

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-72d3e7d060__ 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: " "
  ```


</details>


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

<details>

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

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4790.1.1-n-b683c53424__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: ____, stderr: ____, err: dial tcp 40.115.121.79:22: i/o timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 40.115.121.79:22: i/o time?out_"
      L2: " "
  ```

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

  ```
      L1: " Error: _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-4790.1.1-n-0b0fa84b7a console"
      L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-5c1825ea2e console"
      L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-adfa2ee0ef console_"
      L5: " "
  ```

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

  ```
      L1: " Error: _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-4790.1.1-n-d82c0ae26a console"
      L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-e2098c65d0 console"
      L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-b131ab418a console_"
      L5: " "
  ```

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

  ```
      L1: " Error: _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-4790.1.1-n-6295aaf9ef console"
      L3: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-13d276b725 console"
      L4: "harness.go:621: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container).  ) on machine ci-4790.1.1-n-dd9c2a9850 console_"
      L5: " "
  ```

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

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


</details>


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

<details>

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

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: dial tcp 20.166.72.247:22: i/o timeout:_"
      L2: " "
  ```

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

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

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

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

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

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

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

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


</details>


❌ not ok **kubeadm.v1.35.1.cilium.base**; Failed: azure (1, 2, 3, 4, 5)

<details>

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

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4790.1.1-n-fd372eb8d4): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/northeurope/operations/df070aab-6aae-4a96-a6bf-c3dede4f33a7"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 200: 200 OK"
      L4: "ERROR CODE: OperationPreempted"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__startTime__: __2026-10-22T01:55:14.5769839+00:00__,"
      L8: "__endTime__: __2026-10-22T01:55:45.2123618+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__: __df070aab-6aae-4a96-a6bf-c3dede4f33a7__"
      L15: "}"
      L16: "--------------------------------------------------------------------------------_"
      L17: " "
  ```

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

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

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

  ```
      L1: " Error: _cluster.go:125: I1022 01:24:38.262131    3124 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35"
      L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9"
      L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9"
      L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9"
      L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9"
      L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1"
      L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1"
      L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0"
      L9: "cluster.go:125: I1022 01:25:04.633208    3391 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35"
      L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.9"
      L11: "cluster.go:125: [preflight] Running pre-flight checks"
      L12: "cluster.go:125:  [WARNING Hostname]: hostname __ci-4790.1.1-n-f3f88adfa2__ could not be reached"
      L13: "cluster.go:125:  [WARNING Hostname]: hostname __ci-4790.1.1-n-f3f88adfa2__: lookup ci-4790.1.1-n-f3f88adfa2 on 168.63.129.16:53: no such host"
      L14: "cluster.go:125:  [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
      L15: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
      L16: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
      L17: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
      L18: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
      L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
      L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
      L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4790.1.1-n-f3f88adfa2 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.12]"
      L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
      L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
      L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
      L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
      L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
      L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
      L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
      L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
      L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
      L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
      L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
      L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
      L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
      L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
      L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
      L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
      L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
      L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
      L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
      L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
      L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
      L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
      L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
      L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
      L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
      L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
      L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 64.873074ms"
      L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
      L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.12:6443/livez"
      L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
      L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
      L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.007277832s"
      L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 5.007584244s"
      L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 8.001642448s"
      L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
      L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
      L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
      L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4790.1.1-n-f3f88adfa2 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
      L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4790.1.1-n-f3f88adfa2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
      L61: "cluster.go:125: [bootstrap-token] Using token: ju13n8.f3ev15lxktmxqp7s"
      L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
      L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
      L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials"
      L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
      L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
      L67: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
      L68: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
      L69: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
      L70: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
      L71: "cluster.go:125: "
      L72: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
      L73: "cluster.go:125: "
      L74: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
      L75: "cluster.go:125: "
      L76: "cluster.go:125:   mkdir -p $HOME/.kube"
      L77: "cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
      L78: "cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config"
      L79: "cluster.go:125: "
      L80: "cluster.go:125: Alternatively, if you are the root user, you can run:"
      L81: "cluster.go:125: "
      L82: "cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf"
      L83: "cluster.go:125: "
      L84: "cluster.go:125: You should now deploy a pod network to the cluster."
      L85: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
      L86: "cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/"
      L87: "cluster.go:125: "
      L88: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
      L89: "cluster.go:125: "
      L90: "cluster.go:125: kubeadm join 10.0.0.12:6443 --token ju13n8.f3ev15lxktmxqp7s _"
      L91: "cluster.go:125:  --discovery-token-ca-cert-hash sha256:a05b365c184c58d369ce27c091420a553ac51142ecf76f4ec4540ce90d78b533 "
      L92: "cluster.go:125: i  Using Cilium version 1.12.5"
      L93: "cluster.go:125: ? Auto-detected cluster name: kubernetes"
      L94: "cluster.go:125: ? Auto-detected datapath mode: tunnel"
      L95: "cluster.go:125: ? Auto-detected kube-proxy has been installed"
      L96: "cluster.go:125: i  helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-?cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vx?lan"
      L97: "cluster.go:125: i  Storing helm values file in kube-system/cilium-cli-helm-values Secret"
      L98: "cluster.go:125: ? Created CA in secret cilium-ca"
      L99: "cluster.go:125: ? Generating certificates for Hubble..."
      L100: "cluster.go:125: ? Creating Service accounts..."
      L101: "cluster.go:125: ? Creating Cluster roles..."
      L102: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..."
      L103: "cluster.go:125: i  Manual overwrite in ConfigMap: enable-endpoint-routes=true"
      L104: "cluster.go:125: i  Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17"
      L105: "cluster.go:125: ? Creating Agent DaemonSet..."
      L106: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L107: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the ___appArmorProfile___ fi?eld instead__ subsys=klog"
      L108: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the ___appArmorProfile___ field i?nstead__ subsys=klog"
      L109: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L110: "cluster.go:125: ? Creating Operator Deployment..."
      L111: "cluster.go:125: ? Waiting for Cilium to be installed and ready..."
      L112: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health"
      L113: "cluster.go:125: ?[33m    /??_"
      L114: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m    Cilium:         ?[32mOK?[0m"
      L115: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m    Operator:       ?[32mOK?[0m"
      L116: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m    Hubble:         ?[36mdisabled?[0m"
      L117: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m    ClusterMesh:    ?[36mdisabled?[0m"
      L118: "cluster.go:125: ?[34m    ___/"
      L119: "cluster.go:125: ?[0m"
      L120: "cluster.go:125: Deployment        cilium-operator    Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
      L121: "cluster.go:125: DaemonSet         cilium             Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
      L122: "cluster.go:125: Containers:       cilium-operator    Running: ?[32m1?[0m"
      L123: "cluster.go:125:                   cilium             Running: ?[32m1?[0m"
      L124: "cluster.go:125: Cluster Pods:     2/2 managed by Cilium"
      L125: "cluster.go:125: Image versions    cilium             quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1"
      L126: "cluster.go:125:                   cilium-operator    quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1"
      L127: "cluster.go:125: W1022 01:27:55.158246    2995 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration"
      L128: "cluster.go:125:  [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
      L129: "--- FAIL: kubeadm.v1.35.1.cilium.base/IPSec_encryption (68.35s)"
      L130: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L131: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the ___appArmorProfile___ fi?eld instead__ subsys=klog"
      L132: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the ___appArmorProfile___ field i?nstead__ subsys=klog"
      L133: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L134: "cluster.go:125: Error: Unable to determine status:  timeout while waiting for status to become successful: context deadline exceeded"
      L135: "cluster.go:145: __/opt/bin/cilium status --wait --wait-duration 1m__ failed: output ?[33m    /????_"
      L136: "?[36m /?????[33m___/?[32m????_?[0m    Cilium:         ?[31m1 errors?[0m"
      L137: "?[36m ___?[31m/????_?[32m__/?[0m    Operator:       ?[32mOK?[0m"
      L138: "?[32m /?????[31m___/?[35m????_?[0m    Hubble:         ?[36mdisabled?[0m"
      L139: "?[32m ___?[34m/????_?[35m__/?[0m    ClusterMesh:    ?[36mdisabled?[0m"
      L140: "?[34m    ___/"
      L141: "?[0m"
      L142: "DaemonSet         cilium             Desired: 2, Ready: ?[32m2/2?[0m, Available: ?[32m2/2?[0m"
      L143: "Deployment        cilium-operator    Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
      L144: "Containers:       cilium             Running: ?[32m2?[0m"
      L145: "cilium-operator    Running: ?[32m1?[0m"
      L146: "Cluster Pods:     5/5 managed by Cilium"
      L147: "Image versions    cilium             quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 2"
      L148: "cilium-operator    quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1"
      L149: "Errors:           cilium             cilium-n88bh    unable to retrieve cilium status: error dialing backend: dial tcp 10.10.10.10:10250: i/o timeout, status Process exited with status 1_"
      L150: " "
  ```

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

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

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

  ```
      L1: " Error: _cluster.go:125: I1022 00:43:41.890341    3117 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35"
      L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9"
      L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9"
      L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9"
      L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9"
      L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1"
      L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1"
      L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0"
      L9: "cluster.go:125: I1022 00:44:10.508003    3382 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35"
      L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.9"
      L11: "cluster.go:125: [preflight] Running pre-flight checks"
      L12: "cluster.go:125:  [WARNING Hostname]: hostname __ci-4790.1.1-n-14622dc330__ could not be reached"
      L13: "cluster.go:125:  [WARNING Hostname]: hostname __ci-4790.1.1-n-14622dc330__: lookup ci-4790.1.1-n-14622dc330 on 168.63.129.16:53: no such host"
      L14: "cluster.go:125:  [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
      L15: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
      L16: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
      L17: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
      L18: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
      L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
      L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
      L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4790.1.1-n-14622dc330 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.23]"
      L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
      L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
      L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
      L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
      L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
      L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
      L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
      L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
      L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
      L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
      L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
      L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
      L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
      L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
      L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
      L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
      L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
      L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
      L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
      L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
      L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
      L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
      L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
      L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
      L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
      L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
      L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 442.483??s"
      L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
      L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.23:6443/livez"
      L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
      L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
      L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.004311234s"
      L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.626441714s"
      L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501123827s"
      L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
      L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
      L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
      L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4790.1.1-n-14622dc330 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
      L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4790.1.1-n-14622dc330 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
      L61: "cluster.go:125: [bootstrap-token] Using token: odc57j.3y5xd53c1w2kk3h9"
      L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
      L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
      L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials"
      L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
      L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
      L67: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
      L68: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
      L69: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
      L70: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
      L71: "cluster.go:125: "
      L72: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
      L73: "cluster.go:125: "
      L74: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
      L75: "cluster.go:125: "
      L76: "cluster.go:125:   mkdir -p $HOME/.kube"
      L77: "cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
      L78: "cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config"
      L79: "cluster.go:125: "
      L80: "cluster.go:125: Alternatively, if you are the root user, you can run:"
      L81: "cluster.go:125: "
      L82: "cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf"
      L83: "cluster.go:125: "
      L84: "cluster.go:125: You should now deploy a pod network to the cluster."
      L85: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
      L86: "cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/"
      L87: "cluster.go:125: "
      L88: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
      L89: "cluster.go:125: "
      L90: "cluster.go:125: kubeadm join 10.0.0.23:6443 --token odc57j.3y5xd53c1w2kk3h9 _"
      L91: "cluster.go:125:  --discovery-token-ca-cert-hash sha256:9e915406ce22a146d11185b7eb50f3839d7d0e720c7f214663e66a15d4f8e641 "
      L92: "cluster.go:125: i  Using Cilium version 1.12.5"
      L93: "cluster.go:125: ? Auto-detected cluster name: kubernetes"
      L94: "cluster.go:125: ? Auto-detected datapath mode: tunnel"
      L95: "cluster.go:125: ? Auto-detected kube-proxy has been installed"
      L96: "cluster.go:125: i  helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-?cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vx?lan"
      L97: "cluster.go:125: i  Storing helm values file in kube-system/cilium-cli-helm-values Secret"
      L98: "cluster.go:125: ? Created CA in secret cilium-ca"
      L99: "cluster.go:125: ? Generating certificates for Hubble..."
      L100: "cluster.go:125: ? Creating Service accounts..."
      L101: "cluster.go:125: ? Creating Cluster roles..."
      L102: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..."
      L103: "cluster.go:125: i  Manual overwrite in ConfigMap: enable-endpoint-routes=true"
      L104: "cluster.go:125: i  Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17"
      L105: "cluster.go:125: ? Creating Agent DaemonSet..."
      L106: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L107: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the ___appArmorProfile___ fi?eld instead__ subsys=klog"
      L108: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the ___appArmorProfile___ field i?nstead__ subsys=klog"
      L109: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L110: "cluster.go:125: ? Creating Operator Deployment..."
      L111: "cluster.go:125: ? Waiting for Cilium to be installed and ready..."
      L112: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health"
      L113: "cluster.go:125: ?[33m    /??_"
      L114: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m    Cilium:         ?[32mOK?[0m"
      L115: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m    Operator:       ?[32mOK?[0m"
      L116: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m    Hubble:         ?[36mdisabled?[0m"
      L117: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m    ClusterMesh:    ?[36mdisabled?[0m"
      L118: "cluster.go:125: ?[34m    ___/"
      L119: "cluster.go:125: ?[0m"
      L120: "cluster.go:125: Deployment        cilium-operator    Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
      L121: "cluster.go:125: DaemonSet         cilium             Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
      L122: "cluster.go:125: Containers:       cilium             Running: ?[32m1?[0m"
      L123: "cluster.go:125:                   cilium-operator    Running: ?[32m1?[0m"
      L124: "cluster.go:125: Cluster Pods:     2/2 managed by Cilium"
      L125: "cluster.go:125: Image versions    cilium             quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1"
      L126: "cluster.go:125:                   cilium-operator    quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1"
      L127: "cluster.go:125: W1022 00:48:57.831350    3074 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration"
      L128: "cluster.go:125:  [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
      L129: "--- FAIL: kubeadm.v1.35.1.cilium.base/IPSec_encryption (68.57s)"
      L130: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L131: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the ___appArmorProfile___ fi?eld instead__ subsys=klog"
      L132: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the ___appArmorProfile___ field i?nstead__ subsys=klog"
      L133: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog"
      L134: "cluster.go:125: Error: Unable to determine status:  timeout while waiting for status to become successful: context deadline exceeded"
      L135: "cluster.go:145: __/opt/bin/cilium status --wait --wait-duration 1m__ failed: output ?[33m    /????_"
      L136: "?[36m /?????[33m___/?[32m????_?[0m    Cilium:         ?[31m1 errors?[0m"
      L137: "?[36m ___?[31m/????_?[32m__/?[0m    Operator:       ?[32mOK?[0m"
      L138: "?[32m /?????[31m___/?[35m????_?[0m    Hubble:         ?[36mdisabled?[0m"
      L139: "?[32m ___?[34m/????_?[35m__/?[0m    ClusterMesh:    ?[36mdisabled?[0m"
      L140: "?[34m    ___/"
      L141: "?[0m"
      L142: "DaemonSet         cilium             Desired: 2, Ready: ?[32m2/2?[0m, Available: ?[32m2/2?[0m"
      L143: "Deployment        cilium-operator    Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
      L144: "Containers:       cilium             Running: ?[32m2?[0m"
      L145: "cilium-operator    Running: ?[32m1?[0m"
      L146: "Cluster Pods:     5/5 managed by Cilium"
      L147: "Image versions    cilium             quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 2"
      L148: "cilium-operator    quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1"
      L149: "Errors:           cilium             cilium-8t6lr    unable to retrieve cilium status: error dialing backend: dial tcp 10.10.10.10:10250: i/o timeout, status Process exited with status 1_"
      L150: " "
  ```


</details>


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

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

🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (3); Failed: azure (1, 2)

❌ not ok **kubeadm.v1.36.1.flannel.base**; Failed: azure (1, 2, 3, 4, 5)

<details>

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

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: dial tcp 20.166.58.70:22: i/o timeout:_"
      L2: " "
  ```

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

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

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

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

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

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

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

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


</details>


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

❌ not ok **kubeadm.v1.37.0.cilium.base**; Failed: azure (1, 2, 3, 4, 5)

<details>

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

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/r?esourceGroups/kola-cluster-image-bab5da5889/providers/Microsoft.Compute/virtualMachines/ci-4790.1.1-n-c868728c8f"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 404: 404 Not Found"
      L4: "ERROR CODE: NotFound"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__error__: {"
      L8: "__code__: __NotFound__,"
      L9: "__message__: __The entity was not found in this Azure location.__"
      L10: "}"
      L11: "}"
      L12: "--------------------------------------------------------------------------------_"
      L13: " "
  ```

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

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

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

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

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

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

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

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


</details>


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

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