{"tests":[{"name":"docker.base/docker-info","result":"PASS","duration":2590708801,"output":""},{"name":"cl.ignition.luks","result":"PASS","duration":83629919558,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":83737387478,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"sysext.simple","result":"PASS","duration":84812274947,"output":""},{"name":"docker.base/resources","result":"PASS","duration":9020143639,"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.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.20MB 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:6f83800d28b4d54a7d72c8d161ab7868116231b266bcd853ac70e656858e0a7c done\n cluster.go:125: #5 naming to docker.io/library/sleep\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n"},{"name":"bpf.ig/ig","result":"PASS","duration":92980025938,"output":" cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"bpf.ig","result":"PASS","duration":95294662643,"output":" --- PASS: bpf.ig/ig (92.98s)\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"cl.basic/Microcode","result":"PASS","duration":289113004,"output":""},{"name":"coreos.auth.verify","result":"PASS","duration":113119096837,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":972471472,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":376021965,"output":""},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":113977899805,"output":""},{"name":"cl.ignition.v2.noop","result":"PASS","duration":114027658406,"output":""},{"name":"systemd.sysusers.gshadow","result":"PASS","duration":114117031223,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":274887589,"output":""},{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":114287807905,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":329089096,"output":""},{"name":"cl.ignition.v1.groups","result":"PASS","duration":114522235988,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":266708971,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":270923596,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":303299773,"output":""},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":115372602260,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":271479605,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":299972495,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":319054015,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":1179171660,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":271149302,"output":""},{"name":"coreos.locksmith.tls","result":"PASS","duration":118138345285,"output":""},{"name":"cl.basic","result":"PASS","duration":120068441151,"output":" --- PASS: cl.basic/Microcode (0.29s)\n --- PASS: cl.basic/CloudConfig (0.97s)\n --- PASS: cl.basic/Script (0.38s)\n --- PASS: cl.basic/PortSSH (0.27s)\n --- PASS: cl.basic/DbusPerms (0.33s)\n --- PASS: cl.basic/Symlink (0.27s)\n --- PASS: cl.basic/SymlinkFlatcar (0.27s)\n --- PASS: cl.basic/UpdateEngineKeys (0.30s)\n --- PASS: cl.basic/ReadOnly (0.27s)\n --- PASS: cl.basic/ServicesActive (0.30s)\n --- PASS: cl.basic/RandomUUID (0.32s)\n --- PASS: cl.basic/Useradd (1.18s)\n --- PASS: cl.basic/MachineID (0.27s)\n"},{"name":"coreos.ignition.once","result":"PASS","duration":139969406121,"output":""},{"name":"coreos.selinux.enforce","result":"PASS","duration":142781845237,"output":""},{"name":"cl.update.reboot","result":"PASS","duration":156605509133,"output":""},{"name":"cl.cloudinit.script","result":"PASS","duration":82904785848,"output":""},{"name":"cl.verity/verify","result":"PASS","duration":71959869889,"output":" cluster.go:125: Success\n"},{"name":"cl.ignition.translation","result":"PASS","duration":83210786327,"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":"cl.cloudinit.basic","result":"PASS","duration":83497463305,"output":""},{"name":"cl.cloudinit.multipart-mime","result":"PASS","duration":83728087368,"output":""},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":113754620456,"output":""},{"name":"cl.users.shells","result":"PASS","duration":113091347328,"output":""},{"name":"docker.btrfs-storage","result":"PASS","duration":116206736165,"output":""},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":113569553632,"output":""},{"name":"kubeadm.v1.34.4.calico.cgroupv1.base","result":"FAIL","duration":4390744554,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-916adab6e3\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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.etcd-member.etcdctlv3","result":"PASS","duration":83844265757,"output":" cluster.go:125: {\"level\":\"info\",\"ts\":1780702403.4418352,\"caller\":\"snapshot/v3_snapshot.go:68\",\"msg\":\"created temporary db file\",\"path\":\"/tmp/tmp.fx069pFhiw/snapshot.db.part\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702403.4428911,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:211\",\"msg\":\"opened snapshot stream; downloading\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702403.4429178,\"caller\":\"snapshot/v3_snapshot.go:76\",\"msg\":\"fetching snapshot\",\"endpoint\":\"127.0.0.1:2379\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702403.4443953,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:219\",\"msg\":\"completed snapshot read; closing\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1780702403.4444375,\"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\":1780702403.444497,\"caller\":\"snapshot/v3_snapshot.go:100\",\"msg\":\"saved\",\"path\":\"/tmp/tmp.fx069pFhiw/snapshot.db\"}\n cluster.go:125: Deprecated: Use `etcdutl snapshot status` instead.\n"},{"name":"cl.update.badverity","result":"FAIL","duration":2515300352,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-50562a10c4\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"docker.base/networks-reliably","result":"PASS","duration":154992567781,"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.04MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:242fdb3f052c42306ccc51e8e0117c3aec97aabd39cd8c9dd71416813e84198b 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":1848313257,"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.06MB 0.1s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:3adb0fd6b39fd0e25ed431949e9d09019c69c6ce930fbcd93bbed32d4c4c9656 done\n cluster.go:125: #5 naming to docker.io/library/captest 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"cl.network.wireguard","result":"PASS","duration":112964654724,"output":" cluster.go:152: + ip --json address show kv0 | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n"},{"name":"cl.flannel.vxlan","result":"PASS","duration":140841827216,"output":" flannel.go:121: ping from ci-4081.3.8-n-292f06e18c(10.254.6.0) to ci-4081.3.8-n-82cc35d0d7(10.254.95.0)\n"},{"name":"cl.ignition.v2.btrfsroot","result":"FAIL","duration":2493390056,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-3abc94567c\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"docker.base/ownership","result":"PASS","duration":7178765128,"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: 8211d5969d2e: Pulling fs layer\n cluster.go:125: c2e41b4ede23: Pulling fs layer\n cluster.go:125: f42dd3056dc3: Pulling fs layer\n cluster.go:125: 5e7d222aa83f: Pulling fs layer\n cluster.go:125: ff4adb702729: Pulling fs layer\n cluster.go:125: b526679e807a: Pulling fs layer\n cluster.go:125: f8cb9a22032f: Pulling fs layer\n cluster.go:125: 5e7d222aa83f: Waiting\n cluster.go:125: ff4adb702729: Waiting\n cluster.go:125: b526679e807a: Waiting\n cluster.go:125: f8cb9a22032f: Waiting\n cluster.go:125: f42dd3056dc3: Verifying Checksum\n cluster.go:125: f42dd3056dc3: Download complete\n cluster.go:125: 5e7d222aa83f: Verifying Checksum\n cluster.go:125: 5e7d222aa83f: Download complete\n cluster.go:125: ff4adb702729: Verifying Checksum\n cluster.go:125: ff4adb702729: Download complete\n cluster.go:125: b526679e807a: Verifying Checksum\n cluster.go:125: b526679e807a: Download complete\n cluster.go:125: 8211d5969d2e: Verifying Checksum\n cluster.go:125: 8211d5969d2e: Download complete\n cluster.go:125: f8cb9a22032f: Verifying Checksum\n cluster.go:125: f8cb9a22032f: Download complete\n cluster.go:125: c2e41b4ede23: Verifying Checksum\n cluster.go:125: c2e41b4ede23: Download complete\n cluster.go:125: 8211d5969d2e: Pull complete\n cluster.go:125: c2e41b4ede23: Pull complete\n cluster.go:125: f42dd3056dc3: Pull complete\n cluster.go:125: 5e7d222aa83f: Pull complete\n cluster.go:125: ff4adb702729: Pull complete\n cluster.go:125: b526679e807a: Pull complete\n cluster.go:125: f8cb9a22032f: 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":259017663119,"output":" --- PASS: docker.base/docker-info (2.59s)\n --- PASS: docker.base/resources (9.02s)\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.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.20MB 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:6f83800d28b4d54a7d72c8d161ab7868116231b266bcd853ac70e656858e0a7c done\n cluster.go:125: #5 naming to docker.io/library/sleep\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n --- PASS: docker.base/networks-reliably (154.99s)\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.04MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:242fdb3f052c42306ccc51e8e0117c3aec97aabd39cd8c9dd71416813e84198b 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 (1.85s)\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.06MB 0.1s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:3adb0fd6b39fd0e25ed431949e9d09019c69c6ce930fbcd93bbed32d4c4c9656 done\n cluster.go:125: #5 naming to docker.io/library/captest 0.0s done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.base/ownership (7.18s)\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: 8211d5969d2e: Pulling fs layer\n cluster.go:125: c2e41b4ede23: Pulling fs layer\n cluster.go:125: f42dd3056dc3: Pulling fs layer\n cluster.go:125: 5e7d222aa83f: Pulling fs layer\n cluster.go:125: ff4adb702729: Pulling fs layer\n cluster.go:125: b526679e807a: Pulling fs layer\n cluster.go:125: f8cb9a22032f: Pulling fs layer\n cluster.go:125: 5e7d222aa83f: Waiting\n cluster.go:125: ff4adb702729: Waiting\n cluster.go:125: b526679e807a: Waiting\n cluster.go:125: f8cb9a22032f: Waiting\n cluster.go:125: f42dd3056dc3: Verifying Checksum\n cluster.go:125: f42dd3056dc3: Download complete\n cluster.go:125: 5e7d222aa83f: Verifying Checksum\n cluster.go:125: 5e7d222aa83f: Download complete\n cluster.go:125: ff4adb702729: Verifying Checksum\n cluster.go:125: ff4adb702729: Download complete\n cluster.go:125: b526679e807a: Verifying Checksum\n cluster.go:125: b526679e807a: Download complete\n cluster.go:125: 8211d5969d2e: Verifying Checksum\n cluster.go:125: 8211d5969d2e: Download complete\n cluster.go:125: f8cb9a22032f: Verifying Checksum\n cluster.go:125: f8cb9a22032f: Download complete\n cluster.go:125: c2e41b4ede23: Verifying Checksum\n cluster.go:125: c2e41b4ede23: Download complete\n cluster.go:125: 8211d5969d2e: Pull complete\n cluster.go:125: c2e41b4ede23: Pull complete\n cluster.go:125: f42dd3056dc3: Pull complete\n cluster.go:125: 5e7d222aa83f: Pull complete\n cluster.go:125: ff4adb702729: Pull complete\n cluster.go:125: b526679e807a: Pull complete\n cluster.go:125: f8cb9a22032f: 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":"sysext.disable-containerd","result":"PASS","duration":82807019685,"output":""},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":114791648504,"output":""},{"name":"docker.enable-service.sysext","result":"PASS","duration":82752404102,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":107579734208,"output":""},{"name":"systemd.journal.user","result":"FAIL","duration":2742455514,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-030e12b4de\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"kubeadm.v1.34.4.flannel.cgroupv1.base/node_readiness","result":"PASS","duration":10906135759,"output":""},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":239456108348,"output":" cluster.go:125: I0605 23:34:03.451855 2414 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:16.804720 2717 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-73622daa05\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-73622daa05\": lookup ci-4081.3.8-n-73622daa05 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:17.013301 2717 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-73622daa05 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 500.695329ms\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 2.508981927s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.104121106s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.001959454s\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-73622daa05 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-73622daa05 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: i9nwj2.bbunf6wkemsiz5wa\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 i9nwj2.bbunf6wkemsiz5wa \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:33781e0e9583f59a72318e681679ae7d1c1d171a1a0c5e52e38caba72d197f5d \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 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-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-78588ebd1f\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"docker.selinux","result":"PASS","duration":88791317632,"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: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Verifying Checksum\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: 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.misc.empty","result":"PASS","duration":82641637337,"output":""},{"name":"kubeadm.v1.34.4.flannel.cgroupv1.base/nginx_deployment","result":"PASS","duration":21855373779,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":112614138124,"output":""},{"name":"kubeadm.v1.34.4.calico.base","result":"FAIL","duration":86009859305,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-ec70424b48\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"docker.lib-coreos-dockerd-compat","result":"FAIL","duration":2415589534,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-0afa97bf78\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"coreos.ignition.resource.local","result":"PASS","duration":226174081746,"output":""},{"name":"coreos.ignition.groups","result":"PASS","duration":83490732614,"output":""},{"name":"cl.ignition.v1.ext4root","result":"FAIL","duration":2727374257,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-31bbb9d7ab\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"coreos.ignition.resource.remote","result":"FAIL","duration":2631199307,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-7608fd495e\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":10963362661,"output":""},{"name":"cl.verity/corruption","result":"PASS","duration":169710697175,"output":""},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":110667344396,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-f9550263b1\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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","result":"PASS","duration":354788199235,"output":" --- PASS: cl.verity/verify (71.96s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (169.71s)\n"},{"name":"kubeadm.v1.34.4.flannel.cgroupv1.base/NFS_deployment","result":"PASS","duration":18019627227,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.flannel.cgroupv1.base","result":"PASS","duration":359261706973,"output":" cluster.go:125: I0605 23:32:41.517460 2606 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:53.870850 2825 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-66a98ce5e7\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-66a98ce5e7\": lookup ci-4081.3.8-n-66a98ce5e7 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:54.022544 2825 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-66a98ce5e7 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.24]\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 500.997088ms\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.24: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.334940661s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.841223604s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.501062173s\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-66a98ce5e7 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-66a98ce5e7 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: dcgbum.i81o5k69ig4y0k66\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.24:6443 --token dcgbum.i81o5k69ig4y0k66 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:745aa15b3939de1bd62238b0273cf727bf8ffcf7e3fbc2c8aabcb83a77c00c77 \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:34:28.446361 2441 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.flannel.cgroupv1.base/node_readiness (10.91s)\n --- PASS: kubeadm.v1.34.4.flannel.cgroupv1.base/nginx_deployment (21.86s)\n --- PASS: kubeadm.v1.34.4.flannel.cgroupv1.base/NFS_deployment (18.02s)\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.network.iptables","result":"FAIL","duration":83332457438,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n cluster.go:156: cmd sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right' did not output 80\n"},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":21853477332,"output":""},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":137373018288,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":17784504876,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"PASS","duration":389260269098,"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:32:53.402487 2587 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-de81c0c321\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-de81c0c321\": lookup ci-4081.3.8-n-de81c0c321 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:53.548917 2587 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-de81c0c321 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 602.806µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.25:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 8.781192ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 7.808182ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.502047482s\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-de81c0c321 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-de81c0c321 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: gxu1hv.rovtn4xhphu02ys8\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.25:6443 --token gxu1hv.rovtn4xhphu02ys8 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:b185fa289815872894a3c99b328e80c72cc56fc43194967785e80789520cfae4 \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:34:58.913278 2319 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0605 23:34:58.926324 2319 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:34:59.086326 2319 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.flannel.base/node_readiness (10.96s)\n --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (21.85s)\n --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (17.78s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"cl.ignition.v1.users","result":"PASS","duration":83380748771,"output":""},{"name":"docker.userns","result":"PASS","duration":87360266231,"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.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.24MB 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:fd3f94278b3e63d1e4b5cbcaa976f18278bc881fd25e044e80c6af4ce3c5b636\n cluster.go:125: #5 writing image sha256:fd3f94278b3e63d1e4b5cbcaa976f18278bc881fd25e044e80c6af4ce3c5b636 done\n cluster.go:125: #5 naming to docker.io/library/userns-test done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"kubeadm.v1.34.4.flannel.base/node_readiness","result":"PASS","duration":10957184930,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/node_readiness","result":"PASS","duration":21521336007,"output":""},{"name":"cl.ignition.symlink","result":"PASS","duration":82785763875,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"kubeadm.v1.34.4.flannel.base/nginx_deployment","result":"PASS","duration":21884925459,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/nginx_deployment","result":"PASS","duration":11249618948,"output":""},{"name":"cl.ignition.v2.users","result":"PASS","duration":114154089408,"output":""},{"name":"cl.ignition.v1.once","result":"PASS","duration":109504252638,"output":""},{"name":"cl.metadata.azure","result":"PASS","duration":112831707305,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/NFS_deployment","result":"PASS","duration":17794737811,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.flannel.base/NFS_deployment","result":"PASS","duration":18040559705,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"PASS","duration":357815253686,"output":" cluster.go:125: I0605 23:34:03.183763 2359 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:15.729554 2640 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-555f60e888\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-555f60e888\": lookup ci-4081.3.8-n-555f60e888 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:15.927152 2640 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-555f60e888 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.20]\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 500.911583ms\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.20: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.510480847s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.087428623s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.002127397s\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-555f60e888 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-555f60e888 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: sfs4gh.041r2usik5741fhu\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.20:6443 --token sfs4gh.041r2usik5741fhu \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:6d0b478f95c1a02d348c1ba7bf64d4c0bfbac7d21072f1a603694bb8bc9c2379 \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:36:21.329968 2319 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.34.4.flannel.base/node_readiness (10.96s)\n --- PASS: kubeadm.v1.34.4.flannel.base/nginx_deployment (21.88s)\n --- PASS: kubeadm.v1.34.4.flannel.base/NFS_deployment (18.04s)\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.etcd-member.v2-backup-restore","result":"PASS","duration":76456826572,"output":" cluster.go:125: 2026-06-05T23:36:52Z\tinfo\tetcdutl/backup_command.go:216\tignoring EntryConfChange raft entry\n cluster.go:125: 2026-06-05T23:36:52Z\tinfo\tetcdutl/backup_command.go:231\tignoring member attribute update on\t{\"entry\": \"Term:2 Index:3 Data:\\\"\\\\010\\\\202\\\\262\\\\214\\\\253\\\\242\\\\323\\\\347\\\\277\\\\312\\\\001\\\\022\\\\003PUT\\\\032\u0026/0/members/9445dee0ad4cca7f/attributes\\\\\\\"R{\\\\\\\"name\\\\\\\":\\\\\\\"0de7bfa96e2847a5942af1015744a2a9\\\\\\\",\\\\\\\"clientURLs\\\\\\\":[\\\\\\\"http://10.0.0.16:2379\\\\\\\"]}(\\\\0002\\\\0008\\\\000H\\\\000P\\\\000X\\\\000`\\\\000h\\\\000p\\\\000x\\\\000\\\\200\\\\001\\\\000\\\" \", \"v2Req.Path\": \"/0/members/9445dee0ad4cca7f/attributes\"}\n cluster.go:125: 2026-06-05T23:36:52Z\tinfo\tetcdutl/backup_command.go:252\tignoring v3 raft entry\n cluster.go:125: 2026-06-05T23:36:52Z\tinfo\tmembership/store.go:119\tTrimming membership information from the backend...\n"},{"name":"cl.toolbox.dnf-install","result":"PASS","duration":131245360119,"output":""},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":117264940076,"output":""},{"name":"cl.ignition.v1.noop","result":"PASS","duration":112008701091,"output":""},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"PASS","duration":193114768869,"output":""},{"name":"kubeadm.v1.34.4.cilium.cgroupv1.base/IPSec_encryption","result":"PASS","duration":17691846456,"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.34.4.cilium.cgroupv1.base","result":"PASS","duration":404650348070,"output":" cluster.go:125: I0605 23:34:03.723564 2559 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:16.044915 2872 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-e38a68c85b\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-e38a68c85b\": lookup ci-4081.3.8-n-e38a68c85b 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:16.218460 2872 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-e38a68c85b kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.7]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 500.832025ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.7:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.505276239s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.113121402s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.002235189s\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-e38a68c85b 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-e38a68c85b as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: r956wk.x33xmia1uj9jclk1\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.7:6443 --token r956wk.x33xmia1uj9jclk1 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:b3edb06ae154d1b4d63d0d196413c1d6565a9b22914bcd1fe58338bcae2476c8 \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: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\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:21.176513 2472 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 (21.52s)\n --- PASS: kubeadm.v1.34.4.cilium.cgroupv1.base/nginx_deployment (11.25s)\n --- PASS: kubeadm.v1.34.4.cilium.cgroupv1.base/NFS_deployment (17.79s)\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.34.4.cilium.cgroupv1.base/IPSec_encryption (17.69s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":21545435506,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"PASS","duration":11281650261,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"PASS","duration":17739426411,"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.v2_1.vfat","result":"PASS","duration":83064483021,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"FAIL","duration":31424765958,"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 cluster.go:145: \"/opt/bin/cilium status --wait --wait-duration 1m\" failed: output , status wait: remote command exited without exit status or exit signal\n"},{"name":"cl.swap_activation","result":"PASS","duration":82613845148,"output":""},{"name":"sysext.custom-docker.sysext","result":"FAIL","duration":145234378749,"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: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Verifying Checksum\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: 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 cluster.go:145: \"ONLY_DOCKER=1 FORMAT=ext4 ARCH=x86_64 sysext-bakery/create_docker_sysext.sh 26.1.0 docker \u0026\u0026 ONLY_CONTAINERD=1 FORMAT=ext4 ARCH=x86_64 sysext-bakery/create_docker_sysext.sh 26.1.0 containerd \u0026\u0026 sudo mv docker.raw containerd.raw /etc/extensions/\" failed: output Discarding device blocks: 0/262144\b\b\b\b\b\b\b\b\b\b\b\b\b \b\b\b\b\b\b\b\b\b\b\b\b\bdone \nCreating filesystem with 262144 4k blocks and 65536 inodes\nFilesystem UUID: a46ec372-32b2-4392-b94d-6cd437a1d7e8\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376\n\nAllocating group tables: 0/8\b\b\b \b\b\bdone \nWriting inode tables: 0/8\b\b\b \b\b\bdone \nCreating journal (8192 blocks): done\nCopying files into the device: done\nWriting superblocks and filesystem accounting information: 0/8\b\b\b \b\b\bdone\n\nResizing the filesystem on docker.raw to 41149 (4k) blocks.\nThe filesystem on docker.raw is now 41149 (4k) blocks long.\n\nCreated docker.raw\nDiscarding device blocks: 0/262144\b\b\b\b\b\b\b\b\b\b\b\b\b \b\b\b\b\b\b\b\b\b\b\b\b\bdone \nCreating filesystem with 262144 4k blocks and 65536 inodes\nFilesystem UUID: dc2547d1-abf3-417b-bc80-77364bfe2e25\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376\n\nAllocating group tables: 0/8\b\b\b \b\b\bdone \nWriting inode tables: 0/8\b\b\b \b\b\bdone \nCreating journal (8192 blocks): done\nCopying files into the device: done\nWriting superblocks and filesystem accounting information: 0/8\b\b\b \b\b\bdone\n\nResizing the filesystem on containerd.raw to 37662 (4k) blocks.\nThe filesystem on containerd.raw is now 37662 (4k) blocks long.\n\nCreated containerd.raw, status wait: remote command exited without exit status or exit signal\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":472266914566,"output":" cluster.go:125: I0605 23:34:09.069671 2529 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:32.059620 2754 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-a30aee8bc7\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4081.3.8-n-a30aee8bc7\": lookup ci-4081.3.8-n-a30aee8bc7 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:32.252219 2754 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-a30aee8bc7 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.22]\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 500.773423ms\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.22:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.015646595s\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.507359609s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.50195551s\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-a30aee8bc7 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-a30aee8bc7 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 1dryy9.e0k5etqoog2y5rz2\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.22:6443 --token 1dryy9.e0k5etqoog2y5rz2 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:0b6aa00c6f94f992af6153ca4367ec9fa80997a64ccd506b8288c9756156e9df \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 Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: DaemonSet cilium Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: Containers: cilium Running: \u001b[32m1\u001b[0m\n cluster.go:125: cilium-operator Running: \u001b[32m1\u001b[0m\n cluster.go:125: Cluster Pods: 2/2 managed by Cilium\n cluster.go:125: Image versions cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\n cluster.go:125: cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1\n cluster.go:125: W0605 23:37:14.523140 2344 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 (21.55s)\n --- PASS: kubeadm.v1.35.1.cilium.base/nginx_deployment (11.28s)\n --- PASS: kubeadm.v1.35.1.cilium.base/NFS_deployment (17.74s)\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 --- FAIL: kubeadm.v1.35.1.cilium.base/IPSec_encryption (31.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 cluster.go:145: \"/opt/bin/cilium status --wait --wait-duration 1m\" failed: output , status wait: remote command exited without exit status or exit signal\n"},{"name":"cl.internet","result":"FAIL","duration":88629857771,"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-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-c817e14fd5\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.calico.base","result":"FAIL","duration":235199160639,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-1d272e83cb\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.security.tls","result":"FAIL","duration":108669612476,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.8-n-37337f1071): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-37337f1071\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":132598294364,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.8-n-8c82baa478): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/3e603ab3-45ac-4ff9-ab22-3a87465ed603\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:38:14.2301023+00:00\",\n \"endTime\": \"2026-06-05T23:38:50.050145+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\": \"3e603ab3-45ac-4ff9-ab22-3a87465ed603\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.containerd-restart","result":"FAIL","duration":108803105879,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.8-n-ec0fc38d19): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/6d3fe0d0-47bc-4fd5-bbb1-c7c98d00d6a5\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:37:20.1616441+00:00\",\n \"endTime\": \"2026-06-05T23:38:50.1588335+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\": \"6d3fe0d0-47bc-4fd5-bbb1-c7c98d00d6a5\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":193448132951,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4081.3.8-n-4e1c95e8cb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/9d6a2ee0-71f6-4f2f-a215-37c18544e2f7\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:37:17.4979097+00:00\",\n \"endTime\": \"2026-06-05T23:38:50.2700981+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\": \"9d6a2ee0-71f6-4f2f-a215-37c18544e2f7\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.selinux.boolean","result":"FAIL","duration":108344366899,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4081.3.8-n-ba4269c5d5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/24b19b72-fc10-4334-bb98-c29bad699946\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:37:23.6389714+00:00\",\n \"endTime\": \"2026-06-05T23:38:50.3932209+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\": \"24b19b72-fc10-4334-bb98-c29bad699946\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":110641025702,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4081.3.8-n-96e9ce4e1d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/11d665fc-a256-4732-89ba-d798f0e63f6c\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-05T23:37:33.5099874+00:00\",\n \"endTime\": \"2026-06-05T23:38:50.1588335+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\": \"11d665fc-a256-4732-89ba-d798f0e63f6c\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.ssh.key","result":"FAIL","duration":751140080570,"output":" harness.go:646: Cluster failed starting machines: machine \"ci-4081.3.8-n-37ce87d979\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.166.50.205:22: i/o timeout\n"},{"name":"cl.overlay.cleanup","result":"FAIL","duration":693071249029,"output":" state.go:97: could not reboot: machine \"ci-4081.3.8-n-7a6cf8375c\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 94.245.89.54:22: i/o timeout\n"},{"name":"coreos.locksmith.reboot","result":"FAIL","duration":1097488137530,"output":" locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":3191144269356,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-a9a544d911\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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.locksmith.cluster","result":"FAIL","duration":4067284611631,"output":" harness.go:646: Cluster failed starting machines: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-c685bd7cd9/providers/Microsoft.Compute/virtualMachines/ci-4081.3.8-n-e27a56962f\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 standardDSv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, 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:%22northeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDSv4Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:66,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDSv4Family%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.flannel.udp","result":"FAIL","duration":4802784386817,"output":" harness.go:646: Cluster failed starting machines: machine \"ci-4081.3.8-n-fbf604106d\" failed to enable selinux: unable to enable SELinux audit logs: wait: remote command exited without exit status or exit signal: \n"},{"name":"coreos.update.badusr","result":"FAIL","duration":5118555154713,"output":" update.go:168: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"\", stderr: \"\", err: dial tcp 20.123.17.45:22: i/o timeout, systemctl list-jobs returned stdout: \"\", stderr: \"\", err: dial tcp 20.123.17.45:22: i/o timeout\n"}],"result":"FAIL","platform":"azure","version":"4081.3.8"}