{"tests":[{"name":"coreos.ignition.sethostname","result":"FAIL","duration":13536146080,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 549b4bcfbdd74fd19462bc69c8d8c070)\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":15515086659,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, e489ce972c6c251c8008d4e51aceecfc)\n"},{"name":"kubeadm.v1.33.8.cilium.base","result":"FAIL","duration":15535832295,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, dfec4b880550d5bcf4dbe1df0c444944)\n"},{"name":"coreos.ignition.resource.remote","result":"FAIL","duration":32403109403,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632425347648693)\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":2636112086,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, 08369b448ede4bc3c26142213a44176d)\n"},{"name":"cl.install.cloudinit","result":"FAIL","duration":631092443,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, fe5f7e6bc85df17dad11f09147ab4492)\n"},{"name":"cl.internet","result":"FAIL","duration":705868919,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 21c058a7fe5fd91d2a2cb83df8dde6ad)\n"},{"name":"coreos.ignition.once","result":"FAIL","duration":36642248335,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632425347648685)\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":680393180,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 49a2f9e5aa209ab7b3b4c044078b9534)\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":626855227,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 2e678e96fc8bcc9bfb6ef1c018604037)\n"},{"name":"cl.network.initramfs.second-boot","result":"FAIL","duration":661594079,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 828483342f60411b37f69b05e06c0d7c)\n"},{"name":"cl.ignition.misc.empty","result":"FAIL","duration":38321065190,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632425347648684)\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":38453513430,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632425347648692)\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":38587979411,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632425347648682)\n"},{"name":"cl.ignition.v2.btrfsroot","result":"FAIL","duration":684765716,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 77745a06d5495d19455e741b485b9436)\n"},{"name":"cl.ignition.kargs","result":"FAIL","duration":39498718956,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632425347648681)\n"},{"name":"kubeadm.v1.34.4.calico.base","result":"FAIL","duration":2689504139,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, 315eaaf1ce28c7ee465fb15fc49c747b)\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":2620368033,"output":"        nfs.go:77: Cluster.NewMachine: failed to request new server: error during placement (resource_unavailable, b6e44b8db33b6315f360c2ec1fe89b5c)\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":2686882179,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, 54b7c472753638358792fc094390218e)\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":48361073730,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 1c894ff91c346ffd7fc6b9eef2679e7e)\n"},{"name":"linux.nfs.v3","result":"FAIL","duration":38666506939,"output":"        nfs.go:77: Cluster.NewMachine: failed to create new server: resource not found (not_found, 632425347648739)\n"},{"name":"cl.basic/Script","result":"PASS","duration":472454634,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":322944023,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":259260243,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":263790587,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":261073199,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":254166160,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":276997843,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":254455895,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":232622841,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":426914640,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":247782628,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":233016176,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":720435668,"output":""},{"name":"cl.ignition.v1.noop","result":"PASS","duration":92236391666,"output":""},{"name":"cl.basic","result":"PASS","duration":95921722539,"output":"    --- PASS: cl.basic/Script (0.47s)\n    --- PASS: cl.basic/DbusPerms (0.32s)\n    --- PASS: cl.basic/Symlink (0.26s)\n    --- PASS: cl.basic/SymlinkFlatcar (0.26s)\n    --- PASS: cl.basic/ServicesActive (0.26s)\n    --- PASS: cl.basic/ReadOnly (0.25s)\n    --- PASS: cl.basic/RandomUUID (0.28s)\n    --- PASS: cl.basic/PortSSH (0.25s)\n    --- PASS: cl.basic/UpdateEngineKeys (0.23s)\n    --- PASS: cl.basic/Useradd (0.43s)\n    --- PASS: cl.basic/MachineID (0.25s)\n    --- PASS: cl.basic/Microcode (0.23s)\n    --- PASS: cl.basic/CloudConfig (0.72s)\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":99537364580,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: failed to request new server: error during placement (resource_unavailable, 07859ccf5937c6d14fe5b720a5a57009)\n"},{"name":"coreos.ignition.ssh.key","result":"PASS","duration":84910433455,"output":""},{"name":"kubeadm.v1.33.8.flannel.base/node_readiness","result":"PASS","duration":10910704895,"output":""},{"name":"kubeadm.v1.33.8.calico.base/node_readiness","result":"PASS","duration":16555754379,"output":""},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":227179649054,"output":"        cluster.go:125: I0526 16:06:33.225482    2022 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n        cluster.go:125: I0526 16:06:48.829874    2250 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n        cluster.go:125: [init] Using Kubernetes version: v1.35.5\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4694-0-1-8-c008fadc78\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4694-0-1-8-c008fadc78\": lookup ci-4694-0-1-8-c008fadc78 on 185.12.64.2: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-4694-0-1-8-c008fadc78 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 91.107.219.10]\n        cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n        cluster.go:125: [certs] Generating \"sa\" key and public key\n        cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n        cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n        cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n        cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n        cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n        cluster.go:125: [kubelet-start] Starting the kubelet\n        cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n        cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n        cluster.go:125: [kubelet-check] The kubelet is healthy after 2.502547784s\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://91.107.219.10: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 6.530662841s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 8.145267064s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 9.507408159s\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-4694-0-1-8-c008fadc78 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-4694-0-1-8-c008fadc78 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: y1god8.naxw0r6owvj4n8b7\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 91.107.219.10:6443 --token y1god8.naxw0r6owvj4n8b7 \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:adffc8f76d09ced2f57f470a3114e4dbf1090e196ad5eec34e6e6237aae6450f \n        cluster.go:125: namespace/kube-flannel created\n        cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n        cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n        cluster.go:125: serviceaccount/flannel created\n        cluster.go:125: configmap/kube-flannel-cfg created\n        cluster.go:125: daemonset.apps/kube-flannel-ds created\n        kubeadm.go:197: unable to setup cluster: unable to create worker node: failed to request new server: error during placement (resource_unavailable, e43c5f2928443d498c4616ea2d2b364d)\n"},{"name":"kubeadm.v1.33.8.calico.base/nginx_deployment","result":"PASS","duration":11501943015,"output":""},{"name":"kubeadm.v1.33.8.flannel.base/nginx_deployment","result":"PASS","duration":21989967705,"output":""},{"name":"kubeadm.v1.33.8.flannel.base/NFS_deployment","result":"PASS","duration":12834505490,"output":"        cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n        cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.33.8.calico.base/NFS_deployment","result":"PASS","duration":18444856416,"output":"        cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n        cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.33.8.calico.base","result":"PASS","duration":321515799055,"output":"        cluster.go:125: I0526 16:06:30.048996    2090 version.go:261] remote version is much newer: v1.36.1; falling back to: stable-1.33\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.0\n        cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10\n        cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.5.24-0\n        cluster.go:125: I0526 16:06:39.240696    2304 version.go:261] remote version is much newer: v1.36.1; falling back to: stable-1.33\n        cluster.go:125: [init] Using Kubernetes version: v1.33.12\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4694-0-1-8-fbbcf518d1\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4694-0-1-8-fbbcf518d1\": lookup ci-4694-0-1-8-fbbcf518d1 on 185.12.64.1: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-4694-0-1-8-fbbcf518d1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 178.105.192.231]\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/config.yaml\"\n        cluster.go:125: [kubelet-start] Starting the kubelet\n        cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n        cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n        cluster.go:125: [kubelet-check] The kubelet is healthy after 1.50191248s\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://178.105.192.231: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.032079794s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.858179568s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.502355984s\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-4694-0-1-8-fbbcf518d1 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-4694-0-1-8-fbbcf518d1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: y6yhmg.ya588titpy7r0nmw\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 178.105.192.231:6443 --token y6yhmg.ya588titpy7r0nmw \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f280c85a50d423e4d76430145ce62393be96ea8913308819ef606559b0691171 \n        cluster.go:125: namespace/tigera-operator created\n        cluster.go:125: serviceaccount/tigera-operator created\n        cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n        cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n        cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n        cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n        cluster.go:125: deployment.apps/tigera-operator created\n        cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n        cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n        cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n        cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n        cluster.go:125: installation.operator.tigera.io/default created\n        cluster.go:125: apiserver.operator.tigera.io/default created\n        cluster.go:125: goldmane.operator.tigera.io/default created\n        cluster.go:125: whisker.operator.tigera.io/default created\n        cluster.go:125: W0526 16:07:47.283099    1847 joinconfiguration.go:113] [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.33.8.calico.base/node_readiness (16.56s)\n    --- PASS: kubeadm.v1.33.8.calico.base/nginx_deployment (11.50s)\n    --- PASS: kubeadm.v1.33.8.calico.base/NFS_deployment (18.44s)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.33.8.flannel.base","result":"PASS","duration":333549323792,"output":"        cluster.go:125: I0526 16:06:40.766831    2028 version.go:261] remote version is much newer: v1.36.1; falling back to: stable-1.33\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.33.12\n        cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.0\n        cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10\n        cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.5.24-0\n        cluster.go:125: I0526 16:06:50.309448    2230 version.go:261] remote version is much newer: v1.36.1; falling back to: stable-1.33\n        cluster.go:125: [init] Using Kubernetes version: v1.33.12\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4694-0-1-7-60d7f3dc46\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4694-0-1-7-60d7f3dc46\": lookup ci-4694-0-1-7-60d7f3dc46 on 185.12.64.2: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-4694-0-1-7-60d7f3dc46 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 116.202.28.204]\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/config.yaml\"\n        cluster.go:125: [kubelet-start] Starting the kubelet\n        cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n        cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n        cluster.go:125: [kubelet-check] The kubelet is healthy after 1.001948319s\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://116.202.28.204: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.015989264s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.20376412s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.503506993s\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-4694-0-1-7-60d7f3dc46 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-4694-0-1-7-60d7f3dc46 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: i2samz.besti53njfdd814o\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 116.202.28.204:6443 --token i2samz.besti53njfdd814o \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:c8548110730aac0178cdf6c9f778fc9fce14ff917e47c792b40282afb8a3fa6b \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: W0526 16:07:43.647763    1799 joinconfiguration.go:113] [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.33.8.flannel.base/node_readiness (10.91s)\n    --- PASS: kubeadm.v1.33.8.flannel.base/nginx_deployment (21.99s)\n    --- PASS: kubeadm.v1.33.8.flannel.base/NFS_deployment (12.83s)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:122): Cannot iterate over null (null)\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":680637212713,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, c12ddacf7edf6d9e87bf05a75be354ed)\n"}],"result":"FAIL","platform":"hetzner","version":"4694.0.1"}