{"tests":[{"name":"linux.nfs.v3","result":"FAIL","duration":96582401756,"output":"        nfs.go:77: Cluster.NewMachine: creating server: error creating server wait: found non-GenericOpenApiError: waiting failed. state is ERROR\n"},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":362574212422,"output":""},{"name":"cl.ignition.v1.noop","result":"FAIL","duration":784471974640,"output":"        harness.go:651: Cluster failed starting machines: machine \"c75e3939-4156-4034-a2bb-d4d83afb9aed\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.66.193:22: i/o timeout\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":789164615157,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine \"01d6d117-693b-485e-8b45-06a222fc4d74\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.66.21:22: i/o timeout\n"},{"name":"cl.internet","result":"FAIL","duration":816589366382,"output":"        harness.go:651: Cluster failed starting machines: machine \"17cadadc-fb99-4877-abed-57c5238899ad\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.70.175:22: i/o timeout\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":818082802441,"output":"        harness.go:651: Cluster failed starting machines: machine \"f4665007-20c7-407f-90bb-01f054bc6e56\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.67.54:22: i/o timeout\n"},{"name":"coreos.ignition.sethostname","result":"FAIL","duration":818343518170,"output":"        harness.go:651: Cluster failed starting machines: machine \"cdf5668e-69eb-4e93-ba4d-72edf7de2b16\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.96.187:22: i/o timeout\n"},{"name":"cl.ignition.kargs","result":"FAIL","duration":819949303835,"output":"        harness.go:651: Cluster failed starting machines: machine \"ed17b65f-fb3f-4194-b6f1-0a4e2a1806ba\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 192.214.179.61:22: i/o timeout\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":821292865974,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine \"0d1bfcd0-4ef9-49f9-83a4-d1a12454afa8\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.69.183:22: i/o timeout\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":840412517262,"output":"        harness.go:651: Cluster failed starting machines: machine \"c13e2f73-6272-4fdb-a926-d8215e82a8d1\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.70.86:22: i/o timeout\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":871381605162,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine \"611b2dd9-c146-4069-81e7-16ede7197d0f\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 192.214.172.42:22: i/o timeout\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":774937311730,"output":"        harness.go:651: Cluster failed starting machines: machine \"51b01ae1-a239-4282-9d98-d6f44b283e0f\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 213.17.20.74:22: i/o timeout\n"},{"name":"kubeadm.v1.37.0.cilium.base","result":"FAIL","duration":873146778922,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine \"d762f59a-27eb-4d99-843f-12b15f68d233\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 192.214.184.183:22: i/o timeout\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":873181677720,"output":"        harness.go:651: Cluster failed starting machines: machine \"75ad9278-adaa-4173-89a0-fdcb4451ee6c\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 192.214.182.216:22: i/o timeout\n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":873689754001,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine \"4922729a-fa70-45ec-b7cb-0f13c4436694\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 213.17.20.254:22: i/o timeout\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":873707412670,"output":"        nfs.go:77: Cluster.NewMachine: machine \"69c437a6-e8c8-429d-870e-f5186cdbed5a\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 192.214.183.187:22: i/o timeout\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":877751982383,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine \"d0965ca3-2361-4fbe-849e-003c377e3771\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 213.17.20.130:22: i/o timeout\n"},{"name":"cl.basic/Script","result":"PASS","duration":572887312,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":236977723,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":269849900,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":228967557,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":290602116,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":244272170,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":274648889,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":269988801,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":858333560,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":361854041,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":396244075,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":230836321,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":259618868,"output":""},{"name":"cl.install.cloudinit","result":"PASS","duration":244551899707,"output":""},{"name":"coreos.ignition.ssh.key","result":"PASS","duration":273627489976,"output":""},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":243447350407,"output":""},{"name":"cl.basic","result":"PASS","duration":282983546134,"output":"    --- PASS: cl.basic/Script (0.57s)\n    --- PASS: cl.basic/PortSSH (0.24s)\n    --- PASS: cl.basic/DbusPerms (0.27s)\n    --- PASS: cl.basic/Symlink (0.23s)\n    --- PASS: cl.basic/SymlinkFlatcar (0.29s)\n    --- PASS: cl.basic/UpdateEngineKeys (0.24s)\n    --- PASS: cl.basic/ServicesActive (0.27s)\n    --- PASS: cl.basic/ReadOnly (0.27s)\n    --- PASS: cl.basic/CloudConfig (0.86s)\n    --- PASS: cl.basic/RandomUUID (0.36s)\n    --- PASS: cl.basic/Useradd (0.40s)\n    --- PASS: cl.basic/MachineID (0.23s)\n    --- PASS: cl.basic/Microcode (0.26s)\n"},{"name":"coreos.ignition.once","result":"PASS","duration":273691786219,"output":""},{"name":"cl.ignition.misc.empty","result":"PASS","duration":271953536044,"output":""},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":330878763532,"output":""},{"name":"kubeadm.v1.37.0.flannel.base","result":"FAIL","duration":960000554766,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: machine \"d835de0f-20c4-4857-ab08-412363c77bf7\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.124.230:22: i/o timeout\n"},{"name":"coreos.ignition.resource.local","result":"PASS","duration":485659568940,"output":""},{"name":"kubeadm.v1.36.1.calico.base/node_readiness","result":"PASS","duration":23525613156,"output":""},{"name":"kubeadm.v1.36.1.calico.base/nginx_deployment","result":"PASS","duration":6773513070,"output":""},{"name":"cl.cloudinit.basic","result":"FAIL","duration":802941064653,"output":"        harness.go:651: Cluster failed starting machines: machine \"a927f5ad-011f-424b-893b-de18c46d9562\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.67.54:22: i/o timeout\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":809803328309,"output":"        harness.go:651: Cluster failed starting machines: machine \"234cbc57-2ae3-4a2e-b698-bfb551902bc5\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.66.193:22: i/o timeout\n"},{"name":"kubeadm.v1.36.1.calico.base/NFS_deployment","result":"PASS","duration":32369833091,"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        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        cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"cl.flannel.udp","result":"FAIL","duration":894556257879,"output":"        harness.go:651: Cluster failed starting machines: machine \"aea57619-5869-436a-91dc-1136883cef4d\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.66.21:22: i/o timeout\n"},{"name":"kubeadm.v1.35.1.calico.base/node_readiness","result":"PASS","duration":27495734844,"output":""},{"name":"kubeadm.v1.36.1.calico.base","result":"PASS","duration":910544869187,"output":"        cluster.go:125: I1029 00:29:21.862793    2075 version.go:260] remote version is much newer: v1.37.2; falling back to: stable-1.36\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.6\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.6\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.6\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.6\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: I1029 00:29:38.844948    2324 version.go:260] remote version is much newer: v1.37.2; falling back to: stable-1.36\n        cluster.go:125: [init] Using Kubernetes version: v1.36.6\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4820-1-0-n-9a4226965c\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4820-1-0-n-9a4226965c\": lookup ci-4820-1-0-n-9a4226965c on 1.1.1.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-4820-1-0-n-9a4226965c kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.3.51]\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 3.950882ms\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.3.51: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.571747ms\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 27.203663ms\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.005941123s\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-4820-1-0-n-9a4226965c 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-4820-1-0-n-9a4226965c as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: 8l4hkq.l8xa5jtzfastq07u\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.3.51:6443 --token 8l4hkq.l8xa5jtzfastq07u \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:6b279223cec98c5b630eb10a0dfbb0425e10374ebdb8f2bd9a2e7ad757889edd \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: W1029 00:34:10.276518    1869 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: W1029 00:34:10.587178    1869 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.calico.base/node_readiness (23.53s)\n    --- PASS: kubeadm.v1.36.1.calico.base/nginx_deployment (6.77s)\n    --- PASS: kubeadm.v1.36.1.calico.base/NFS_deployment (32.37s)\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            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            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.calico.base/nginx_deployment","result":"PASS","duration":22678430290,"output":""},{"name":"kubeadm.v1.35.1.calico.base/NFS_deployment","result":"PASS","duration":35482709329,"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        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        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.calico.base","result":"PASS","duration":935965861432,"output":"        cluster.go:125: I1029 00:30:30.204028    1925 version.go:260] remote version is much newer: v1.37.2; falling back to: stable-1.35\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.10\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.10\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.10\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.10\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: I1029 00:30:43.788892    2153 version.go:260] remote version is much newer: v1.37.2; falling back to: stable-1.35\n        cluster.go:125: [init] Using Kubernetes version: v1.35.10\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4820-1-0-n-1a8474257e\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4820-1-0-n-1a8474257e\": lookup ci-4820-1-0-n-1a8474257e on 1.1.1.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-4820-1-0-n-1a8474257e kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.6.72]\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.797499ms\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.6.72: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.508806647s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.288671149s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.51430174s\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-4820-1-0-n-1a8474257e 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-4820-1-0-n-1a8474257e as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: rxom4i.mebcgsgj7n8km8zo\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.6.72:6443 --token rxom4i.mebcgsgj7n8km8zo \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:53caeb074e5f596db8e95f20c1af254c7c39673ef78af2b3dda97d0a607f4687 \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: W1029 00:35:09.239777    1869 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.calico.base/node_readiness (27.50s)\n    --- PASS: kubeadm.v1.35.1.calico.base/nginx_deployment (22.68s)\n    --- PASS: kubeadm.v1.35.1.calico.base/NFS_deployment (35.48s)\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            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            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":"stackit","version":"4820.1.0"}