### Test report for 4081.3.10 / amd64 **Platforms tested** : azure 🟢 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) 🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--b94c3249bb" 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: " " ```
🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--c5d28dffc6" 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: " " ```
🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--d0ca290118" 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: " " ```
🟢 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)
                Diagnostic output for azure, run 5 ``` 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: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.10--9d316fc9bc): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/northeurope/operations/60a5cd00-5631-4b9d-b96a-cbe1b4696259" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-08-12T01:46:04.4618554+00:00__," L8: "__endTime__: __2026-08-12T01:58:49.8222406+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__: __60a5cd00-5631-4b9d-b96a-cbe1b4696259__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 3 ``` 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: " " ```                 Diagnostic output for azure, run 2 ``` 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: " " ```                 Diagnostic output for azure, run 1 ``` 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: " " ```
🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--c00d8a2141" 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: " " ```
🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--b8dfc720eb" 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: " " ```
🟢 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)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.10--65321adcf0__ 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: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.10--ea23b3974c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/northeurope/operations/6e613b17-c031-4678-9df7-77b56cfde748" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-08-12T01:46:04.3439433+00:00__," L8: "__endTime__: __2026-08-12T01:58:49.3688965+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__: __6e613b17-c031-4678-9df7-77b56cfde748__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.10--b22784bf1f__ 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: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.10--ed1704f8c8__ 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: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.10--99bae1b49e__ 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: " " ```
🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--7df8442082" 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: " " ```
🟢 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 (1) 🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` 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-c62a4?994cc/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--a93d86ff8d" 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: " " ```
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.3" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.3" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.3" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.3" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2" L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2" L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0" L8: "cluster.go:125: [init] Using Kubernetes version: v1.36.3" L9: "cluster.go:125: [preflight] Running pre-flight checks" L10: "cluster.go:125: E0812 01:00:17.525922 2692 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__" L11: "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.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri" L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--6c94ddb394__ could not be reached" L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--6c94ddb394__: lookup ci-4081.3.10--6c94ddb394 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: W0812 01:00:17.650541 2692 checks.go:907] 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.2__ as the CRI sandbox image." L19: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__" L20: "cluster.go:125: [certs] Generating __ca__ certificate and key" L21: "cluster.go:125: [certs] Generating __apiserver__ certificate and key" L22: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.10--6c94ddb394 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.30]" L23: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key" L24: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key" L25: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key" L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation" L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation" L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation" L29: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation" L30: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation" L31: "cluster.go:125: [certs] Generating __sa__ key and public key" L32: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__" L33: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file" L34: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file" L35: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file" L36: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file" L37: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file" L38: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__" L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__" L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__" L41: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__" L42: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__" L43: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__" L44: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__" L45: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__" L46: "cluster.go:125: [kubelet-start] Starting the kubelet" L47: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__" L48: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s" L49: "cluster.go:125: [kubelet-check] The kubelet is healthy after 1.034041379s" L50: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s" L51: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.30:6443/livez" L52: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz" L53: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez" L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 8.630639ms" L55: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 18.378797ms" L56: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 502.255502ms" L57: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace" L58: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster" L59: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs" L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--6c94ddb394 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]" L61: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--6c94ddb394 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L62: "cluster.go:125: [bootstrap-token] Using token: g77mn1.alpehlj8mtagzde4" L63: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles" L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes" L65: "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" L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token" L67: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster" L68: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API" 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.30:6443 --token g77mn1.alpehlj8mtagzde4 _" L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:207a372258e0d0372537e1b8af315e368e35d8df213eb66fa758b0c887886c35 " L94: "cluster.go:125: namespace/tigera-operator created" L95: "cluster.go:125: serviceaccount/tigera-operator created" L96: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created" L97: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created" L98: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created" L99: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created" L100: "cluster.go:125: deployment.apps/tigera-operator created" L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met" L102: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met" L103: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met" L104: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met" L105: "cluster.go:125: installation.operator.tigera.io/default created" L106: "cluster.go:125: apiserver.operator.tigera.io/default created" L107: "cluster.go:125: goldmane.operator.tigera.io/default created" L108: "cluster.go:125: whisker.operator.tigera.io/default created" L109: "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-c62a4994cc/?providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--b52ee40678" L110: "--------------------------------------------------------------------------------" L111: "RESPONSE 409: 409 Conflict" L112: "ERROR CODE: OperationNotAllowed" L113: "--------------------------------------------------------------------------------" L114: "{" L115: "__error__: {" L116: "__code__: __OperationNotAllowed__," L117: "__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__" L118: "}" L119: "}" L120: "--------------------------------------------------------------------------------_" L121: " " ```
🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c62a4994cc/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--e61fd5e0e5" 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: " " ```
🟢 ok **systemd.journal.user**; Succeeded: azure (1) 🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)