{"tests":[{"name":"cl.internet","result":"FAIL","duration":37917616484,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632571376638850)\n"},{"name":"cl.install.cloudinit","result":"FAIL","duration":640024164,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, efc6aa653335538be78d89450ddd5119)\n"},{"name":"kubeadm.v1.33.8.calico.base","result":"FAIL","duration":40174551933,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to create new server: resource not found (not_found, 632571376638851)\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":40697262948,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632571376638857)\n"},{"name":"coreos.ignition.once","result":"FAIL","duration":674856261,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, e9dd59fa8873ae47fa879fbb1ae9e3ed)\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":40938758467,"output":"        nfs.go:77: Cluster.NewMachine: failed to create new server: resource not found (not_found, 632571376638852)\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":40997505455,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632571376638859)\n"},{"name":"kubeadm.v1.33.8.cilium.base","result":"FAIL","duration":2747983391,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, 9ea91d0681cf947272976a3ecf99b824)\n"},{"name":"kubeadm.v1.33.8.flannel.base","result":"FAIL","duration":41305871231,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to create new server: resource not found (not_found, 632571376638856)\n"},{"name":"cl.ignition.misc.empty","result":"FAIL","duration":655115369,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 1b0ef209fef71ac84fffc2a725d92c61)\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":41358588931,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632571376638860)\n"},{"name":"cl.basic","result":"FAIL","duration":666605803,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 0b6cba4f704a553663e03c8802ca143e)\n"},{"name":"cl.network.initramfs.second-boot","result":"FAIL","duration":649395510,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 73f121dd531c6f114678b1ac527a92cf)\n"},{"name":"coreos.ignition.sethostname","result":"FAIL","duration":41662551734,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632571376638861)\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":41686929603,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to create new server: resource not found (not_found, 632571376638854)\n"},{"name":"coreos.ignition.resource.remote","result":"FAIL","duration":874832981,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, 839b29dfb51be84a9b9c760a4a6f3d25)\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":673022960,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, ce0956982ebb9633a7746943f655ed46)\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":42033377528,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to create new server: resource not found (not_found, 632571376638855)\n"},{"name":"cl.ignition.kargs","result":"FAIL","duration":719334124,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: error during placement (resource_unavailable, ceef1ec28a04516ef2e17252d1903351)\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":42379618766,"output":"        harness.go:646: Cluster failed starting machines: failed to request new server: internal server error (server_error, 928e1b4ceb9117e9aedde2670e8c2727)\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":43437783177,"output":"        harness.go:646: Cluster failed starting machines: failed to create new server: resource not found (not_found, 632571376638864)\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":2689392030,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, 993965478b4e6cec5250e3c711420890)\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":2748248816,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, d6aa2f5be35883778a7c68b43f47c0dc)\n"},{"name":"linux.nfs.v3","result":"FAIL","duration":2727554297,"output":"        nfs.go:77: Cluster.NewMachine: failed to request new server: error during placement (resource_unavailable, 16b3362f8f5981f0673fa7505c99315b)\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":2714794013,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: failed to request new server: error during placement (resource_unavailable, 5699576e4c7c95e5bd10562dc118353e)\n"},{"name":"cl.ignition.v1.noop","result":"PASS","duration":57410760280,"output":""},{"name":"coreos.ignition.ssh.key","result":"PASS","duration":60888562282,"output":""},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":63813100598,"output":""},{"name":"kubeadm.v1.34.4.calico.base/node_readiness","result":"PASS","duration":16617198056,"output":""},{"name":"kubeadm.v1.34.4.calico.base/nginx_deployment","result":"PASS","duration":11424008387,"output":""},{"name":"kubeadm.v1.34.4.calico.base/NFS_deployment","result":"PASS","duration":18214482795,"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.34.4.calico.base","result":"PASS","duration":272364003212,"output":"        cluster.go:125: I0527 09:08:01.371877    2058 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n        cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.5-0\n        cluster.go:125: I0527 09:08:09.681093    2272 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n        cluster.go:125: [init] Using Kubernetes version: v1.34.8\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593-2-2-d-ff4cca792a\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593-2-2-d-ff4cca792a\": lookup ci-4593-2-2-d-ff4cca792a 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-4593-2-2-d-ff4cca792a kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 5.75.236.113]\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.00088408s\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://5.75.236.113: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.58594384s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.04152252s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.5021402s\n        cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n        cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n        cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n        cluster.go:125: [mark-control-plane] Marking the node ci-4593-2-2-d-ff4cca792a as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n        cluster.go:125: [mark-control-plane] Marking the node ci-4593-2-2-d-ff4cca792a as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: dkfp3l.ta4yxclquffqdhjm\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 5.75.236.113:6443 --token dkfp3l.ta4yxclquffqdhjm \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:21a2643f71247a6ab111f241eabf92c6f0d3b65bcddea9f584d07a848336216e \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: W0527 09:09:14.574546    1830 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n        cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n    --- PASS: kubeadm.v1.34.4.calico.base/node_readiness (16.62s)\n    --- PASS: kubeadm.v1.34.4.calico.base/nginx_deployment (11.42s)\n    --- PASS: kubeadm.v1.34.4.calico.base/NFS_deployment (18.21s)\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":"4593.2.2"}