{"tests":[{"name":"coreos.ignition.ssh.key","result":"PASS","duration":125291994306,"output":""},{"name":"coreos.auth.verify","result":"PASS","duration":125306194023,"output":""},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":125514179162,"output":""},{"name":"cl.ignition.misc.empty","result":"PASS","duration":125545056025,"output":""},{"name":"sysext.disable-containerd","result":"PASS","duration":125593730699,"output":""},{"name":"cl.ignition.v1.ext4root","result":"PASS","duration":127707980064,"output":""},{"name":"cl.etcd-member.etcdctlv3","result":"PASS","duration":127983472146,"output":" cluster.go:125: {\"level\":\"info\",\"ts\":\"2026-10-21T07:19:16.341221Z\",\"caller\":\"snapshot/v3_snapshot.go:65\",\"msg\":\"created temporary db file\",\"path\":\"/tmp/tmp.VSNIesSXk0/snapshot.db.part\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":\"2026-10-21T07:19:16.341538Z\",\"logger\":\"client\",\"caller\":\"v3@v3.5.33/maintenance.go:212\",\"msg\":\"opened snapshot stream; downloading\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":\"2026-10-21T07:19:16.341554Z\",\"caller\":\"snapshot/v3_snapshot.go:73\",\"msg\":\"fetching snapshot\",\"endpoint\":\"127.0.0.1:2379\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":\"2026-10-21T07:19:16.345152Z\",\"logger\":\"client\",\"caller\":\"v3@v3.5.33/maintenance.go:220\",\"msg\":\"completed snapshot read; closing\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":\"2026-10-21T07:19:16.345408Z\",\"caller\":\"snapshot/v3_snapshot.go:88\",\"msg\":\"fetched snapshot\",\"endpoint\":\"127.0.0.1:2379\",\"size\":\"20 kB\",\"took\":\"now\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":\"2026-10-21T07:19:16.345735Z\",\"caller\":\"snapshot/v3_snapshot.go:97\",\"msg\":\"saved\",\"path\":\"/tmp/tmp.VSNIesSXk0/snapshot.db\"}\n cluster.go:125: Deprecated: Use `etcdutl snapshot status` instead.\n"},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":128492825805,"output":""},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":128871517573,"output":""},{"name":"coreos.ignition.groups","result":"PASS","duration":129380099992,"output":""},{"name":"sysext.simple","result":"PASS","duration":132274506290,"output":""},{"name":"cl.internet/NTPDate","result":"PASS","duration":10570228790,"output":""},{"name":"cl.internet/UpdateEngine","result":"PASS","duration":1392159535,"output":""},{"name":"docker.selinux","result":"PASS","duration":146317613737,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: dbc3eadfebd7: Pulling fs layer\n cluster.go:125: dbc3eadfebd7: Download complete\n cluster.go:125: dbc3eadfebd7: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: sh: can't create /opt/hello: Permission denied\n"},{"name":"cl.internet/DockerPing","result":"PASS","duration":17154934852,"output":""},{"name":"cl.internet/DockerEcho","result":"PASS","duration":1579225996,"output":""},{"name":"cl.internet","result":"PASS","duration":162228276292,"output":" --- PASS: cl.internet/NTPDate (10.57s)\n --- PASS: cl.internet/UpdateEngine (1.39s)\n --- PASS: cl.internet/DockerPing (17.15s)\n --- PASS: cl.internet/DockerEcho (1.58s)\n"},{"name":"coreos.locksmith.tls","result":"PASS","duration":172578893629,"output":""},{"name":"docker.containerd-restart","result":"PASS","duration":203535730447,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: dbc3eadfebd7: Pulling fs layer\n cluster.go:125: dbc3eadfebd7: Download complete\n cluster.go:125: dbc3eadfebd7: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n"},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"PASS","duration":247426338229,"output":""},{"name":"cl.network.wireguard","result":"PASS","duration":125436585591,"output":" cluster.go:152: + ip --json address show kv0 | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n"},{"name":"docker.enable-service.sysext","result":"PASS","duration":125850736981,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"cl.ignition.kargs","result":"PASS","duration":124304995787,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":124773599577,"output":""},{"name":"cl.toolbox.dnf-install","result":"PASS","duration":144363838136,"output":""},{"name":"sysext.custom-docker.sysext","result":"PASS","duration":155766588095,"output":" cluster.go:125: bash: line 1: docker: command not found\n cluster.go:125: Cloning into 'sysext-bakery'...\n cluster.go:125: Note: switching to '9850ffd5b2353f45a9b3bf4fb84f8138a149e3e7'.\n cluster.go:125: \n cluster.go:125: You are in 'detached HEAD' state. You can look around, make experimental\n cluster.go:125: changes and commit them, and you can discard any commits you make in this\n cluster.go:125: state without impacting any branches by switching back to a branch.\n cluster.go:125: \n cluster.go:125: If you want to create a new branch to retain commits you create, you may\n cluster.go:125: do so (now or later) by using -c with the switch command. Example:\n cluster.go:125: \n cluster.go:125: git switch -c \u003cnew-branch-name\u003e\n cluster.go:125: \n cluster.go:125: Or undo this operation with:\n cluster.go:125: \n cluster.go:125: git switch -\n cluster.go:125: \n cluster.go:125: Turn off this advice by setting config variable advice.detachedHead to false\n cluster.go:125: \n cluster.go:125: HEAD is now at 9850ffd Merge pull request #31 from flatcar/t-lo/fix-docker-23-containerd-shim\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: dbc3eadfebd7: Pulling fs layer\n cluster.go:125: dbc3eadfebd7: Verifying Checksum\n cluster.go:125: dbc3eadfebd7: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: mke2fs 1.47.4 (6-Mar-2025)\n cluster.go:125: resize2fs 1.47.4 (6-Mar-2025)\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":153699883855,"output":""},{"name":"coreos.selinux.boolean","result":"PASS","duration":160634474982,"output":""},{"name":"cl.overlay.cleanup","result":"PASS","duration":161428092966,"output":""},{"name":"cl.ignition.v1.groups","result":"PASS","duration":127974397553,"output":""},{"name":"cl.network.nftables","result":"PASS","duration":124607780141,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":201042578420,"output":""},{"name":"cl.users.shells","result":"PASS","duration":124111723753,"output":""},{"name":"cl.flannel.vxlan","result":"PASS","duration":177513888736,"output":" flannel.go:121: ping from ci-4859.0.0-n-5c77dc5221(10.254.8.0) to ci-4859.0.0-n-fa1dd353a0(10.254.74.0)\n"},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":1370963864,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":1383159358,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":1298049407,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":2039204573,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":1295023366,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":1289232433,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":1297133309,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":1421007447,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":1736433295,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":1294749716,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":1563468362,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":1428689464,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":124645143900,"output":""},{"name":"cl.ignition.translation","result":"PASS","duration":127009171737,"output":" cluster.go:152: + ip --json address show kola | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n cluster.go:152: + cat /etc/systemd/network/00-dummy.network\n"},{"name":"cl.basic/Symlink","result":"PASS","duration":1297813866,"output":""},{"name":"cl.basic","result":"PASS","duration":150813840677,"output":" --- PASS: cl.basic/UpdateEngineKeys (1.37s)\n --- PASS: cl.basic/ServicesActive (1.38s)\n --- PASS: cl.basic/MachineID (1.30s)\n --- PASS: cl.basic/CloudConfig (2.04s)\n --- PASS: cl.basic/PortSSH (1.30s)\n --- PASS: cl.basic/SymlinkFlatcar (1.29s)\n --- PASS: cl.basic/ReadOnly (1.30s)\n --- PASS: cl.basic/RandomUUID (1.42s)\n --- PASS: cl.basic/Useradd (1.74s)\n --- PASS: cl.basic/Microcode (1.29s)\n --- PASS: cl.basic/Script (1.56s)\n --- PASS: cl.basic/DbusPerms (1.43s)\n --- PASS: cl.basic/Symlink (1.30s)\n"},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":126469651912,"output":""},{"name":"coreos.selinux.enforce","result":"PASS","duration":164522204476,"output":""},{"name":"cl.ignition.v1.once","result":"PASS","duration":155716761777,"output":""},{"name":"cl.etcd-member.discovery","result":"PASS","duration":152347574919,"output":""},{"name":"cl.ignition.v2_1.vfat","result":"PASS","duration":156211460728,"output":""},{"name":"cl.etcd-member.v2-backup-restore","result":"PASS","duration":153288419754,"output":" cluster.go:125: 2026-10-21T07:24:37Z\tinfo\tetcdutl/backup_command.go:223\tignoring EntryConfChange raft entry\n cluster.go:125: 2026-10-21T07:24:37Z\tinfo\tetcdutl/backup_command.go:238\tignoring member attribute update on\t{\"entry\": \"Term:2 Index:3 Data:\\\"\\\\010\\\\202\\\\244\\\\223\\\\306\\\\325\\\\253\\\\350\\\\320\\\\200\\\\001\\\\022\\\\003PUT\\\\032\u0026/0/members/77e3476bcc6080a1/attributes\\\\\\\"R{\\\\\\\"name\\\\\\\":\\\\\\\"2bb68eb5ff584995931793849d48dbab\\\\\\\",\\\\\\\"clientURLs\\\\\\\":[\\\\\\\"http://10.0.0.17:2379\\\\\\\"]}(\\\\0002\\\\0008\\\\000H\\\\000P\\\\000X\\\\000`\\\\000h\\\\000p\\\\000x\\\\000\\\\200\\\\001\\\\000\\\" \", \"v2Req.Path\": \"/0/members/77e3476bcc6080a1/attributes\"}\n cluster.go:125: 2026-10-21T07:24:37Z\tinfo\tetcdutl/backup_command.go:259\tignoring v3 raft entry\n cluster.go:125: 2026-10-21T07:24:37Z\tinfo\tmembership/store.go:138\tTrimming membership information from the backend...\n"},{"name":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":7756070811,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":9127486097,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/node_readiness","result":"PASS","duration":14081293007,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":18632250515,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:121): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.cilium.base/nginx_deployment","result":"PASS","duration":15534288571,"output":""},{"name":"kubeadm.v1.36.1.flannel.base","result":"PASS","duration":491809007654,"output":" cluster.go:125: I1021 07:21:55.165031 2476 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I1021 07:22:04.491235 2869 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-c4947523ad\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-c4947523ad\": lookup ci-4859.0.0-n-c4947523ad 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-4859.0.0-n-c4947523ad kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.5]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 656.159µ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.5:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.427466ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.816028ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.000791785s\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-4859.0.0-n-c4947523ad 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-4859.0.0-n-c4947523ad as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: wsk9ia.0q8n1d5bgt4zjizs\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.5:6443 --token wsk9ia.0q8n1d5bgt4zjizs \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:0b5f508debdfa6664e994f7d9def0d37bfa54ad0a2d92320579ce25c87ee1642 \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W1021 07:24:40.923403 2477 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W1021 07:24:41.066887 2477 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.flannel.base/node_readiness (7.76s)\n --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (9.13s)\n --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (18.63s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:121): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.cilium.base/NFS_deployment","result":"PASS","duration":18843452612,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"cl.cloudinit.multipart-mime","result":"PASS","duration":131208930765,"output":""},{"name":"docker.network-openbsd-nc","result":"PASS","duration":154655778519,"output":" docker.go:411: creating netcat containers\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.46MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:c7e646a3794854914ed9668a0455d7d35958a724f09ce4284e03613806ae0824\n cluster.go:125: #5 exporting manifest sha256:c7e646a3794854914ed9668a0455d7d35958a724f09ce4284e03613806ae0824 0.0s done\n cluster.go:125: #5 exporting config sha256:f4e73a7baeffe1313f115508a5ba447e2f47d5570ca4e346354bbc8ec2fc480d 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:bc5ec6d3b9212351dd3e7f94ea3cf2dc24648001950baa8ae8bc11b50e1ba5e8 0.1s done\n cluster.go:125: #5 exporting manifest list sha256:458e694ca7b2796972034daba8c94b2923fe2fe9876d88678e56e2ee3e0d1698\n cluster.go:125: #5 exporting manifest list sha256:458e694ca7b2796972034daba8c94b2923fe2fe9876d88678e56e2ee3e0d1698 0.0s done\n cluster.go:125: #5 naming to docker.io/library/netcat:latest done\n cluster.go:125: #5 unpacking to docker.io/library/netcat:latest 0.1s done\n cluster.go:125: #5 DONE 0.4s\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 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.46MB 0.0s done\n cluster.go:125: #3 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:1ac0bd0c2d81edc229818f3dfc8202b6857ecf776dce3ed2d6677aaec8ac8030 0.0s done\n cluster.go:125: #5 exporting config sha256:6b977582cb4f07edc50b9d3b92af57f7c27e98515363298e4bb161900c08556a 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:84c64ea0c0596f61ce1d8e06b82504c65cca6eb5de811e44f4434eca49dede28 0.0s done\n cluster.go:125: #5 exporting manifest list sha256:af0746f81b7913951417138906274846614cb384e72155abea00cc7fc9956ce0 0.0s done\n cluster.go:125: #5 naming to docker.io/library/netcat:latest done\n cluster.go:125: #5 unpacking to docker.io/library/netcat:latest 0.1s done\n cluster.go:125: #5 DONE 0.4s\n"},{"name":"kubeadm.v1.36.1.cilium.base/IPSec_encryption","result":"PASS","duration":19770280807,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"cl.locksmith.cluster","result":"PASS","duration":529408704801,"output":""},{"name":"kubeadm.v1.36.1.cilium.base","result":"PASS","duration":531814703864,"output":" cluster.go:125: I1021 07:21:58.847185 2754 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I1021 07:22:08.043262 2989 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-8830553fb8\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-8830553fb8\": lookup ci-4859.0.0-n-8830553fb8 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-4859.0.0-n-8830553fb8 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.8]\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 923.121µ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.8:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.112491ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 6.147124ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.501780138s\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-4859.0.0-n-8830553fb8 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-4859.0.0-n-8830553fb8 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: sw6ecu.0vi5pxgvp5dwpxpu\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.8:6443 --token sw6ecu.0vi5pxgvp5dwpxpu \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:7ad38b6d1b256d07a5d933b63285e7197fabf946db4e7306c3374f8989cb4389 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: Deployment cilium-operator \n cluster.go:125: DaemonSet cilium \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W1021 07:24:48.687776 2771 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W1021 07:24:48.825049 2771 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.cilium.base/node_readiness (14.08s)\n --- PASS: kubeadm.v1.36.1.cilium.base/nginx_deployment (15.53s)\n --- PASS: kubeadm.v1.36.1.cilium.base/NFS_deployment (18.84s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.36.1.cilium.base/IPSec_encryption (19.77s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"systemd.journal.user","result":"PASS","duration":155839616671,"output":""},{"name":"coreos.ignition.once","result":"PASS","duration":186426275326,"output":""},{"name":"cl.ignition.luks","result":"PASS","duration":187732919549,"output":""},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":157454489803,"output":""},{"name":"cl.update.badverity","result":"PASS","duration":470280875881,"output":""},{"name":"docker.userns","result":"PASS","duration":113786424111,"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 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.19MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:37695f9bc9ac3a96faee10f061a26e4163fd480b073244850a82f4b9800a8ffb done\n cluster.go:125: #5 naming to docker.io/library/userns-test 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.btrfs-storage","result":"PASS","duration":187705186665,"output":""},{"name":"cl.cloudinit.basic","result":"PASS","duration":155616922391,"output":""},{"name":"systemd.sysusers.gshadow","result":"PASS","duration":97544746004,"output":""},{"name":"cl.verity","result":"FAIL","duration":66741299700,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-1f6e5b693d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/c40ac4ae-9bd3-457d-9d66-373494e6df22\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:26:27.7038329+00:00\",\n \"endTime\": \"2026-10-21T07:26:32.1566069+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"c40ac4ae-9bd3-457d-9d66-373494e6df22\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.swap_activation","result":"PASS","duration":94897079354,"output":""},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":96685655893,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":20563970954,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"PASS","duration":9101367208,"output":""},{"name":"cl.ignition.v1.noop","result":"FAIL","duration":67285385748,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-da0bb86b4d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/dcfb0e85-bf42-4ba6-a23e-309f732f253f\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:09.8079198+00:00\",\n \"endTime\": \"2026-10-21T07:27:13.6313594+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"dcfb0e85-bf42-4ba6-a23e-309f732f253f\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"bpf.ig/ig","result":"FAIL","duration":68214931030,"output":" ig.go:57: creating node: PollUntilDone(ci-4859.0.0-n-56bcc988b2): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/4536862b-87cb-4d63-9e58-4a2bbe755410\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:13.564592+00:00\",\n \"endTime\": \"2026-10-21T07:27:18.0145368+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"4536862b-87cb-4d63-9e58-4a2bbe755410\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"PASS","duration":18756851383,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"bpf.ig","result":"FAIL","duration":70215378058,"output":" --- FAIL: bpf.ig/ig (68.21s)\n ig.go:57: creating node: PollUntilDone(ci-4859.0.0-n-56bcc988b2): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/4536862b-87cb-4d63-9e58-4a2bbe755410\n --------------------------------------------------------------------------------\n RESPONSE 200: 200 OK\n ERROR CODE: AllocationFailed\n --------------------------------------------------------------------------------\n {\n \"startTime\": \"2026-10-21T07:27:13.564592+00:00\",\n \"endTime\": \"2026-10-21T07:27:18.0145368+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"4536862b-87cb-4d63-9e58-4a2bbe755410\"\n }\n --------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":68354844591,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-210251cb9e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/823ca2ef-317d-4def-8407-db0e0c1517f4\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:16.3146076+00:00\",\n \"endTime\": \"2026-10-21T07:27:21.4525842+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"823ca2ef-317d-4def-8407-db0e0c1517f4\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":235188552959,"output":" security.go:132: starting client: PollUntilDone(ci-4859.0.0-n-90df582bae): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/837eafb6-e979-4113-a351-12162bd3c3e3\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:18.8437138+00:00\",\n \"endTime\": \"2026-10-21T07:27:22.7812589+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"837eafb6-e979-4113-a351-12162bd3c3e3\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"FAIL","duration":67734886504,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-06f9df95d9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/74a0209b-e52b-4fe8-b24c-76709a2af54e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:23.8815807+00:00\",\n \"endTime\": \"2026-10-21T07:27:27.5640711+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"74a0209b-e52b-4fe8-b24c-76709a2af54e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2.users","result":"FAIL","duration":683299233651,"output":" harness.go:651: Cluster failed starting machines: machine \"ci-4859.0.0-n-e68d5c08f4\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.112.113.14:22: i/o timeout\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":251593473149,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4859.0.0-n-978e0d6782): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/4ee69837-3834-4090-b2e0-3c20336a02ef\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:31.2678447+00:00\",\n \"endTime\": \"2026-10-21T07:27:35.0634633+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"4ee69837-3834-4090-b2e0-3c20336a02ef\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"PASS","duration":19485096820,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"azure.nvme-friendly-naming","result":"FAIL","duration":68052852324,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-3dcc88f7c2): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/72f20bb2-dd42-4d28-8a81-e8f36e70b11e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:34.4568537+00:00\",\n \"endTime\": \"2026-10-21T07:27:41.2168421+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"72f20bb2-dd42-4d28-8a81-e8f36e70b11e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.users","result":"FAIL","duration":68228637804,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-0887811462): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/5f32437f-5c4c-49a7-ae6b-8517c65504a9\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:35.4775901+00:00\",\n \"endTime\": \"2026-10-21T07:27:39.1613785+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"5f32437f-5c4c-49a7-ae6b-8517c65504a9\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"PASS","duration":565541459531,"output":" cluster.go:125: I1021 07:24:06.339324 2559 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I1021 07:24:15.283301 2773 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-196fba8167\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-196fba8167\": lookup ci-4859.0.0-n-196fba8167 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-4859.0.0-n-196fba8167 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.18]\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.89021ms\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.18:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.008536589s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.201319259s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.001120628s\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-4859.0.0-n-196fba8167 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-4859.0.0-n-196fba8167 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: i63nb5.ac0p8j4m2uefcck9\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.18:6443 --token i63nb5.ac0p8j4m2uefcck9 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:54cfaad28849fd9131d57fce6d25827f600193f08a38cd8618a3c64cf8525157 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W1021 07:27:30.541565 2638 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.35.1.cilium.base/node_readiness (20.56s)\n --- PASS: kubeadm.v1.35.1.cilium.base/nginx_deployment (9.10s)\n --- PASS: kubeadm.v1.35.1.cilium.base/NFS_deployment (18.76s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.35.1.cilium.base/IPSec_encryption (19.49s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"cl.ignition.v2.btrfsroot","result":"FAIL","duration":68505542636,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-bec8173c84): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/7a033d8c-3550-4506-acf6-56d160f7aafc\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:42.6522615+00:00\",\n \"endTime\": \"2026-10-21T07:27:47.42269+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"7a033d8c-3550-4506-acf6-56d160f7aafc\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.network.iptables","result":"PASS","duration":94714585970,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":381119880313,"output":" cluster.go:125: I1021 07:27:10.707517 2774 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I1021 07:27:20.104246 2986 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-0f72d9bec1\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-0f72d9bec1\": lookup ci-4859.0.0-n-0f72d9bec1 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-4859.0.0-n-0f72d9bec1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.4]\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.673592ms\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.4:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.506885432s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.79788475s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.002994504s\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-4859.0.0-n-0f72d9bec1 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-4859.0.0-n-0f72d9bec1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: fzwfqy.k983fo0vf6ezs2ak\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.4:6443 --token fzwfqy.k983fo0vf6ezs2ak \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:2c284079f455a1ce64d9b0f1e45e7bcc8919cab24a5f88ad0b998868d53b8372 \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-4859.0.0-n-31ec2d8424): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/782219f0-7bcd-46c9-89a5-57c0ceb9dfdf\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:47.9646205+00:00\",\n \"endTime\": \"2026-10-21T07:27:52.6071276+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"782219f0-7bcd-46c9-89a5-57c0ceb9dfdf\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.locksmith.reboot","result":"PASS","duration":461044435388,"output":""},{"name":"docker.base/docker-info","result":"PASS","duration":33914205715,"output":""},{"name":"kubeadm.v1.37.0.cilium.base","result":"FAIL","duration":424518544287,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-7334419bf2\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-7334419bf2\": lookup ci-4859.0.0-n-7334419bf2 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-4859.0.0-n-7334419bf2 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.31]\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 651.077µ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.31: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.236642ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 4.403968ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.003129025s\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-4859.0.0-n-7334419bf2 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-4859.0.0-n-7334419bf2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 2nsi2r.d3qprtrhkf0zu50x\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.31:6443 --token 2nsi2r.d3qprtrhkf0zu50x \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:35ccdd6f35bfe298322f921565a140d594abf2830ea2d6ee39c8b9d57224b915 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: Deployment cilium-operator \n cluster.go:125: DaemonSet cilium \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4859.0.0-n-0855495275): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/396e59f9-d3b3-4aff-9258-29818b1c4985\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:27:57.1628636+00:00\",\n \"endTime\": \"2026-10-21T07:28:02.0167436+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"396e59f9-d3b3-4aff-9258-29818b1c4985\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.base/resources","result":"PASS","duration":9719821190,"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 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.12MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:86531621ffcc33502185c2cb5bbd081239cbc873a77997491cbfa40fc58b9f15\n cluster.go:125: #5 exporting manifest sha256:86531621ffcc33502185c2cb5bbd081239cbc873a77997491cbfa40fc58b9f15 0.0s done\n cluster.go:125: #5 exporting config sha256:e68581b3ef78975ea61f3c67cc9d997548de1c9e40be0266869293a2cf773346 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:e5265f0f5bd1fb4923ec55a524f44b29ab5d0555d6ac085ca7be3f053d04eeb0 0.1s done\n cluster.go:125: #5 exporting manifest list sha256:7135de7f94b85953bf12b8b1aecf0274274627d1fdc471e0bdff2b4bd1549afe 0.0s done\n cluster.go:125: #5 naming to docker.io/library/sleep:latest done\n cluster.go:125: #5 unpacking to docker.io/library/sleep:latest 0.1s done\n cluster.go:125: #5 DONE 0.6s\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.cloudinit.script","result":"PASS","duration":125158525909,"output":""},{"name":"cl.ignition.symlink","result":"PASS","duration":125022321191,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"cl.metadata.azure","result":"FAIL","duration":66198218815,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4859.0.0-n-412c206902): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/d2746da4-9d43-46a2-804d-fbc734cb8915\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:28:36.8401784+00:00\",\n \"endTime\": \"2026-10-21T07:28:40.8685708+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"d2746da4-9d43-46a2-804d-fbc734cb8915\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":165096405390,"output":""},{"name":"cl.update.reboot","result":"PASS","duration":163420425884,"output":""},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":171860167977,"output":" resource.go:333: starting client: PollUntilDone(ci-4859.0.0-n-0e7dc7af1c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/95bd7e3f-a727-4e83-a78a-590baa8fd4d0\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:30:05.9281447+00:00\",\n \"endTime\": \"2026-10-21T07:30:10.1372171+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"95bd7e3f-a727-4e83-a78a-590baa8fd4d0\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.update.badusr","result":"PASS","duration":449794393343,"output":""},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":188925242450,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4859.0.0-n-af7b3c9b96): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/15e7ac91-8f81-4cf2-a19f-da79a0aa97d3\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T07:30:28.2923545+00:00\",\n \"endTime\": \"2026-10-21T07:30:33.1376586+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"15e7ac91-8f81-4cf2-a19f-da79a0aa97d3\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.base/networks-reliably","result":"PASS","duration":147752465188,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.23MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:44f5e7b4866ea536606676ff8af4543e8ccc8f4135178a97be2a2cb217e1809f 0.0s done\n cluster.go:125: #5 exporting config sha256:2bbcc36000d4442b19ebe7fc99333a30edc5f11859067291f473c7c27f5a82b5 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:98cd1faf195ce9dfc5e8e00389510c7d011c3a05d4ed78de9c919062c3d2acaa 0.0s done\n cluster.go:125: #5 exporting manifest list sha256:20b0adf4baa1d504b6fb600ec0db69beeabce25df3b2e1dce9b204056ec0f243\n cluster.go:125: #5 exporting manifest list sha256:20b0adf4baa1d504b6fb600ec0db69beeabce25df3b2e1dce9b204056ec0f243 0.0s done\n cluster.go:125: #5 naming to docker.io/library/ping:latest done\n cluster.go:125: #5 unpacking to docker.io/library/ping:latest 0.1s done\n cluster.go:125: #5 DONE 0.5s\n"},{"name":"docker.base/user-no-caps","result":"PASS","duration":4409857261,"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.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.22MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:0ed0ef70e0ac43ea41b8560403ea03e5aa665cc033ea66c48ecc9ec47d81511d 0.0s done\n cluster.go:125: #5 exporting config sha256:c9b2fd07d2f651d16c3e5fb9b45ed3cced53abbdc0e7725c27c3d16826254131 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:9f878f8e0e63d6e0a326fc08f61f15c291c972b0792ee9e292395181ccf8c011 0.0s done\n cluster.go:125: #5 exporting manifest list sha256:467836ddc4d94b518c80fe50c8e0d3aeff311a4d8f67568dbc7e4e89420826cb\n cluster.go:125: #5 exporting manifest list sha256:467836ddc4d94b518c80fe50c8e0d3aeff311a4d8f67568dbc7e4e89420826cb 0.0s done\n cluster.go:125: #5 naming to docker.io/library/captest:latest done\n cluster.go:125: #5 unpacking to docker.io/library/captest:latest 0.1s done\n cluster.go:125: #5 DONE 0.5s\n"},{"name":"docker.base/ownership","result":"PASS","duration":8941964143,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 0d6ad25c5ec8: Pulling fs layer\n cluster.go:125: bb482e962a91: Pulling fs layer\n cluster.go:125: 7cdd1ba5135a: Pulling fs layer\n cluster.go:125: 8083d0331109: Pulling fs layer\n cluster.go:125: f5c24fc2ff22: Pulling fs layer\n cluster.go:125: c403c18c260c: Pulling fs layer\n cluster.go:125: 1a47f466819b: Pulling fs layer\n cluster.go:125: bb482e962a91: Download complete\n cluster.go:125: 0d6ad25c5ec8: Download complete\n cluster.go:125: 1a47f466819b: Download complete\n cluster.go:125: f5c24fc2ff22: Download complete\n cluster.go:125: c403c18c260c: Download complete\n cluster.go:125: 7cdd1ba5135a: Download complete\n cluster.go:125: 8083d0331109: Download complete\n cluster.go:125: 7cdd1ba5135a: Pull complete\n cluster.go:125: bb482e962a91: Pull complete\n cluster.go:125: 8083d0331109: Pull complete\n cluster.go:125: 1a47f466819b: Pull complete\n cluster.go:125: f5c24fc2ff22: Pull complete\n cluster.go:125: c403c18c260c: Pull complete\n cluster.go:125: 0d6ad25c5ec8: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.base","result":"PASS","duration":358184256973,"output":" --- PASS: docker.base/docker-info (33.91s)\n --- PASS: docker.base/resources (9.72s)\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 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.12MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:86531621ffcc33502185c2cb5bbd081239cbc873a77997491cbfa40fc58b9f15\n cluster.go:125: #5 exporting manifest sha256:86531621ffcc33502185c2cb5bbd081239cbc873a77997491cbfa40fc58b9f15 0.0s done\n cluster.go:125: #5 exporting config sha256:e68581b3ef78975ea61f3c67cc9d997548de1c9e40be0266869293a2cf773346 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:e5265f0f5bd1fb4923ec55a524f44b29ab5d0555d6ac085ca7be3f053d04eeb0 0.1s done\n cluster.go:125: #5 exporting manifest list sha256:7135de7f94b85953bf12b8b1aecf0274274627d1fdc471e0bdff2b4bd1549afe 0.0s done\n cluster.go:125: #5 naming to docker.io/library/sleep:latest done\n cluster.go:125: #5 unpacking to docker.io/library/sleep:latest 0.1s done\n cluster.go:125: #5 DONE 0.6s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n --- PASS: docker.base/networks-reliably (147.75s)\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.23MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:44f5e7b4866ea536606676ff8af4543e8ccc8f4135178a97be2a2cb217e1809f 0.0s done\n cluster.go:125: #5 exporting config sha256:2bbcc36000d4442b19ebe7fc99333a30edc5f11859067291f473c7c27f5a82b5 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:98cd1faf195ce9dfc5e8e00389510c7d011c3a05d4ed78de9c919062c3d2acaa 0.0s done\n cluster.go:125: #5 exporting manifest list sha256:20b0adf4baa1d504b6fb600ec0db69beeabce25df3b2e1dce9b204056ec0f243\n cluster.go:125: #5 exporting manifest list sha256:20b0adf4baa1d504b6fb600ec0db69beeabce25df3b2e1dce9b204056ec0f243 0.0s done\n cluster.go:125: #5 naming to docker.io/library/ping:latest done\n cluster.go:125: #5 unpacking to docker.io/library/ping:latest 0.1s done\n cluster.go:125: #5 DONE 0.5s\n --- PASS: docker.base/user-no-caps (4.41s)\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.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.22MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 exporting manifest sha256:0ed0ef70e0ac43ea41b8560403ea03e5aa665cc033ea66c48ecc9ec47d81511d 0.0s done\n cluster.go:125: #5 exporting config sha256:c9b2fd07d2f651d16c3e5fb9b45ed3cced53abbdc0e7725c27c3d16826254131 0.0s done\n cluster.go:125: #5 exporting attestation manifest sha256:9f878f8e0e63d6e0a326fc08f61f15c291c972b0792ee9e292395181ccf8c011 0.0s done\n cluster.go:125: #5 exporting manifest list sha256:467836ddc4d94b518c80fe50c8e0d3aeff311a4d8f67568dbc7e4e89420826cb\n cluster.go:125: #5 exporting manifest list sha256:467836ddc4d94b518c80fe50c8e0d3aeff311a4d8f67568dbc7e4e89420826cb 0.0s done\n cluster.go:125: #5 naming to docker.io/library/captest:latest done\n cluster.go:125: #5 unpacking to docker.io/library/captest:latest 0.1s done\n cluster.go:125: #5 DONE 0.5s\n --- PASS: docker.base/ownership (8.94s)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 0d6ad25c5ec8: Pulling fs layer\n cluster.go:125: bb482e962a91: Pulling fs layer\n cluster.go:125: 7cdd1ba5135a: Pulling fs layer\n cluster.go:125: 8083d0331109: Pulling fs layer\n cluster.go:125: f5c24fc2ff22: Pulling fs layer\n cluster.go:125: c403c18c260c: Pulling fs layer\n cluster.go:125: 1a47f466819b: Pulling fs layer\n cluster.go:125: bb482e962a91: Download complete\n cluster.go:125: 0d6ad25c5ec8: Download complete\n cluster.go:125: 1a47f466819b: Download complete\n cluster.go:125: f5c24fc2ff22: Download complete\n cluster.go:125: c403c18c260c: Download complete\n cluster.go:125: 7cdd1ba5135a: Download complete\n cluster.go:125: 8083d0331109: Download complete\n cluster.go:125: 7cdd1ba5135a: Pull complete\n cluster.go:125: bb482e962a91: Pull complete\n cluster.go:125: 8083d0331109: Pull complete\n cluster.go:125: 1a47f466819b: Pull complete\n cluster.go:125: f5c24fc2ff22: Pull complete\n cluster.go:125: c403c18c260c: Pull complete\n cluster.go:125: 0d6ad25c5ec8: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"kubeadm.v1.37.0.flannel.base/node_readiness","result":"PASS","duration":7855591858,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":7779340115,"output":""},{"name":"kubeadm.v1.37.0.flannel.base/nginx_deployment","result":"PASS","duration":21661999395,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":21707121470,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":18565470117,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.37.0.flannel.base/NFS_deployment","result":"PASS","duration":18667122702,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"PASS","duration":520040004486,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-4e3fdb4762\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-4e3fdb4762\": lookup ci-4859.0.0-n-4e3fdb4762 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-4859.0.0-n-4e3fdb4762 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.14]\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 505.056µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.14: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.040295ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 7.128112ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002704606s\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-4859.0.0-n-4e3fdb4762 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-4859.0.0-n-4e3fdb4762 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: as836a.8tix8gm6464e8q39\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.14:6443 --token as836a.8tix8gm6464e8q39 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:424f8428c9b46d2fe6352a96be08719281f76b4567c41ae35b17ad7585ab2dcd \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W1021 07:36:13.295143 2429 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.37.0.flannel.base/node_readiness (7.86s)\n --- PASS: kubeadm.v1.37.0.flannel.base/nginx_deployment (21.66s)\n --- PASS: kubeadm.v1.37.0.flannel.base/NFS_deployment (18.67s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"PASS","duration":534915603662,"output":" cluster.go:125: I1021 07:33:27.124652 2655 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I1021 07:33:36.994945 2866 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-b817c7113d\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4859.0.0-n-b817c7113d\": lookup ci-4859.0.0-n-b817c7113d 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-4859.0.0-n-b817c7113d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.12]\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.210552ms\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.12:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.005731906s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.421283305s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.500912196s\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-4859.0.0-n-b817c7113d 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-4859.0.0-n-b817c7113d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 5zydrt.xk4gjxy0uvbdgjbi\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.12:6443 --token 5zydrt.xk4gjxy0uvbdgjbi \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:32a98462ce60d052fb85a7c7e1cf166e4272867ca6fa738238b18effc71fe93b \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W1021 07:36:13.365725 2574 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.35.1.flannel.base/node_readiness (7.78s)\n --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (21.71s)\n --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (18.57s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"}],"result":"FAIL","platform":"azure","version":"4859.0.0"}