### Test report for 4757.2.2 / arm64
**Platforms tested** : azure
🟢 ok **azure.nvme-friendly-naming # SKIP**; Succeeded: azure (1)
🟢 ok **bpf.ig**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " _bpf.ig/ig (68.48s)"
L2: "ig.go:57: creating node: PollUntilDone(ci-4757.2.2-a-40518c88c5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/oper?ations/9bf58286-bf3e-4022-88fb-eee7e473c2f5"
L3: "--------------------------------------------------------------------------------"
L4: "RESPONSE 200: 200 OK"
L5: "ERROR CODE: AllocationFailed"
L6: "--------------------------------------------------------------------------------"
L7: "{"
L8: "__startTime__: __2026-10-21T16:28:17.2099463+00:00__,"
L9: "__endTime__: __2026-10-21T16:28:21.2434102+00:00__,"
L10: "__status__: __Failed__,"
L11: "__error__: {"
L12: "__code__: __AllocationFailed__,"
L13: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L14: "},"
L15: "__name__: __9bf58286-bf3e-4022-88fb-eee7e473c2f5__"
L16: "}"
L17: "--------------------------------------------------------------------------------_"
L18: " "
```
Diagnostic output for azure, run 1
```
L1: " _bpf.ig/ig (0.20s)"
L2: "ig.go:57: creating node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Networ?k/publicIPAddresses/ip-da2b2f17ec"
L3: "--------------------------------------------------------------------------------"
L4: "RESPONSE 409: 409 Conflict"
L5: "ERROR CODE: ResourceGroupBeingDeleted"
L6: "--------------------------------------------------------------------------------"
L7: "{"
L8: "__error__: {"
L9: "__code__: __ResourceGroupBeingDeleted__,"
L10: "__message__: __The resource group _kola-cluster-image-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L11: "}"
L12: "}"
L13: "--------------------------------------------------------------------------------_"
L14: " "
```
🟢 ok **cl.basic**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.basic**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.multipart-mime**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-875a36269c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/64d43e1c-5ab9-4c9e-8329-013a5af46e17"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:55:10.3084185+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:32.9241441+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__: __64d43e1c-5ab9-4c9e-8329-013a5af46e17__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 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:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-bb28fa6214): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/9aba8875-91df-4dc8-be84-4259df9d66f1"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:55:05.278697+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:32.8093845+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__: __9aba8875-91df-4dc8-be84-4259df9d66f1__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.etcd-member.etcdctlv3**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-bb79997cd7): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/73f92fee-17d4-4779-bd98-52cc74ec493c"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:53:55.7224526+00:00__,"
L8: "__endTime__: __2026-10-21T14:53:59.9299741+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __73f92fee-17d4-4779-bd98-52cc74ec493c__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.etcd-member.v2-backup-restore**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-8aca7cc558): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/b9631250-0f28-4ff1-84b8-51b095918851"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:53:56.7464436+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:00.3699147+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __b9631250-0f28-4ff1-84b8-51b095918851__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.flannel.vxlan**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-88b2b011b5"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.ignition.kargs**; Succeeded: azure (1)
🟢 ok **cl.ignition.luks**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-ddad7bd9c9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/ac01070b-b28e-4f0c-9358-0af9d58bef50"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:05.5979081+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:09.5829315+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __ac01070b-b28e-4f0c-9358-0af9d58bef50__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.misc.empty**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-e1c14c4933): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/63c845d9-f924-44ec-b59c-caa760efe76d"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:26:48.9045363+00:00__,"
L8: "__endTime__: __2026-10-21T16:26:53.9696835+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __63c845d9-f924-44ec-b59c-caa760efe76d__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-aa5de34f06): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/285ed2d8-9cac-4551-8bd7-2a9e8c071a5e"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:55:11.1831268+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:32.8093845+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__: __285ed2d8-9cac-4551-8bd7-2a9e8c071a5e__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.symlink**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-21c12976d1"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.ignition.translation**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.btrfsroot**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-17177447ad): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/71b3afe8-12ac-4d2f-8ac8-53655156e52b"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:55:13.6117248+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:15.5581679+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __ResourceGroupBeingDeleted__,"
L12: "__message__: __The resource group _KOLA-CLUSTER-IMAGE-ADA2AA83E1_ is in deprovisioning state and cannot perform this operation. Target: _/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGr?oups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Compute/disks/ci-4757.2.2-a-17177447ad_OsDisk_1_6e7dfb9d0dd94cd7bcd750982904b4b1_.__"
L13: "},"
L14: "__name__: __71b3afe8-12ac-4d2f-8ac8-53655156e52b__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.v1.ext4root**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-105b6a4420"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.ignition.v1.groups**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-35f269eeef): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/ed82392d-a90d-47e7-8b70-10e1c7099815"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:02.1835789+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:05.7718562+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __ed82392d-a90d-47e7-8b70-10e1c7099815__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.v1.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.once**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-eef6cc2575): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/6233c6ae-90c1-4158-b120-3cdc8369a54d"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:43.5317645+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:39.5417814+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__: __6233c6ae-90c1-4158-b120-3cdc8369a54d__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.v1.users**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-548874e66e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/0eb2a78a-314c-4ef6-912e-80296d690f88"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:33.4841609+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:38.290917+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __0eb2a78a-314c-4ef6-912e-80296d690f88__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.v1.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.ext4root**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.ext4checkexisting**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-769c3de443"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.ignition.v2_1.swap**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-0fad9ab348): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/bd554aae-e1be-41d3-84ce-5a9ba4abf395"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:43.5941657+00:00__,"
L8: "__endTime__: __2026-10-21T14:57:00.0155577+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__: __bd554aae-e1be-41d3-84ce-5a9ba4abf395__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.ignition.v2_1.vfat**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-fb6ab7c185): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/9de5b0ce-d16b-4d01-b6ed-d653f14b1234"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:33.4822917+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:37.5340235+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __9de5b0ce-d16b-4d01-b6ed-d653f14b1234__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-1aab4a8809): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/fc494ac7-2f92-43e5-86c4-d8c2683578e2"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: ResourceGroupBeingDeleted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:55:13.9573807+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:15.9517549+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __ResourceGroupBeingDeleted__,"
L12: "__message__: __The resource group _KOLA-CLUSTER-IMAGE-ADA2AA83E1_ is in deprovisioning state and cannot perform this operation. Target: _/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGr?oups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Compute/disks/ci-4757.2.2-a-1aab4a8809_OsDisk_1_f1e99818dd3b45239cd894b8da994ab4_.__"
L13: "},"
L14: "__name__: __fc494ac7-2f92-43e5-86c4-d8c2683578e2__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.internet**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-7db9a1e27b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/f32cb0f6-d278-447a-a046-4868ea6fb29d"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:13.0655128+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:16.9197444+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __f32cb0f6-d278-447a-a046-4868ea6fb29d__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.locksmith.cluster**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-9d00f36617): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/58ababa4-c090-42f9-ae59-f97557250055"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:04.9193326+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:08.5941346+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __58ababa4-c090-42f9-ae59-f97557250055__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.metadata.azure**; Succeeded: azure (1)
🟢 ok **cl.network.initramfs.second-boot**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-c910e05905"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.network.iptables**; Succeeded: azure (1)
🟢 ok **cl.network.nftables**; Succeeded: azure (1)
🟢 ok **cl.network.wireguard**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-48e4778ddb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/39ac5f00-9995-4194-bb70-d5f3b26f7819"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:23.7732526+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:27.9941229+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __39ac5f00-9995-4194-bb70-d5f3b26f7819__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.osreset.ignition-rerun**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-3ca940b74b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/9ba49015-8790-4ac6-9762-229e3a9ed623"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:55.1198999+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:59.0054321+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __9ba49015-8790-4ac6-9762-229e3a9ed623__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-136c71b4f9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/39ab5b42-8b0c-4ada-b191-b00e3e698324"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:02.2001654+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:12.1114883+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __39ab5b42-8b0c-4ada-b191-b00e3e698324__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **cl.overlay.cleanup**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-be63c6a9b6"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.swap_activation**; Succeeded: azure (1)
🟢 ok **cl.toolbox.dnf-install**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-b6efbc5f53"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 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 20.98.90.104:22: i/o ?timeout, systemctl list-jobs returned stdout: ____, stderr: ____, err: dial tcp 20.98.90.104:22: i/o timeout_"
L2: " "
```
🟢 ok **cl.update.reboot**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _update.go:91: couldn_t reboot: machine __ci-4757.2.2-a-a0be03e32c__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.125.16.93:22: i/o timeout_"
L2: " "
```
🟢 ok **cl.users.shells**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-3f68a32540"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **cl.verity**; Succeeded: azure (1)
🟢 ok **coreos.auth.verify**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-d5aeed7b1a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/4ff8950d-bafb-431f-9805-9b95d2b50346"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:14.4523316+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:18.1530781+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __4ff8950d-bafb-431f-9805-9b95d2b50346__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **coreos.ignition.groups**; Succeeded: azure (1)
🟢 ok **coreos.ignition.once**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-6a04daf0a8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/1ee3e101-8b12-47de-9725-5c657393e4f7"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:52.1136395+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:55.9745181+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __1ee3e101-8b12-47de-9725-5c657393e4f7__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-0660e03918"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **coreos.ignition.resource.local**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-ff946920ee"
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-ada2aa83e1_ 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 (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-169f7058c3): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/000a5856-ccb3-43f1-9dc9-5e75d4c364a1"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:54.5832743+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:59.7001908+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __000a5856-ccb3-43f1-9dc9-5e75d4c364a1__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-de464a4e78"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **coreos.ignition.ssh.key**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-3b8b8ca809"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **coreos.ignition.systemd.enable-service**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-419221536f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/8298e15e-128f-47fc-bf8c-9ab0f6e6d011"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:44.6195173+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:48.3476314+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __8298e15e-128f-47fc-bf8c-9ab0f6e6d011__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-55305f2c69"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **coreos.locksmith.reboot**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded_"
L2: " "
```
🟢 ok **coreos.locksmith.tls**; Succeeded: azure (1)
🟢 ok **coreos.selinux.boolean**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-43548a421e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/322d32e0-c080-453c-84a1-b44d60227aef"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:20.8499426+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:25.2899257+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __322d32e0-c080-453c-84a1-b44d60227aef__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **coreos.selinux.enforce**; Succeeded: azure (1)
🟢 ok **coreos.tls.fetch-urls**; Succeeded: azure (1)
🟢 ok **coreos.update.badusr**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-5eb8b2f28a"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **docker.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-dd1f052885): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/eb9d9314-5efd-4b09-ad41-418dce49acb0"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:53:05.3294251+00:00__,"
L8: "__endTime__: __2026-10-21T14:53:09.5623345+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __eb9d9314-5efd-4b09-ad41-418dce49acb0__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 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 (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-83144e2f6d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/f1c81233-f0a7-4a36-9887-766d4c6c4eec"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:53:35.6433359+00:00__,"
L8: "__endTime__: __2026-10-21T14:53:39.8161631+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __f1c81233-f0a7-4a36-9887-766d4c6c4eec__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **docker.network-openbsd-nc**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1?/providers/Microsoft.Network/networkInterfaces/nic-987926d689"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **docker.selinux**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-ed63d7141a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/467f18fc-389c-4eba-9c23-61654538654b"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:53:35.9586847+00:00__,"
L8: "__endTime__: __2026-10-21T14:53:39.8085313+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __467f18fc-389c-4eba-9c23-61654538654b__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **docker.userns**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.35.1.calico.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 etcd node: PollUntilDone(ci-4757.2.2-a-0982f0594f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/d200b7e0-a6a2-4a5c-81d3-ea7d4ca8c06a"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:20.3859483+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:24.8478228+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __d200b7e0-a6a2-4a5c-81d3-ea7d4ca8c06a__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I1021 14:52:38.660825 2738 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1"
L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0"
L9: "cluster.go:125: I1021 14:52:47.787282 3109 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.9"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-cc4c460fd2__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-cc4c460fd2__: lookup ci-4757.2.2-a-cc4c460fd2 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: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-cc4c460fd2 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.15]"
L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 502.318222ms"
L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.15:6443/livez"
L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.51480727s"
L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.744279247s"
L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.501815052s"
L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-cc4c460fd2 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-cc4c460fd2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L61: "cluster.go:125: [bootstrap-token] Using token: mw5rem.ivfssnxw0lwb13x6"
L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L64: "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"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L67: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L68: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L69: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L70: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L71: "cluster.go:125: "
L72: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L73: "cluster.go:125: "
L74: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L75: "cluster.go:125: "
L76: "cluster.go:125: mkdir -p $HOME/.kube"
L77: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L78: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L79: "cluster.go:125: "
L80: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L81: "cluster.go:125: "
L82: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L83: "cluster.go:125: "
L84: "cluster.go:125: You should now deploy a pod network to the cluster."
L85: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L86: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L87: "cluster.go:125: "
L88: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L89: "cluster.go:125: "
L90: "cluster.go:125: kubeadm join 10.0.0.15:6443 --token mw5rem.ivfssnxw0lwb13x6 _"
L91: "cluster.go:125: --discovery-token-ca-cert-hash sha256:8389284b84f9892f5eeb6a749de1c9de64dea1300c4b2f0b260b1d0e81a7320a "
L92: "cluster.go:125: namespace/tigera-operator created"
L93: "cluster.go:125: serviceaccount/tigera-operator created"
L94: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created"
L95: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created"
L96: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created"
L97: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created"
L98: "cluster.go:125: deployment.apps/tigera-operator created"
L99: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L100: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L102: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L103: "cluster.go:125: installation.operator.tigera.io/default created"
L104: "cluster.go:125: apiserver.operator.tigera.io/default created"
L105: "cluster.go:125: goldmane.operator.tigera.io/default created"
L106: "cluster.go:125: whisker.operator.tigera.io/default created"
L107: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-b5e45eea45): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/b80767ab-7dda-4a2a-b32b-435aa91a8f7a"
L108: "--------------------------------------------------------------------------------"
L109: "RESPONSE 200: 200 OK"
L110: "ERROR CODE: AllocationFailed"
L111: "--------------------------------------------------------------------------------"
L112: "{"
L113: "__startTime__: __2026-10-21T14:53:18.7798548+00:00__,"
L114: "__endTime__: __2026-10-21T14:53:25.1057755+00:00__,"
L115: "__status__: __Failed__,"
L116: "__error__: {"
L117: "__code__: __AllocationFailed__,"
L118: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L119: "},"
L120: "__name__: __b80767ab-7dda-4a2a-b32b-435aa91a8f7a__"
L121: "}"
L122: "--------------------------------------------------------------------------------_"
L123: " "
```
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.2-a-710c41162e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/d6b95fc7-5c00-4562-aada-bf01bb6a8d3e"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:55:03.6656462+00:00__,"
L8: "__endTime__: __2026-10-21T14:55:33.0352223+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__: __d6b95fc7-5c00-4562-aada-bf01bb6a8d3e__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4757.2.2-a-dca1b5a882): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/westus2/operations/462f0fea-c340-4004-8bf9-e77374fc291f"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:52:45.3295118+00:00__,"
L8: "__endTime__: __2026-10-21T14:52:49.9585549+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __462f0fea-c340-4004-8bf9-e77374fc291f__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I1021 14:52:37.177095 2722 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L9: "cluster.go:125: I1021 14:52:46.341259 3123 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-26a109c965__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-26a109c965__: lookup ci-4757.2.2-a-26a109c965 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: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-26a109c965 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.6]"
L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 555.118??s"
L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.6:6443/livez"
L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.968759ms"
L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 8.394125ms"
L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002402768s"
L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-26a109c965 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-26a109c965 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L61: "cluster.go:125: [bootstrap-token] Using token: 9bsbio.62868o5s2dtr65p2"
L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L64: "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"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L67: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
L68: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L69: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L70: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L71: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L72: "cluster.go:125: "
L73: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L74: "cluster.go:125: "
L75: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L76: "cluster.go:125: "
L77: "cluster.go:125: mkdir -p $HOME/.kube"
L78: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L79: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L80: "cluster.go:125: "
L81: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L82: "cluster.go:125: "
L83: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L84: "cluster.go:125: "
L85: "cluster.go:125: You should now deploy a pod network to the cluster."
L86: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L87: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L88: "cluster.go:125: "
L89: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L90: "cluster.go:125: "
L91: "cluster.go:125: kubeadm join 10.0.0.6:6443 --token 9bsbio.62868o5s2dtr65p2 _"
L92: "cluster.go:125: --discovery-token-ca-cert-hash sha256:25fde63755a442665d7414ca87752f4604d0170473d75757cf5d5141fb766783 "
L93: "cluster.go:125: namespace/tigera-operator created"
L94: "cluster.go:125: serviceaccount/tigera-operator created"
L95: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created"
L96: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created"
L97: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created"
L98: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created"
L99: "cluster.go:125: deployment.apps/tigera-operator created"
L100: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L102: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L103: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L104: "cluster.go:125: installation.operator.tigera.io/default created"
L105: "cluster.go:125: apiserver.operator.tigera.io/default created"
L106: "cluster.go:125: goldmane.operator.tigera.io/default created"
L107: "cluster.go:125: whisker.operator.tigera.io/default created"
L108: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-66cdefb781): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/8276a5d5-6d78-4a09-aae8-2654ca2bc3cc"
L109: "--------------------------------------------------------------------------------"
L110: "RESPONSE 200: 200 OK"
L111: "ERROR CODE: AllocationFailed"
L112: "--------------------------------------------------------------------------------"
L113: "{"
L114: "__startTime__: __2026-10-21T14:53:11.7940767+00:00__,"
L115: "__endTime__: __2026-10-21T14:53:15.7039393+00:00__,"
L116: "__status__: __Failed__,"
L117: "__error__: {"
L118: "__code__: __AllocationFailed__,"
L119: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L120: "},"
L121: "__name__: __8276a5d5-6d78-4a09-aae8-2654ca2bc3cc__"
L122: "}"
L123: "--------------------------------------------------------------------------------_"
L124: " "
```
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _cluster.go:125: I1021 16:29:02.526448 2952 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L9: "cluster.go:125: I1021 16:29:11.651557 3171 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-85dad49ce2__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-85dad49ce2__: lookup ci-4757.2.2-a-85dad49ce2 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: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-85dad49ce2 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.37]"
L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 834.708??s"
L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.37:6443/livez"
L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.741327ms"
L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 9.272955ms"
L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.000959281s"
L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-85dad49ce2 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-85dad49ce2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L61: "cluster.go:125: [bootstrap-token] Using token: kt9u9b.jdhep25dolvrtbvh"
L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L64: "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"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L67: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
L68: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L69: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L70: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L71: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L72: "cluster.go:125: "
L73: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L74: "cluster.go:125: "
L75: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L76: "cluster.go:125: "
L77: "cluster.go:125: mkdir -p $HOME/.kube"
L78: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L79: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L80: "cluster.go:125: "
L81: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L82: "cluster.go:125: "
L83: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L84: "cluster.go:125: "
L85: "cluster.go:125: You should now deploy a pod network to the cluster."
L86: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L87: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L88: "cluster.go:125: "
L89: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L90: "cluster.go:125: "
L91: "cluster.go:125: kubeadm join 10.0.0.37:6443 --token kt9u9b.jdhep25dolvrtbvh _"
L92: "cluster.go:125: --discovery-token-ca-cert-hash sha256:321ac6fce6d62153ea925e73c2be4a6dbc8ddc223c46937e7fb92d9c4b5b63ba "
L93: "cluster.go:125: i Using Cilium version 1.12.5"
L94: "cluster.go:125: ? Auto-detected cluster name: kubernetes"
L95: "cluster.go:125: ? Auto-detected datapath mode: tunnel"
L96: "cluster.go:125: ? Auto-detected kube-proxy has been installed"
L97: "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"
L98: "cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret"
L99: "cluster.go:125: ? Created CA in secret cilium-ca"
L100: "cluster.go:125: ? Generating certificates for Hubble..."
L101: "cluster.go:125: ? Creating Service accounts..."
L102: "cluster.go:125: ? Creating Cluster roles..."
L103: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..."
L104: "cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true"
L105: "cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17"
L106: "cluster.go:125: ? Creating Agent DaemonSet..."
L107: "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"
L108: "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"
L109: "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"
L110: "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"
L111: "cluster.go:125: ? Creating Operator Deployment..."
L112: "cluster.go:125: ? Waiting for Cilium to be installed and ready..."
L113: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health"
L114: "cluster.go:125: ?[33m /??_"
L115: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m Cilium: ?[32mOK?[0m"
L116: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m Operator: ?[32mOK?[0m"
L117: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m Hubble: ?[36mdisabled?[0m"
L118: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m ClusterMesh: ?[36mdisabled?[0m"
L119: "cluster.go:125: ?[34m ___/"
L120: "cluster.go:125: ?[0m"
L121: "cluster.go:125: Deployment cilium-operator "
L122: "cluster.go:125: DaemonSet cilium "
L123: "cluster.go:125: Containers: cilium "
L124: "cluster.go:125: cilium-operator "
L125: "cluster.go:125: Cluster Pods: 0/0 managed by Cilium"
L126: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-44a6fbbe57): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/8d9fa910-784f-45cf-8a87-c6d59c1328c2"
L127: "--------------------------------------------------------------------------------"
L128: "RESPONSE 200: 200 OK"
L129: "ERROR CODE: AllocationFailed"
L130: "--------------------------------------------------------------------------------"
L131: "{"
L132: "__startTime__: __2026-10-21T16:29:25.0640225+00:00__,"
L133: "__endTime__: __2026-10-21T16:29:29.4266054+00:00__,"
L134: "__status__: __Failed__,"
L135: "__error__: {"
L136: "__code__: __AllocationFailed__,"
L137: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L138: "},"
L139: "__name__: __8d9fa910-784f-45cf-8a87-c6d59c1328c2__"
L140: "}"
L141: "--------------------------------------------------------------------------------_"
L142: " "
```
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-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-6c4a940b9d"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: I1021 14:52:43.972082 2680 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L9: "cluster.go:125: I1021 14:52:55.243053 3086 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-67b4a5a51d__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-67b4a5a51d__: lookup ci-4757.2.2-a-67b4a5a51d 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: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-67b4a5a51d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.9]"
L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 688.944??s"
L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.9:6443/livez"
L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L53: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.622089ms"
L54: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.053444ms"
L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002026409s"
L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-67b4a5a51d as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-67b4a5a51d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L61: "cluster.go:125: [bootstrap-token] Using token: na266k.mc9nalfs8piytk2e"
L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L64: "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"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L67: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
L68: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L69: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L70: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L71: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L72: "cluster.go:125: "
L73: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L74: "cluster.go:125: "
L75: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L76: "cluster.go:125: "
L77: "cluster.go:125: mkdir -p $HOME/.kube"
L78: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L79: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L80: "cluster.go:125: "
L81: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L82: "cluster.go:125: "
L83: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L84: "cluster.go:125: "
L85: "cluster.go:125: You should now deploy a pod network to the cluster."
L86: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L87: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L88: "cluster.go:125: "
L89: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L90: "cluster.go:125: "
L91: "cluster.go:125: kubeadm join 10.0.0.9:6443 --token na266k.mc9nalfs8piytk2e _"
L92: "cluster.go:125: --discovery-token-ca-cert-hash sha256:4cc5b3e9f5eff2b0387d5fd3fb50ca18f26cee796c07d19ce3f7246464abbce9 "
L93: "cluster.go:125: namespace/kube-flannel created"
L94: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created"
L95: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created"
L96: "cluster.go:125: serviceaccount/flannel created"
L97: "cluster.go:125: configmap/kube-flannel-cfg created"
L98: "cluster.go:125: daemonset.apps/kube-flannel-ds created"
L99: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-ca34c5dd5f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/df581dc3-e1db-4b6d-8c0a-3ee758887e51"
L100: "--------------------------------------------------------------------------------"
L101: "RESPONSE 200: 200 OK"
L102: "ERROR CODE: AllocationFailed"
L103: "--------------------------------------------------------------------------------"
L104: "{"
L105: "__startTime__: __2026-10-21T14:53:08.161515+00:00__,"
L106: "__endTime__: __2026-10-21T14:53:12.013674+00:00__,"
L107: "__status__: __Failed__,"
L108: "__error__: {"
L109: "__code__: __AllocationFailed__,"
L110: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L111: "},"
L112: "__name__: __df581dc3-e1db-4b6d-8c0a-3ee758887e51__"
L113: "}"
L114: "--------------------------------------------------------------------------------_"
L115: " "
```
🟢 ok **kubeadm.v1.37.0.calico.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 etcd node: PollUntilDone(ci-4757.2.2-a-8f3096f2e0): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/8138af9e-7d4c-4c75-a6ab-2067c7913ed0"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:16.5488226+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:20.8067692+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __8138af9e-7d4c-4c75-a6ab-2067c7913ed0__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0"
L8: "cluster.go:125: [init] Using Kubernetes version: v1.37.1"
L9: "cluster.go:125: [preflight] Running pre-flight checks"
L10: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-f97d4e6e6c__ could not be reached"
L11: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.2-a-f97d4e6e6c__: lookup ci-4757.2.2-a-f97d4e6e6c on 168.63.129.16:53: no such host"
L12: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
L13: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
L14: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
L15: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
L16: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L17: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L18: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L19: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-f97d4e6e6c kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.21]"
L20: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L21: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L22: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L23: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L24: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L28: "cluster.go:125: [certs] Generating __sa__ key and public key"
L29: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L30: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L31: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L32: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L35: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L36: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L37: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L39: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L40: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L41: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L43: "cluster.go:125: [kubelet-start] Starting the kubelet"
L44: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L45: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L46: "cluster.go:125: [kubelet-check] The kubelet is healthy after 770.761??s"
L47: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L48: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.21:6443/livez"
L49: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L50: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L51: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.172241ms"
L52: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.127152ms"
L53: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.50183742s"
L54: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L55: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L56: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L57: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-f97d4e6e6c as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L58: "cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-f97d4e6e6c as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L59: "cluster.go:125: [bootstrap-token] Using token: v7p2zc.sumzi0ywrvfywv65"
L60: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L61: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L62: "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"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
L66: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L67: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L68: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L69: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L70: "cluster.go:125: "
L71: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L72: "cluster.go:125: "
L73: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L74: "cluster.go:125: "
L75: "cluster.go:125: mkdir -p $HOME/.kube"
L76: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L77: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L78: "cluster.go:125: "
L79: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L80: "cluster.go:125: "
L81: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L82: "cluster.go:125: "
L83: "cluster.go:125: You should now deploy a pod network to the cluster."
L84: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L85: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L86: "cluster.go:125: "
L87: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L88: "cluster.go:125: "
L89: "cluster.go:125: kubeadm join 10.0.0.21:6443 --token v7p2zc.sumzi0ywrvfywv65 _"
L90: "cluster.go:125: --discovery-token-ca-cert-hash sha256:9a294a57ecfb73d9dcbd300f809801d97d02d79afee81051d0df591bc069e8ed "
L91: "cluster.go:125: namespace/tigera-operator created"
L92: "cluster.go:125: serviceaccount/tigera-operator created"
L93: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created"
L94: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created"
L95: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created"
L96: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created"
L97: "cluster.go:125: deployment.apps/tigera-operator created"
L98: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L99: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L100: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L102: "cluster.go:125: installation.operator.tigera.io/default created"
L103: "cluster.go:125: apiserver.operator.tigera.io/default created"
L104: "cluster.go:125: goldmane.operator.tigera.io/default created"
L105: "cluster.go:125: whisker.operator.tigera.io/default created"
L106: "kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-db0296184f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/2c7dc7f2-f242-44b9-a9f6-a2a72fef6c75"
L107: "--------------------------------------------------------------------------------"
L108: "RESPONSE 200: 200 OK"
L109: "ERROR CODE: AllocationFailed"
L110: "--------------------------------------------------------------------------------"
L111: "{"
L112: "__startTime__: __2026-10-21T14:54:01.8106496+00:00__,"
L113: "__endTime__: __2026-10-21T14:54:06.4123093+00:00__,"
L114: "__status__: __Failed__,"
L115: "__error__: {"
L116: "__code__: __AllocationFailed__,"
L117: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L118: "},"
L119: "__name__: __2c7dc7f2-f242-44b9-a9f6-a2a72fef6c75__"
L120: "}"
L121: "--------------------------------------------------------------------------------_"
L122: " "
```
🟢 ok **kubeadm.v1.37.0.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 etcd node: PollUntilDone(ci-4757.2.2-a-3cbb0008ec): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/fbde2732-ff44-4c85-9d80-6a2a12601abf"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:49.6489213+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:53.8985432+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __fbde2732-ff44-4c85-9d80-6a2a12601abf__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1"
L5: "kubeadm.go:197: unable to setup cluster: unable to run master script: wait: remote command exited without exit status or exit signal_"
L6: " "
```
🟢 ok **kubeadm.v1.37.0.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 master node: PollUntilDone(ci-4757.2.2-a-f6572a734e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/westus2/operations/179b245d-406e-461d-b43d-e8a22b40c02a"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:53:02.7015886+00:00__,"
L8: "__endTime__: __2026-10-21T14:53:06.5794435+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __179b245d-406e-461d-b43d-e8a22b40c02a__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-798965549d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/13f2b838-a721-45ca-9c4f-de4b3af92291"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T16:27:42.3968075+00:00__,"
L8: "__endTime__: __2026-10-21T16:27:46.5919396+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __13f2b838-a721-45ca-9c4f-de4b3af92291__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2?aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-385ecaca95"
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-ada2aa83e1_ is in deprovisioning state and cannot perform this operation.__"
L10: "}"
L11: "}"
L12: "--------------------------------------------------------------------------------_"
L13: " "
```
🟢 ok **sysext.disable-containerd**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-474391c3de): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/b98900c9-88c5-44ca-a40d-3b8829e098e1"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:52:46.8877216+00:00__,"
L8: "__endTime__: __2026-10-21T14:52:50.6467282+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __b98900c9-88c5-44ca-a40d-3b8829e098e1__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **sysext.disable-docker**; Succeeded: azure (2); Failed: azure (1)
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-04f138464c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/4869b1cd-c370-4e9e-913d-2723b978422e"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:51:16.1327825+00:00__,"
L8: "__endTime__: __2026-10-21T14:51:21.7056146+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __4869b1cd-c370-4e9e-913d-2723b978422e__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 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:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-db2a1bd81a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/f910fa74-94dd-4c91-87f4-3cea81954634"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: AllocationFailed"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-21T14:54:20.5255634+00:00__,"
L8: "__endTime__: __2026-10-21T14:54:25.3246418+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __AllocationFailed__,"
L12: "__message__: __Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-gu?idance__"
L13: "},"
L14: "__name__: __f910fa74-94dd-4c91-87f4-3cea81954634__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)