### Test report for 4081.3.10+nightly-20261016-2100 / amd64 **Platforms tested** : azure ❌ not ok **azure.nvme-friendly-naming**; Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--2e05129bbf" 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 **azure.nvme-friendly-naming # SKIP**; Succeeded: azure (2, 3, 4, 5) 🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--a356bea54c" 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.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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--fcb9e29120" 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.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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--9652bb5480" 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.v1.noop**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.once**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--155ae7f2a0" 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.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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--3987a39734" 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.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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--cbb75cae8a" 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.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: _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 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--f17be0796d" 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.osreset.ignition-rerun**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--04d9d4eacb" 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.overlay.cleanup**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--0519b2dead" 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.swap_activation**; Succeeded: azure (1) 🟢 ok **cl.toolbox.dnf-install**; Succeeded: azure (1) 🟢 ok **cl.update.badverity**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _update.go:168: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: ____, stderr: ____, err: dial tcp 20.107.184.225:22: i/?o timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 20.107.184.225:22: i/o timeout_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--586276dd65" 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.update.reboot**; Succeeded: azure (1) 🟢 ok **cl.users.shells**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--a1a815bcf6" 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.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.systemd.enable-service**; Succeeded: azure (1) 🟢 ok **coreos.locksmith.reboot**; Succeeded: azure (1) 🟢 ok **coreos.locksmith.tls**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--96f1661b7a" 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.selinux.boolean**; Succeeded: azure (1) 🟢 ok **coreos.selinux.enforce**; Succeeded: azure (1) 🟢 ok **coreos.tls.fetch-urls**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--a1e6dda4e1" 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.update.badusr**; Succeeded: azure (1) 🟢 ok **docker.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " _docker.base/networks-reliably (135.82s)" L2: "cluster.go:125: #1 [internal] load build definition from Dockerfile" L3: "cluster.go:125: #1 transferring dockerfile: 108B done" L4: "cluster.go:125: #1 DONE 0.0s" L5: "cluster.go:125: " L6: "cluster.go:125: #2 [internal] load .dockerignore" L7: "cluster.go:125: #2 transferring context: 2B done" L8: "cluster.go:125: #2 DONE 0.0s" L9: "cluster.go:125: " L10: "cluster.go:125: #3 [internal] load build context" L11: "cluster.go:125: #3 transferring context: 4.04MB 0.0s done" L12: "cluster.go:125: #3 DONE 0.1s" L13: "cluster.go:125: " L14: "cluster.go:125: #4 [1/1] COPY . /" L15: "cluster.go:125: #4 DONE 0.0s" L16: "cluster.go:125: " L17: "cluster.go:125: #5 exporting to image" L18: "cluster.go:125: #5 exporting layers 0.1s done" L19: "cluster.go:125: #5 writing image sha256:5dd7af912107f4251d2ce08935e1d6cf25e028491d563069467b501683f8ef8a done" L20: "cluster.go:125: #5 naming to docker.io/library/ping done" L21: "cluster.go:125: #5 DONE 0.1s" L22: "cluster.go:145: __for i in $(seq 1 100); do_n_t_techo -n ___$i: ____n_t_tdocker run --rm ping sh -c _ping -i 0.2 172.17.0.1 -w 1 _/dev/null && echo PASS || echo FAIL__n_tdone__ failed: output 1: PASS" L23: "2: PASS" L24: "3: PASS" L25: "4: PASS" L26: "5: PASS" L27: "6: PASS" L28: "7: PASS" L29: "8: PASS" L30: "9: PASS" L31: "10: PASS" L32: "11: PASS" L33: "12: PASS" L34: "13: PASS" L35: "14: PASS" L36: "15: PASS" L37: "16: PASS" L38: "17: PASS" L39: "18: PASS" L40: "19: PASS" L41: "20: PASS" L42: "21: PASS" L43: "22: PASS" L44: "23: PASS" L45: "24: PASS" L46: "25: PASS" L47: "26: PASS" L48: "27: PASS" L49: "28: PASS" L50: "29: PASS" L51: "30: PASS" L52: "31: PASS" L53: "32: PASS" L54: "33: PASS" L55: "34: PASS" L56: "35: PASS" L57: "36: PASS" L58: "37: PASS" L59: "38: PASS" L60: "39: PASS" L61: "40: PASS" L62: "41: PASS" L63: "42: PASS" L64: "43: PASS" L65: "44: PASS" L66: "45: PASS" L67: "46: PASS" L68: "47: PASS" L69: "48: PASS" L70: "49: PASS" L71: "50: PASS" L72: "51: PASS" L73: "52: PASS" L74: "53: PASS" L75: "54: PASS" L76: "55: PASS" L77: "56: PASS" L78: "57: PASS" L79: "58: PASS" L80: "59: PASS" L81: "60: PASS" L82: "61: PASS" L83: "62: PASS" L84: "63: PASS" L85: "64: PASS" L86: "65: PASS" L87: "66: PASS" L88: "67: PASS" L89: "68: PASS" L90: "69: PASS" L91: "70: PASS" L92: "71: PASS" L93: "72: PASS" L94: "73: PASS" L95: "74: PASS" L96: "75: PASS" L97: "76: PASS" L98: "77: PASS" L99: "78: PASS" L100: "79: PASS" L101: "80: PASS" L102: "81: PASS" L103: "82: PASS" L104: "83: PASS" L105: "84: PASS" L106: "85: PASS" L107: "86: PASS" L108: "87: PASS" L109: "88:, status wait: remote command exited without exit status or exit signal" L110: "--- FAIL: docker.base/user-no-caps (0.04s)" L111: "cluster.go:145: __tmpdir=$(mktemp -d); cd $tmpdir; echo -e ___FROM scratch__nCOPY . /___ _ Dockerfile;_n_t b=$(which capsh sh grep cat ls); libs=$(sudo ldd $b | grep -o /lib_[^ ]*_ | sort -u);_?n_t sudo rsync -av --relative --copy-links $b $libs ./;_n_t sudo docker build -t captest .__ failed: output , status ssh: handshake failed: read tcp 10.200.1.4:58578-_20.107.208.193:22: ?read: connection reset by peer" L112: "--- FAIL: docker.base/ownership (0.04s)" L113: "cluster.go:145: __docker run --name ownership ghcr.io/flatcar/nginx stat -c ___%u/%g___ /etc/shadow__ failed: output , status ssh: handshake failed: read tcp 10.200.1.4:58588-_20.107.208.193:22: read:? connection reset by peer_" L114: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--88e4b4348d" 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.btrfs-storage**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--e0dd3d7672" 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.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.35.1.calico.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.35.1.calico.cgroupv1.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.35.1.cilium.cgroupv1.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.10--ba2b7e6b59): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/northeurope/operations/e64d415a-9334-4830-9dec-a4d25f4c1915" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-16T23:53:57.1291055+00:00__," L8: "__endTime__: __2026-10-16T23:54:59.7136502+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__: __e64d415a-9334-4830-9dec-a4d25f4c1915__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 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-ca281?f57ae/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--3e49701619" 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.flannel.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: I1016 23:53:45.416516 2346 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: I1016 23:53:58.943595 2664 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 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--420a118536__ could not be reached" L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--420a118536__: lookup ci-4081.3.10--420a118536 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: W1016 23:53:59.143897 2664 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--420a118536 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.24]" 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 500.722324ms" 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.24: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-scheduler is healthy after 5.519288363s" L56: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 6.006419574s" L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 8.501977601s" 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--420a118536 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--420a118536 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L63: "cluster.go:125: [bootstrap-token] Using token: x3go3f.75x3635xxy5l5nfi" 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.24:6443 --token x3go3f.75x3635xxy5l5nfi _" L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:39b178086fd66d3d6209c0fb1113374832dec9bf32fd2ae627b9dcb3fd51db29 " L94: "cluster.go:125: namespace/kube-flannel created" L95: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created" L96: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created" L97: "cluster.go:125: serviceaccount/flannel created" L98: "cluster.go:125: configmap/kube-flannel-cfg created" L99: "cluster.go:125: daemonset.apps/kube-flannel-ds created" L100: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4081.3.10--cb7d78a6dc): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/northeurope/operations/31b25a6e-bfe4-4a63-94b7-30d302be3753" L101: "--------------------------------------------------------------------------------" L102: "RESPONSE 200: 200 OK" L103: "ERROR CODE: OperationPreempted" L104: "--------------------------------------------------------------------------------" L105: "{" L106: "__startTime__: __2026-10-16T23:54:26.3239064+00:00__," L107: "__endTime__: __2026-10-16T23:54:59.5891553+00:00__," L108: "__status__: __Canceled__," L109: "__error__: {" L110: "__code__: __OperationPreempted__," L111: "__message__: __Operation execution has been preempted by a more recent operation.__" L112: "}," L113: "__name__: __31b25a6e-bfe4-4a63-94b7-30d302be3753__" L114: "}" L115: "--------------------------------------------------------------------------------_" L116: " " ```                 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-ca281?f57ae/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--62bc2a368b" 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.flannel.cgroupv1.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.10--2a18a3c7a3): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/northeurope/operations/bfcb2baa-2e36-4961-9192-da8544550981" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-16T23:53:46.0698747+00:00__," L8: "__endTime__: __2026-10-16T23:54:59.4640753+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__: __bfcb2baa-2e36-4961-9192-da8544550981__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```                 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-ca281?f57ae/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--fd54bd8a1e" 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.36.1.calico.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: I1016 23:53:46.272676 2391 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5" L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2" L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2" L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0" L9: "cluster.go:125: I1016 23:53:59.262985 2623 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36" L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5" L11: "cluster.go:125: [preflight] Running pre-flight checks" L12: "cluster.go:125: E1016 23:53:59.325180 2623 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__" L13: "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" L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--26dcfdec5d__ could not be reached" L15: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--26dcfdec5d__: lookup ci-4081.3.10--26dcfdec5d on 168.63.129.16:53: no such host" L16: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_" L17: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster" L18: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection" L19: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_" L20: "cluster.go:125: W1016 23:53:59.454202 2623 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." L21: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__" L22: "cluster.go:125: [certs] Generating __ca__ certificate and key" L23: "cluster.go:125: [certs] Generating __apiserver__ certificate and key" L24: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.10--26dcfdec5d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.25]" L25: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key" L26: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key" L27: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key" L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation" L29: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation" L30: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation" L31: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation" L32: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation" L33: "cluster.go:125: [certs] Generating __sa__ key and public key" L34: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__" L35: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file" L36: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file" L37: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file" L38: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file" L39: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file" L40: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__" L41: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__" L42: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__" L43: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__" L44: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__" L45: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__" L46: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__" L47: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__" L48: "cluster.go:125: [kubelet-start] Starting the kubelet" L49: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__" L50: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s" L51: "cluster.go:125: [kubelet-check] The kubelet is healthy after 2.767639ms" L52: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s" L53: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.25:6443/livez" L54: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz" L55: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez" L56: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 10.221245ms" L57: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 15.020013ms" L58: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.003294567s" L59: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace" L60: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster" L61: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs" L62: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--26dcfdec5d as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]" L63: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--26dcfdec5d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L64: "cluster.go:125: [bootstrap-token] Using token: 6e0tf8.4ou0ib9j9ylb4mno" L65: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles" L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes" L67: "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" L68: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token" L69: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster" L70: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API" L71: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace" L72: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key" L73: "cluster.go:125: [addons] Applied essential addon: CoreDNS" L74: "cluster.go:125: [addons] Applied essential addon: kube-proxy" L75: "cluster.go:125: " L76: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!" L77: "cluster.go:125: " L78: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:" L79: "cluster.go:125: " L80: "cluster.go:125: mkdir -p $HOME/.kube" L81: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config" L82: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config" L83: "cluster.go:125: " L84: "cluster.go:125: Alternatively, if you are the root user, you can run:" L85: "cluster.go:125: " L86: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf" L87: "cluster.go:125: " L88: "cluster.go:125: You should now deploy a pod network to the cluster." L89: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:" L90: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/" L91: "cluster.go:125: " L92: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:" L93: "cluster.go:125: " L94: "cluster.go:125: kubeadm join 10.0.0.25:6443 --token 6e0tf8.4ou0ib9j9ylb4mno _" L95: "cluster.go:125: --discovery-token-ca-cert-hash sha256:ed4101c3267a5dc01f3b760739aa62b04f45e2e0eeb1b7b07e9f0aa4af7eee1c " L96: "cluster.go:125: namespace/tigera-operator created" L97: "cluster.go:125: serviceaccount/tigera-operator created" L98: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created" L99: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created" L100: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created" L101: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created" L102: "cluster.go:125: deployment.apps/tigera-operator created" L103: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met" L104: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met" L105: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met" L106: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met" L107: "cluster.go:125: installation.operator.tigera.io/default created" L108: "cluster.go:125: apiserver.operator.tigera.io/default created" L109: "cluster.go:125: goldmane.operator.tigera.io/default created" L110: "cluster.go:125: whisker.operator.tigera.io/default created" L111: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4081.3.10--bcb065bfa6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/northeurope/operations/e1eeb79f-cbfc-4a12-b649-7143c419660f" L112: "--------------------------------------------------------------------------------" L113: "RESPONSE 200: 200 OK" L114: "ERROR CODE: OperationPreempted" L115: "--------------------------------------------------------------------------------" L116: "{" L117: "__startTime__: __2026-10-16T23:54:28.9729325+00:00__," L118: "__endTime__: __2026-10-16T23:54:59.953029+00:00__," L119: "__status__: __Canceled__," L120: "__error__: {" L121: "__code__: __OperationPreempted__," L122: "__message__: __Operation execution has been preempted by a more recent operation.__" L123: "}," L124: "__name__: __e1eeb79f-cbfc-4a12-b649-7143c419660f__" L125: "}" L126: "--------------------------------------------------------------------------------_" L127: " " ```                 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-ca281?f57ae/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--c8777537bb" 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.36.1.cilium.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: I1016 23:53:47.173853 2365 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5" L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2" L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2" L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0" L9: "cluster.go:125: I1016 23:54:00.891195 2596 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36" L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5" L11: "cluster.go:125: [preflight] Running pre-flight checks" L12: "cluster.go:125: E1016 23:54:00.954007 2596 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__" L13: "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" L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--2803cc7737__ could not be reached" L15: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--2803cc7737__: lookup ci-4081.3.10--2803cc7737 on 168.63.129.16:53: no such host" L16: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_" L17: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster" L18: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection" L19: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_" L20: "cluster.go:125: W1016 23:54:01.102239 2596 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." L21: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__" L22: "cluster.go:125: [certs] Generating __ca__ certificate and key" L23: "cluster.go:125: [certs] Generating __apiserver__ certificate and key" L24: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.10--2803cc7737 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.27]" L25: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key" L26: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key" L27: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key" L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation" L29: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation" L30: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation" L31: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation" L32: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation" L33: "cluster.go:125: [certs] Generating __sa__ key and public key" L34: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__" L35: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file" L36: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file" L37: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file" L38: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file" L39: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file" L40: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__" L41: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__" L42: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__" L43: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__" L44: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__" L45: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__" L46: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__" L47: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__" L48: "cluster.go:125: [kubelet-start] Starting the kubelet" L49: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__" L50: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s" L51: "cluster.go:125: [kubelet-check] The kubelet is healthy after 870.097??s" L52: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s" L53: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.27:6443/livez" L54: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz" L55: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez" L56: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 7.455677ms" L57: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 52.01344ms" L58: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002725363s" L59: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace" L60: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster" L61: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs" L62: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--2803cc7737 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]" L63: "cluster.go:125: [mark-control-plane] Marking the node ci-4081.3.10--2803cc7737 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L64: "cluster.go:125: [bootstrap-token] Using token: a2kg09.4ymjplga1y0carvm" L65: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles" L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes" L67: "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" L68: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token" L69: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster" L70: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API" L71: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace" L72: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key" L73: "cluster.go:125: [addons] Applied essential addon: CoreDNS" L74: "cluster.go:125: [addons] Applied essential addon: kube-proxy" L75: "cluster.go:125: " L76: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!" L77: "cluster.go:125: " L78: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:" L79: "cluster.go:125: " L80: "cluster.go:125: mkdir -p $HOME/.kube" L81: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config" L82: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config" L83: "cluster.go:125: " L84: "cluster.go:125: Alternatively, if you are the root user, you can run:" L85: "cluster.go:125: " L86: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf" L87: "cluster.go:125: " L88: "cluster.go:125: You should now deploy a pod network to the cluster." L89: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:" L90: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/" L91: "cluster.go:125: " L92: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:" L93: "cluster.go:125: " L94: "cluster.go:125: kubeadm join 10.0.0.27:6443 --token a2kg09.4ymjplga1y0carvm _" L95: "cluster.go:125: --discovery-token-ca-cert-hash sha256:d66e2e1646561d6ee4809661a9daf61c8d52936133cad84fa45c8bd85c1e54ba " L96: "cluster.go:125: i Using Cilium version 1.12.5" L97: "cluster.go:125: ? Auto-detected cluster name: kubernetes" L98: "cluster.go:125: ? Auto-detected datapath mode: tunnel" L99: "cluster.go:125: ? Auto-detected kube-proxy has been installed" L100: "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" L101: "cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret" L102: "cluster.go:125: ? Created CA in secret cilium-ca" L103: "cluster.go:125: ? Generating certificates for Hubble..." L104: "cluster.go:125: ? Creating Service accounts..." L105: "cluster.go:125: ? Creating Cluster roles..." L106: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..." L107: "cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true" L108: "cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17" L109: "cluster.go:125: ? Creating Agent DaemonSet..." L110: "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" L111: "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" L112: "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" L113: "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" L114: "cluster.go:125: ? Creating Operator Deployment..." L115: "cluster.go:125: ? Waiting for Cilium to be installed and ready..." L116: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health" L117: "cluster.go:125: ?[33m /??_" L118: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m Cilium: ?[32mOK?[0m" L119: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m Operator: ?[32mOK?[0m" L120: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m Hubble: ?[36mdisabled?[0m" L121: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m ClusterMesh: ?[36mdisabled?[0m" L122: "cluster.go:125: ?[34m ___/" L123: "cluster.go:125: ?[0m" L124: "cluster.go:125: DaemonSet cilium " L125: "cluster.go:125: Deployment cilium-operator " L126: "cluster.go:125: Containers: cilium " L127: "cluster.go:125: cilium-operator " L128: "cluster.go:125: Cluster Pods: 0/0 managed by Cilium" L129: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4081.3.10--325bf40820): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/northeurope/operations/57b65bdf-5dd5-48d8-a156-8aa27bd13a78" L130: "--------------------------------------------------------------------------------" L131: "RESPONSE 200: 200 OK" L132: "ERROR CODE: OperationPreempted" L133: "--------------------------------------------------------------------------------" L134: "{" L135: "__startTime__: __2026-10-16T23:54:17.6953446+00:00__," L136: "__endTime__: __2026-10-16T23:54:59.5891553+00:00__," L137: "__status__: __Canceled__," L138: "__error__: {" L139: "__code__: __OperationPreempted__," L140: "__message__: __Operation execution has been preempted by a more recent operation.__" L141: "}," L142: "__name__: __57b65bdf-5dd5-48d8-a156-8aa27bd13a78__" L143: "}" L144: "--------------------------------------------------------------------------------_" L145: " " ```                 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-ca281?f57ae/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--60680ab04f" 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.36.1.flannel.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.37.0.calico.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6" 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.7.0-0" L8: "cluster.go:125: [init] Using Kubernetes version: v1.37.1" L9: "cluster.go:125: [preflight] Running pre-flight checks" L10: "cluster.go:125: E1016 23:53:58.848155 2583 remote_runtime.go:1359] __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.38. 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--0104bd7b01__ could not be reached" L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.10--0104bd7b01__: lookup ci-4081.3.10--0104bd7b01 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: W1016 23:53:58.976167 2583 checks.go:920] 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--0104bd7b01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.26]" 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 2.648729ms" 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.26: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-controller-manager is healthy after 6.177667ms" L55: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 12.821739ms" L56: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002767373s" 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--0104bd7b01 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--0104bd7b01 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L62: "cluster.go:125: [bootstrap-token] Using token: ap0hx4.kjfqkzgpjwyw0srd" 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.26:6443 --token ap0hx4.kjfqkzgpjwyw0srd _" L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:b854f62f1ab4fa303c47706bb0ffa0d8bd5b341e370171a825f980379f3a3247 " 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: PollUntilDone(ci-4081.3.10--5e03c64c69): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/northeurope/operations/2fbc288c-119f-4a50-aff2-45930bdc3d89" L110: "--------------------------------------------------------------------------------" L111: "RESPONSE 200: 200 OK" L112: "ERROR CODE: OperationPreempted" L113: "--------------------------------------------------------------------------------" L114: "{" L115: "__startTime__: __2026-10-16T23:54:29.7574439+00:00__," L116: "__endTime__: __2026-10-16T23:54:59.953029+00:00__," L117: "__status__: __Canceled__," L118: "__error__: {" L119: "__code__: __OperationPreempted__," L120: "__message__: __Operation execution has been preempted by a more recent operation.__" L121: "}," L122: "__name__: __2fbc288c-119f-4a50-aff2-45930bdc3d89__" L123: "}" L124: "--------------------------------------------------------------------------------_" L125: " " ```                 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-ca281?f57ae/providers/Microsoft.Compute/virtualMachines/ci-4081.3.10--79d2ba6e55" 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.37.0.cilium.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: azure (1) 🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ca281f57ae/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.10--a2a37dbe3f" 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 **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)