### Test report for 4081.3.8+nightly-20260605-2100 / amd64 **Platforms tested** : azure 🟢 ok **bpf.ig**; Succeeded: azure (1) 🟢 ok **cl.basic**; Succeeded: azure (1) 🟢 ok **cl.cloudinit.basic**; Succeeded: azure (1) 🟢 ok **cl.cloudinit.multipart-mime**; Succeeded: azure (1) 🟢 ok **cl.cloudinit.script**; Succeeded: azure (1) 🟢 ok **cl.etcd-member.discovery**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-a9a544d911" 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.etcdctlv3**; Succeeded: azure (1) 🟢 ok **cl.etcd-member.v2-backup-restore**; Succeeded: azure (1) 🟢 ok **cl.flannel.udp**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-d55678672d/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-39875cb21d" 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: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.8-n-fbf604106d__ failed to enable selinux: unable to enable SELinux audit logs: wait: remote command exited without exit s?tatus or exit signal:_" L2: " " ```
🟢 ok **cl.flannel.vxlan**; Succeeded: azure (1) 🟢 ok **cl.ignition.kargs**; Succeeded: azure (1) 🟢 ok **cl.ignition.luks**; Succeeded: azure (1) 🟢 ok **cl.ignition.misc.empty**; Succeeded: azure (1) 🟢 ok **cl.ignition.symlink**; Succeeded: azure (1) 🟢 ok **cl.ignition.translation**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.btrfsroot**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.ext4root**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-31bbb9d7ab" 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.groups**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.noop**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.once**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.users**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.xfsroot**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-3abc94567c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: OperationNotAllowed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __OperationNotAllowed__," L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
🟢 ok **cl.ignition.v2.ext4root**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2.noop**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2.users**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2.xfsroot**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2_1.ext4checkexisting**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2_1.swap**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2_1.vfat**; Succeeded: azure (1) 🟢 ok **cl.internet**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-?cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-c817e14fd5" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 404: 404 Not Found" L4: "ERROR CODE: NotFound" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __NotFound__," L9: "__message__: __The entity was not found in this Azure location.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
🟢 ok **cl.locksmith.cluster**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-e27a56962f" 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.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: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-d55678672d/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-60321b7d42" 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: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _cluster.go:152: + sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_" L2: "cluster.go:156: cmd sudo nft --json list ruleset | jq _.nftables[] | select(.rule) | .rule.expr[0].match.right_ did not output 80_" L3: " " ```
🟢 ok **cl.network.wireguard**; Succeeded: azure (1) 🟢 ok **cl.osreset.ignition-rerun**; Succeeded: azure (1) 🟢 ok **cl.overlay.cleanup**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _state.go:97: could not reboot: machine __ci-4081.3.8-n-7a6cf8375c__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 94.245.89.54:22: i/o timeout_" L2: " " ```
🟢 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: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-d55678672d/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-b20c534607" 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: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-50562a10c4" 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 (1) 🟢 ok **cl.verity**; Succeeded: azure (1) 🟢 ok **coreos.auth.verify**; Succeeded: azure (1) 🟢 ok **coreos.ignition.groups**; Succeeded: azure (1) 🟢 ok **coreos.ignition.once**; Succeeded: azure (1) 🟢 ok **coreos.ignition.resource.local**; Succeeded: azure (1) 🟢 ok **coreos.ignition.resource.remote**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-7608fd495e" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: OperationNotAllowed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __OperationNotAllowed__," L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
🟢 ok **coreos.ignition.security.tls**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.8-n-37337f1071): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/ko?la-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-37337f1071" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 404: 404 Not Found" L4: "ERROR CODE: NotFound" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __NotFound__," L9: "__message__: __The entity was not found in this Azure location.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
❌ not ok **coreos.ignition.ssh.key**; Failed: azure (1, 2, 3, 4, 5)
                Diagnostic output for azure, run 5 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.8-n-3ca78b69e1__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_" L2: " " ```                 Diagnostic output for azure, run 4 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.8-n-9080c1b34e__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 68.219.100.178:22: i/o timeout_" L2: " " ```                 Diagnostic output for azure, run 3 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.8-n-6bf18f8195__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_" L2: " " ```                 Diagnostic output for azure, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.8-n-f46aafbe65__ failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: ssh: unable to authen?ticate, attempted methods [none publickey], no supported methods remain_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.8-n-37ce87d979__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.166.50.205:22: i/o timeout_" L2: " " ```
