### Test report for 4757.2.1+nightly-20261019-2100 / arm64 **Platforms tested** : azure ❌ not ok **azure.nvme-friendly-naming**; Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-fe579eebc7): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/3eff9e2b-38fb-4b40-b4c5-9ece97afd49c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:01.9127159+00:00__," L8: "__endTime__: __2026-10-19T23:34:05.8461665+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__: __3eff9e2b-38fb-4b40-b4c5-9ece97afd49c__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **azure.nvme-friendly-naming # SKIP**; Succeeded: azure (2, 3, 4, 5) 🟢 ok **bpf.ig**; Succeeded: azure (1) 🟢 ok **cl.basic**; Succeeded: azure (1) 🟢 ok **cl.cloudinit.basic**; Succeeded: azure (1) 🟢 ok **cl.cloudinit.multipart-mime**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-2dced5452d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/b67e730b-6c5c-4849-9fc7-e18e12f54c53" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:05.1066282+00:00__," L8: "__endTime__: __2026-10-19T23:34:09.0633984+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__: __b67e730b-6c5c-4849-9fc7-e18e12f54c53__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.cloudinit.script**; 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.1-n-9a9279efbd): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/e653b216-a1c2-4386-9b95-df769ae83ba6" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:01.5391839+00:00__," L8: "__endTime__: __2026-10-19T23:34:06.2984048+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__: __e653b216-a1c2-4386-9b95-df769ae83ba6__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.etcd-member.discovery**; Succeeded: azure (1) 🟢 ok **cl.etcd-member.etcdctlv3**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-f63f4b2695): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/c5b365a6-aeef-4e3c-a95e-73d5012091fd" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.7295057+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.608657+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__: __c5b365a6-aeef-4e3c-a95e-73d5012091fd__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.etcd-member.v2-backup-restore**; Succeeded: azure (1) 🟢 ok **cl.flannel.vxlan**; Succeeded: azure (1) 🟢 ok **cl.ignition.kargs**; Succeeded: azure (1) 🟢 ok **cl.ignition.luks**; Succeeded: azure (1) 🟢 ok **cl.ignition.misc.empty**; Succeeded: azure (1) 🟢 ok **cl.ignition.symlink**; Succeeded: azure (1) 🟢 ok **cl.ignition.translation**; 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.1-n-edd91f2775): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/369e7663-1eb8-4c41-880f-27cd1608152e" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.1297445+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.7318733+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__: __369e7663-1eb8-4c41-880f-27cd1608152e__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.ignition.v1.btrfsroot**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.ext4root**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.groups**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-9cd490229d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/9eef5983-3749-44bb-8ae0-8871385155be" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.6112305+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8044629+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__: __9eef5983-3749-44bb-8ae0-8871385155be__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.ignition.v1.noop**; 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.1-n-ba4497e284): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/38194267-c2c4-402a-87c7-7a9c40afefb6" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.3362511+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.608657+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__: __38194267-c2c4-402a-87c7-7a9c40afefb6__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 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.1-n-b4a2db251f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/2b675372-c265-4738-86a9-85ae62122797" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.5555103+00:00__," L8: "__endTime__: __2026-10-19T23:30:53.0743076+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__: __2b675372-c265-4738-86a9-85ae62122797__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.ignition.v1.users**; Succeeded: azure (1) 🟢 ok **cl.ignition.v1.xfsroot**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-be1be219ed): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/8e46ed18-7c40-4492-9bbb-0bad1a570aac" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.6492193+00:00__," L8: "__endTime__: __2026-10-19T23:30:53.5937263+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__: __8e46ed18-7c40-4492-9bbb-0bad1a570aac__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.ignition.v2.ext4root**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2.noop**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-c76a218387): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/13fb61a4-ad6a-4fc4-b261-0eaab992378c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.3877904+00:00__," L8: "__endTime__: __2026-10-19T23:30:53.3341999+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__: __13fb61a4-ad6a-4fc4-b261-0eaab992378c__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 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: _filesystem.go:415: Couldn_t start machine: PollUntilDone(ci-4757.2.1-n-d52995d9fe): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Comp?ute/locations/westus2/operations/161b5b13-4f81-4c40-b8fb-891b8fd43e30" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:33:28.6485081+00:00__," L8: "__endTime__: __2026-10-19T23:33:33.7138719+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__: __161b5b13-4f81-4c40-b8fb-891b8fd43e30__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.ignition.v2_1.swap**; Succeeded: azure (1) 🟢 ok **cl.ignition.v2_1.vfat**; Succeeded: azure (1) 🟢 ok **cl.internet**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-97a97d3dd8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/89695990-60b8-4ff3-9d08-3d1196861bf7" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:18.8756817+00:00__," L8: "__endTime__: __2026-10-19T23:34:24.1208459+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__: __89695990-60b8-4ff3-9d08-3d1196861bf7__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.locksmith.cluster**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _locksmith.go:184: [0] ssh unreachable or system not ready: context deadline exceeded [1] ssh unreachable or system not ready: context deadline exceeded [2] ssh unreachable or system not ready:? context deadline exceeded_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-d4d570c57c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/935a28dc-fc79-45f5-a19e-b6b7a2570264" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.1609765+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8044629+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__: __935a28dc-fc79-45f5-a19e-b6b7a2570264__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.metadata.azure**; Succeeded: azure (1) 🟢 ok **cl.network.initramfs.second-boot**; Succeeded: azure (1) 🟢 ok **cl.network.iptables**; Succeeded: azure (1) 🟢 ok **cl.network.nftables**; 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.1-n-ed78a36112): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/02c69306-3803-4b29-a442-9c46bcc16304" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:01.5391839+00:00__," L8: "__endTime__: __2026-10-19T23:34:07.025497+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__: __02c69306-3803-4b29-a442-9c46bcc16304__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.network.wireguard**; Succeeded: azure (1) 🟢 ok **cl.osreset.ignition-rerun**; Succeeded: azure (1) 🟢 ok **cl.overlay.cleanup**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-8f7eb1f19c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/242309ce-a412-498e-976d-6a3f5fbc1304" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:10.4407934+00:00__," L8: "__endTime__: __2026-10-19T23:34:14.3196729+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__: __242309ce-a412-498e-976d-6a3f5fbc1304__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.swap_activation**; Succeeded: azure (1) 🟢 ok **cl.toolbox.dnf-install**; Succeeded: azure (1) 🟢 ok **cl.update.badverity**; Succeeded: azure (1) 🟢 ok **cl.update.reboot**; 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.1-n-2fd25ed59b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/2c9ed5ed-ca4e-4fcf-b6aa-8820b5f10821" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.4724+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8044629+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__: __2c9ed5ed-ca4e-4fcf-b6aa-8820b5f10821__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **cl.users.shells**; Succeeded: azure (1) 🟢 ok **cl.verity**; Succeeded: azure (1) 🟢 ok **coreos.auth.verify**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-dd8ef9855e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/bd7a7ed6-c803-43b1-8adc-8cdace6e5bce" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.3293717+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.7420733+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__: __bd7a7ed6-c803-43b1-8adc-8cdace6e5bce__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **coreos.ignition.groups**; Succeeded: azure (1) 🟢 ok **coreos.ignition.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.1-n-5999a6c988): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/803c8cab-c7dd-46ed-8224-d8703d5b3a2b" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.9116845+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8141308+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__: __803c8cab-c7dd-46ed-8224-d8703d5b3a2b__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **coreos.ignition.resource.local**; Succeeded: azure (1) 🟢 ok **coreos.ignition.resource.remote**; Succeeded: azure (1) 🟢 ok **coreos.ignition.security.tls**; Succeeded: azure (1) 🟢 ok **coreos.ignition.ssh.key**; 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.1-n-a735fa65d2): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/ee0427ec-1422-4e0e-9dba-5ca737f63d4e" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:37.400191+00:00__," L8: "__endTime__: __2026-10-19T23:34:42.8335595+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__: __ee0427ec-1422-4e0e-9dba-5ca737f63d4e__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **coreos.ignition.systemd.enable-service**; Succeeded: azure (1) 🟢 ok **coreos.locksmith.reboot**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded_" L2: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-8255d0038e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/516714ad-29e4-4561-81ad-16dc0f7426f2" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.2526043+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8044629+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__: __516714ad-29e4-4561-81ad-16dc0f7426f2__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 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.1-n-d613207df6): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/d9dc91e5-2341-4b3c-998e-a28dc790c73a" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.2526043+00:00__," L8: "__endTime__: __2026-10-19T23:30:53.2940211+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__: __d9dc91e5-2341-4b3c-998e-a28dc790c73a__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **coreos.selinux.enforce**; 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.1-n-3e38947c13): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/1a0beb59-4730-4905-908a-c5936680c799" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.5347436+00:00__," L8: "__endTime__: __2026-10-19T23:30:53.4434929+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__: __1a0beb59-4730-4905-908a-c5936680c799__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **coreos.tls.fetch-urls**; Succeeded: azure (1) 🟢 ok **coreos.update.badusr**; Succeeded: azure (1) 🟢 ok **docker.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " _docker.base/networks-reliably (64.70s)" L2: "cluster.go:125: #0 building with __default__ instance using docker driver" L3: "cluster.go:125: " L4: "cluster.go:125: #1 [internal] load build definition from Dockerfile" L5: "cluster.go:125: #1 transferring dockerfile: 108B done" L6: "cluster.go:125: #1 DONE 0.0s" L7: "cluster.go:125: " L8: "cluster.go:125: #2 [internal] load .dockerignore" L9: "cluster.go:125: #2 transferring context: 2B done" L10: "cluster.go:125: #2 DONE 0.0s" L11: "cluster.go:125: " L12: "cluster.go:125: #3 [internal] load build context" L13: "cluster.go:125: #3 transferring context: 4.23MB 0.0s done" L14: "cluster.go:125: #3 DONE 0.1s" L15: "cluster.go:125: " L16: "cluster.go:125: #4 [1/1] COPY . /" L17: "cluster.go:125: #4 DONE 0.0s" L18: "cluster.go:125: " L19: "cluster.go:125: #5 exporting to image" L20: "cluster.go:125: #5 exporting layers 0.0s done" L21: "cluster.go:125: #5 writing image sha256:7f0972e8b0768a461de17298e6bcac47fa1b045e763d56efcb91d6bea9af4edc done" L22: "cluster.go:125: #5 naming to docker.io/library/ping done" L23: "cluster.go:125: #5 DONE 0.1s" L24: "cluster.go:145: __for i in $(seq 1 100); do_n_t_techo -n ___$i: ____n_t_tdocker run --rm ping sh -c _ping -i 0.2 172.17.0.1 -w 1 _/dev/null && echo PASS || echo FAIL__n_tdone__ failed: output 1: PASS" L25: "2: PASS" L26: "3: PASS" L27: "4: PASS" L28: "5: PASS" L29: "6: PASS" L30: "7: PASS" L31: "8: PASS" L32: "9: PASS" L33: "10: PASS" L34: "11: PASS" L35: "12: PASS" L36: "13: PASS" L37: "14: PASS" L38: "15: PASS" L39: "16: PASS" L40: "17: PASS" L41: "18: PASS" L42: "19: PASS" L43: "20: PASS" L44: "21: PASS" L45: "22: PASS" L46: "23: PASS" L47: "24:, status wait: remote command exited without exit status or exit signal" L48: "--- FAIL: docker.base/user-no-caps (0.28s)" L49: "cluster.go:145: __tmpdir=$(mktemp -d); cd $tmpdir; echo -e ___FROM scratch__nCOPY . /___ _ Dockerfile;_n_t b=$(which capsh sh grep cat ls); libs=$(sudo ldd $b | grep -o /lib_[^ ]*_ | sort -u);_?n_t sudo rsync -av --relative --copy-links $b $libs ./;_n_t sudo docker build -t captest .__ failed: output , status ssh: handshake failed: read tcp 10.200.1.4:32876-_20.236.6.56:22: rea?d: connection reset by peer" L50: "--- FAIL: docker.base/ownership (0.28s)" L51: "cluster.go:145: __docker run --name ownership ghcr.io/flatcar/nginx stat -c ___%u/%g___ /etc/shadow__ failed: output , status ssh: handshake failed: read tcp 10.200.1.4:32882-_20.236.6.56:22: read: co?nnection reset by peer_" L52: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-06737be462): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/2d3400f7-15d4-438e-9493-8833470a76cb" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:24.5209742+00:00__," L8: "__endTime__: __2026-10-19T23:34:29.3185472+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__: __2d3400f7-15d4-438e-9493-8833470a76cb__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **docker.btrfs-storage**; Succeeded: azure (1) 🟢 ok **docker.containerd-restart**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: Unable to find image _ghcr.io/flatcar/busybox:latest_ locally" L2: "cluster.go:125: latest: Pulling from flatcar/busybox" L3: "cluster.go:125: dbc3eadfebd7: Pulling fs layer" L4: "cluster.go:125: dbc3eadfebd7: Verifying Checksum" L5: "cluster.go:125: dbc3eadfebd7: Download complete" L6: "cluster.go:125: dbc3eadfebd7: Pull complete" L7: "cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e" L8: "cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest" L9: "docker.go:638: unable to run docker container: running docker container: dial tcp 20.112.77.138:22: i/o timeout after killing containerd with signal: SIGTERM_" L10: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-0543382a29): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/caa4bdf9-012e-4e3e-beab-82d9e9a18b79" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.3377498+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.6151944+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__: __caa4bdf9-012e-4e3e-beab-82d9e9a18b79__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **docker.enable-service.sysext**; Succeeded: azure (1) 🟢 ok **docker.lib-coreos-dockerd-compat**; Succeeded: azure (1) 🟢 ok **docker.network-openbsd-nc**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-2e10667837): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/803247e1-ea3a-4f1a-bfc8-a64acc809b78" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.8083705+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.6151944+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__: __803247e1-ea3a-4f1a-bfc8-a64acc809b78__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **docker.selinux**; Succeeded: azure (1) 🟢 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: _cluster.go:125: I1019 23:53:19.719602 2893 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: I1019 23:53:28.571929 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.1-n-9f5990d839__ could not be reached" L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.1-n-9f5990d839__: lookup ci-4757.2.1-n-9f5990d839 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.1-n-9f5990d839 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.30]" 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 1.001582647s" 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.30: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.006374097s" L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.56869983s" L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.002643284s" 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.1-n-9f5990d839 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.1-n-9f5990d839 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L61: "cluster.go:125: [bootstrap-token] Using token: 97j87z.di1fxedfu7opk210" 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.30:6443 --token 97j87z.di1fxedfu7opk210 _" L91: "cluster.go:125: --discovery-token-ca-cert-hash sha256:233bf86e081897081fc0ae5f1f4e1183aee2f695006a0a194a4cef68d4748bdc " 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.1-n-e420612e94): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/bd7d2932-3c5a-4799-9057-c071eaa8770e" L108: "--------------------------------------------------------------------------------" L109: "RESPONSE 200: 200 OK" L110: "ERROR CODE: OperationPreempted" L111: "--------------------------------------------------------------------------------" L112: "{" L113: "__startTime__: __2026-10-19T23:53:57.1874036+00:00__," L114: "__endTime__: __2026-10-19T23:55:27.4880821+00:00__," L115: "__status__: __Canceled__," L116: "__error__: {" L117: "__code__: __OperationPreempted__," L118: "__message__: __Operation execution has been preempted by a more recent operation.__" L119: "}," L120: "__name__: __bd7d2932-3c5a-4799-9057-c071eaa8770e__" L121: "}" L122: "--------------------------------------------------------------------------------_" L123: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.1-n-e67e47c9fc): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/629e8efe-218e-4db5-8293-6b39b1c2d531" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.7876832+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8044629+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__: __629e8efe-218e-4db5-8293-6b39b1c2d531__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: I1019 23:53:15.114479 2643 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: I1019 23:53:24.781093 2857 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.1-n-7eb164ee08__ could not be reached" L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.1-n-7eb164ee08__: lookup ci-4757.2.1-n-7eb164ee08 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.1-n-7eb164ee08 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.27]" 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 501.014491ms" 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.27: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.506027709s" L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.688055615s" L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.002995505s" 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.1-n-7eb164ee08 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.1-n-7eb164ee08 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L61: "cluster.go:125: [bootstrap-token] Using token: jp110z.poexf3c618w54pxu" 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.27:6443 --token jp110z.poexf3c618w54pxu _" L91: "cluster.go:125: --discovery-token-ca-cert-hash sha256:2427140e0da9d3b8798ef8148a187fa658e655535cfee47411e334fd8ca9966b " L92: "cluster.go:125: namespace/kube-flannel created" L93: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created" L94: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created" L95: "cluster.go:125: serviceaccount/flannel created" L96: "cluster.go:125: configmap/kube-flannel-cfg created" L97: "cluster.go:125: daemonset.apps/kube-flannel-ds created" L98: "cluster.go:125: W1019 23:55:02.898383 2454 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration" L99: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_" L100: "--- FAIL: kubeadm.v1.35.1.flannel.base/node_readiness (7.30s)" L101: "cluster.go:145: __kubectl get nodes | grep ___ Ready___| wc -l__ failed: output , status dial tcp 20.114.10.102:22: connect: connection refused" L102: "--- FAIL: kubeadm.v1.35.1.flannel.base/nginx_deployment (0.96s)" L103: "kubeadm.go:219: unable to deploy nginx: dial tcp 20.114.10.102:22: connect: connection refused" L104: "--- FAIL: kubeadm.v1.35.1.flannel.base/NFS_deployment (0.96s)" L105: "kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.114.10.102:22: connect: connection refused_" L106: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.1-n-6a0244359b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/eefb734b-c6b9-419e-8265-d0e53c77302d" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.732039+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.9282076+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__: __eefb734b-c6b9-419e-8265-d0e53c77302d__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: I1019 23:53:19.875947 2972 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: I1019 23:53:29.686037 3204 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.1-n-76aa4110d1__ could not be reached" L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.1-n-76aa4110d1__: lookup ci-4757.2.1-n-76aa4110d1 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.1-n-76aa4110d1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.29]" 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 696.148??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.29: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 4.721456ms" L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 8.251686ms" L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.00137484s" 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.1-n-76aa4110d1 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.1-n-76aa4110d1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L61: "cluster.go:125: [bootstrap-token] Using token: d87ely.puv6o5qpk8vni6pd" 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.29:6443 --token d87ely.puv6o5qpk8vni6pd _" L92: "cluster.go:125: --discovery-token-ca-cert-hash sha256:71eaa03f0946aa971718936567d8198c1b305bdcb9c36df2108dbd361175db6c " 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: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourc?eGroups/kola-cluster-image-f16ebf8414/providers/Microsoft.Compute/virtualMachines/ci-4757.2.1-n-c474a5b504" L109: "--------------------------------------------------------------------------------" L110: "RESPONSE 404: 404 Not Found" L111: "ERROR CODE: NotFound" L112: "--------------------------------------------------------------------------------" L113: "{" L114: "__error__: {" L115: "__code__: __NotFound__," L116: "__message__: __The entity was not found in this Azure location.__" L117: "}" L118: "}" L119: "--------------------------------------------------------------------------------_" L120: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.1-n-1a1e849795): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/8346cecc-b969-4915-bde2-c76f9a4afc2f" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:33:31.7346121+00:00__," L8: "__endTime__: __2026-10-19T23:33:36.6670188+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__: __8346cecc-b969-4915-bde2-c76f9a4afc2f__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: I1019 23:53:14.288500 2675 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: I1019 23:53:23.633415 3078 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.1-n-143722957d__ could not be reached" L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.1-n-143722957d__: lookup ci-4757.2.1-n-143722957d 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.1-n-143722957d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.26]" 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 1.720034ms" 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.26: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 3.724172ms" L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 7.139352ms" L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.501550196s" 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.1-n-143722957d 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.1-n-143722957d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L61: "cluster.go:125: [bootstrap-token] Using token: kcq4dd.rus2p1s1amznh8ut" 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.26:6443 --token kcq4dd.rus2p1s1amznh8ut _" L92: "cluster.go:125: --discovery-token-ca-cert-hash sha256:0e5fb5dee2c27bbe724aefba6ce4748b87d2f710def7a543fe57787445148358 " 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: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourc?eGroups/kola-cluster-image-f16ebf8414/providers/Microsoft.Compute/virtualMachines/ci-4757.2.1-n-e124394db2" L100: "--------------------------------------------------------------------------------" L101: "RESPONSE 404: 404 Not Found" L102: "ERROR CODE: NotFound" L103: "--------------------------------------------------------------------------------" L104: "{" L105: "__error__: {" L106: "__code__: __NotFound__," L107: "__message__: __The entity was not found in this Azure location.__" L108: "}" L109: "}" L110: "--------------------------------------------------------------------------------_" L111: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.1-n-18cb97cd1f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2?e/providers/Microsoft.Compute/locations/westus2/operations/5d7dca64-b156-4274-808f-834966f80017" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:01.3468364+00:00__," L8: "__endTime__: __2026-10-19T23:34:06.4437542+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__: __5d7dca64-b156-4274-808f-834966f80017__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.37.0.calico.base**; Succeeded: azure (3); Failed: azure (1, 2)
                Diagnostic output for azure, run 2 ``` L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6" L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2" L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0" L8: "cluster.go:125: [init] Using Kubernetes version: v1.37.1" L9: "cluster.go:125: [preflight] Running pre-flight checks" L10: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.1-n-1a09d92064__ could not be reached" L11: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757.2.1-n-1a09d92064__: lookup ci-4757.2.1-n-1a09d92064 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.1-n-1a09d92064 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.28]" 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 697.157??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.28: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 5.57905ms" L52: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.027508ms" L53: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.001435733s" 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.1-n-1a09d92064 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.1-n-1a09d92064 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L59: "cluster.go:125: [bootstrap-token] Using token: 6kdkjg.j30qpsf37uaoh2jh" 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.28:6443 --token 6kdkjg.j30qpsf37uaoh2jh _" L90: "cluster.go:125: --discovery-token-ca-cert-hash sha256:3b7d8b0bdd665349f406d57f919acc41c00b34913d63e30b114c9fa854ba3b9b " 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.1-n-9f2d4a501b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/prov?iders/Microsoft.Compute/locations/westus2/operations/7ba012a8-7450-4160-9ee6-d56badb60b15" L107: "--------------------------------------------------------------------------------" L108: "RESPONSE 200: 200 OK" L109: "ERROR CODE: OperationPreempted" L110: "--------------------------------------------------------------------------------" L111: "{" L112: "__startTime__: __2026-10-19T23:54:01.9188086+00:00__," L113: "__endTime__: __2026-10-19T23:55:21.4099336+00:00__," L114: "__status__: __Canceled__," L115: "__error__: {" L116: "__code__: __OperationPreempted__," L117: "__message__: __Operation execution has been preempted by a more recent operation.__" L118: "}," L119: "__name__: __7ba012a8-7450-4160-9ee6-d56badb60b15__" L120: "}" L121: "--------------------------------------------------------------------------------_" L122: " " ```                 Diagnostic output for azure, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4757.2.1-n-ab876eb985): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80c?b2e/providers/Microsoft.Compute/locations/westus2/operations/a33efd8e-990f-48f1-8cff-4054016edaaf" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:34:01.2592981+00:00__," L8: "__endTime__: __2026-10-19T23:34:05.4424561+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__: __a33efd8e-990f-48f1-8cff-4054016edaaf__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **kubeadm.v1.37.0.cilium.base**; Succeeded: azure (1) 🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: azure (1) 🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (1) 🟢 ok **sysext.disable-containerd**; Succeeded: azure (1) 🟢 ok **sysext.disable-docker**; Succeeded: azure (1) 🟢 ok **sysext.simple**; Succeeded: azure (2); Failed: azure (1)
                Diagnostic output for azure, run 1 ``` L1: " Error: _harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.1-n-e4965db9d9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/15569240-77d7-448e-8386-e825041efc57" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:48.690612+00:00__," L8: "__endTime__: __2026-10-19T23:30:52.8044629+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__: __15569240-77d7-448e-8386-e825041efc57__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```
🟢 ok **systemd.journal.user**; Succeeded: azure (1) 🟢 ok **systemd.sysusers.gshadow**; 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.1-n-22de9babe5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microso?ft.Compute/locations/westus2/operations/52b9250c-37a5-4564-8b38-ffe43326d52c" L2: "--------------------------------------------------------------------------------" L3: "RESPONSE 200: 200 OK" L4: "ERROR CODE: AllocationFailed" L5: "--------------------------------------------------------------------------------" L6: "{" L7: "__startTime__: __2026-10-19T23:30:47.4238324+00:00__," L8: "__endTime__: __2026-10-19T23:30:53.0743076+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__: __52b9250c-37a5-4564-8b38-ffe43326d52c__" L15: "}" L16: "--------------------------------------------------------------------------------_" L17: " " ```