### Test report for 4081.3.9+nightly-20260720-2100 / arm64
**Platforms tested** : azure
❌ not ok **bpf.ig**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " _bpf.ig/ig (127.50s)"
L2: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help"
L3: "cluster.go:125: time=__2026-07-21T05:09:28Z__ level=warning msg=__Failed to create container-collection__"
L4: "cluster.go:125: + trap _kill %%_ ERR"
L5: "cluster.go:125: + timeout 30 grep -F -m1 running..."
L6: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose"
L7: "cluster.go:125: ++ kill %%"
L8: "cluster.go:125: bash: line 6: kill: %%: no such job"
L9: "ig.go:79: ig run trace_exec did not behave as expected: Process exited with status 1_"
L10: " "
```
Diagnostic output for azure, run 4
```
L1: " _bpf.ig/ig (98.02s)"
L2: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help"
L3: "cluster.go:125: time=__2026-07-21T04:53:06Z__ level=warning msg=__Failed to create container-collection__"
L4: "cluster.go:125: + trap _kill %%_ ERR"
L5: "cluster.go:125: + timeout 30 grep -F -m1 running..."
L6: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose"
L7: "cluster.go:125: ++ kill %%"
L8: "cluster.go:125: bash: line 6: kill: %%: no such job"
L9: "ig.go:79: ig run trace_exec did not behave as expected: Process exited with status 1_"
L10: " "
```
Diagnostic output for azure, run 3
```
L1: " _bpf.ig/ig (95.64s)"
L2: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help"
L3: "cluster.go:125: time=__2026-07-21T04:36:53Z__ level=warning msg=__Failed to create container-collection__"
L4: "cluster.go:125: + trap _kill %%_ ERR"
L5: "cluster.go:125: + timeout 30 grep -F -m1 running..."
L6: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose"
L7: "cluster.go:125: ++ kill %%"
L8: "cluster.go:125: bash: line 6: kill: %%: no such job"
L9: "ig.go:79: ig run trace_exec did not behave as expected: Process exited with status 1_"
L10: " "
```
Diagnostic output for azure, run 2
```
L1: " _bpf.ig/ig (96.31s)"
L2: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help"
L3: "cluster.go:125: time=__2026-07-21T04:12:24Z__ level=warning msg=__Failed to create container-collection__"
L4: "cluster.go:125: + trap _kill %%_ ERR"
L5: "cluster.go:125: + timeout 30 grep -F -m1 running..."
L6: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose"
L7: "cluster.go:125: ++ kill %%"
L8: "cluster.go:125: bash: line 6: kill: %%: no such job"
L9: "ig.go:79: ig run trace_exec did not behave as expected: Process exited with status 1_"
L10: " "
```
Diagnostic output for azure, run 1
```
L1: " _bpf.ig/ig (95.59s)"
L2: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help"
L3: "cluster.go:125: time=__2026-07-21T02:38:43Z__ level=warning msg=__Failed to create container-collection__"
L4: "cluster.go:125: + trap _kill %%_ ERR"
L5: "cluster.go:125: + timeout 30 grep -F -m1 running..."
L6: "cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose"
L7: "cluster.go:125: ++ kill %%"
L8: "cluster.go:125: bash: line 6: kill: %%: no such job"
L9: "ig.go:79: ig run trace_exec did not behave as expected: Process exited with status 1_"
L10: " "
```
🟢 ok **cl.basic**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.9-n-a012670eac__ failed basic checks: no /etc/os-release file: ssh: handshake failed: read tcp 10.200.1.7:43594-_20.3.75.1?75:22: read: connection reset by peer:_"
L2: " "
```
🟢 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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-284fa05642"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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 (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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-af78ac2761"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.flannel.vxlan**; Succeeded: azure (1)
🟢 ok **cl.ignition.kargs**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-80686c18c0"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 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:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-62e2216602"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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 (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.9-n-f61dede546): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/ko?la-cluster-image-555204181e/providers/Microsoft.Compute/virtualMachines/ci-4081.3.9-n-f61dede546"
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.ignition.translation**; 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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-f76031815f"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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.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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-02f95caa53"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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.ext4root**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.groups**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.once**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-1393237bcf"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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 (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-3065bac798"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.ignition.v2.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.ext4checkexisting**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.swap**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.vfat**; Succeeded: azure (1)
🟢 ok **cl.internet**; Succeeded: azure (1)
🟢 ok **cl.locksmith.cluster**; Succeeded: azure (4); Failed: azure (1, 2, 3)
Diagnostic output for azure, run 3
```
L1: " Error: _harness.go:616: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4081.3.9-n-4f041f2d5f console_"
L2: " "
```
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-ce7af0f6f5/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-82a635b16e"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-543bf30638"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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)
🟢 ok **cl.network.iptables**; Succeeded: azure (1)
🟢 ok **cl.network.wireguard**; Succeeded: azure (1)
🟢 ok **cl.osreset.ignition-rerun**; Succeeded: azure (1)
🟢 ok **cl.overlay.cleanup**; Succeeded: azure (1)
🟢 ok **cl.swap_activation**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.9-n-4a9a2709e5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/37463931-3e97-4d5c-804b-aec19e8fa3a7"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-07-21T02:44:00.3290223+00:00__,"
L8: "__endTime__: __2026-07-21T02:44:02.6020025+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __ResourceGroupBeingDeleted__,"
L12: "__message__: __The resource group _KOLA-CLUSTER-IMAGE-555204181E_ is in deprovisioning state and cannot perform this operation. Target: _/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGr?oups/kola-cluster-image-555204181e/providers/Microsoft.Compute/disks/ci-4081.3.9-n-4a9a2709e5_OsDisk_1_a095adc8b89045e99e8960b4ef9090d4_.__"
L13: "},"
L14: "__name__: __37463931-3e97-4d5c-804b-aec19e8fa3a7__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.toolbox.dnf-install**; Succeeded: azure (1)
🟢 ok **cl.update.badverity**; 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 4.155.104.79:22: i/o ?timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 4.155.104.79:22: i/o timeout_"
L2: " "
```
🟢 ok **cl.update.reboot**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-09aa33106e"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.users.shells**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-09726ea285"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.verity**; 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.9-n-0c04f9be85): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/7332837c-9633-4429-8555-7f9dba8ecc19"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-07-21T02:44:00.195974+00:00__,"
L8: "__endTime__: __2026-07-21T02:44:02.5998904+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __ResourceGroupBeingDeleted__,"
L12: "__message__: __The resource group _KOLA-CLUSTER-IMAGE-555204181E_ is in deprovisioning state and cannot perform this operation. Target: _/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGr?oups/kola-cluster-image-555204181e/providers/Microsoft.Compute/disks/ci-4081.3.9-n-0c04f9be85_OsDisk_1_82836add452e4bcbb5c8c74f090fe84f_.__"
L13: "},"
L14: "__name__: __7332837c-9633-4429-8555-7f9dba8ecc19__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **coreos.auth.verify**; Succeeded: azure (1)
🟢 ok **coreos.ignition.groups**; 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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-24c9edabf9"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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.once**; Succeeded: azure (1)
🟢 ok **coreos.ignition.resource.local**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-7ca5880cd5"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **coreos.ignition.resource.remote**; Succeeded: azure (1)
🟢 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: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-c60a8823d2"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
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.9-n-8836bb9499__ 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.9-n-4a8aaa540e__ 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 3
```
L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.9-n-853fbea26a__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.83.242.206:22: i/o timeout_"
L2: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:646: Cluster failed starting machines: machine __ci-4081.3.9-n-7e83216e94__ 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: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-d07ee829aa"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **coreos.ignition.systemd.enable-service**; 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.9-n-2c7da4f80e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/4f990ac7-97f0-476f-997f-0d6dd5b74961"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-07-21T02:43:53.9415192+00:00__,"
L8: "__endTime__: __2026-07-21T02:44:21.3615674+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__: __4f990ac7-97f0-476f-997f-0d6dd5b74961__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 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 (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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-9267ad77aa"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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 (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.9-n-eb482cb762): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/bf64e0c6-e0db-4251-b7a5-8ae00cdae428"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-07-21T02:43:53.2823998+00:00__,"
L8: "__endTime__: __2026-07-21T02:44:22.1131489+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__: __bf64e0c6-e0db-4251-b7a5-8ae00cdae428__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 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: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-7226eacec3"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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.base**; Succeeded: azure (1)
🟢 ok **docker.btrfs-storage**; Succeeded: azure (1)
🟢 ok **docker.containerd-restart**; Succeeded: azure (1)
🟢 ok **docker.enable-service.sysext**; Succeeded: azure (1)
🟢 ok **docker.lib-coreos-dockerd-compat**; Succeeded: azure (1)
🟢 ok **docker.network-openbsd-nc**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-81aae99b18"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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 (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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-2db81f7441"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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.userns**; 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.9-n-b3022f46a2): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/f3a79c3e-441c-4e5b-a741-98f0921005ae"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-07-21T02:43:53.5652704+00:00__,"
L8: "__endTime__: __2026-07-21T02:44:21.6438443+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__: __f3a79c3e-441c-4e5b-a741-98f0921005ae__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 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: machine __ci-4081.3.9-n-2e6db5a29c__ failed basic checks: ssh unreachable or system not ready: failure checking if machin?e is running: systemctl is-system-running returned stdout: ____, stderr: ____, err: dial tcp 20.230.169.204:22: i/o timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 20.2?30.169.204:22: i/o timeout_"
L2: " "
```
🟢 ok **kubeadm.v1.34.4.calico.cgroupv1.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I0721 02:43:43.943651 2554 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.9"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.9"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.9"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.9"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0"
L9: "cluster.go:125: I0721 02:43:54.910945 2840 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.34.9"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-bdca407e0f__ could not be reached"
L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-bdca407e0f__: lookup ci-4081.3.9-n-bdca407e0f 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: W0721 02:43:55.125377 2840 checks.go:827] 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.9-n-bdca407e0f kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.26]"
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 1.00132736s"
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.26: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.601447562s"
L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.624510212s"
L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501664174s"
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.9-n-bdca407e0f 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.9-n-bdca407e0f as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L63: "cluster.go:125: [bootstrap-token] Using token: kl3lr6.1atqqnwzyvgbqsjs"
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.26:6443 --token kl3lr6.1atqqnwzyvgbqsjs _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:f2d63fd2e32ea231c4f5d87f3166f68139bbe31ecf1bffa581e68b90e41a53e8 "
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: "kubeadm.go:197: unable to setup cluster: unable to run master script: wait: remote command exited without exit status or exit signal_"
L102: " "
```
🟢 ok **kubeadm.v1.34.4.cilium.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.34.4.cilium.cgroupv1.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I0721 02:42:30.275028 2573 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.9"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.9"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.9"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.9"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0"
L9: "cluster.go:125: I0721 02:42:42.372687 2829 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.34.9"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-284c62718d__ could not be reached"
L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-284c62718d__: lookup ci-4081.3.9-n-284c62718d 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: W0721 02:42:42.532066 2829 checks.go:827] 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.9-n-284c62718d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.31]"
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 1.001456323s"
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.31: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.622200737s"
L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.818291493s"
L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.001946462s"
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.9-n-284c62718d 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.9-n-284c62718d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L63: "cluster.go:125: [bootstrap-token] Using token: pqnjmy.n3y6eedvw8jpv2k3"
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.31:6443 --token pqnjmy.n3y6eedvw8jpv2k3 _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:bd14bec656c45c9cb62a70b7d1da49183d97592d6ece288fb1b7670c4d0e2e87 "
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 "
L123: "cluster.go:125: DaemonSet cilium "
L124: "cluster.go:125: Containers: cilium-operator "
L125: "cluster.go:125: cilium "
L126: "cluster.go:125: Cluster Pods: 0/0 managed by Cilium"
L127: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4081.3.9-n-d970ca7115): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/aa064a43-c892-4f8d-9ea8-dc16f2d5f261"
L128: "--------------------------------------------------------------------------------"
L129: "RESPONSE 200: 200 OK"
L130: "ERROR CODE: OperationPreempted"
L131: "--------------------------------------------------------------------------------"
L132: "{"
L133: "__startTime__: __2026-07-21T02:43:01.7318291+00:00__,"
L134: "__endTime__: __2026-07-21T02:44:28.5067427+00:00__,"
L135: "__status__: __Canceled__,"
L136: "__error__: {"
L137: "__code__: __OperationPreempted__,"
L138: "__message__: __Operation execution has been preempted by a more recent operation.__"
L139: "},"
L140: "__name__: __aa064a43-c892-4f8d-9ea8-dc16f2d5f261__"
L141: "}"
L142: "--------------------------------------------------------------------------------_"
L143: " "
```
🟢 ok **kubeadm.v1.34.4.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.9-n-104bd24c80): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/64a54e3c-db70-4f6b-aa36-5e4f705b9c3c"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-07-21T02:43:32.1642251+00:00__,"
L8: "__endTime__: __2026-07-21T02:56:15.1570768+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__: __64a54e3c-db70-4f6b-aa36-5e4f705b9c3c__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **kubeadm.v1.34.4.flannel.cgroupv1.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I0721 02:42:44.375625 2564 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.9"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.9"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.9"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.9"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0"
L9: "cluster.go:125: I0721 02:42:55.949869 2784 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.34.9"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-51070e94bf__ could not be reached"
L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-51070e94bf__: lookup ci-4081.3.9-n-51070e94bf 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: W0721 02:42:56.065980 2784 checks.go:827] 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.9-n-51070e94bf kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.17]"
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 2.000827779s"
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.17:6443/livez"
L53: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L54: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L55: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.961911737s"
L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.117533942s"
L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 6.501132426s"
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.9-n-51070e94bf 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.9-n-51070e94bf as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L63: "cluster.go:125: [bootstrap-token] Using token: 604zit.swl9efcsf3eraqgv"
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.17:6443 --token 604zit.swl9efcsf3eraqgv _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:1ea907591b56b7b3b632a9b12b9bdc5b217ce5c0cc161a8e53f33327a24ace6b "
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.9-n-d505c83a70): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/bdbc3219-4d5b-40d2-ab9e-3d479845c194"
L101: "--------------------------------------------------------------------------------"
L102: "RESPONSE 200: 200 OK"
L103: "ERROR CODE: OperationPreempted"
L104: "--------------------------------------------------------------------------------"
L105: "{"
L106: "__startTime__: __2026-07-21T02:43:17.5339486+00:00__,"
L107: "__endTime__: __2026-07-21T02:44:28.2677215+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__: __bdbc3219-4d5b-40d2-ab9e-3d479845c194__"
L114: "}"
L115: "--------------------------------------------------------------------------------_"
L116: " "
```
🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _cluster.go:125: I0721 04:14:48.362883 2462 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.6"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.6"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.6"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.6"
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: I0721 04:15:47.454518 2747 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.6"
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.9-n-da070283bd__ could not be reached"
L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-da070283bd__: lookup ci-4081.3.9-n-da070283bd 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: W0721 04:15:47.684093 2747 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.9-n-da070283bd kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.32]"
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 2.506316329s"
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.32: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 5.007534602s"
L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 5.864190459s"
L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.501137662s"
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.9-n-da070283bd 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.9-n-da070283bd as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L63: "cluster.go:125: [bootstrap-token] Using token: ojwcjb.b0y82ifho22ohprz"
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.32:6443 --token ojwcjb.b0y82ifho22ohprz _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:29f35c31300833f2ea67d0b369cc5fcad51cdf5e89fcf2029c47efea7aceedb5 "
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-ce7af0f6f5/?providers/Microsoft.Compute/virtualMachines/ci-4081.3.9-n-251b6afb63"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
L118: "}"
L119: "}"
L120: "--------------------------------------------------------------------------------_"
L121: " "
```
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-55520?4181e/providers/Microsoft.Compute/virtualMachines/ci-4081.3.9-n-4a4b50ffcb"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (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: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ce7?af0f6f5/providers/Microsoft.Compute/virtualMachines/ci-4081.3.9-n-3d24f8d962"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola?-cluster-image-555204181e/providers/Microsoft.Network/publicIPAddresses/ip-0cf11b06d9"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I0721 02:41:57.302057 2339 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.6"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.6"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.6"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.6"
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: I0721 02:42:10.635347 2601 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.6"
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.9-n-aa3d4379cf__ could not be reached"
L14: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-aa3d4379cf__: lookup ci-4081.3.9-n-aa3d4379cf 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: W0721 02:42:10.826091 2601 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.9-n-aa3d4379cf kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.7]"
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 1.016387491s"
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.7:6443/livez"
L53: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L54: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L55: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.014115326s"
L56: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.391450763s"
L57: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.001441251s"
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.9-n-aa3d4379cf 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.9-n-aa3d4379cf as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L63: "cluster.go:125: [bootstrap-token] Using token: b81wlc.dafygrl1j1jb907j"
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.7:6443 --token b81wlc.dafygrl1j1jb907j _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:c290d56ece98757adbbfb88b719c27aa28dff3fb2ea35fa5aa1c665143fc9048 "
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: "cluster.go:125: W0721 02:43:53.507617 2216 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration"
L101: "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"
L102: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
L103: "--- FAIL: kubeadm.v1.35.1.flannel.base/node_readiness (14.06s)"
L104: "cluster.go:145: __kubectl get nodes | grep ___ Ready___| wc -l__ failed: output , status ssh: handshake failed: read tcp 10.200.1.7:45960-_20.94.253.238:22: read: connection reset by peer"
L105: "--- FAIL: kubeadm.v1.35.1.flannel.base/nginx_deployment (0.31s)"
L106: "kubeadm.go:219: unable to deploy nginx: ssh: handshake failed: read tcp 10.200.1.7:45966-_20.94.253.238:22: read: connection reset by peer"
L107: "--- FAIL: kubeadm.v1.35.1.flannel.base/NFS_deployment (0.99s)"
L108: "kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.94.253.238:22: connect: connection refused_"
L109: " "
```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.2"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.2"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.2"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.2"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L8: "cluster.go:125: [init] Using Kubernetes version: v1.36.2"
L9: "cluster.go:125: [preflight] Running pre-flight checks"
L10: "cluster.go:125: E0721 02:43:34.349334 2690 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__"
L11: "cluster.go:125: [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet conf?ig will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-8278c60b36__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-8278c60b36__: lookup ci-4081.3.9-n-8278c60b36 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: W0721 02:43:34.553230 2690 checks.go:907] detected that the sandbox image __registry.k8s.io/pause:3.8__ of the container runtime is inconsistent with that used by kubeadm. It is rec?ommended to use __registry.k8s.io/pause:3.10.2__ as the CRI sandbox image."
L19: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L20: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L21: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L22: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.9-n-8278c60b36 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.21]"
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 582.604??s"
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.21: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 11.935629ms"
L55: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 17.076899ms"
L56: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002649716s"
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.9-n-8278c60b36 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.9-n-8278c60b36 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L62: "cluster.go:125: [bootstrap-token] Using token: woaf9x.9dw9ldt3wqankqke"
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.21:6443 --token woaf9x.9dw9ldt3wqankqke _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:6d5fd52e4f4c7f511857ca80803a7f54610e86f2c08bbd19e870ab92a1709f61 "
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: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-ima?ge-555204181e/providers/Microsoft.Network/networkInterfaces/nic-f2a34cf4e0"
L110: "--------------------------------------------------------------------------------"
L111: "RESPONSE 409: 409 Conflict"
L112: "ERROR CODE: ResourceGroupBeingDeleted"
L113: "--------------------------------------------------------------------------------"
L114: "{"
L115: "__error__: {"
L116: "__code__: __ResourceGroupBeingDeleted__,"
L117: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L118: "}"
L119: "}"
L120: "--------------------------------------------------------------------------------_"
L121: " "
```
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.2"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.2"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.2"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.2"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L8: "cluster.go:125: [init] Using Kubernetes version: v1.36.2"
L9: "cluster.go:125: [preflight] Running pre-flight checks"
L10: "cluster.go:125: E0721 02:42:46.080511 2692 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__"
L11: "cluster.go:125: [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet conf?ig will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-7c85b0cac1__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-7c85b0cac1__: lookup ci-4081.3.9-n-7c85b0cac1 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: W0721 02:42:46.191350 2692 checks.go:907] detected that the sandbox image __registry.k8s.io/pause:3.8__ of the container runtime is inconsistent with that used by kubeadm. It is rec?ommended to use __registry.k8s.io/pause:3.10.2__ as the CRI sandbox image."
L19: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L20: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L21: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L22: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.9-n-7c85b0cac1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.32]"
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 665.963??s"
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.32:6443/livez"
L52: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L53: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 9.50952ms"
L55: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 11.80409ms"
L56: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002554969s"
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.9-n-7c85b0cac1 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.9-n-7c85b0cac1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L62: "cluster.go:125: [bootstrap-token] Using token: qgm6qn.qdoe9mx1jxaa6v2q"
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.32:6443 --token qgm6qn.qdoe9mx1jxaa6v2q _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:c7c73306f3d478f9f84991dfabd187295f08ce731198680eb0d3755126bdbe44 "
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 "
L123: "cluster.go:125: DaemonSet cilium "
L124: "cluster.go:125: Containers: cilium "
L125: "cluster.go:125: cilium-operator "
L126: "cluster.go:125: Cluster Pods: 0/0 managed by Cilium"
L127: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-555204181e/?providers/Microsoft.Compute/virtualMachines/ci-4081.3.9-n-43fadfc5ac"
L128: "--------------------------------------------------------------------------------"
L129: "RESPONSE 409: 409 Conflict"
L130: "ERROR CODE: OperationNotAllowed"
L131: "--------------------------------------------------------------------------------"
L132: "{"
L133: "__error__: {"
L134: "__code__: __OperationNotAllowed__,"
L135: "__message__: __Operation could not be completed as it results in exceeding approved standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests__"
L136: "}"
L137: "}"
L138: "--------------------------------------------------------------------------------_"
L139: " "
```
🟢 ok **kubeadm.v1.36.1.flannel.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: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ce7?af0f6f5/providers/Microsoft.Compute/virtualMachines/ci-4081.3.9-n-df5d4ed58e"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.2"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.2"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.2"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.2"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L8: "cluster.go:125: [init] Using Kubernetes version: v1.36.2"
L9: "cluster.go:125: [preflight] Running pre-flight checks"
L10: "cluster.go:125: E0721 02:42:06.296901 2661 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__"
L11: "cluster.go:125: [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet conf?ig will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-44c28335b1__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4081.3.9-n-44c28335b1__: lookup ci-4081.3.9-n-44c28335b1 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: W0721 02:42:06.467671 2661 checks.go:907] detected that the sandbox image __registry.k8s.io/pause:3.8__ of the container runtime is inconsistent with that used by kubeadm. It is rec?ommended to use __registry.k8s.io/pause:3.10.2__ as the CRI sandbox image."
L19: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L20: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L21: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L22: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4081.3.9-n-44c28335b1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.22]"
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 93.883733ms"
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.22: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 11.41906ms"
L55: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 13.39907ms"
L56: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.501674863s"
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.9-n-44c28335b1 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.9-n-44c28335b1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L62: "cluster.go:125: [bootstrap-token] Using token: xobbx5.zlqy1p30d5sne101"
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.22:6443 --token xobbx5.zlqy1p30d5sne101 _"
L93: "cluster.go:125: --discovery-token-ca-cert-hash sha256:744fdad7adf32bd76a647cfb8c30a96871928d75c0992f883e80698af86f0f80 "
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: "cluster.go:125: W0721 02:43:50.310478 2203 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration"
L101: "cluster.go:125: E0721 02:43:50.320248 2203 remote_runtime.go:1177] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__"
L102: "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"
L103: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
L104: "cluster.go:125: W0721 02:43:50.473015 2203 utils.go:69] The recommended value for __bindAddress__ in __KubeProxyConfiguration__ is: ::; the provided value is: 0.0.0.0"
L105: "--- FAIL: kubeadm.v1.36.1.flannel.base/node_readiness (14.39s)"
L106: "cluster.go:145: __kubectl get nodes | grep ___ Ready___| wc -l__ failed: output , status dial tcp 20.114.57.196:22: connect: connection refused"
L107: "--- FAIL: kubeadm.v1.36.1.flannel.base/nginx_deployment (0.99s)"
L108: "kubeadm.go:219: unable to deploy nginx: dial tcp 20.114.57.196:22: connect: connection refused"
L109: "--- FAIL: kubeadm.v1.36.1.flannel.base/NFS_deployment (0.99s)"
L110: "kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.114.57.196:22: connect: connection refused_"
L111: " "
```
🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (1)
🟢 ok **sysext.disable-containerd**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-5552?04181e/providers/Microsoft.Network/publicIPAddresses/ip-887a9b511a"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 409: 409 Conflict"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__error__: {"
L8: "__code__: __ResourceGroupBeingDeleted__,"
L9: "__message__: __The resource group _kola-cluster-image-555204181e_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 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-555204181e/providers/Mic?rosoft.Compute/virtualMachines/ci-4081.3.9-n-6b0fdc3670"
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 standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Curren?t 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 req?uest for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command?%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22propertie?s%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ???Details??? section for deployment to succee?d. 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)