{"tests":[{"name":"coreos.ignition.ssh.key","result":"FAIL","duration":141882612343,"output":"        harness.go:646: Cluster failed starting machines: error creating IP address: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"},{"name":"coreos.ignition.sethostname","result":"FAIL","duration":173067513689,"output":"        harness.go:646: Cluster failed starting machines: error creating IP address: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":98426963680,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: error creating IP address: 409 Conflict, status code 409, Body: {\"code\":409,\"msg\":\"conflict: Quota exceeded for resources: ['floatingip'].\"}\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":86130781059,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: error creating IP address: 409 Conflict, status code 409, Body: {\"code\":409,\"msg\":\"conflict: Quota exceeded for resources: ['floatingip'].\"}\n"},{"name":"cl.ignition.v2.noop","result":"FAIL","duration":39795472328,"output":"        harness.go:646: Cluster failed starting machines: error creating IP address: 409 Conflict, status code 409, Body: {\"code\":409,\"msg\":\"conflict: Quota exceeded for resources: ['floatingip'].\"}\n"},{"name":"cl.ignition.kargs","result":"FAIL","duration":28423049307,"output":"        harness.go:646: Cluster failed starting machines: error creating IP address: 409 Conflict, status code 409, Body: {\"code\":409,\"msg\":\"conflict: Quota exceeded for resources: ['floatingip'].\"}\n"},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":277906979091,"output":""},{"name":"coreos.ignition.security.tls","result":"PASS","duration":632662132373,"output":""},{"name":"cl.cloudinit.basic","result":"PASS","duration":237509210814,"output":""},{"name":"cl.ignition.v1.noop","result":"FAIL","duration":939354481156,"output":"        harness.go:646: Cluster failed starting machines: machine \"9519f27f-6e2b-43a0-8037-63d91227ac42\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 192.214.175.106:22: i/o timeout\n"},{"name":"kubeadm.v1.34.4.flannel.base/node_readiness","result":"PASS","duration":16020203860,"output":""},{"name":"kubeadm.v1.34.4.flannel.base/nginx_deployment","result":"PASS","duration":5754392667,"output":""},{"name":"kubeadm.v1.34.4.flannel.base/NFS_deployment","result":"PASS","duration":17145372744,"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"},{"name":"kubeadm.v1.34.4.flannel.base","result":"PASS","duration":851091052261,"output":"        cluster.go:125: I0708 09:50:29.405253    2153 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.9\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.9\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.9\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.9\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: I0708 09:50:40.598300    2369 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34\n        cluster.go:125: [init] Using Kubernetes version: v1.34.9\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593-2-4-c-9f5802fcf8\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593-2-4-c-9f5802fcf8\": lookup ci-4593-2-4-c-9f5802fcf8 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-4593-2-4-c-9f5802fcf8 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.197]\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 500.859073ms\n        cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n        cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.197: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.098222492s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.465684319s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.501296437s\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-4-c-9f5802fcf8 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-4-c-9f5802fcf8 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: fyrt0a.rlbvpzc483b80hr6\n        cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n        cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n        cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n        cluster.go:125: [addons] Applied essential addon: CoreDNS\n        cluster.go:125: [addons] Applied essential addon: kube-proxy\n        cluster.go:125: \n        cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n        cluster.go:125: \n        cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n        cluster.go:125: \n        cluster.go:125:   mkdir -p $HOME/.kube\n        cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n        cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config\n        cluster.go:125: \n        cluster.go:125: Alternatively, if you are the root user, you can run:\n        cluster.go:125: \n        cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf\n        cluster.go:125: \n        cluster.go:125: You should now deploy a pod network to the cluster.\n        cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n        cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/\n        cluster.go:125: \n        cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n        cluster.go:125: \n        cluster.go:125: kubeadm join 10.0.0.197:6443 --token fyrt0a.rlbvpzc483b80hr6 \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f5fea9e4dcc9bec6e0c267a2f8c73bc3e51ee4f1527ec47fd25190db3535b638 \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: W0708 09:55:05.313134    1961 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.flannel.base/node_readiness (16.02s)\n    --- PASS: kubeadm.v1.34.4.flannel.base/nginx_deployment (5.75s)\n    --- PASS: kubeadm.v1.34.4.flannel.base/NFS_deployment (17.15s)\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.ignition.misc.empty","result":"PASS","duration":284302530908,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":10735883672,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":5810848593,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":17417176029,"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":745373381635,"output":"        cluster.go:125: I0708 09:54:19.293868    2123 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.6\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.6\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.6\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.6\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: I0708 09:54:30.801281    2355 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35\n        cluster.go:125: [init] Using Kubernetes version: v1.35.6\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593-2-4-f-c106d3c43b\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593-2-4-f-c106d3c43b\": lookup ci-4593-2-4-f-c106d3c43b 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-4593-2-4-f-c106d3c43b kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.1.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 501.575842ms\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.1.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 3.506432348s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.878667915s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 5.502149239s\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-4-f-c106d3c43b 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-4-f-c106d3c43b as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: 3eswuw.kwwbsf432d1mzhpm\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.1.10:6443 --token 3eswuw.kwwbsf432d1mzhpm \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:176d1566c6e2fd9734451ed8ff2b5ee0a2b65a0376e2c80765a79a87f96a5df6 \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: W0708 09:57:51.313753    1912 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.74s)\n    --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (5.81s)\n    --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (17.42s)\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.install.cloudinit","result":"PASS","duration":321502837572,"output":""},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":266680534225,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: attaching public IP address: failed to add public ip to server: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"},{"name":"coreos.ignition.once","result":"PASS","duration":529207626455,"output":""},{"name":"linux.nfs.v3","result":"FAIL","duration":1802250976209,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"cl.flannel.udp","result":"FAIL","duration":1803250239271,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"kubeadm.v1.34.4.calico.base","result":"FAIL","duration":1803263822632,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":1803359516279,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":1804174893112,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"cl.internet","result":"FAIL","duration":1804485615943,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":1804497675546,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":1804630735667,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":1804778319152,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"coreos.ignition.resource.remote","result":"FAIL","duration":1813207509313,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"cl.basic","result":"FAIL","duration":1813398303648,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":918428485706,"output":"        harness.go:646: Cluster failed starting machines: machine \"0f42d5fc-2fca-45fc-a345-e245eca801db\" failed basic checks: some systemd units failed:\n● flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)\nstatus: \njournal:-- No entries --\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":370555676772,"output":"        harness.go:646: Cluster failed starting machines: error creating IP address: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":770598823936,"output":""},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":4927850969785,"output":"        harness.go:646: Cluster failed starting machines: error creating IP address: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"}],"result":"FAIL","platform":"stackit","version":"4593.2.4"}