### Test report for 4081.3.10+nightly-20260904-2100 / amd64

**Platforms tested** : azure 

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

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

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

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

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

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

<details>

<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: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c6c2dc3cb2/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--9596ae17bb"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 409: 409 Conflict"
      L4: "ERROR CODE: OperationNotAllowed"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__error__: {"
      L8: "__code__: __OperationNotAllowed__,"
      L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
      L10: "}"
      L11: "}"
      L12: "--------------------------------------------------------------------------------_"
      L13: " "
  ```


</details>


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

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

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

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

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

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

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

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

🟢 ok **cl.network.initramfs.second-boot**; Succeeded: azure (1)

❌ not ok **cl.network.iptables**; 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: _cluster.go:152: + sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_"
      L2: "cluster.go:156: cmd sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_ did not output 80_"
      L3: " "
  ```

<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: _cluster.go:152: + sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_"
      L2: "cluster.go:156: cmd sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_ did not output 80_"
      L3: " "
  ```

<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:152: + sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_"
      L2: "cluster.go:156: cmd sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_ did not output 80_"
      L3: " "
  ```

<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: _cluster.go:152: + sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_"
      L2: "cluster.go:156: cmd sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_ did not output 80_"
      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: _cluster.go:152: + sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_"
      L2: "cluster.go:156: cmd sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_ did not output 80_"
      L3: " "
  ```


</details>


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

❌ not ok **coreos.ignition.ssh.key**; 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-4081.3.10--9d788eaa26__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_"
      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-4081.3.10--fa2086482a__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.107.201.83: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 3</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ci-4081.3.10--1f651ca1a0__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_"
      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: _harness.go:651: Cluster failed starting machines: machine __ci-4081.3.10--0d87b751ca__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_"
      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: _harness.go:651: Cluster failed starting machines: machine __ci-4081.3.10--78c5d0770a__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_"
      L2: " "
  ```


</details>


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

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

<details>

<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 create master node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c6c?2dc3cb2/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--14241b87f4"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 409: 409 Conflict"
      L4: "ERROR CODE: OperationNotAllowed"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__error__: {"
      L8: "__code__: __OperationNotAllowed__,"
      L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
      L10: "}"
      L11: "}"
      L12: "--------------------------------------------------------------------------------_"
      L13: " "
  ```


</details>


🟢 ok **kubeadm.v1.34.4.calico.cgroupv1.base**; Succeeded: azure (1)

🟢 ok **kubeadm.v1.34.4.cilium.base**; Succeeded: azure (1)

🟢 ok **kubeadm.v1.34.4.cilium.cgroupv1.base**; Succeeded: azure (1)

🟢 ok **kubeadm.v1.34.4.flannel.base**; Succeeded: azure (1)

🟢 ok **kubeadm.v1.34.4.flannel.cgroupv1.base**; Succeeded: azure (1)

🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: azure (1)

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

<details>

<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: I0904 23:55:49.182835    2505 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35"
      L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8"
      L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8"
      L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8"
      L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8"
      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: I0904 23:56:01.304529    2715 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35"
      L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.8"
      L11: "cluster.go:125: [preflight] Running pre-flight checks"
      L12: "cluster.go:125:  [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet conf?ig will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri"
      L13: "cluster.go:125:  [WARNING Hostname]: hostname __ci-4081.3.10--2559affb10__ could not be reached"
      L14: "cluster.go:125:  [WARNING Hostname]: hostname __ci-4081.3.10--2559affb10__: lookup ci-4081.3.10--2559affb10 on 168.63.129.16:53: no such host"
      L15: "cluster.go:125:  [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
      L16: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
      L17: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
      L18: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
      L19: "cluster.go:125: W0904 23:56:01.532160    2715 checks.go:906] detected that the sandbox image __registry.k8s.io/pause:3.8__ of the container runtime is inconsistent with that used by kubeadm. It is rec?ommended to use __registry.k8s.io/pause:3.10.1__ as the CRI sandbox image."
      L20: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
      L21: "cluster.go:125: [certs] Generating __ca__ certificate and key"
      L22: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
      L23: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.10--2559affb10 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.27]"
      L24: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
      L25: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
      L26: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
      L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
      L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
      L29: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
      L30: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
      L31: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
      L32: "cluster.go:125: [certs] Generating __sa__ key and public key"
      L33: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
      L34: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
      L35: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
      L36: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
      L37: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
      L38: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
      L39: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
      L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
      L41: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
      L42: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
      L43: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
      L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
      L45: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
      L46: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
      L47: "cluster.go:125: [kubelet-start] Starting the kubelet"
      L48: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
      L49: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
      L50: "cluster.go:125: [kubelet-check] The kubelet is healthy after 501.545888ms"
      L51: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
      L52: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.27:6443/livez"
      L53: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
      L54: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
      L55: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.007752231s"
      L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.900176884s"
      L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.50142132s"
      L58: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
      L59: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
      L60: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
      L61: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--2559affb10 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
      L62: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--2559affb10 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
      L63: "cluster.go:125: [bootstrap-token] Using token: e68n4q.8d53a6xcz4xct9ow"
      L64: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
      L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
      L66: "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"
      L67: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
      L68: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
      L69: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
      L70: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
      L71: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
      L72: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
      L73: "cluster.go:125: "
      L74: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
      L75: "cluster.go:125: "
      L76: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
      L77: "cluster.go:125: "
      L78: "cluster.go:125:   mkdir -p $HOME/.kube"
      L79: "cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
      L80: "cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config"
      L81: "cluster.go:125: "
      L82: "cluster.go:125: Alternatively, if you are the root user, you can run:"
      L83: "cluster.go:125: "
      L84: "cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf"
      L85: "cluster.go:125: "
      L86: "cluster.go:125: You should now deploy a pod network to the cluster."
      L87: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
      L88: "cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/"
      L89: "cluster.go:125: "
      L90: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
      L91: "cluster.go:125: "
      L92: "cluster.go:125: kubeadm join 10.0.0.27:6443 --token e68n4q.8d53a6xcz4xct9ow _"
      L93: "cluster.go:125:  --discovery-token-ca-cert-hash sha256:01d6c72e5f623feb31777ea2db4401e9ce82760432958d1b7f8edc7e37b56ecf "
      L94: "cluster.go:125: i  Using Cilium version 1.12.5"
      L95: "cluster.go:125: ? Auto-detected cluster name: kubernetes"
      L96: "cluster.go:125: ? Auto-detected datapath mode: tunnel"
      L97: "cluster.go:125: ? Auto-detected kube-proxy has been installed"
      L98: "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"
      L99: "cluster.go:125: i  Storing helm values file in kube-system/cilium-cli-helm-values Secret"
      L100: "cluster.go:125: ? Created CA in secret cilium-ca"
      L101: "cluster.go:125: ? Generating certificates for Hubble..."
      L102: "cluster.go:125: ? Creating Service accounts..."
      L103: "cluster.go:125: ? Creating Cluster roles..."
      L104: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..."
      L105: "cluster.go:125: i  Manual overwrite in ConfigMap: enable-endpoint-routes=true"
      L106: "cluster.go:125: i  Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17"
      L107: "cluster.go:125: ? Creating Agent DaemonSet..."
      L108: "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"
      L109: "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"
      L110: "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"
      L111: "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"
      L112: "cluster.go:125: ? Creating Operator Deployment..."
      L113: "cluster.go:125: ? Waiting for Cilium to be installed and ready..."
      L114: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health"
      L115: "cluster.go:125: ?[33m    /??_"
      L116: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m    Cilium:         ?[32mOK?[0m"
      L117: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m    Operator:       ?[32mOK?[0m"
      L118: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m    Hubble:         ?[36mdisabled?[0m"
      L119: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m    ClusterMesh:    ?[36mdisabled?[0m"
      L120: "cluster.go:125: ?[34m    ___/"
      L121: "cluster.go:125: ?[0m"
      L122: "cluster.go:125: DaemonSet        cilium             "
      L123: "cluster.go:125: Deployment       cilium-operator    "
      L124: "cluster.go:125: Containers:      cilium-operator    "
      L125: "cluster.go:125:                  cilium             "
      L126: "cluster.go:125: Cluster Pods:    0/0 managed by Cilium"
      L127: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c6c2dc3cb2/?providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--9f276e667c"
      L128: "--------------------------------------------------------------------------------"
      L129: "RESPONSE 409: 409 Conflict"
      L130: "ERROR CODE: OperationNotAllowed"
      L131: "--------------------------------------------------------------------------------"
      L132: "{"
      L133: "__error__: {"
      L134: "__code__: __OperationNotAllowed__,"
      L135: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
      L136: "}"
      L137: "}"
      L138: "--------------------------------------------------------------------------------_"
      L139: " "
  ```


</details>


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

<details>

<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 create etcd node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c6c2d?c3cb2/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--e8cf5bfd36"
      L2: "--------------------------------------------------------------------------------"
      L3: "RESPONSE 409: 409 Conflict"
      L4: "ERROR CODE: OperationNotAllowed"
      L5: "--------------------------------------------------------------------------------"
      L6: "{"
      L7: "__error__: {"
      L8: "__code__: __OperationNotAllowed__,"
      L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
      L10: "}"
      L11: "}"
      L12: "--------------------------------------------------------------------------------_"
      L13: " "
  ```


</details>


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

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

🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: azure (1)

🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (1)

🟢 ok **sysext.disable-containerd**; Succeeded: azure (1)

🟢 ok **sysext.disable-docker**; Succeeded: azure (1)

🟢 ok **sysext.simple**; Succeeded: azure (1)

🟢 ok **systemd.journal.user**; Succeeded: azure (1)

🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)
