{"tests":[{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":138677280007,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: error creating IP address: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":402622156725,"output":""},{"name":"cl.ignition.misc.empty","result":"PASS","duration":293122024260,"output":""},{"name":"cl.install.cloudinit","result":"PASS","duration":434593681435,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":440052933787,"output":""},{"name":"cl.flannel.udp","result":"PASS","duration":589470229413,"output":"        cluster.go:125: Timeout occurred while waiting for network connectivity.\n        flannel.go:121: ping from 256e1374-5e56-4159-8c80-2fb82c163df1(10.254.33.0) to cd432ce5-c19b-47a8-8e88-a011eb141850(10.254.55.1)\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":645674439742,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: server does not have a public IP address\n"},{"name":"coreos.ignition.resource.local","result":"PASS","duration":784992992884,"output":""},{"name":"kubeadm.v1.34.4.flannel.base","result":"FAIL","duration":796210391235,"output":"        cluster.go:125: I0708 12:32:06.036471    2642 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 12:32:17.770539    2860 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-4722-1-0-6-8de9044d3d\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4722-1-0-6-8de9044d3d\": lookup ci-4722-1-0-6-8de9044d3d 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-4722-1-0-6-8de9044d3d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.20.71]\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.600527ms\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.20.71: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.045502143s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.671720317s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.502064193s\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-4722-1-0-6-8de9044d3d 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-4722-1-0-6-8de9044d3d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: uwahyp.5wu5cckztjtsrvl1\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.20.71:6443 --token uwahyp.5wu5cckztjtsrvl1 \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f3fa79394bcc8cc6d91972e63be74f8b1081711df1f34021de0a3e1e7a393372 \n        cluster.go:125: namespace/kube-flannel created\n        cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n        cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n        cluster.go:125: serviceaccount/flannel created\n        cluster.go:125: configmap/kube-flannel-cfg created\n        cluster.go:125: daemonset.apps/kube-flannel-ds created\n        kubeadm.go:197: unable to setup cluster: unable to create worker node: error creating IP address: 504 Gateway Timeout, status code 504, Body: upstream request timeout\n"},{"name":"cl.cloudinit.basic","result":"FAIL","duration":1802755966353,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":1802814068897,"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":1802845320990,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"FAIL","duration":1802879822031,"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":1803392033367,"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":1803400347530,"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":1803416607866,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"},{"name":"cl.ignition.v1.noop","result":"FAIL","duration":1803664816948,"output":"        harness.go:608: Cluster failed: creating network for cluster: WaitWithContext() has timed out: context deadline exceeded\n"}],"result":"FAIL","platform":"stackit","version":"4722.1.0"}