{"tests":[{"name":"cl.metadata.azure","result":"PASS","duration":104733505141,"output":""},{"name":"cl.network.iptables","result":"PASS","duration":104767465387,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":104822766490,"output":""},{"name":"cl.ignition.v1.groups","result":"PASS","duration":105092692174,"output":""},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":106534801721,"output":""},{"name":"coreos.ignition.ssh.key","result":"PASS","duration":106716095705,"output":""},{"name":"docker.userns","result":"PASS","duration":118573812036,"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: 3.48MB 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:a547cc3959c909ae0351a37436c34150663a9ffd53d22fa27f0bad83fb15ee78 done\n cluster.go:125: #5 naming to docker.io/library/userns-test done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.selinux","result":"PASS","duration":121695619988,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Verifying Checksum\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: sh: can't create /opt/hello: Permission denied\n"},{"name":"bpf.ig/ig","result":"PASS","duration":133463861704,"output":" cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: time=\"2026-06-04T00:35:05Z\" level=warning msg=\"Runtime enricher (docker): couldn't get current containers: listing containers with options {Size:false All:true Latest:false Since: Before: Limit:0 Filters:{fields:map[]}}: Get \\\"http://%2Frun%2Fdocker.sock/v1.51/containers/json?all=1\\\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)\"\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"coreos.selinux.enforce","result":"PASS","duration":134414061569,"output":""},{"name":"bpf.ig","result":"PASS","duration":135829086969,"output":" --- PASS: bpf.ig/ig (133.46s)\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: time=\"2026-06-04T00:35:05Z\" level=warning msg=\"Runtime enricher (docker): couldn't get current containers: listing containers with options {Size:false All:true Latest:false Since: Before: Limit:0 Filters:{fields:map[]}}: Get \\\"http://%2Frun%2Fdocker.sock/v1.51/containers/json?all=1\\\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)\"\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"sysext.custom-docker.sysext","result":"PASS","duration":148834495177,"output":" cluster.go:125: bash: line 1: docker: command not found\n cluster.go:125: Cloning into 'sysext-bakery'...\n cluster.go:125: Note: switching to '9850ffd5b2353f45a9b3bf4fb84f8138a149e3e7'.\n cluster.go:125: \n cluster.go:125: You are in 'detached HEAD' state. You can look around, make experimental\n cluster.go:125: changes and commit them, and you can discard any commits you make in this\n cluster.go:125: state without impacting any branches by switching back to a branch.\n cluster.go:125: \n cluster.go:125: If you want to create a new branch to retain commits you create, you may\n cluster.go:125: do so (now or later) by using -c with the switch command. Example:\n cluster.go:125: \n cluster.go:125: git switch -c \u003cnew-branch-name\u003e\n cluster.go:125: \n cluster.go:125: Or undo this operation with:\n cluster.go:125: \n cluster.go:125: git switch -\n cluster.go:125: \n cluster.go:125: Turn off this advice by setting config variable advice.detachedHead to false\n cluster.go:125: \n cluster.go:125: HEAD is now at 9850ffd Merge pull request #31 from flatcar/t-lo/fix-docker-23-containerd-shim\n cluster.go:125: mke2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: resize2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: mke2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: resize2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Verifying Checksum\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: mke2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: resize2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: mke2fs 1.47.3 (8-Jul-2025)\n cluster.go:125: resize2fs 1.47.3 (8-Jul-2025)\n"},{"name":"docker.containerd-restart","result":"PASS","duration":169221353955,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n"},{"name":"coreos.ignition.resource.local","result":"PASS","duration":188043373689,"output":""},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":84371168457,"output":""},{"name":"cl.update.reboot","result":"PASS","duration":193826732696,"output":""},{"name":"cl.verity/verify","result":"PASS","duration":18423328506,"output":" cluster.go:125: Success\n"},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":88593569912,"output":""},{"name":"docker.lib-coreos-dockerd-compat/docker-info","result":"PASS","duration":8670529666,"output":""},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":77583336045,"output":""},{"name":"cl.overlay.cleanup","result":"PASS","duration":113382103278,"output":""},{"name":"cl.ignition.v1.once","result":"PASS","duration":112299624124,"output":""},{"name":"docker.lib-coreos-dockerd-compat/resources","result":"PASS","duration":15022267049,"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: 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: 3.44MB 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:e5978cb4ebd98d26b12837cea2598ddc138b95a465ccb637722d9b35ac021bf3 done\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n"},{"name":"cl.flannel.udp","result":"SKIP","duration":10548040373,"output":" harness.go:640: Failed to create discovery endpoint: Discovery service returned \"503 Service Unavailable\"\n"},{"name":"cl.ignition.v2.noop","result":"PASS","duration":83626217371,"output":""},{"name":"coreos.locksmith.tls","result":"PASS","duration":117530794085,"output":""},{"name":"cl.etcd-member.v2-backup-restore","result":"SKIP","duration":10313741264,"output":" harness.go:640: Failed to create discovery endpoint: Discovery service returned \"503 Service Unavailable\"\n"},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"PASS","duration":164558052225,"output":""},{"name":"cl.ignition.luks","result":"PASS","duration":83584029864,"output":""},{"name":"cl.cloudinit.script","result":"PASS","duration":83228426681,"output":""},{"name":"cl.ignition.v1.noop","result":"PASS","duration":83279069573,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":83487679964,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":81024733695,"output":""},{"name":"docker.lib-coreos-dockerd-compat/networks-reliably","result":"FAIL","duration":80606407086,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.34MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:560f0ff9dffe585264478d1626e32617338fd329498e6d2841ef44f6925744b5 done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:145: \"for i in $(seq 1 100); do\\n\\t\\techo -n \\\"$i: \\\"\\n\\t\\tdocker run --rm ping sh -c 'ping -i 0.2 172.17.0.1 -w 1 \u003e/dev/null \u0026\u0026 echo PASS || echo FAIL'\\n\\tdone\" failed: output 1: PASS\n2: PASS\n3: PASS\n4: PASS\n5: PASS\n6: PASS\n7: PASS\n8: PASS\n9: PASS\n10: PASS\n11: PASS\n12: PASS\n13: PASS\n14: PASS\n15: PASS\n16: PASS\n17: PASS\n18: PASS\n19: PASS\n20: PASS\n21: PASS\n22: PASS\n23: PASS\n24: PASS\n25: PASS\n26: PASS\n27: PASS\n28: PASS\n29: PASS\n30: PASS\n31: PASS\n32: PASS\n33: PASS\n34: PASS\n35: PASS\n36: PASS\n37: PASS\n38: PASS\n39: PASS\n40: PASS\n41: PASS\n42: PASS\n43: PASS\n44: PASS\n45: PASS\n46: PASS\n47: PASS\n48: PASS\n49: PASS\n50: PASS\n51: PASS\n52: PASS\n53: PASS\n54:, status wait: remote command exited without exit status or exit signal\n"},{"name":"docker.lib-coreos-dockerd-compat/user-no-caps","result":"FAIL","duration":36739856,"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:36926-\u003e20.234.14.178:22: read: connection reset by peer\n"},{"name":"docker.lib-coreos-dockerd-compat/ownership","result":"FAIL","duration":42031497,"output":" cluster.go:145: \"docker run --name ownership ghcr.io/flatcar/nginx stat -c \\\"%u/%g\\\" /etc/shadow\" failed: output , status ssh: handshake failed: read tcp 10.200.1.6:36932-\u003e20.234.14.178:22: read: connection reset by peer\n"},{"name":"cl.update.badverity","result":"FAIL","duration":89743665570,"output":" cluster.go:145: \"sudo dd if=/dev/disk/by-partlabel/USR-A of=/dev/disk/by-partlabel/USR-B bs=10M status=none\" failed: output , status wait: remote command exited without exit status or exit signal\n"},{"name":"sysext.disable-containerd","result":"FAIL","duration":69360850,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-c27d4e7622\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.ext4root","result":"FAIL","duration":76274995,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-7b8df5fd2d\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.groups","result":"FAIL","duration":67160484,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-ca7569aea7\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.tls.fetch-urls","result":"FAIL","duration":74060101,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-379b7b8bb9\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":203783987990,"output":" cluster.go:125: I0604 00:38:03.602513 3310 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I0604 00:38:14.028481 3522 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-e8d59efef8\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-e8d59efef8\": lookup ci-4628.1.2-n-e8d59efef8 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-4628.1.2-n-e8d59efef8 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.13]\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.636858ms\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.13:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.004841384s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.567550486s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.501596487s\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-4628.1.2-n-e8d59efef8 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-4628.1.2-n-e8d59efef8 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: ddl79m.kbdu83dz0f610o5p\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.13:6443 --token ddl79m.kbdu83dz0f610o5p \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:4dffb795aca5330404131fe353e6ff497c887c8fc3fd98513d11fd5b5e041ba2 \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 kubeadm.go:197: unable to setup cluster: unable to run master script: wait: remote command exited without exit status or exit signal\n"},{"name":"cl.ignition.v2_1.vfat","result":"FAIL","duration":65919587,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-a820ccce9d\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.btrfs-storage","result":"FAIL","duration":86490806,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-881b6d591a\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"sysext.simple","result":"FAIL","duration":57187535,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-05207d2ac4\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.swap_activation","result":"FAIL","duration":69104678,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-d0e23655f8\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.users","result":"FAIL","duration":137063123,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-7da0ce403c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2_1.swap","result":"FAIL","duration":135297563,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-c643fbf61f\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.selinux.boolean","result":"FAIL","duration":68785667,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-db7fd83e8a\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":78576483,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-82ba185531\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.translation","result":"FAIL","duration":61027703,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-949779bf2b\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.base","result":"FAIL","duration":54839341,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-abbac37960\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.once","result":"FAIL","duration":53191145,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-b761fcf45b\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.enable-service.sysext","result":"FAIL","duration":82675841,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-f3330552f0\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.toolbox.dnf-install","result":"FAIL","duration":106882169,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-868b7bff36\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"FAIL","duration":187937904791,"output":" --- PASS: docker.lib-coreos-dockerd-compat/docker-info (8.67s)\n --- PASS: docker.lib-coreos-dockerd-compat/resources (15.02s)\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: 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: 3.44MB 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:e5978cb4ebd98d26b12837cea2598ddc138b95a465ccb637722d9b35ac021bf3 done\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n --- FAIL: docker.lib-coreos-dockerd-compat/networks-reliably (80.61s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.34MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:560f0ff9dffe585264478d1626e32617338fd329498e6d2841ef44f6925744b5 done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:145: \"for i in $(seq 1 100); do\\n\\t\\techo -n \\\"$i: \\\"\\n\\t\\tdocker run --rm ping sh -c 'ping -i 0.2 172.17.0.1 -w 1 \u003e/dev/null \u0026\u0026 echo PASS || echo FAIL'\\n\\tdone\" failed: output 1: PASS\n 2: PASS\n 3: PASS\n 4: PASS\n 5: PASS\n 6: PASS\n 7: PASS\n 8: PASS\n 9: PASS\n 10: PASS\n 11: PASS\n 12: PASS\n 13: PASS\n 14: PASS\n 15: PASS\n 16: PASS\n 17: PASS\n 18: PASS\n 19: PASS\n 20: PASS\n 21: PASS\n 22: PASS\n 23: PASS\n 24: PASS\n 25: PASS\n 26: PASS\n 27: PASS\n 28: PASS\n 29: PASS\n 30: PASS\n 31: PASS\n 32: PASS\n 33: PASS\n 34: PASS\n 35: PASS\n 36: PASS\n 37: PASS\n 38: PASS\n 39: PASS\n 40: PASS\n 41: PASS\n 42: PASS\n 43: PASS\n 44: PASS\n 45: PASS\n 46: PASS\n 47: PASS\n 48: PASS\n 49: PASS\n 50: PASS\n 51: PASS\n 52: PASS\n 53: PASS\n 54:, status wait: remote command exited without exit status or exit signal\n --- FAIL: docker.lib-coreos-dockerd-compat/user-no-caps (0.04s)\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:36926-\u003e20.234.14.178:22: read: connection reset by peer\n --- FAIL: docker.lib-coreos-dockerd-compat/ownership (0.04s)\n cluster.go:145: \"docker run --name ownership ghcr.io/flatcar/nginx stat -c \\\"%u/%g\\\" /etc/shadow\" failed: output , status ssh: handshake failed: read tcp 10.200.1.6:36932-\u003e20.234.14.178:22: read: connection reset by peer\n"},{"name":"cl.ignition.v1.xfsroot","result":"FAIL","duration":53495911,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-fc9f5d469b\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.etcd-member.etcdctlv3","result":"FAIL","duration":76659264,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-899042f83e\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.symlink","result":"FAIL","duration":240427250,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-cd71ef21d5\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.network.wireguard","result":"FAIL","duration":110989526,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-d774c950e3\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.users.shells","result":"FAIL","duration":121860024,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-bab3ce6363\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"sysext.disable-docker","result":"FAIL","duration":109530708,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-a25386e806\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.misc.empty","result":"FAIL","duration":102288523,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-18f5096d61\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.auth.verify","result":"FAIL","duration":62447760,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-26b0c44bb2\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":2056801426,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-2812990824\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":316066956310,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-1b1ac94928\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-1b1ac94928\": lookup ci-4628.1.2-n-1b1ac94928 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-4628.1.2-n-1b1ac94928 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.19]\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.507055ms\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.19:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.205209ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 7.442472ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.003551463s\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-4628.1.2-n-1b1ac94928 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-4628.1.2-n-1b1ac94928 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: p07833.1lzbnx02rh376lbt\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.19:6443 --token p07833.1lzbnx02rh376lbt \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:44aec93ccdd77b5416563c2884b6fe7904a45c0a19091740e376dfc2ecacd653 \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n kubeadm.go:197: unable to setup cluster: unable to create worker node: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e3cf9d480/providers/Microsoft.Compute/virtualMachines/ci-4628.1.2-n-373189fa7d\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":"cl.ignition.v2.users","result":"FAIL","duration":60320095,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-56f3bfec2c\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"systemd.journal.user","result":"FAIL","duration":65508817,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-d96e025eba\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.internet","result":"FAIL","duration":58684506,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-acb82eea41\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.basic","result":"FAIL","duration":63312954,"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-6e3cf9d480/providers/Microsoft.Network/publicIPAddresses/ip-12eede8b45\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-6e3cf9d480' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.resource.remote","result":"FAIL","duration":89698540914,"output":" harness.go:646: Cluster failed starting machines: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e3cf9d480/providers/Microsoft.Compute/virtualMachines/ci-4628.1.2-n-0d5bdcb9d6\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":"cl.locksmith.cluster","result":"SKIP","duration":10313158842,"output":" harness.go:640: Failed to create discovery endpoint: Discovery service returned \"503 Service Unavailable\"\n"},{"name":"cl.etcd-member.discovery","result":"SKIP","duration":10312589755,"output":" harness.go:640: Failed to create discovery endpoint: Discovery service returned \"503 Service Unavailable\"\n"},{"name":"cl.cloudinit.basic","result":"FAIL","duration":50361749308,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4628.1.2-n-7530349322): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/aacb3b51-4500-4933-8aad-1e88fc504ab7\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:37:49.7293537+00:00\",\n \"endTime\": \"2026-06-04T00:38:33.8751037+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\": \"aacb3b51-4500-4933-8aad-1e88fc504ab7\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":50851887093,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4628.1.2-n-912ac7c7f2): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/01acdf60-6f07-40bc-ab4d-9562edcb57dd\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:37:50.0554264+00:00\",\n \"endTime\": \"2026-06-04T00:38:34.2332608+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\": \"01acdf60-6f07-40bc-ab4d-9562edcb57dd\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.flannel.vxlan","result":"SKIP","duration":10313232202,"output":" harness.go:640: Failed to create discovery endpoint: Discovery service returned \"503 Service Unavailable\"\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":50325166603,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4628.1.2-n-dabb906193): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/c0345b6a-872d-449e-bbf2-897aec573e54\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:37:50.827971+00:00\",\n \"endTime\": \"2026-06-04T00:38:33.9853644+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\": \"c0345b6a-872d-449e-bbf2-897aec573e54\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.network.nftables","result":"FAIL","duration":91009454368,"output":" harness.go:646: Cluster failed starting machines: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e3cf9d480/providers/Microsoft.Compute/virtualMachines/ci-4628.1.2-n-59ba633209\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":324151138791,"output":" cluster.go:125: I0604 00:36:46.634087 3150 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.5-0\n cluster.go:125: I0604 00:36:57.033665 3365 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-17ba9a8cf9\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-17ba9a8cf9\": lookup ci-4628.1.2-n-17ba9a8cf9 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-4628.1.2-n-17ba9a8cf9 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.24]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 501.45424ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.24:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.66931506s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.091304855s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.001582513s\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-4628.1.2-n-17ba9a8cf9 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-4628.1.2-n-17ba9a8cf9 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: y71u25.vkegwym90w5w7lpz\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.24:6443 --token y71u25.vkegwym90w5w7lpz \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:b80a01e527225f76b33ff316ee06771e5ba48ddb8a1795204e6f178522f35819 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \n cluster.go:125: Containers: cilium-operator \n cluster.go:125: cilium \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n kubeadm.go:197: unable to setup cluster: unable to create worker node: waiting for machine to become active: GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e3cf9d480/providers/Microsoft.Compute/virtualMachines/ci-4628.1.2-n-48740a7130\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.34.4.calico.base","result":"FAIL","duration":324217070872,"output":" cluster.go:125: I0604 00:36:40.948985 3198 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.5-0\n cluster.go:125: I0604 00:36:52.581023 3448 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-9363945c0f\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-9363945c0f\": lookup ci-4628.1.2-n-9363945c0f 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-4628.1.2-n-9363945c0f kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.26]\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 502.147784ms\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.26:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.70105863s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.436039914s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.501753346s\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-4628.1.2-n-9363945c0f 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-4628.1.2-n-9363945c0f as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: dktp0p.h2oim5a4t65a47hd\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.26:6443 --token dktp0p.h2oim5a4t65a47hd \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:3b524cb1b5f339754ff54af23e31085c62ffaafeb52cab402ce519d90dcdfc6c \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4628.1.2-n-9c85b8c522): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e3cf9d480/providers/Microsoft.Compute/virtualMachines/ci-4628.1.2-n-9c85b8c522\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: NotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"NotFound\",\n \"message\": \"The entity was not found in this Azure location.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":324656834056,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-eb965506b7\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-eb965506b7\": lookup ci-4628.1.2-n-eb965506b7 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-4628.1.2-n-eb965506b7 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.25]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 966.808µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.25:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.679056ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.456286ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.500823085s\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-4628.1.2-n-eb965506b7 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-4628.1.2-n-eb965506b7 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 7bfovn.x0l2k23e3yic1ra9\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 10.0.0.25:6443 --token 7bfovn.x0l2k23e3yic1ra9 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:ce0db1dfd9c0933241e0f8ac70c01258469861ff5fd633fa3de3ada46aa44b9d \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4628.1.2-n-2e1f45291b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-6e3cf9d480/providers/Microsoft.Compute/virtualMachines/ci-4628.1.2-n-2e1f45291b\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":"cl.cloudinit.multipart-mime","result":"FAIL","duration":49509086765,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4628.1.2-n-bd06611f12): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/e7cfadef-dae1-4421-b02a-248a6f75a89b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:37:56.1370769+00:00\",\n \"endTime\": \"2026-06-04T00:38:33.8751037+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\": \"e7cfadef-dae1-4421-b02a-248a6f75a89b\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":333396557535,"output":" cluster.go:125: I0604 00:36:53.687538 3243 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I0604 00:37:04.774462 3489 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-da3a135f39\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628.1.2-n-da3a135f39\": lookup ci-4628.1.2-n-da3a135f39 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-4628.1.2-n-da3a135f39 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.042604ms\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 1.00717886s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.417553936s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.001550676s\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-4628.1.2-n-da3a135f39 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-4628.1.2-n-da3a135f39 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 4j6y37.ac8rrv7jt9p5tczg\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 4j6y37.ac8rrv7jt9p5tczg \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:66ae4fd06c1791ec04b8228ac477f7d668f51da31e158dd99f9033f3d9ae1fcc \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4628.1.2-n-de8ab9b757): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/0e6aa850-67e5-456b-bf82-4776c0cb3a0d\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:37:29.1822568+00:00\",\n \"endTime\": \"2026-06-04T00:38:34.1096579+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\": \"0e6aa850-67e5-456b-bf82-4776c0cb3a0d\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"systemd.sysusers.gshadow","result":"FAIL","duration":48519237436,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4628.1.2-n-d0b00ad73a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/9f7481c6-3f75-4669-beda-590faaa43ae2\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:38:08.9247689+00:00\",\n \"endTime\": \"2026-06-04T00:38:41.0020935+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\": \"9f7481c6-3f75-4669-beda-590faaa43ae2\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.btrfsroot","result":"FAIL","duration":48725448265,"output":" harness.go:646: Cluster failed starting machines: PollUntilDone(ci-4628.1.2-n-1e154809ff): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/3dfd359b-14d6-44a9-a74e-e66d955c1757\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:38:11.3619544+00:00\",\n \"endTime\": \"2026-06-04T00:38:40.7028725+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\": \"3dfd359b-14d6-44a9-a74e-e66d955c1757\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":81008421225,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4628.1.2-n-92d50e4ffe): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/northeurope/operations/c73c62cc-bcfc-4d9a-86f2-5103c1ff64fd\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-06-04T00:37:42.136114+00:00\",\n \"endTime\": \"2026-06-04T00:38:34.4715102+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\": \"c73c62cc-bcfc-4d9a-86f2-5103c1ff64fd\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.verity/corruption","result":"PASS","duration":169140238414,"output":""},{"name":"cl.verity","result":"PASS","duration":270996204956,"output":" --- PASS: cl.verity/verify (18.42s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (169.14s)\n"},{"name":"coreos.locksmith.reboot","result":"FAIL","duration":1166674534434,"output":" locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded\n"},{"name":"coreos.update.badusr","result":"FAIL","duration":5238246087904,"output":" update.go:168: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"\", stderr: \"\", err: dial tcp 168.63.71.162:22: i/o timeout, systemctl list-jobs returned stdout: \"\", stderr: \"\", err: dial tcp 168.63.71.162:22: i/o timeout\n"}],"result":"FAIL","platform":"azure","version":"4628.1.2"}