{"tests":[{"name":"cl.ignition.misc.empty","result":"FAIL","duration":35976880019,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632597146475460)\n"},{"name":"coreos.ignition.resource.remote","result":"FAIL","duration":36588743603,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632597146475465)\n"},{"name":"linux.nfs.v3","result":"FAIL","duration":37633096405,"output":"        nfs.go:77: Cluster.NewMachine: failed to create new server: resource not found (not_found, 632597146475459)\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":38236451200,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to create new server: resource not found (not_found, 632597146475463)\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":38330998505,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632597146475476)\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":38620152599,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632597146475477)\n"},{"name":"kubeadm.v1.33.8.cilium.base","result":"FAIL","duration":2703348421,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, f52556c6a1401f6dab647df436df0c54)\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":38815381863,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to create new server: resource not found (not_found, 632597146475464)\n"},{"name":"coreos.ignition.sethostname","result":"PASS","duration":56610723320,"output":""},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":58099729796,"output":"        resource.go:333: starting client: failed to request new server: error during placement (resource_unavailable, a2acbac7072a3fcaf8c38c101454b2bd)\n"},{"name":"cl.install.cloudinit","result":"PASS","duration":72082200772,"output":""},{"name":"kubeadm.v1.33.8.flannel.base","result":"FAIL","duration":83741224003,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: failed to request new server: error during placement (resource_unavailable, 5df2728f0309c39f4a95c2637aa295fc)\n"},{"name":"kubeadm.v1.33.8.calico.base","result":"FAIL","duration":83889687682,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: failed to request new server: error during placement (resource_unavailable, c5ecada679bccfb109b3b61844a9ed1d)\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":84360247788,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: failed to request new server: error during placement (resource_unavailable, 5ed3845c83ef02e978d4c51bdb267e1c)\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":84443757439,"output":"        nfs.go:80: NFS server booted.\n        nfs.go:85: Test file \"/tmp/tmp.DLsIjmeANd\" created on server.\n        nfs.go:122: Cluster.NewMachine: failed to request new server: error during placement (resource_unavailable, e8430ca07de59c7b929b37fe4bc53b86)\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":91535739802,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: failed to request new server: error during placement (resource_unavailable, 62e0b1ed2dc35920220e4fcaa713614c)\n"},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":10918290298,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":5981022799,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":12736454629,"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.35.1.flannel.base","result":"PASS","duration":272115690777,"output":"        cluster.go:125: I0527 12:50:30.061397    2006 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: I0527 12:50:38.498931    2235 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n        cluster.go:125: [init] Using Kubernetes version: v1.35.5\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628-1-2-1-ace712011f\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4628-1-2-1-ace712011f\": lookup ci-4628-1-2-1-ace712011f 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-4628-1-2-1-ace712011f kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 178.105.198.57]\n        cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n        cluster.go:125: [certs] Generating \"sa\" key and public key\n        cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n        cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n        cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n        cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n        cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n        cluster.go:125: [kubelet-start] Starting the kubelet\n        cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n        cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n        cluster.go:125: [kubelet-check] The kubelet is healthy after 1.00208744s\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.198.57:6443/livez\n        cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n        cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n        cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.51148384s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.96359988s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.00208728s\n        cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n        cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n        cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n        cluster.go:125: [mark-control-plane] Marking the node ci-4628-1-2-1-ace712011f as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n        cluster.go:125: [mark-control-plane] Marking the node ci-4628-1-2-1-ace712011f as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: jp42e9.o10v5adbv7zptstg\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.198.57:6443 --token jp42e9.o10v5adbv7zptstg \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:c106c656c9e226971bc5663e706a48d9766ae1c1d752f09a1757e46603285bde \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: W0527 12:51:25.980239    1753 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 (10.92s)\n    --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (5.98s)\n    --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (12.74s)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"}],"result":"FAIL","platform":"hetzner","version":"4628.1.2"}