{"tests":[{"name":"docker.base/docker-info","result":"PASS","duration":3387311885,"output":""},{"name":"cl.network.wireguard","result":"PASS","duration":97487920018,"output":" cluster.go:152: + ip --json address show kv0 | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n"},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":97926074883,"output":""},{"name":"cl.etcd-member.etcdctlv3","result":"PASS","duration":99149715273,"output":" cluster.go:125: {\"level\":\"info\",\"ts\":1780702159.4415858,\"caller\":\"snapshot/v3_snapshot.go:68\",\"msg\":\"created temporary db file\",\"path\":\"/tmp/tmp.jYiCWqubK2/snapshot.db.part\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702159.4444504,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:211\",\"msg\":\"opened snapshot stream; downloading\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702159.444484,\"caller\":\"snapshot/v3_snapshot.go:76\",\"msg\":\"fetching snapshot\",\"endpoint\":\"127.0.0.1:2379\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702159.4466538,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:219\",\"msg\":\"completed snapshot read; closing\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702159.4466956,\"caller\":\"snapshot/v3_snapshot.go:91\",\"msg\":\"fetched snapshot\",\"endpoint\":\"127.0.0.1:2379\",\"size\":\"20 kB\",\"took\":\"now\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702159.446725,\"caller\":\"snapshot/v3_snapshot.go:100\",\"msg\":\"saved\",\"path\":\"/tmp/tmp.jYiCWqubK2/snapshot.db\"}\n cluster.go:125: Deprecated: Use `etcdutl snapshot status` instead.\n"},{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":99682463402,"output":""},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":100755583379,"output":""},{"name":"cl.ignition.v1.ext4root","result":"PASS","duration":101075418140,"output":""},{"name":"cl.ignition.translation","result":"PASS","duration":101653561734,"output":" cluster.go:152: + ip --json address show kola | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n cluster.go:152: + cat /etc/systemd/network/00-dummy.network\n"},{"name":"coreos.ignition.groups","result":"PASS","duration":103095393134,"output":""},{"name":"cl.etcd-member.v2-backup-restore","result":"PASS","duration":103643191670,"output":" cluster.go:125: 2026-06-05T23:29:22Z\tinfo\tetcdutl/backup_command.go:216\tignoring EntryConfChange raft entry\n cluster.go:125: 2026-06-05T23:29:22Z\tinfo\tetcdutl/backup_command.go:231\tignoring member attribute update on\t{\"entry\": \"Term:2 Index:3 Data:\\\"\\\\010\\\\201\\\\320\\\\232\\\\363\\\\241\\\\323\\\\347\\\\244#\\\\022\\\\003PUT\\\\032\u0026/0/members/719d6f67bb522349/attributes\\\\\\\"R{\\\\\\\"name\\\\\\\":\\\\\\\"11d0510b9e8044f88c47ca9758852627\\\\\\\",\\\\\\\"clientURLs\\\\\\\":[\\\\\\\"http://10.0.0.25:2379\\\\\\\"]}(\\\\0002\\\\0008\\\\000H\\\\000P\\\\000X\\\\000`\\\\000h\\\\000p\\\\000x\\\\000\\\\200\\\\001\\\\000\\\" \", \"v2Req.Path\": \"/0/members/719d6f67bb522349/attributes\"}\n cluster.go:125: 2026-06-05T23:29:22Z\tinfo\tetcdutl/backup_command.go:252\tignoring v3 raft entry\n cluster.go:125: 2026-06-05T23:29:22Z\tinfo\tmembership/store.go:119\tTrimming membership information from the backend...\n"},{"name":"cl.ignition.v1.users","result":"PASS","duration":106254679534,"output":""},{"name":"docker.base/resources","result":"PASS","duration":12066092212,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring 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: 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:b2cfa9d33531e363f027d6fb2e371290879e9555cc7e9a80679b940ca7a952c7\n cluster.go:125: #5 writing image sha256:b2cfa9d33531e363f027d6fb2e371290879e9555cc7e9a80679b940ca7a952c7 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 OomKillDisable. OomKillDisable discarded.\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n"},{"name":"cl.cloudinit.multipart-mime","result":"PASS","duration":108627905641,"output":""},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":122153477443,"output":""},{"name":"cl.ignition.v1.once","result":"PASS","duration":122632474962,"output":""},{"name":"coreos.ignition.once","result":"PASS","duration":123835045669,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":128805160863,"output":""},{"name":"cl.flannel.vxlan","result":"PASS","duration":139578765277,"output":" flannel.go:121: ping from ci-4081.3.8-n-ea1e92aabf(10.254.48.0) to ci-4081.3.8-n-3ad9e42563(10.254.72.0)\n"},{"name":"docker.network-openbsd-nc","result":"PASS","duration":143355197100,"output":" docker.go:413: creating netcat containers\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.53MB 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:af869aef2c15f9c922e4094ea03bbbde143b53fa2cc6d543183443e55936fb88 done\n cluster.go:125: #5 naming to docker.io/library/netcat 0.0s done\n cluster.go:125: #5 DONE 0.1s\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: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.53MB 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.1s\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:cc0a3287a371f92a6c3c23a559a9f9974f68a011ffe7f5a0f3e8690b4a096568 done\n cluster.go:125: #5 naming to docker.io/library/netcat 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"cl.verity/verify","result":"PASS","duration":95412504896,"output":" cluster.go:125: Success\n"},{"name":"cl.swap_activation","result":"PASS","duration":96237866004,"output":""},{"name":"cl.ignition.symlink","result":"PASS","duration":96597403962,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"docker.enable-service.sysext","result":"PASS","duration":96301459774,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"cl.metadata.azure","result":"PASS","duration":96503577629,"output":""},{"name":"cl.users.shells","result":"PASS","duration":96015791404,"output":""},{"name":"cl.toolbox.dnf-install","result":"PASS","duration":115101912769,"output":""},{"name":"docker.selinux","result":"PASS","duration":113547856623,"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.ignition.v2_1.vfat","result":"PASS","duration":98146474729,"output":""},{"name":"coreos.selinux.boolean","result":"PASS","duration":126881273307,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":99956294108,"output":""},{"name":"docker.base/networks-reliably","result":"PASS","duration":145881050639,"output":" 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.16MB 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:dab2ae9b327a83fb33b1d97efd21211cd853c138f827384af53c9e87dc1fe9a6 done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.base/user-no-caps","result":"PASS","duration":4338384320,"output":" 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.22MB 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:714417aed0046ff137387d7efbc34556cf303390c6baa8917439f6016f95edc8 done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":139087158209,"output":""},{"name":"docker.base/ownership","result":"PASS","duration":9260148462,"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: cf84d112621e: Pulling fs layer\n cluster.go:125: 210438394bdb: Pulling fs layer\n cluster.go:125: 0b92d3a9794b: Pulling fs layer\n cluster.go:125: f11479c4f377: Pulling fs layer\n cluster.go:125: b56daa2f5448: Pulling fs layer\n cluster.go:125: 4678031b247f: Pulling fs layer\n cluster.go:125: d0acbf743fbf: Pulling fs layer\n cluster.go:125: f11479c4f377: Waiting\n cluster.go:125: b56daa2f5448: Waiting\n cluster.go:125: 4678031b247f: Waiting\n cluster.go:125: d0acbf743fbf: Waiting\n cluster.go:125: 0b92d3a9794b: Verifying Checksum\n cluster.go:125: 0b92d3a9794b: Download complete\n cluster.go:125: f11479c4f377: Verifying Checksum\n cluster.go:125: f11479c4f377: Download complete\n cluster.go:125: b56daa2f5448: Verifying Checksum\n cluster.go:125: b56daa2f5448: Download complete\n cluster.go:125: 210438394bdb: Verifying Checksum\n cluster.go:125: 210438394bdb: Download complete\n cluster.go:125: d0acbf743fbf: Verifying Checksum\n cluster.go:125: d0acbf743fbf: Download complete\n cluster.go:125: cf84d112621e: Verifying Checksum\n cluster.go:125: cf84d112621e: Download complete\n cluster.go:125: 4678031b247f: Verifying Checksum\n cluster.go:125: 4678031b247f: Download complete\n cluster.go:125: cf84d112621e: Pull complete\n cluster.go:125: 210438394bdb: Pull complete\n cluster.go:125: 0b92d3a9794b: Pull complete\n cluster.go:125: f11479c4f377: Pull complete\n cluster.go:125: b56daa2f5448: Pull complete\n cluster.go:125: 4678031b247f: Pull complete\n cluster.go:125: d0acbf743fbf: Pull complete\n cluster.go:125: Digest: sha256:244b60108323653955f0ab9e8b44399c4bd0843f056eb262a8c09239341d3f8f\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.base","result":"PASS","duration":270235817517,"output":" --- PASS: docker.base/docker-info (3.39s)\n --- PASS: docker.base/resources (12.07s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring 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: 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:b2cfa9d33531e363f027d6fb2e371290879e9555cc7e9a80679b940ca7a952c7\n cluster.go:125: #5 writing image sha256:b2cfa9d33531e363f027d6fb2e371290879e9555cc7e9a80679b940ca7a952c7 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 OomKillDisable. OomKillDisable discarded.\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n --- PASS: docker.base/networks-reliably (145.88s)\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.16MB 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:dab2ae9b327a83fb33b1d97efd21211cd853c138f827384af53c9e87dc1fe9a6 done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.base/user-no-caps (4.34s)\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.22MB 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:714417aed0046ff137387d7efbc34556cf303390c6baa8917439f6016f95edc8 done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.base/ownership (9.26s)\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: cf84d112621e: Pulling fs layer\n cluster.go:125: 210438394bdb: Pulling fs layer\n cluster.go:125: 0b92d3a9794b: Pulling fs layer\n cluster.go:125: f11479c4f377: Pulling fs layer\n cluster.go:125: b56daa2f5448: Pulling fs layer\n cluster.go:125: 4678031b247f: Pulling fs layer\n cluster.go:125: d0acbf743fbf: Pulling fs layer\n cluster.go:125: f11479c4f377: Waiting\n cluster.go:125: b56daa2f5448: Waiting\n cluster.go:125: 4678031b247f: Waiting\n cluster.go:125: d0acbf743fbf: Waiting\n cluster.go:125: 0b92d3a9794b: Verifying Checksum\n cluster.go:125: 0b92d3a9794b: Download complete\n cluster.go:125: f11479c4f377: Verifying Checksum\n cluster.go:125: f11479c4f377: Download complete\n cluster.go:125: b56daa2f5448: Verifying Checksum\n cluster.go:125: b56daa2f5448: Download complete\n cluster.go:125: 210438394bdb: Verifying Checksum\n cluster.go:125: 210438394bdb: Download complete\n cluster.go:125: d0acbf743fbf: Verifying Checksum\n cluster.go:125: d0acbf743fbf: Download complete\n cluster.go:125: cf84d112621e: Verifying Checksum\n cluster.go:125: cf84d112621e: Download complete\n cluster.go:125: 4678031b247f: Verifying Checksum\n cluster.go:125: 4678031b247f: Download complete\n cluster.go:125: cf84d112621e: Pull complete\n cluster.go:125: 210438394bdb: Pull complete\n cluster.go:125: 0b92d3a9794b: Pull complete\n cluster.go:125: f11479c4f377: Pull complete\n cluster.go:125: b56daa2f5448: Pull complete\n cluster.go:125: 4678031b247f: Pull complete\n cluster.go:125: d0acbf743fbf: Pull complete\n cluster.go:125: Digest: sha256:244b60108323653955f0ab9e8b44399c4bd0843f056eb262a8c09239341d3f8f\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"coreos.auth.verify","result":"PASS","duration":74982214449,"output":""},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":100508092555,"output":""},{"name":"docker.btrfs-storage","result":"PASS","duration":98573162683,"output":""},{"name":"docker.containerd-restart","result":"PASS","duration":168406908076,"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"},{"name":"cl.cloudinit.script","result":"PASS","duration":96582009703,"output":""},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":108389971029,"output":""},{"name":"sysext.simple","result":"PASS","duration":102713936331,"output":""},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"FAIL","duration":102037509072,"output":" filesystem.go:415: Couldn't start machine: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-20c65161f7/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-2a9cdd5161\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: OperationNotAllowed\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"OperationNotAllowed\",\n \"message\": \"Operation could not be completed as it results in exceeding approved standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Current Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.verity/corruption","result":"PASS","duration":176802301989,"output":""},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":99513685697,"output":""},{"name":"cl.verity","result":"PASS","duration":369968521949,"output":" --- PASS: cl.verity/verify (95.41s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (176.80s)\n"},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":1706395006,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":2048907545,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":1734158883,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":1731973675,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":2174713901,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":1827526590,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":1657651952,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":1635237553,"output":""},{"name":"kubeadm.v1.36.1.calico.base/node_readiness","result":"PASS","duration":22001129634,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":15189524777,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":1668544306,"output":""},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":248113034647,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\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: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0605 23:33:50.018904 2574 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-5cec9cec18\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-5cec9cec18\": lookup ci-4081.3.8-n-5cec9cec18 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: W0605 23:33:50.193718 2574 checks.go:907] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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-4081.3.8-n-5cec9cec18 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.17]\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 785.919µ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.17: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 8.931265ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 18.494889ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.501192058s\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-4081.3.8-n-5cec9cec18 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-4081.3.8-n-5cec9cec18 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: wf65t0.0xxhq8aax5zs13aa\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.17:6443 --token wf65t0.0xxhq8aax5zs13aa \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:dade8b95357634e7d336a1b0a80b9f8e24ccc74d3be6084a94f0be6ae9ac5152 \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-20c65161f7/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-0f2d075e2d\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: OperationNotAllowed\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"OperationNotAllowed\",\n \"message\": \"Operation could not be completed as it results in exceeding approved standardDPLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Current Limit: 65, Current Usage: 64, Additional Required: 2, (Minimum) New Limit Required: 66. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%220e46bd28-a80f-4d3a-8200-d9eb8d80cb2e%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDPLSv5Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDPLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.basic/ServicesActive","result":"PASS","duration":1630522622,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":1693095283,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":96083282427,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"cl.basic/RandomUUID","result":"PASS","duration":1722505106,"output":""},{"name":"cl.ignition.misc.empty","result":"PASS","duration":96581099176,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":1714028071,"output":""},{"name":"kubeadm.v1.36.1.calico.base/nginx_deployment","result":"PASS","duration":10225787411,"output":""},{"name":"cl.basic","result":"PASS","duration":124849074323,"output":" --- PASS: cl.basic/UpdateEngineKeys (1.71s)\n --- PASS: cl.basic/Useradd (2.05s)\n --- PASS: cl.basic/MachineID (1.73s)\n --- PASS: cl.basic/Microcode (1.73s)\n --- PASS: cl.basic/CloudConfig (2.17s)\n --- PASS: cl.basic/Script (1.83s)\n --- PASS: cl.basic/PortSSH (1.66s)\n --- PASS: cl.basic/Symlink (1.64s)\n --- PASS: cl.basic/SymlinkFlatcar (1.67s)\n --- PASS: cl.basic/ServicesActive (1.63s)\n --- PASS: cl.basic/ReadOnly (1.69s)\n --- PASS: cl.basic/RandomUUID (1.72s)\n --- PASS: cl.basic/DbusPerms (1.71s)\n"},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":10194551063,"output":""},{"name":"cl.network.iptables","result":"PASS","duration":95965575971,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":21220261567,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"PASS","duration":324644764342,"output":" cluster.go:125: I0605 23:32:26.286176 2337 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\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: I0605 23:32:39.803302 2600 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-e9355e95f2\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-e9355e95f2\": lookup ci-4081.3.8-n-e9355e95f2 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: W0605 23:32:39.986442 2600 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-e9355e95f2 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 1.001880571s\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-controller-manager is healthy after 3.013479567s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.828577434s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501401s\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-4081.3.8-n-e9355e95f2 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-4081.3.8-n-e9355e95f2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: udbb12.jioaxd8ap3gihfx1\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.23:6443 --token udbb12.jioaxd8ap3gihfx1 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:b87296f04cf999bba02c3b09e4a34f66e38dcc3872629bd3a40bbfae77c02987 \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: W0605 23:33:52.469395 2176 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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.flannel.base/node_readiness (15.19s)\n --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (10.19s)\n --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (21.22s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.calico.base/NFS_deployment","result":"PASS","duration":34826915265,"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 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":"coreos.ignition.security.tls","result":"PASS","duration":205754263994,"output":""},{"name":"kubeadm.v1.36.1.calico.base","result":"PASS","duration":434550224097,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\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: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0605 23:31:10.648273 2614 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-6852c2afb3\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-6852c2afb3\": lookup ci-4081.3.8-n-6852c2afb3 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: W0605 23:31:10.756474 2614 checks.go:907] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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-4081.3.8-n-6852c2afb3 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.27]\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 595.88µ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.27: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 12.620003ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 14.100603ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002254795s\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-4081.3.8-n-6852c2afb3 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-4081.3.8-n-6852c2afb3 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: i0m2vv.3wnhswgep7thgdc2\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.27:6443 --token i0m2vv.3wnhswgep7thgdc2 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:8a646f6724ceb04afd960e0d87b25b317aea8cb310df02455b7e27828d49d00e \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0605 23:33:44.576364 2258 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0605 23:33:44.591206 2258 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W0605 23:33:44.730788 2258 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.calico.base/node_readiness (22.00s)\n --- PASS: kubeadm.v1.36.1.calico.base/nginx_deployment (10.23s)\n --- PASS: kubeadm.v1.36.1.calico.base/NFS_deployment (34.83s)\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 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":"cl.overlay.cleanup","result":"PASS","duration":131786898003,"output":""},{"name":"cl.ignition.v1.noop","result":"PASS","duration":96494934370,"output":""},{"name":"cl.ignition.v2.users","result":"PASS","duration":74211716422,"output":""},{"name":"kubeadm.v1.34.4.calico.cgroupv1.base/node_readiness","result":"PASS","duration":35520859909,"output":""},{"name":"systemd.journal.user","result":"PASS","duration":96884193346,"output":""},{"name":"sysext.custom-docker.sysext","result":"PASS","duration":160838241394,"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.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\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.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n"},{"name":"kubeadm.v1.34.4.calico.cgroupv1.base/nginx_deployment","result":"PASS","duration":17000208983,"output":""},{"name":"docker.userns","result":"PASS","duration":106044981184,"output":" 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: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.26MB 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:cf8005e3ea65cfc705e2d58f3ca2f3a83ad535f9f779b995d01867529ec6b186 done\n cluster.go:125: #5 naming to docker.io/library/userns-test 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"coreos.locksmith.tls","result":"PASS","duration":164903864265,"output":""},{"name":"coreos.selinux.enforce","result":"PASS","duration":135568251557,"output":""},{"name":"kubeadm.v1.34.4.calico.cgroupv1.base/NFS_deployment","result":"PASS","duration":34603058069,"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 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":"docker.lib-coreos-dockerd-compat/docker-info","result":"PASS","duration":3324536767,"output":""},{"name":"kubeadm.v1.34.4.calico.cgroupv1.base","result":"PASS","duration":427715344791,"output":" cluster.go:125: I0605 23:32:39.397786 2520 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0\n cluster.go:125: I0605 23:32:52.505833 2826 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-d0fb7aae66\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-d0fb7aae66\": lookup ci-4081.3.8-n-d0fb7aae66 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: W0605 23:32:52.656250 2826 checks.go:827] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-d0fb7aae66 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.16]\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 2.00761698s\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.16: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 4.633159389s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 5.332387387s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.501343821s\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-4081.3.8-n-d0fb7aae66 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-4081.3.8-n-d0fb7aae66 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: nvx2dp.gy6tcpy12p295qs9\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.16:6443 --token nvx2dp.gy6tcpy12p295qs9 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:7ec805c00c007358bfc98d086b7c9b2b8196e97dad6444b1ff443c9e36e8196c \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0605 23:35:00.436312 2389 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.34.4.calico.cgroupv1.base/node_readiness (35.52s)\n --- PASS: kubeadm.v1.34.4.calico.cgroupv1.base/nginx_deployment (17.00s)\n --- PASS: kubeadm.v1.34.4.calico.cgroupv1.base/NFS_deployment (34.60s)\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 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":"docker.lib-coreos-dockerd-compat/resources","result":"PASS","duration":12023934036,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring 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: 2B done\n cluster.go:125: #2 DONE 0.1s\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.1s\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:587ae40196650c10da83608b36ab1224eb66856c20d1a6330dbc24e4b3223d76 done\n cluster.go:125: #5 naming to docker.io/library/sleep 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n"},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":15173523750,"output":""},{"name":"cl.update.badverity","result":"PASS","duration":456908999346,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/node_readiness","result":"PASS","duration":22008038623,"output":""},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":100174425497,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"PASS","duration":16973666009,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/nginx_deployment","result":"PASS","duration":10196833047,"output":""},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":99396904139,"output":""},{"name":"cl.locksmith.cluster","result":"PASS","duration":449656550598,"output":""},{"name":"cl.ignition.v1.groups","result":"PASS","duration":80545306157,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"PASS","duration":20968875451,"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":"cl.ignition.luks","result":"PASS","duration":97914758574,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/NFS_deployment","result":"PASS","duration":20687087666,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"cl.ignition.v2.noop","result":"PASS","duration":95802070013,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"PASS","duration":21871351434,"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":"cl.internet/DockerEcho","result":"PASS","duration":5840961184,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/IPSec_encryption","result":"PASS","duration":22417664979,"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":393111372773,"output":" cluster.go:125: I0605 23:34:34.267381 2401 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\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: I0605 23:34:48.189918 2665 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-9359deb34d\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-9359deb34d\": lookup ci-4081.3.8-n-9359deb34d 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: W0605 23:34:48.440911 2665 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-9359deb34d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.33]\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 512.789139ms\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.33: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 3.011559003s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.798035159s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501735397s\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-4081.3.8-n-9359deb34d 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-4081.3.8-n-9359deb34d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 2sej7c.v8tgpakhdppqb27p\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.33:6443 --token 2sej7c.v8tgpakhdppqb27p \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:2d91c5dfc2a2876f0ea9759004e6a553176a748eeef9c9208b23f69a1213ff53 \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: W0605 23:36:33.782068 2248 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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 (15.17s)\n --- PASS: kubeadm.v1.35.1.cilium.base/nginx_deployment (16.97s)\n --- PASS: kubeadm.v1.35.1.cilium.base/NFS_deployment (20.97s)\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.35.1.cilium.base/IPSec_encryption (21.87s)\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":"coreos.locksmith.reboot","result":"PASS","duration":413985699453,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base","result":"PASS","duration":411145877400,"output":" cluster.go:125: I0605 23:34:33.252294 2535 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0\n cluster.go:125: I0605 23:34:46.297082 2753 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-7c942a1a41\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-7c942a1a41\": lookup ci-4081.3.8-n-7c942a1a41 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: W0605 23:34:46.449391 2753 checks.go:827] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-7c942a1a41 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.32]\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 2.002143106s\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.32: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 2.745641221s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.761494593s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501803505s\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-4081.3.8-n-7c942a1a41 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-4081.3.8-n-7c942a1a41 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 82mtep.8n5aueubdreg80cw\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.32:6443 --token 82mtep.8n5aueubdreg80cw \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:e93bf290217322372684f80b370facef7e6fc62c5934379b13773b910fb84787 \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: W0605 23:36:37.707835 2383 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is in maintenance mode, please migrate to cgroups v2\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.34.4.cilium.cgroupv1.base/node_readiness (22.01s)\n --- PASS: kubeadm.v1.34.4.cilium.cgroupv1.base/nginx_deployment (10.20s)\n --- PASS: kubeadm.v1.34.4.cilium.cgroupv1.base/NFS_deployment (20.69s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.34.4.cilium.cgroupv1.base/IPSec_encryption (22.42s)\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.internet/NTPDate","result":"PASS","duration":8473492038,"output":""},{"name":"cl.internet/UpdateEngine","result":"PASS","duration":1724381663,"output":""},{"name":"cl.internet/DockerPing","result":"PASS","duration":5271731488,"output":""},{"name":"cl.internet","result":"PASS","duration":123139407380,"output":" --- PASS: cl.internet/DockerEcho (5.84s)\n --- PASS: cl.internet/NTPDate (8.47s)\n --- PASS: cl.internet/UpdateEngine (1.72s)\n --- PASS: cl.internet/DockerPing (5.27s)\n"},{"name":"systemd.sysusers.gshadow","result":"PASS","duration":80233014800,"output":""},{"name":"docker.lib-coreos-dockerd-compat/networks-reliably","result":"FAIL","duration":113430841115,"output":" 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.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.16MB 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.1s\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:1937d71d39654b80270ee16774e795f35661921518e5fa65f0a353e28293e51f\n cluster.go:125: #5 writing image sha256:1937d71d39654b80270ee16774e795f35661921518e5fa65f0a353e28293e51f done\n cluster.go:125: #5 naming to docker.io/library/ping 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:145: \"for i in $(seq 1 100); do\\n\\t\\techo -n \\\"$i: \\\"\\n\\t\\tdocker run --rm ping sh -c 'ping -i 0.2 172.17.0.1 -w 1 \u003e/dev/null \u0026\u0026 echo PASS || echo FAIL'\\n\\tdone\" failed: output 1: PASS\n2: PASS\n3: PASS\n4: PASS\n5: PASS\n6: PASS\n7: PASS\n8: PASS\n9: PASS\n10: PASS\n11: PASS\n12: PASS\n13: PASS\n14: PASS\n15: PASS\n16: PASS\n17: PASS\n18: PASS\n19: PASS\n20: PASS\n21: PASS\n22: PASS\n23: PASS\n24: PASS\n25: PASS\n26: PASS\n27: PASS\n28: PASS\n29: PASS\n30: PASS\n31: PASS\n32: PASS\n33: PASS\n34: PASS\n35: PASS\n36: PASS\n37: PASS\n38: PASS\n39: PASS\n40: PASS\n41: PASS\n42: PASS\n43: PASS\n44: PASS\n45: PASS\n46: PASS\n47: PASS\n48: PASS\n49: PASS\n50: PASS\n51: PASS\n52: PASS\n53: PASS\n54: PASS\n55: PASS\n56: PASS\n57: PASS\n58: PASS\n59: PASS\n60: PASS\n61: PASS\n62: PASS\n63: PASS\n64: PASS\n65: PASS\n66: PASS\n67: PASS\n68: PASS\n69: PASS\n70: PASS\n71: PASS\n72: PASS\n73:, status wait: remote command exited without exit status or exit signal\n"},{"name":"docker.lib-coreos-dockerd-compat/user-no-caps","result":"FAIL","duration":287211681,"output":" cluster.go:145: \"tmpdir=$(mktemp -d); cd $tmpdir; echo -e \\\"FROM scratch\\\\nCOPY . /\\\" \u003e Dockerfile;\\n\\t b=$(which capsh sh grep cat ls); libs=$(sudo ldd $b | grep -o /lib'[^ ]*' | sort -u);\\n\\t sudo rsync -av --relative --copy-links $b $libs ./;\\n\\t sudo docker build -t captest .\" failed: output , status ssh: handshake failed: read tcp 10.200.1.7:50882-\u003e20.94.200.245:22: read: connection reset by peer\n"},{"name":"cl.cloudinit.basic","result":"FAIL","duration":66944568921,"output":" cluster.go:145: \"hostnamectl\" failed: output , status ssh: unexpected packet in response to channel open: \u003cnil\u003e\n"},{"name":"cl.update.reboot","result":"FAIL","duration":101219096634,"output":" cluster.go:145: \"sudo dd if=/dev/disk/by-partlabel/USR-A of=/dev/disk/by-partlabel/USR-B bs=10M status=none\" failed: output , status wait: remote command exited without exit status or exit signal\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":250289845090,"output":" cluster.go:125: I0605 23:38:13.801978 2499 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\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: I0605 23:38:26.015509 2709 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-8f25eb42d4\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-8f25eb42d4\": lookup ci-4081.3.8-n-8f25eb42d4 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: W0605 23:38:26.177783 2709 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-8f25eb42d4 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 1.002204485s\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-scheduler is healthy after 3.936559795s\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.008098709s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 6.00184256s\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-4081.3.8-n-8f25eb42d4 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-4081.3.8-n-8f25eb42d4 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: vlhk48.g0j6smeigdhhht2b\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 kubeadm.go:197: unable to setup cluster: unable to run master script: wait: remote command exited without exit status or exit signal\n"},{"name":"kubeadm.v1.34.4.calico.base","result":"FAIL","duration":235742621033,"output":" cluster.go:125: I0605 23:37:56.551465 2396 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0\n cluster.go:125: I0605 23:38:07.359457 2678 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-fc7f92f79d\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-fc7f92f79d\": lookup ci-4081.3.8-n-fc7f92f79d 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: W0605 23:38:07.585141 2678 checks.go:827] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-fc7f92f79d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.5]\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.001656822s\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.5: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 3.233655664s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.589005316s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.002015074s\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-4081.3.8-n-fc7f92f79d 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-4081.3.8-n-fc7f92f79d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 4162ip.4xqqmm7r9ek80wnn\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.5:6443 --token 4162ip.4xqqmm7r9ek80wnn \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:3f3408ff0dc76f1d0f43d2e803b354a265efb119eeed857edcfd7a06d744a587 \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n kubeadm.go:197: unable to setup cluster: unable to run master script: wait: remote command exited without exit status or exit signal\n"},{"name":"docker.lib-coreos-dockerd-compat/ownership","result":"FAIL","duration":10721653678,"output":" cluster.go:145: \"docker run --name ownership ghcr.io/flatcar/nginx stat -c \\\"%u/%g\\\" /etc/shadow\" failed: output , status dial tcp 20.94.200.245:22: i/o timeout\n"},{"name":"sysext.disable-containerd","result":"FAIL","duration":92085011976,"output":" harness.go:646: Cluster failed starting machines: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-20c65161f7/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-50db7b9576\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"FAIL","duration":233948112308,"output":" --- PASS: docker.lib-coreos-dockerd-compat/docker-info (3.32s)\n --- PASS: docker.lib-coreos-dockerd-compat/resources (12.02s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring 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: 2B done\n cluster.go:125: #2 DONE 0.1s\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.1s\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:587ae40196650c10da83608b36ab1224eb66856c20d1a6330dbc24e4b3223d76 done\n cluster.go:125: #5 naming to docker.io/library/sleep 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n --- FAIL: docker.lib-coreos-dockerd-compat/networks-reliably (113.43s)\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.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.16MB 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.1s\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:1937d71d39654b80270ee16774e795f35661921518e5fa65f0a353e28293e51f\n cluster.go:125: #5 writing image sha256:1937d71d39654b80270ee16774e795f35661921518e5fa65f0a353e28293e51f done\n cluster.go:125: #5 naming to docker.io/library/ping 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:145: \"for i in $(seq 1 100); do\\n\\t\\techo -n \\\"$i: \\\"\\n\\t\\tdocker run --rm ping sh -c 'ping -i 0.2 172.17.0.1 -w 1 \u003e/dev/null \u0026\u0026 echo PASS || echo FAIL'\\n\\tdone\" failed: output 1: PASS\n 2: PASS\n 3: PASS\n 4: PASS\n 5: PASS\n 6: PASS\n 7: PASS\n 8: PASS\n 9: PASS\n 10: PASS\n 11: PASS\n 12: PASS\n 13: PASS\n 14: PASS\n 15: PASS\n 16: PASS\n 17: PASS\n 18: PASS\n 19: PASS\n 20: PASS\n 21: PASS\n 22: PASS\n 23: PASS\n 24: PASS\n 25: PASS\n 26: PASS\n 27: PASS\n 28: PASS\n 29: PASS\n 30: PASS\n 31: PASS\n 32: PASS\n 33: PASS\n 34: PASS\n 35: PASS\n 36: PASS\n 37: PASS\n 38: PASS\n 39: PASS\n 40: PASS\n 41: PASS\n 42: PASS\n 43: PASS\n 44: PASS\n 45: PASS\n 46: PASS\n 47: PASS\n 48: PASS\n 49: PASS\n 50: PASS\n 51: PASS\n 52: PASS\n 53: PASS\n 54: PASS\n 55: PASS\n 56: PASS\n 57: PASS\n 58: PASS\n 59: PASS\n 60: PASS\n 61: PASS\n 62: PASS\n 63: PASS\n 64: PASS\n 65: PASS\n 66: PASS\n 67: PASS\n 68: PASS\n 69: PASS\n 70: PASS\n 71: PASS\n 72: PASS\n 73:, status wait: remote command exited without exit status or exit signal\n --- FAIL: docker.lib-coreos-dockerd-compat/user-no-caps (0.29s)\n cluster.go:145: \"tmpdir=$(mktemp -d); cd $tmpdir; echo -e \\\"FROM scratch\\\\nCOPY . /\\\" \u003e Dockerfile;\\n\\t b=$(which capsh sh grep cat ls); libs=$(sudo ldd $b | grep -o /lib'[^ ]*' | sort -u);\\n\\t sudo rsync -av --relative --copy-links $b $libs ./;\\n\\t sudo docker build -t captest .\" failed: output , status ssh: handshake failed: read tcp 10.200.1.7:50882-\u003e20.94.200.245:22: read: connection reset by peer\n --- FAIL: docker.lib-coreos-dockerd-compat/ownership (10.72s)\n cluster.go:145: \"docker run --name ownership ghcr.io/flatcar/nginx stat -c \\\"%u/%g\\\" /etc/shadow\" failed: output , status dial tcp 20.94.200.245:22: i/o timeout\n"},{"name":"kubeadm.v1.34.4.flannel.cgroupv1.base","result":"FAIL","duration":83250885512,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4081.3.8-n-fffe2f043d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-20c65161f7/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-fffe2f043d\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":194893711770,"output":" resource.go:333: starting client: PollUntilDone(ci-4081.3.8-n-1cfb48701a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/81f582e2-0cd8-42c5-970e-e35a002aea0b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:37:39.293001+00:00\",\n \"endTime\": \"2026-06-05T23:38:50.1203992+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"81f582e2-0cd8-42c5-970e-e35a002aea0b\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":313615727699,"output":" cluster.go:125: I0605 23:36:58.769344 2349 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0\n cluster.go:125: I0605 23:37:10.170776 2630 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-a6a42f8e1c\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-a6a42f8e1c\": lookup ci-4081.3.8-n-a6a42f8e1c 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: W0605 23:37:10.321711 2630 checks.go:827] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-a6a42f8e1c kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.30]\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.001201948s\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.30: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 3.627819449s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.826152553s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501229419s\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-4081.3.8-n-a6a42f8e1c 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-4081.3.8-n-a6a42f8e1c as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: stbx5y.zyh1qoa3v39xcu92\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.30:6443 --token stbx5y.zyh1qoa3v39xcu92 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:22ee5e36849ccd21b6d7fdd8ec6d57f42900025d599fbddb05a1e9e17d575c9b \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-20c65161f7/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-0a5e14b90c\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":154980054686,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.8-n-fc36551dd8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/bceb61eb-fad7-4a7f-90eb-32e32d7c8fe0\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:38:11.7858216+00:00\",\n \"endTime\": \"2026-06-05T23:38:49.7310134+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"bceb61eb-fad7-4a7f-90eb-32e32d7c8fe0\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":294491681908,"output":" cluster.go:125: I0605 23:37:28.138303 2396 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.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.5-0\n cluster.go:125: I0605 23:37:55.392116 2662 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-e75af2c1f3\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-e75af2c1f3\": lookup ci-4081.3.8-n-e75af2c1f3 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: W0605 23:37:55.539288 2662 checks.go:827] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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-4081.3.8-n-e75af2c1f3 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.17]\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.001563321s\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.17: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 3.349386034s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.1561492s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 6.001930548s\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-4081.3.8-n-e75af2c1f3 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-4081.3.8-n-e75af2c1f3 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 4sv0ce.rf7sd5hxyo4l6o19\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.17:6443 --token 4sv0ce.rf7sd5hxyo4l6o19 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:41c7c4f232dbed19e62ab11bc19fd4b0ec47b026fe547a32b5b05a17831cee6d \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4081.3.8-n-0872b253a9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/f292a6c9-8f3c-4dce-936e-32fdfdc25c1b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:38:15.4869702+00:00\",\n \"endTime\": \"2026-06-05T23:38:49.3264187+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"f292a6c9-8f3c-4dce-936e-32fdfdc25c1b\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.ssh.key","result":"FAIL","duration":755076298911,"output":" harness.go:646: Cluster failed starting machines: machine \"ci-4081.3.8-n-7307521df7\" failed to start: ssh journalctl failed: time limit exceeded: ssh: handshake failed: EOF\n"},{"name":"bpf.ig/ig","result":"FAIL","duration":723827662197,"output":" ig.go:50: creating node: machine \"ci-4081.3.8-n-9eb7815e1d\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.94.202.44:22: i/o timeout\n"},{"name":"bpf.ig","result":"FAIL","duration":725828898167,"output":" --- FAIL: bpf.ig/ig (723.83s)\n ig.go:50: creating node: machine \"ci-4081.3.8-n-9eb7815e1d\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.94.202.44:22: i/o timeout\n"},{"name":"coreos.update.badusr","result":"FAIL","duration":1316035169030,"output":" update.go:168: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"\", stderr: \"\", err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, systemctl list-jobs returned stdout: \"\", stderr: \"\", err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":4807264862605,"output":" harness.go:646: Cluster failed starting machines: machine \"ci-4081.3.8-n-5fb93b7c7e\" failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"\", stderr: \"\", err: dial tcp 20.109.164.252:22: i/o timeout, systemctl list-jobs returned stdout: \"\", stderr: \"\", err: dial tcp 20.109.164.252:22: i/o timeout\n"}],"result":"FAIL","platform":"azure","version":"4081.3.8"}