{"tests":[{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":96234310278,"output":""},{"name":"cl.ignition.luks","result":"PASS","duration":96747965112,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":96751570268,"output":""},{"name":"cl.ignition.misc.empty","result":"PASS","duration":97135695842,"output":""},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":98307959250,"output":""},{"name":"cl.etcd-member.discovery","result":"PASS","duration":99759458223,"output":""},{"name":"cl.cloudinit.multipart-mime","result":"PASS","duration":102119073489,"output":""},{"name":"cl.ignition.v2.users","result":"PASS","duration":102907777447,"output":""},{"name":"docker.userns","result":"PASS","duration":104673812195,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.19MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:f13fa6cac6e7d876d515a34c57afb821ee2446713070345e27a4b764e03c84e6 done\n cluster.go:125: #5 naming to docker.io/library/userns-test done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":121688387140,"output":""},{"name":"cl.ignition.v1.once","result":"PASS","duration":121982814390,"output":""},{"name":"cl.overlay.cleanup","result":"PASS","duration":127295180147,"output":""},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":129613673415,"output":""},{"name":"cl.ignition.v1.users","result":"PASS","duration":133346274284,"output":""},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":140343028546,"output":""},{"name":"cl.verity/verify","result":"PASS","duration":93312924034,"output":" cluster.go:125: Success\n"},{"name":"cl.cloudinit.basic","result":"PASS","duration":96706360981,"output":""},{"name":"cl.internet/UpdateEngine","result":"PASS","duration":1362361386,"output":""},{"name":"cl.ignition.v1.groups","result":"PASS","duration":99269198749,"output":""},{"name":"cl.cloudinit.script","result":"PASS","duration":94951581461,"output":""},{"name":"cl.internet/DockerPing","result":"PASS","duration":8366375897,"output":""},{"name":"cl.internet/DockerEcho","result":"PASS","duration":1760043945,"output":""},{"name":"docker.network-openbsd-nc","result":"PASS","duration":110045536347,"output":" docker.go:411: creating netcat containers\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.46MB 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:d406cdfc63db601ee8b5b9f2e0e2471c5b8fd02b21ed50f3847817e066784075 done\n cluster.go:125: #5 naming to docker.io/library/netcat 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.46MB 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:9966e11c6c77549b4c5272a93ff48c18ff91675787314face73fff2788f2309d done\n cluster.go:125: #5 naming to docker.io/library/netcat 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"cl.internet/NTPDate","result":"PASS","duration":8198478155,"output":""},{"name":"cl.ignition.v1.noop","result":"PASS","duration":96253619861,"output":""},{"name":"cl.internet","result":"PASS","duration":121768700047,"output":" --- PASS: cl.internet/UpdateEngine (1.36s)\n --- PASS: cl.internet/DockerPing (8.37s)\n --- PASS: cl.internet/DockerEcho (1.76s)\n --- PASS: cl.internet/NTPDate (8.20s)\n"},{"name":"cl.flannel.vxlan","result":"PASS","duration":114285865616,"output":" flannel.go:121: ping from ci-4593.2.4-l-2c7a194571(10.254.92.0) to ci-4593.2.4-l-8332f8dc12(10.254.1.0)\n"},{"name":"coreos.selinux.boolean","result":"PASS","duration":123273918813,"output":""},{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":98032201708,"output":""},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":108174922518,"output":""},{"name":"docker.btrfs-storage","result":"PASS","duration":98942295162,"output":""},{"name":"coreos.selinux.enforce","result":"PASS","duration":130749292502,"output":""},{"name":"coreos.locksmith.tls","result":"PASS","duration":142336785127,"output":""},{"name":"docker.enable-service.sysext","result":"PASS","duration":95962920154,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":98665580501,"output":""},{"name":"cl.ignition.symlink","result":"PASS","duration":96886032247,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"systemd.journal.user","result":"PASS","duration":96195857159,"output":""},{"name":"docker.base/docker-info","result":"PASS","duration":4054952711,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":128508368671,"output":""},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":97493311133,"output":""},{"name":"docker.base/resources","result":"PASS","duration":8345639321,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.12MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:766f64eeb66f72db19480768b38dea3128bf6ab3b4df531ae81fa076ca4b5948 done\n cluster.go:125: #5 naming to docker.io/library/sleep 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support 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":"kubeadm.v1.34.4.calico.base/node_readiness","result":"PASS","duration":20703826494,"output":""},{"name":"docker.base/networks-reliably","result":"FAIL","duration":15007684799,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.09MB 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:229a57236518d453b3a19a84cb514f8870e0cea5956e909f6616b8513cf7c065 done\n cluster.go:125: #5 naming to docker.io/library/ping 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:145: \"for i in $(seq 1 100); do\\n\\t\\techo -n \\\"$i: \\\"\\n\\t\\tdocker run --rm ping sh -c 'ping -i 0.2 172.17.0.1 -w 1 \u003e/dev/null \u0026\u0026 echo PASS || echo FAIL'\\n\\tdone\" failed: output 1: PASS\n2: PASS\n3: PASS\n4: PASS\n5: PASS\n6: PASS\n7: PASS\n8:, status wait: remote command exited without exit status or exit signal\n"},{"name":"cl.ignition.kargs","result":"FAIL","duration":117227706115,"output":" harness.go:646: Cluster failed starting machines: machine \"ci-4593.2.4-l-872fa9e755\" failed basic checks: no /etc/os-release file: ssh: handshake failed: read tcp 10.200.1.6:60342-\u003e52.247.205.116:22: read: connection reset by peer: \n"},{"name":"docker.base/user-no-caps","result":"FAIL","duration":289507327,"output":" cluster.go:145: \"tmpdir=$(mktemp -d); cd $tmpdir; echo -e \\\"FROM scratch\\\\nCOPY . /\\\" \u003e Dockerfile;\\n\\t b=$(which capsh sh grep cat ls); libs=$(sudo ldd $b | grep -o /lib'[^ ]*' | sort -u);\\n\\t sudo rsync -av --relative --copy-links $b $libs ./;\\n\\t sudo docker build -t captest .\" failed: output , status ssh: handshake failed: read tcp 10.200.1.6:40294-\u003e4.154.210.182:22: read: connection reset by peer\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":326043166,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-df8e609dbc\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":2282369303,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-09dd68ca0c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base/node_readiness","result":"FAIL","duration":13778360860,"output":" cluster.go:145: \"kubectl get nodes | grep \\\" Ready\\\"| wc -l\" failed: output , status dial tcp 20.230.209.158:22: connect: connection refused\n"},{"name":"coreos.ignition.ssh.key","result":"FAIL","duration":287739766,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-b525275401\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.basic","result":"FAIL","duration":279733861,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-6f497d9fd0\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"sysext.simple","result":"FAIL","duration":319184520,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-86039ce68c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base/nginx_deployment","result":"FAIL","duration":987943198,"output":" kubeadm.go:219: unable to deploy nginx: dial tcp 20.230.209.158:22: connect: connection refused\n"},{"name":"cl.users.shells","result":"FAIL","duration":281545560,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-50bc79c216\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.calico.base/nginx_deployment","result":"FAIL","duration":8774442896,"output":" cluster.go:145: \"kubectl get deployments -o json | jq '.items | .[] | .status.readyReplicas'\" failed: output , status dial tcp 20.114.24.125:22: connect: connection refused\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"FAIL","duration":596633039,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-f3689f4c27\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.groups","result":"FAIL","duration":274998212,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-dee0bd4b2a\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base/NFS_deployment","result":"FAIL","duration":996637046,"output":" kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.230.209.158:22: connect: connection refused\n"},{"name":"cl.metadata.azure","result":"FAIL","duration":290393140,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-eef2a9e3e8\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.swap_activation","result":"FAIL","duration":271146491,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-4d793b1d0c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":2313877670,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-cc8bdbc04c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.containerd-restart","result":"FAIL","duration":301836783,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-add14ecbe7\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"bpf.ig/ig","result":"FAIL","duration":304054444,"output":" ig.go:50: creating node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-6491030747\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"bpf.ig","result":"FAIL","duration":2305187535,"output":" --- FAIL: bpf.ig/ig (0.30s)\n ig.go:50: creating node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-6491030747\n --------------------------------------------------------------------------------\n RESPONSE 409: 409 Conflict\n ERROR CODE: ResourceGroupBeingDeleted\n --------------------------------------------------------------------------------\n {\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n }\n --------------------------------------------------------------------------------\n"},{"name":"cl.verity/corruption","result":"PASS","duration":174948294681,"output":""},{"name":"cl.network.iptables","result":"FAIL","duration":372263951,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-e820999048\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":282592315,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-7ff60a5b6b\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.update.reboot","result":"FAIL","duration":345909469,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-69c472cbf9\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.network.wireguard","result":"FAIL","duration":288746903,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-13a912288c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.toolbox.dnf-install","result":"FAIL","duration":301437608,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-236166e384\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2.ext4root","result":"FAIL","duration":287207638,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-9d4c6f0405\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.ext4root","result":"FAIL","duration":287159553,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-0ca94a8efc\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.selinux","result":"FAIL","duration":289996695,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-55b6fd3182\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":329439761,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-bd612441f6\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.auth.verify","result":"FAIL","duration":295991643,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-510eb70728\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"systemd.sysusers.gshadow","result":"FAIL","duration":295805639,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-0e6128b5c4\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.verity","result":"PASS","duration":363522138814,"output":" --- PASS: cl.verity/verify (93.31s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (174.95s)\n"},{"name":"cl.etcd-member.v2-backup-restore","result":"FAIL","duration":696402036,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-c4d5ffc334\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"sysext.disable-containerd","result":"FAIL","duration":269870230,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-8a105358cb\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.update.badverity","result":"FAIL","duration":313624270,"output":" harness.go:646: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Network/publicIPAddresses/ip-99559ad985\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-1c73d491fb' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.base/ownership","result":"FAIL","duration":15565125195,"output":" cluster.go:145: \"docker run --name ownership ghcr.io/flatcar/nginx stat -c \\\"%u/%g\\\" /etc/shadow\" failed: output , status dial tcp 4.154.210.182:22: i/o timeout\n"},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"FAIL","duration":82829808290,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-1ea3f23530): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-1c73d491fb/providers/Microsoft.Compute/virtualMachines/ci-4593.2.4-l-1ea3f23530\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.base","result":"FAIL","duration":138334829076,"output":" --- PASS: docker.base/docker-info (4.05s)\n --- PASS: docker.base/resources (8.35s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.12MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:766f64eeb66f72db19480768b38dea3128bf6ab3b4df531ae81fa076ca4b5948 done\n cluster.go:125: #5 naming to docker.io/library/sleep 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support 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 --- FAIL: docker.base/networks-reliably (15.01s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.09MB 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:229a57236518d453b3a19a84cb514f8870e0cea5956e909f6616b8513cf7c065 done\n cluster.go:125: #5 naming to docker.io/library/ping 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:145: \"for i in $(seq 1 100); do\\n\\t\\techo -n \\\"$i: \\\"\\n\\t\\tdocker run --rm ping sh -c 'ping -i 0.2 172.17.0.1 -w 1 \u003e/dev/null \u0026\u0026 echo PASS || echo FAIL'\\n\\tdone\" failed: output 1: PASS\n 2: PASS\n 3: PASS\n 4: PASS\n 5: PASS\n 6: PASS\n 7: PASS\n 8:, status wait: remote command exited without exit status or exit signal\n --- FAIL: docker.base/user-no-caps (0.29s)\n cluster.go:145: \"tmpdir=$(mktemp -d); cd $tmpdir; echo -e \\\"FROM scratch\\\\nCOPY . /\\\" \u003e Dockerfile;\\n\\t b=$(which capsh sh grep cat ls); libs=$(sudo ldd $b | grep -o /lib'[^ ]*' | sort -u);\\n\\t sudo rsync -av --relative --copy-links $b $libs ./;\\n\\t sudo docker build -t captest .\" failed: output , status ssh: handshake failed: read tcp 10.200.1.6:40294-\u003e4.154.210.182:22: read: connection reset by peer\n --- FAIL: docker.base/ownership (15.57s)\n cluster.go:145: \"docker run --name ownership ghcr.io/flatcar/nginx stat -c \\\"%u/%g\\\" /etc/shadow\" failed: output , status dial tcp 4.154.210.182:22: i/o timeout\n"},{"name":"coreos.ignition.once","result":"FAIL","duration":54331935347,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-dfc6668a00): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/c25f4445-27de-4734-8737-2c15cf5653c1\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:43.5060881+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.173972+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\": \"c25f4445-27de-4734-8737-2c15cf5653c1\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":151048216766,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4593.2.4-l-d05fbf401b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/1766f07d-568f-4962-9140-b30c9b1aa7a0\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:41.9861972+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.2882049+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\": \"1766f07d-568f-4962-9140-b30c9b1aa7a0\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.calico.base/NFS_deployment","result":"FAIL","duration":20434856477,"output":" kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.114.24.125:22: i/o timeout\n"},{"name":"sysext.custom-docker.sysext","result":"FAIL","duration":52828169425,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-85a4c231ad): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/5d7c1e71-c4e0-44d9-8ad6-f3c625d799cd\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:49.8564492+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.173972+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\": \"5d7c1e71-c4e0-44d9-8ad6-f3c625d799cd\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":181891600336,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4593.2.4-l-01bbfa97d3): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/91418e57-41a6-495a-8850-a276708f648a\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:15.7933544+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.2882049+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\": \"91418e57-41a6-495a-8850-a276708f648a\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.translation","result":"FAIL","duration":82193978091,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-46b667b4b8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/4f376759-803f-4770-b377-916f24a302e2\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:21.692901+00:00\",\n \"endTime\": \"2026-07-29T16:45:32.3156101+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\": \"4f376759-803f-4770-b377-916f24a302e2\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.calico.base","result":"FAIL","duration":378850044976,"output":" cluster.go:125: I0729 16:42:36.446577 2861 version.go:260] remote version is much newer: v1.36.3; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.10\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.10\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.10\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.10\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: I0729 16:42:47.493954 3191 version.go:260] remote version is much newer: v1.36.3; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.10\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-110122c45f\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-110122c45f\": lookup ci-4593.2.4-l-110122c45f on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4593.2.4-l-110122c45f kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.29]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.001259589s\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.29: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.504420632s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.038102823s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.002140666s\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-4593.2.4-l-110122c45f 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-4593.2.4-l-110122c45f as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 4u4cy0.6blj30f9s1g5oknd\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.29:6443 --token 4u4cy0.6blj30f9s1g5oknd \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:067476b1e88d45aee7e833b95598937da650a786aba643144342924642ef5d6e \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0729 16:44:45.928034 2604 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.calico.base/node_readiness (20.70s)\n --- FAIL: kubeadm.v1.34.4.calico.base/nginx_deployment (8.77s)\n cluster.go:145: \"kubectl get deployments -o json | jq '.items | .[] | .status.readyReplicas'\" failed: output , status dial tcp 20.114.24.125:22: connect: connection refused\n --- FAIL: kubeadm.v1.34.4.calico.base/NFS_deployment (20.43s)\n kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.114.24.125:22: i/o timeout\n"},{"name":"cl.network.nftables","result":"FAIL","duration":52699406634,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-327d4a5dc8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/5b11d1f9-d0c5-455c-aeed-8e8bb29332d1\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:55.4188591+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.528754+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\": \"5b11d1f9-d0c5-455c-aeed-8e8bb29332d1\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2_1.vfat","result":"FAIL","duration":51998682342,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-9eb8347cbc): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/6b1a1947-3ddf-4b69-bb3b-dd221f0e1039\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:58.7966969+00:00\",\n \"endTime\": \"2026-07-29T16:45:25.6821787+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\": \"6b1a1947-3ddf-4b69-bb3b-dd221f0e1039\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base/IPSec_encryption","result":"FAIL","duration":30145008385,"output":" cluster.go:145: \"/opt/bin/cilium uninstall\" failed: output , status dial tcp 20.230.209.158:22: i/o timeout\n"},{"name":"cl.etcd-member.etcdctlv3","result":"FAIL","duration":82319048877,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4593.2.4-l-d462d71db5): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/b7261e12-b79d-4306-aec0-0061e362b8ad\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:34.2900759+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.528754+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\": \"b7261e12-b79d-4306-aec0-0061e362b8ad\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":388242997211,"output":" cluster.go:125: I0729 16:42:34.443330 2774 version.go:260] remote version is much newer: v1.36.3; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.10\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.10\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.10\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.10\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: I0729 16:42:45.556384 3105 version.go:260] remote version is much newer: v1.36.3; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.10\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-918b62bedf\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-918b62bedf\": lookup ci-4593.2.4-l-918b62bedf on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4593.2.4-l-918b62bedf kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.28]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.000746186s\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.28:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.504248076s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.832939915s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.002795714s\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-4593.2.4-l-918b62bedf 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-4593.2.4-l-918b62bedf as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: tf20i6.iqni7u1u3rcbigq9\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.28:6443 --token tf20i6.iqni7u1u3rcbigq9 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:1489ec241963d4a743cb07c7c414dad24e51cdcaeb741d95a02763616175c0c5 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: Deployment cilium-operator \n cluster.go:125: DaemonSet cilium \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W0729 16:45:00.926018 2607 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 --- FAIL: kubeadm.v1.34.4.cilium.base/node_readiness (13.78s)\n cluster.go:145: \"kubectl get nodes | grep \\\" Ready\\\"| wc -l\" failed: output , status dial tcp 20.230.209.158:22: connect: connection refused\n --- FAIL: kubeadm.v1.34.4.cilium.base/nginx_deployment (0.99s)\n kubeadm.go:219: unable to deploy nginx: dial tcp 20.230.209.158:22: connect: connection refused\n --- FAIL: kubeadm.v1.34.4.cilium.base/NFS_deployment (1.00s)\n kubeadm.go:238: unable to add helm NFS repo: dial tcp 20.230.209.158:22: connect: connection refused\n --- FAIL: kubeadm.v1.34.4.cilium.base/IPSec_encryption (30.15s)\n cluster.go:145: \"/opt/bin/cilium uninstall\" failed: output , status dial tcp 20.230.209.158:22: i/o timeout\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":260313209654,"output":" cluster.go:125: I0729 16:44:38.493047 2795 version.go:260] remote version is much newer: v1.36.3; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.7\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.7\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.7\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.7\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: I0729 16:44:50.031745 3008 version.go:260] remote version is much newer: v1.36.3; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.7\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-5a91759cb5\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-5a91759cb5\": lookup ci-4593.2.4-l-5a91759cb5 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4593.2.4-l-5a91759cb5 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.6]\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 501.596999ms\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.6: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.003336139s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.176002733s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.001621943s\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-4593.2.4-l-5a91759cb5 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-4593.2.4-l-5a91759cb5 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: k8wqfb.da20b2mc09wjux9z\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.6:6443 --token k8wqfb.da20b2mc09wjux9z \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:aa233cdc67a08d5f615656cbc6acdc09b34503d526f46a63a970c23d362cdc28 \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4593.2.4-l-1b94cd12b1): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/00067ff4-ab4d-4bdf-aba6-3f08d4fa1d29\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:45:02.7125287+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.173972+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\": \"00067ff4-ab4d-4bdf-aba6-3f08d4fa1d29\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":297005265700,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.3\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.3\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.3\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.3\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.3\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-38957d591e\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-l-38957d591e\": lookup ci-4593.2.4-l-38957d591e on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4593.2.4-l-38957d591e kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.27]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 814.056µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.27:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 5.492582ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 6.172312ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.501663485s\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-4593.2.4-l-38957d591e 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-4593.2.4-l-38957d591e as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: usd9hw.rndoc5t6z5ci6wg7\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.27:6443 --token usd9hw.rndoc5t6z5ci6wg7 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:d4ffa5627de2b6def9be336946faa6219fef33724b8218d025c5b5924a2f43e7 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: Deployment cilium-operator \n cluster.go:125: DaemonSet cilium \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4593.2.4-l-a7dae64a45): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/5988fab3-a40a-4acf-bd0a-cf142e498e53\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:39.090937+00:00\",\n \"endTime\": \"2026-07-29T16:45:26.3964622+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\": \"5988fab3-a40a-4acf-bd0a-cf142e498e53\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":177564696193,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4593.2.4-l-eaf73df47f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/33843893-6ebe-40e3-85fa-ee698164bda8\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-07-29T16:44:40.1118801+00:00\",\n \"endTime\": \"2026-07-29T16:45:32.6831458+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\": \"33843893-6ebe-40e3-85fa-ee698164bda8\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.update.badusr","result":"PASS","duration":422993517689,"output":""},{"name":"coreos.locksmith.reboot","result":"FAIL","duration":1081259849433,"output":" locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded\n"},{"name":"cl.locksmith.cluster","result":"FAIL","duration":1111950723933,"output":" locksmith.go:184: [0] ssh unreachable or system not ready: context deadline exceeded [1] ssh unreachable or system not ready: context deadline exceeded [2] ssh unreachable or system not ready: context deadline exceeded\n"}],"result":"FAIL","platform":"azure","version":"4593.2.4"}