{"tests":[{"name":"cl.ignition.v1.noop","result":"FAIL","duration":68243641904,"output":" 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/Microsoft.Compute/locations/westus2/operations/38194267-c2c4-402a-87c7-7a9c40afefb6\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.3362511+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.608657+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"38194267-c2c4-402a-87c7-7a9c40afefb6\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"systemd.sysusers.gshadow","result":"FAIL","duration":68246758650,"output":" 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/Microsoft.Compute/locations/westus2/operations/52b9250c-37a5-4564-8b38-ffe43326d52c\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.4238324+00:00\",\n \"endTime\": \"2026-10-19T23:30:53.0743076+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"52b9250c-37a5-4564-8b38-ffe43326d52c\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.etcd-member.etcdctlv3","result":"FAIL","duration":68331503745,"output":" 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/Microsoft.Compute/locations/westus2/operations/c5b365a6-aeef-4e3c-a95e-73d5012091fd\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.7295057+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.608657+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"c5b365a6-aeef-4e3c-a95e-73d5012091fd\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.groups","result":"FAIL","duration":68537613310,"output":" 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/Microsoft.Compute/locations/westus2/operations/9eef5983-3749-44bb-8ae0-8871385155be\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.6112305+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8044629+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"9eef5983-3749-44bb-8ae0-8871385155be\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.once","result":"FAIL","duration":68752738596,"output":" 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/Microsoft.Compute/locations/westus2/operations/803c8cab-c7dd-46ed-8224-d8703d5b3a2b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.9116845+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8141308+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"803c8cab-c7dd-46ed-8224-d8703d5b3a2b\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.selinux.boolean","result":"FAIL","duration":68809525999,"output":" 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/Microsoft.Compute/locations/westus2/operations/d9dc91e5-2341-4b3c-998e-a28dc790c73a\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.2526043+00:00\",\n \"endTime\": \"2026-10-19T23:30:53.2940211+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"d9dc91e5-2341-4b3c-998e-a28dc790c73a\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":68971299421,"output":" 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/Microsoft.Compute/locations/westus2/operations/803247e1-ea3a-4f1a-bfc8-a64acc809b78\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.8083705+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.6151944+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"803247e1-ea3a-4f1a-bfc8-a64acc809b78\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.translation","result":"FAIL","duration":69039715066,"output":" 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/Microsoft.Compute/locations/westus2/operations/369e7663-1eb8-4c41-880f-27cd1608152e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.1297445+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.7318733+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"369e7663-1eb8-4c41-880f-27cd1608152e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":69211028843,"output":" 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/Microsoft.Compute/locations/westus2/operations/13fb61a4-ad6a-4fc4-b261-0eaab992378c\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.3877904+00:00\",\n \"endTime\": \"2026-10-19T23:30:53.3341999+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"13fb61a4-ad6a-4fc4-b261-0eaab992378c\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.auth.verify","result":"FAIL","duration":69234008002,"output":" 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/Microsoft.Compute/locations/westus2/operations/bd7a7ed6-c803-43b1-8adc-8cdace6e5bce\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.3293717+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.7420733+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"bd7a7ed6-c803-43b1-8adc-8cdace6e5bce\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.update.reboot","result":"FAIL","duration":69290750650,"output":" 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/Microsoft.Compute/locations/westus2/operations/2c9ed5ed-ca4e-4fcf-b6aa-8820b5f10821\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.4724+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8044629+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"2c9ed5ed-ca4e-4fcf-b6aa-8820b5f10821\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.containerd-restart","result":"FAIL","duration":69305335198,"output":" 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/Microsoft.Compute/locations/westus2/operations/caa4bdf9-012e-4e3e-beab-82d9e9a18b79\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.3377498+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.6151944+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"caa4bdf9-012e-4e3e-beab-82d9e9a18b79\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.selinux.enforce","result":"FAIL","duration":69359343888,"output":" 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/Microsoft.Compute/locations/westus2/operations/1a0beb59-4730-4905-908a-c5936680c799\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.5347436+00:00\",\n \"endTime\": \"2026-10-19T23:30:53.4434929+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"1a0beb59-4730-4905-908a-c5936680c799\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.locksmith.reboot","result":"FAIL","duration":69368610249,"output":" 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/Microsoft.Compute/locations/westus2/operations/516714ad-29e4-4561-81ad-16dc0f7426f2\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.2526043+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8044629+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"516714ad-29e4-4561-81ad-16dc0f7426f2\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2.btrfsroot","result":"FAIL","duration":69508061081,"output":" 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/Microsoft.Compute/locations/westus2/operations/8e46ed18-7c40-4492-9bbb-0bad1a570aac\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.6492193+00:00\",\n \"endTime\": \"2026-10-19T23:30:53.5937263+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"8e46ed18-7c40-4492-9bbb-0bad1a570aac\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"sysext.simple","result":"FAIL","duration":69587186912,"output":" 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/Microsoft.Compute/locations/westus2/operations/15569240-77d7-448e-8386-e825041efc57\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.690612+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8044629+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"15569240-77d7-448e-8386-e825041efc57\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.once","result":"FAIL","duration":69593771669,"output":" 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/Microsoft.Compute/locations/westus2/operations/2b675372-c265-4738-86a9-85ae62122797\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.5555103+00:00\",\n \"endTime\": \"2026-10-19T23:30:53.0743076+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"2b675372-c265-4738-86a9-85ae62122797\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":70747104755,"output":" 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-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/629e8efe-218e-4db5-8293-6b39b1c2d531\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:47.7876832+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8044629+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"629e8efe-218e-4db5-8293-6b39b1c2d531\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":71184709872,"output":" 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-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/eefb734b-c6b9-419e-8265-d0e53c77302d\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.732039+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.9282076+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"eefb734b-c6b9-419e-8265-d0e53c77302d\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.misc.empty","result":"PASS","duration":94988139160,"output":""},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":103562427771,"output":""},{"name":"sysext.disable-containerd","result":"PASS","duration":125371447807,"output":""},{"name":"cl.metadata.azure","result":"PASS","duration":124378322127,"output":""},{"name":"cl.users.shells","result":"PASS","duration":125424749679,"output":""},{"name":"cl.network.iptables","result":"PASS","duration":124313159531,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"cl.ignition.kargs","result":"PASS","duration":125161173265,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"coreos.ignition.groups","result":"PASS","duration":128285868573,"output":""},{"name":"cl.ignition.v1.users","result":"PASS","duration":131647202822,"output":""},{"name":"docker.lib-coreos-dockerd-compat/docker-info","result":"PASS","duration":18659606570,"output":""},{"name":"docker.userns","result":"PASS","duration":143192855585,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.19MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:6ddaf024691f505948978e628dbfab85dff225c5852ecc8d0ae7c5e879b21854 done\n cluster.go:125: #5 naming to docker.io/library/userns-test done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/resources","result":"PASS","duration":9001605332,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.12MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:ffa439b91d0f419f045764b0a27f69a4ef7030d4b2af2388011d05239b11c377 done\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n"},{"name":"sysext.custom-docker.sysext","result":"PASS","duration":148099845780,"output":" cluster.go:125: bash: line 1: docker: command not found\n cluster.go:125: Cloning into 'sysext-bakery'...\n cluster.go:125: Note: switching to '9850ffd5b2353f45a9b3bf4fb84f8138a149e3e7'.\n cluster.go:125: \n cluster.go:125: You are in 'detached HEAD' state. You can look around, make experimental\n cluster.go:125: changes and commit them, and you can discard any commits you make in this\n cluster.go:125: state without impacting any branches by switching back to a branch.\n cluster.go:125: \n cluster.go:125: If you want to create a new branch to retain commits you create, you may\n cluster.go:125: do so (now or later) by using -c with the switch command. Example:\n cluster.go:125: \n cluster.go:125: git switch -c \u003cnew-branch-name\u003e\n cluster.go:125: \n cluster.go:125: Or undo this operation with:\n cluster.go:125: \n cluster.go:125: git switch -\n cluster.go:125: \n cluster.go:125: Turn off this advice by setting config variable advice.detachedHead to false\n cluster.go:125: \n cluster.go:125: HEAD is now at 9850ffd Merge pull request #31 from flatcar/t-lo/fix-docker-23-containerd-shim\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: dbc3eadfebd7: Pulling fs layer\n cluster.go:125: dbc3eadfebd7: Verifying Checksum\n cluster.go:125: dbc3eadfebd7: Download complete\n cluster.go:125: dbc3eadfebd7: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n"},{"name":"cl.flannel.vxlan","result":"PASS","duration":160355775900,"output":" flannel.go:121: ping from ci-4757.2.1-n-79a7fa29f0(10.254.29.0) to ci-4757.2.1-n-2389c04f03(10.254.73.0)\n"},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"FAIL","duration":161601394711,"output":" 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.Compute/locations/westus2/operations/161b5b13-4f81-4c40-b8fb-891b8fd43e30\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:33:28.6485081+00:00\",\n \"endTime\": \"2026-10-19T23:33:33.7138719+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"161b5b13-4f81-4c40-b8fb-891b8fd43e30\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":69964694154,"output":" 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-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/8346cecc-b969-4915-bde2-c76f9a4afc2f\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:33:31.7346121+00:00\",\n \"endTime\": \"2026-10-19T23:33:36.6670188+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"8346cecc-b969-4915-bde2-c76f9a4afc2f\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":166243060858,"output":""},{"name":"cl.network.nftables","result":"FAIL","duration":68516557982,"output":" 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/Microsoft.Compute/locations/westus2/operations/02c69306-3803-4b29-a442-9c46bcc16304\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:01.5391839+00:00\",\n \"endTime\": \"2026-10-19T23:34:07.025497+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"02c69306-3803-4b29-a442-9c46bcc16304\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"azure.nvme-friendly-naming","result":"FAIL","duration":68426440998,"output":" 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/Microsoft.Compute/locations/westus2/operations/3eff9e2b-38fb-4b40-b4c5-9ece97afd49c\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:01.9127159+00:00\",\n \"endTime\": \"2026-10-19T23:34:05.8461665+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"3eff9e2b-38fb-4b40-b4c5-9ece97afd49c\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.cloudinit.script","result":"FAIL","duration":68993496063,"output":" 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/Microsoft.Compute/locations/westus2/operations/e653b216-a1c2-4386-9b95-df769ae83ba6\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:01.5391839+00:00\",\n \"endTime\": \"2026-10-19T23:34:06.2984048+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"e653b216-a1c2-4386-9b95-df769ae83ba6\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":70046471036,"output":" 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-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/5d7dca64-b156-4274-808f-834966f80017\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:01.3468364+00:00\",\n \"endTime\": \"2026-10-19T23:34:06.4437542+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"5d7dca64-b156-4274-808f-834966f80017\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.cloudinit.multipart-mime","result":"FAIL","duration":67898098145,"output":" 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/Microsoft.Compute/locations/westus2/operations/b67e730b-6c5c-4849-9fc7-e18e12f54c53\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:05.1066282+00:00\",\n \"endTime\": \"2026-10-19T23:34:09.0633984+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"b67e730b-6c5c-4849-9fc7-e18e12f54c53\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":196623637838,"output":" 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-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/a33efd8e-990f-48f1-8cff-4054016edaaf\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:01.2592981+00:00\",\n \"endTime\": \"2026-10-19T23:34:05.4424561+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"a33efd8e-990f-48f1-8cff-4054016edaaf\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.verity/verify","result":"PASS","duration":78932182205,"output":" cluster.go:125: Success\n"},{"name":"cl.overlay.cleanup","result":"FAIL","duration":67858476602,"output":" 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/Microsoft.Compute/locations/westus2/operations/242309ce-a412-498e-976d-6a3f5fbc1304\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:10.4407934+00:00\",\n \"endTime\": \"2026-10-19T23:34:14.3196729+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"242309ce-a412-498e-976d-6a3f5fbc1304\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.ext4root","result":"PASS","duration":98026545120,"output":""},{"name":"cl.internet","result":"FAIL","duration":68066576713,"output":" 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/Microsoft.Compute/locations/westus2/operations/89695990-60b8-4ff3-9d08-3d1196861bf7\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:18.8756817+00:00\",\n \"endTime\": \"2026-10-19T23:34:24.1208459+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"89695990-60b8-4ff3-9d08-3d1196861bf7\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.base","result":"FAIL","duration":68585460266,"output":" 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/Microsoft.Compute/locations/westus2/operations/2d3400f7-15d4-438e-9493-8833470a76cb\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:24.5209742+00:00\",\n \"endTime\": \"2026-10-19T23:34:29.3185472+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"2d3400f7-15d4-438e-9493-8833470a76cb\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.resource.local","result":"PASS","duration":228199024954,"output":""},{"name":"coreos.ignition.ssh.key","result":"FAIL","duration":68229026331,"output":" 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/Microsoft.Compute/locations/westus2/operations/ee0427ec-1422-4e0e-9dba-5ca737f63d4e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:34:37.400191+00:00\",\n \"endTime\": \"2026-10-19T23:34:42.8335595+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"ee0427ec-1422-4e0e-9dba-5ca737f63d4e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.toolbox.dnf-install","result":"PASS","duration":81584084524,"output":""},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":127456973632,"output":""},{"name":"coreos.ignition.security.tls","result":"PASS","duration":261134723718,"output":""},{"name":"cl.swap_activation","result":"PASS","duration":125398677578,"output":""},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":93196234313,"output":""},{"name":"docker.lib-coreos-dockerd-compat/networks-reliably","result":"PASS","duration":140927089512,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.23MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:3b1714c0e4a1a48dc2fa157d29fa6d1092796816fd0c141ff3d22d06bad17d5a done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/user-no-caps","result":"PASS","duration":3625830714,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.15MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:7002c7a33d5c99223fa9b831ddc49419c171c87aadc4c386e1de76f891be7f95\n cluster.go:125: #5 writing image sha256:7002c7a33d5c99223fa9b831ddc49419c171c87aadc4c386e1de76f891be7f95 done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/ownership","result":"PASS","duration":8651873850,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 7cdd1ba5135a: Pulling fs layer\n cluster.go:125: 8083d0331109: Pulling fs layer\n cluster.go:125: bb482e962a91: Pulling fs layer\n cluster.go:125: c403c18c260c: Pulling fs layer\n cluster.go:125: f5c24fc2ff22: Pulling fs layer\n cluster.go:125: 1a47f466819b: Pulling fs layer\n cluster.go:125: 0d6ad25c5ec8: Pulling fs layer\n cluster.go:125: c403c18c260c: Waiting\n cluster.go:125: f5c24fc2ff22: Waiting\n cluster.go:125: 1a47f466819b: Waiting\n cluster.go:125: 0d6ad25c5ec8: Waiting\n cluster.go:125: bb482e962a91: Verifying Checksum\n cluster.go:125: bb482e962a91: Download complete\n cluster.go:125: c403c18c260c: Verifying Checksum\n cluster.go:125: c403c18c260c: Download complete\n cluster.go:125: 7cdd1ba5135a: Verifying Checksum\n cluster.go:125: 7cdd1ba5135a: Download complete\n cluster.go:125: f5c24fc2ff22: Verifying Checksum\n cluster.go:125: f5c24fc2ff22: Download complete\n cluster.go:125: 1a47f466819b: Verifying Checksum\n cluster.go:125: 1a47f466819b: Download complete\n cluster.go:125: 8083d0331109: Verifying Checksum\n cluster.go:125: 8083d0331109: Download complete\n cluster.go:125: 0d6ad25c5ec8: Verifying Checksum\n cluster.go:125: 0d6ad25c5ec8: Download complete\n cluster.go:125: 7cdd1ba5135a: Pull complete\n cluster.go:125: 8083d0331109: Pull complete\n cluster.go:125: bb482e962a91: Pull complete\n cluster.go:125: c403c18c260c: Pull complete\n cluster.go:125: f5c24fc2ff22: Pull complete\n cluster.go:125: 1a47f466819b: Pull complete\n cluster.go:125: 0d6ad25c5ec8: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.btrfs-storage","result":"PASS","duration":108010756709,"output":""},{"name":"docker.lib-coreos-dockerd-compat","result":"PASS","duration":303703718095,"output":" --- PASS: docker.lib-coreos-dockerd-compat/docker-info (18.66s)\n --- PASS: docker.lib-coreos-dockerd-compat/resources (9.00s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.12MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:ffa439b91d0f419f045764b0a27f69a4ef7030d4b2af2388011d05239b11c377 done\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n --- PASS: docker.lib-coreos-dockerd-compat/networks-reliably (140.93s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.23MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:3b1714c0e4a1a48dc2fa157d29fa6d1092796816fd0c141ff3d22d06bad17d5a done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.lib-coreos-dockerd-compat/user-no-caps (3.63s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.15MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:7002c7a33d5c99223fa9b831ddc49419c171c87aadc4c386e1de76f891be7f95\n cluster.go:125: #5 writing image sha256:7002c7a33d5c99223fa9b831ddc49419c171c87aadc4c386e1de76f891be7f95 done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.lib-coreos-dockerd-compat/ownership (8.65s)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 7cdd1ba5135a: Pulling fs layer\n cluster.go:125: 8083d0331109: Pulling fs layer\n cluster.go:125: bb482e962a91: Pulling fs layer\n cluster.go:125: c403c18c260c: Pulling fs layer\n cluster.go:125: f5c24fc2ff22: Pulling fs layer\n cluster.go:125: 1a47f466819b: Pulling fs layer\n cluster.go:125: 0d6ad25c5ec8: Pulling fs layer\n cluster.go:125: c403c18c260c: Waiting\n cluster.go:125: f5c24fc2ff22: Waiting\n cluster.go:125: 1a47f466819b: Waiting\n cluster.go:125: 0d6ad25c5ec8: Waiting\n cluster.go:125: bb482e962a91: Verifying Checksum\n cluster.go:125: bb482e962a91: Download complete\n cluster.go:125: c403c18c260c: Verifying Checksum\n cluster.go:125: c403c18c260c: Download complete\n cluster.go:125: 7cdd1ba5135a: Verifying Checksum\n cluster.go:125: 7cdd1ba5135a: Download complete\n cluster.go:125: f5c24fc2ff22: Verifying Checksum\n cluster.go:125: f5c24fc2ff22: Download complete\n cluster.go:125: 1a47f466819b: Verifying Checksum\n cluster.go:125: 1a47f466819b: Download complete\n cluster.go:125: 8083d0331109: Verifying Checksum\n cluster.go:125: 8083d0331109: Download complete\n cluster.go:125: 0d6ad25c5ec8: Verifying Checksum\n cluster.go:125: 0d6ad25c5ec8: Download complete\n cluster.go:125: 7cdd1ba5135a: Pull complete\n cluster.go:125: 8083d0331109: Pull complete\n cluster.go:125: bb482e962a91: Pull complete\n cluster.go:125: c403c18c260c: Pull complete\n cluster.go:125: f5c24fc2ff22: Pull complete\n cluster.go:125: 1a47f466819b: Pull complete\n cluster.go:125: 0d6ad25c5ec8: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.selinux","result":"PASS","duration":112640626851,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: dbc3eadfebd7: Pulling fs layer\n cluster.go:125: dbc3eadfebd7: Verifying Checksum\n cluster.go:125: dbc3eadfebd7: Download complete\n cluster.go:125: dbc3eadfebd7: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: sh: can't create /opt/hello: Permission denied\n"},{"name":"cl.cloudinit.basic","result":"PASS","duration":94959163995,"output":""},{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":125509664268,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":124656354060,"output":""},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":122495254325,"output":""},{"name":"cl.etcd-member.v2-backup-restore","result":"PASS","duration":97660325635,"output":" cluster.go:125: 2026-10-19T23:37:15Z\tinfo\tetcdutl/backup_command.go:216\tignoring EntryConfChange raft entry\n cluster.go:125: 2026-10-19T23:37:15Z\tinfo\tetcdutl/backup_command.go:231\tignoring member attribute update on\t{\"entry\": \"Term:2 Index:3 Data:\\\"\\\\010\\\\202\\\\224\\\\346\\\\263\\\\350\\\\252\\\\250\\\\305b\\\\022\\\\003PUT\\\\032\u0026/0/members/bb1d52fa2b47628a/attributes\\\\\\\"R{\\\\\\\"name\\\\\\\":\\\\\\\"db4c86c7dc5b49ba88c0e09a26db599d\\\\\\\",\\\\\\\"clientURLs\\\\\\\":[\\\\\\\"http://10.0.0.12:2379\\\\\\\"]}(\\\\0002\\\\0008\\\\000H\\\\000P\\\\000X\\\\000`\\\\000h\\\\000p\\\\000x\\\\000\\\\200\\\\001\\\\000\\\" \", \"v2Req.Path\": \"/0/members/bb1d52fa2b47628a/attributes\"}\n cluster.go:125: 2026-10-19T23:37:15Z\tinfo\tetcdutl/backup_command.go:252\tignoring v3 raft entry\n cluster.go:125: 2026-10-19T23:37:15Z\tinfo\tmembership/store.go:141\tTrimming membership information from the backend...\n"},{"name":"docker.enable-service.sysext","result":"PASS","duration":124238278030,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"bpf.ig/ig","result":"PASS","duration":142310022351,"output":" cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: time=\"2026-10-19T23:37:20Z\" level=warning msg=\"Runtime enricher (docker): couldn't get current containers: listing containers with options {Size:false All:true Latest:false Since: Before: Limit:0 Filters:{fields:map[]}}: Error response from daemon: client version 1.51 is too new. Maximum supported API version is 1.50\"\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: WARNING: This output is designed for human readability. For machine-readable output, please use --format.\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"bpf.ig","result":"PASS","duration":145054730841,"output":" --- PASS: bpf.ig/ig (142.31s)\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: time=\"2026-10-19T23:37:20Z\" level=warning msg=\"Runtime enricher (docker): couldn't get current containers: listing containers with options {Size:false All:true Latest:false Since: Before: Limit:0 Filters:{fields:map[]}}: Error response from daemon: client version 1.51 is too new. Maximum supported API version is 1.50\"\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: WARNING: This output is designed for human readability. For machine-readable output, please use --format.\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":66152718697,"output":""},{"name":"cl.verity/corruption","result":"PASS","duration":175027751690,"output":""},{"name":"cl.verity","result":"PASS","duration":376873885194,"output":" --- PASS: cl.verity/verify (78.93s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (175.03s)\n"},{"name":"cl.ignition.v2_1.vfat","result":"PASS","duration":95160495249,"output":""},{"name":"systemd.journal.user","result":"PASS","duration":62563312206,"output":""},{"name":"cl.ignition.v2.users","result":"PASS","duration":69682666647,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":96244178584,"output":""},{"name":"cl.ignition.luks","result":"PASS","duration":125586578043,"output":""},{"name":"cl.ignition.symlink","result":"PASS","duration":94035542538,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"cl.basic/Microcode","result":"PASS","duration":1330228904,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":1839389243,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":1300698111,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":1392801100,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":1328827545,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":1451239417,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":1496490246,"output":""},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":96573149821,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":1866640791,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":1784227536,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":1291163130,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":1294546704,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":1313375623,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":1294352400,"output":""},{"name":"coreos.locksmith.tls","result":"PASS","duration":140598516875,"output":""},{"name":"cl.basic","result":"PASS","duration":149947401179,"output":" --- PASS: cl.basic/Microcode (1.33s)\n --- PASS: cl.basic/Script (1.84s)\n --- PASS: cl.basic/PortSSH (1.30s)\n --- PASS: cl.basic/DbusPerms (1.39s)\n --- PASS: cl.basic/Symlink (1.33s)\n --- PASS: cl.basic/ServicesActive (1.45s)\n --- PASS: cl.basic/RandomUUID (1.50s)\n --- PASS: cl.basic/Useradd (1.87s)\n --- PASS: cl.basic/CloudConfig (1.78s)\n --- PASS: cl.basic/SymlinkFlatcar (1.29s)\n --- PASS: cl.basic/UpdateEngineKeys (1.29s)\n --- PASS: cl.basic/ReadOnly (1.31s)\n --- PASS: cl.basic/MachineID (1.29s)\n"},{"name":"cl.etcd-member.discovery","result":"PASS","duration":129010964251,"output":""},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":127002061096,"output":""},{"name":"cl.network.wireguard","result":"PASS","duration":94568206481,"output":" cluster.go:152: + ip --json address show kv0 | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n"},{"name":"kubeadm.v1.37.0.cilium.base/node_readiness","result":"PASS","duration":26938842341,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/nginx_deployment","result":"PASS","duration":9066448714,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/NFS_deployment","result":"PASS","duration":18854403461,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.37.0.cilium.base/IPSec_encryption","result":"PASS","duration":19496078951,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.37.0.cilium.base","result":"PASS","duration":304676355294,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-fb5ecf1864\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-fb5ecf1864\": lookup ci-4757.2.1-n-fb5ecf1864 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.1-n-fb5ecf1864 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.23]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 702.743µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.23:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.222606ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.614163ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.0031541s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-fb5ecf1864 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-fb5ecf1864 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: n312by.4oummisx479oe5dd\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n 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\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.23:6443 --token n312by.4oummisx479oe5dd \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:4a6212f5e19322d0b60034ecb9bf4c087d46abb5f324eeb700ce298e407b25f3 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W1019 23:39:26.487787 2444 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.37.0.cilium.base/node_readiness (26.94s)\n --- PASS: kubeadm.v1.37.0.cilium.base/nginx_deployment (9.07s)\n --- PASS: kubeadm.v1.37.0.cilium.base/NFS_deployment (18.85s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.37.0.cilium.base/IPSec_encryption (19.50s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.36.1.cilium.base/node_readiness","result":"PASS","duration":20504746550,"output":""},{"name":"kubeadm.v1.37.0.flannel.base/node_readiness","result":"PASS","duration":14055584570,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/nginx_deployment","result":"PASS","duration":9115112281,"output":""},{"name":"kubeadm.v1.37.0.flannel.base/nginx_deployment","result":"PASS","duration":9278868583,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":14180329353,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"PASS","duration":9169580017,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/NFS_deployment","result":"PASS","duration":18776264076,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.37.0.flannel.base/NFS_deployment","result":"PASS","duration":18558777175,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"PASS","duration":336084371781,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-b4d5d08f74\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-b4d5d08f74\": lookup ci-4757.2.1-n-b4d5d08f74 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.1-n-b4d5d08f74 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.25]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 598.983µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.25:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 6.09801ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 9.895746ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.004143984s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-b4d5d08f74 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-b4d5d08f74 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 58ybvz.wfm6uxsbcpi0iwxy\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n 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\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.25:6443 --token 58ybvz.wfm6uxsbcpi0iwxy \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:c4b98bafbe272cafe5ee28393a8cf1d9fcfa7c070eeb1254cb1bb28f6aacb4c3 \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W1019 23:40:51.330265 2493 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.37.0.flannel.base/node_readiness (14.06s)\n --- PASS: kubeadm.v1.37.0.flannel.base/nginx_deployment (9.28s)\n --- PASS: kubeadm.v1.37.0.flannel.base/NFS_deployment (18.56s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"PASS","duration":18644834082,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.cilium.base/IPSec_encryption","result":"PASS","duration":19598845814,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"PASS","duration":439015372798,"output":" cluster.go:125: I1019 23:38:08.559204 2856 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I1019 23:38:45.523800 3114 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-e98b2deac8\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-e98b2deac8\": lookup ci-4757.2.1-n-e98b2deac8 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.1-n-e98b2deac8 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.28]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.273774ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.28:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.352222ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.009391238s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.001856403s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-e98b2deac8 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-e98b2deac8 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: vi0vtj.fp7vkpn7gktcxcv1\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n 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\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.28:6443 --token vi0vtj.fp7vkpn7gktcxcv1 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:546dc8d442ff51baad1c7f244684a8ba8356b55ef699d0a41221f604a3cbf02f \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: Deployment cilium-operator \n cluster.go:125: DaemonSet cilium \n cluster.go:125: Containers: cilium-operator \n cluster.go:125: cilium \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W1019 23:40:42.864227 2528 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W1019 23:40:42.983275 2528 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.cilium.base/node_readiness (20.50s)\n --- PASS: kubeadm.v1.36.1.cilium.base/nginx_deployment (9.12s)\n --- PASS: kubeadm.v1.36.1.cilium.base/NFS_deployment (18.78s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.36.1.cilium.base/IPSec_encryption (19.60s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"PASS","duration":19440555528,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"PASS","duration":371397554330,"output":" cluster.go:125: I1019 23:38:39.455014 2692 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I1019 23:38:53.501586 2906 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-6473210994\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.1-n-6473210994\": lookup ci-4757.2.1-n-6473210994 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.1-n-6473210994 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.7]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.001657117s\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.7:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.504847844s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.783297994s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.502434916s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-6473210994 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.1-n-6473210994 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: yvy00p.bv4f46w52a4l9od3\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n 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\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.7:6443 --token yvy00p.bv4f46w52a4l9od3 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:feb924e0fade239a5e156bc7fe687a33779988313f33a24bd83318229f8873ca \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: Deployment cilium-operator \n cluster.go:125: DaemonSet cilium \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W1019 23:41:04.794704 2728 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.35.1.cilium.base/node_readiness (14.18s)\n --- PASS: kubeadm.v1.35.1.cilium.base/nginx_deployment (9.17s)\n --- PASS: kubeadm.v1.35.1.cilium.base/NFS_deployment (18.64s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.35.1.cilium.base/IPSec_encryption (19.44s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"cl.update.badverity","result":"PASS","duration":449649947548,"output":""},{"name":"coreos.update.badusr","result":"PASS","duration":420067150061,"output":""},{"name":"cl.locksmith.cluster","result":"FAIL","duration":871379814106,"output":" 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/Microsoft.Compute/locations/westus2/operations/935a28dc-fc79-45f5-a19e-b6b7a2570264\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-19T23:30:48.1609765+00:00\",\n \"endTime\": \"2026-10-19T23:30:52.8044629+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"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-guidance\"\n },\n \"name\": \"935a28dc-fc79-45f5-a19e-b6b7a2570264\"\n}\n--------------------------------------------------------------------------------\n"}],"result":"FAIL","platform":"azure","version":"4757.2.1"}