🟢 ok **coreos.ignition.systemd.enable-service**; Succeeded: azure (1) 🟢 ok **coreos.locksmith.reboot**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded_" L2: " " ```
🟢 ok **coreos.locksmith.tls**; Succeeded: azure (1) 🟢 ok **coreos.selinux.boolean**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.8-n-ba4269c5d5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/northeurope/operations/24b19b72-fc10-4334-bb98-c29bad699946" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-06-05T23:37:23.6389714+00:00__," L8: "__endTime__: __2026-06-05T23:38:50.3932209+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__: __24b19b72-fc10-4334-bb98-c29bad699946__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **coreos.selinux.enforce**; Succeeded: azure (1) 🟢 ok **coreos.tls.fetch-urls**; Succeeded: azure (1) 🟢 ok **coreos.update.badusr**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` 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.123.17.45:22: i/o ?timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 20.123.17.45:22: i/o timeout_" L2: " " ```
🟢 ok **docker.base**; Succeeded: azure (1) 🟢 ok **docker.btrfs-storage**; Succeeded: azure (1) 🟢 ok **docker.containerd-restart**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.8-n-ec0fc38d19): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/northeurope/operations/6d3fe0d0-47bc-4fd5-bbb1-c7c98d00d6a5" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-06-05T23:37:20.1616441+00:00__," L8: "__endTime__: __2026-06-05T23:38:50.1588335+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__: __6d3fe0d0-47bc-4fd5-bbb1-c7c98d00d6a5__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **docker.enable-service.sysext**; Succeeded: azure (1) 🟢 ok **docker.lib-coreos-dockerd-compat**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-0afa97bf78" 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.network-openbsd-nc**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-f9550263b1" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: OperationNotAllowed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __OperationNotAllowed__," L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
🟢 ok **docker.selinux**; Succeeded: azure (1) 🟢 ok **docker.userns**; Succeeded: azure (1) 🟢 ok **extra-test.[V1].cl.internet**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.34.4.calico.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c68?5bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-ec70424b48" 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.34.4.calico.cgroupv1.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685b?d7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-916adab6e3" 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.34.4.cilium.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.8-n-4e1c95e8cb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/northeurope/operations/9d6a2ee0-71f6-4f2f-a215-37c18544e2f7" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-06-05T23:37:17.4979097+00:00__," L8: "__endTime__: __2026-06-05T23:38:50.2700981+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__: __9d6a2ee0-71f6-4f2f-a215-37c18544e2f7__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.34.4.cilium.cgroupv1.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.34.4.flannel.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.34.4.flannel.cgroupv1.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _cluster.go:125: I0605 23:34:03.451855 2414 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5" 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: I0605 23:34:16.804720 2717 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35" L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.5" 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.8-n-73622daa05__ could not be reached" L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.8-n-73622daa05__: lookup ci-4081.3.8-n-73622daa05 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: W0605 23:34:17.013301 2717 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.8-n-73622daa05 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.23]" 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.695329ms" 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.23:6443/livez" L53: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz" L54: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez" L55: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.508981927s" L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.104121106s" L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.001959454s" 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.8-n-73622daa05 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.8-n-73622daa05 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L63: "cluster.go:125: [bootstrap-token] Using token: i9nwj2.bbunf6wkemsiz5wa" 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.23:6443 --token i9nwj2.bbunf6wkemsiz5wa _" L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:33781e0e9583f59a72318e681679ae7d1c1d171a1a0c5e52e38caba72d197f5d " L94: "cluster.go:125: namespace/tigera-operator created" L95: "cluster.go:125: serviceaccount/tigera-operator created" L96: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created" L97: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created" L98: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created" L99: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created" L100: "cluster.go:125: deployment.apps/tigera-operator created" L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met" L102: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met" L103: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met" L104: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met" L105: "cluster.go:125: installation.operator.tigera.io/default created" L106: "cluster.go:125: apiserver.operator.tigera.io/default created" L107: "cluster.go:125: goldmane.operator.tigera.io/default created" L108: "cluster.go:125: whisker.operator.tigera.io/default created" L109: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/?providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-78588ebd1f" L110: "--------------------------------------------------------------------------------" L111: "RESPONSE 409: 409 Conflict" L112: "ERROR CODE: OperationNotAllowed" L113: "--------------------------------------------------------------------------------" L114: "{" L115: "__error__: {" L116: "__code__: __OperationNotAllowed__," L117: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__" L118: "}" L119: "}" L120: "--------------------------------------------------------------------------------_" L121: " " ```
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _cluster.go:125: I0605 23:34:09.069671 2529 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5" 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: I0605 23:34:32.059620 2754 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35" L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.5" 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.8-n-a30aee8bc7__ could not be reached" L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.8-n-a30aee8bc7__: lookup ci-4081.3.8-n-a30aee8bc7 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: W0605 23:34:32.252219 2754 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.8-n-a30aee8bc7 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.22]" 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.773423ms" 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.22: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 4.015646595s" L56: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.507359609s" L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.50195551s" 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.8-n-a30aee8bc7 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.8-n-a30aee8bc7 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L63: "cluster.go:125: [bootstrap-token] Using token: 1dryy9.e0k5etqoog2y5rz2" 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.22:6443 --token 1dryy9.e0k5etqoog2y5rz2 _" L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:0b6aa00c6f94f992af6153ca4367ec9fa80997a64ccd506b8288c9756156e9df " L94: "cluster.go:125: i Using Cilium version 1.12.5" L95: "cluster.go:125: ? Auto-detected cluster name: kubernetes" L96: "cluster.go:125: ? Auto-detected datapath mode: tunnel" L97: "cluster.go:125: ? Auto-detected kube-proxy has been installed" L98: "cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-?cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vx?lan" L99: "cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret" L100: "cluster.go:125: ? Created CA in secret cilium-ca" L101: "cluster.go:125: ? Generating certificates for Hubble..." L102: "cluster.go:125: ? Creating Service accounts..." L103: "cluster.go:125: ? Creating Cluster roles..." L104: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..." L105: "cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true" L106: "cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17" L107: "cluster.go:125: ? Creating Agent DaemonSet..." L108: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog" L109: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the ___appArmorProfile___ fi?eld instead__ subsys=klog" L110: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the ___appArmorProfile___ field i?nstead__ subsys=klog" L111: "cluster.go:125: level=warning msg=__spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the ___appArmorProfile___ field instead?__ subsys=klog" L112: "cluster.go:125: ? Creating Operator Deployment..." L113: "cluster.go:125: ? Waiting for Cilium to be installed and ready..." L114: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health" L115: "cluster.go:125: ?[33m /??_" L116: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m Cilium: ?[32mOK?[0m" L117: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m Operator: ?[32mOK?[0m" L118: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m Hubble: ?[36mdisabled?[0m" L119: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m ClusterMesh: ?[36mdisabled?[0m" L120: "cluster.go:125: ?[34m ___/" L121: "cluster.go:125: ?[0m" L122: "cluster.go:125: Deployment cilium-operator Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m" L123: "cluster.go:125: DaemonSet cilium Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m" L124: "cluster.go:125: Containers: cilium Running: ?[32m1?[0m" L125: "cluster.go:125: cilium-operator Running: ?[32m1?[0m" L126: "cluster.go:125: Cluster Pods: 2/2 managed by Cilium" L127: "cluster.go:125: Image versions cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1" L128: "cluster.go:125: cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1" L129: "cluster.go:125: W0605 23:37:14.523140 2344 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration" L130: "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" L131: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_" L132: "--- FAIL: kubeadm.v1.35.1.cilium.base/IPSec_encryption (31.42s)" L133: "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" L134: "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" L135: "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" L136: "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" L137: "cluster.go:145: __/opt/bin/cilium status --wait --wait-duration 1m__ failed: output , status wait: remote command exited without exit status or exit signal_" L138: " " ```
🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4081.3.8-n-96e9ce4e1d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/northeurope/operations/11d665fc-a256-4732-89ba-d798f0e63f6c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-06-05T23:37:33.5099874+00:00__," L8: "__endTime__: __2026-06-05T23:38:50.1588335+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__: __11d665fc-a256-4732-89ba-d798f0e63f6c__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e?/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-1d272e83cb" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 404: 404 Not Found" L4: "ERROR CODE: NotFound" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __NotFound__," L9: "__message__: __The entity was not found in this Azure location.__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.8-n-8c82baa478): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/northeurope/operations/3e603ab3-45ac-4ff9-ab22-3a87465ed603" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: OperationPreempted" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-06-05T23:38:14.2301023+00:00__," L8: "__endTime__: __2026-06-05T23:38:50.050145+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__: __3e603ab3-45ac-4ff9-ab22-3a87465ed603__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: azure (1) 🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _cluster.go:125: bash: line 1: docker: command not found" L2: "cluster.go:125: Cloning into _sysext-bakery_..." L3: "cluster.go:125: Note: switching to _9850ffd5b2353f45a9b3bf4fb84f8138a149e3e7_." L4: "cluster.go:125: " L5: "cluster.go:125: You are in _detached HEAD_ state. You can look around, make experimental" L6: "cluster.go:125: changes and commit them, and you can discard any commits you make in this" L7: "cluster.go:125: state without impacting any branches by switching back to a branch." L8: "cluster.go:125: " L9: "cluster.go:125: If you want to create a new branch to retain commits you create, you may" L10: "cluster.go:125: do so (now or later) by using -c with the switch command. Example:" L11: "cluster.go:125: " L12: "cluster.go:125: git switch -c 🟢 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 (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.8-n-030e12b4de" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 409: 409 Conflict" L4: "ERROR CODE: OperationNotAllowed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__error__: {" L8: "__code__: __OperationNotAllowed__," L9: "__message__: __Operation could not be completed as it results in exceeding approved standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Curr?ent Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a r?equest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22comma?nd%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22prope?rties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succ?eed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__" L10: "}" L11: "}" L12: "--------------------------------------------------------------------------------_" L13: " " ```
🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)