### Test report for 4757.2.3 / arm64
**Platforms tested** : stackit
🟢 ok **cl.basic**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __80cc6e1c-4691-458d-a5d6-aebb5bc3d160__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.113.57:22: i/o t?imeout_"
L2: " "
```
🟢 ok **cl.cloudinit.basic**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __34ea0ed2-5fac-4b10-a695-d03d40b0b15b__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.115.248:22: i/o ?timeout_"
L2: " "
```
🟢 ok **cl.etcd-member.discovery**; Succeeded: stackit (1)
🟢 ok **cl.flannel.vxlan**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __dbe281f2-9ede-4378-a51d-74f0d57df3de__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.76.115:22: i/o t?imeout_"
L2: " "
```
🟢 ok **cl.ignition.kargs**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ed724d24-d0a5-46b9-a0b8-5f578e08f054__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.76.222:22: i/o t?imeout_"
L2: " "
```
🟢 ok **cl.ignition.misc.empty**; Succeeded: stackit (1)
🟢 ok **cl.ignition.v1.noop**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __2624d081-dabc-4fc0-8994-c78e17064b5c__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.76.69:22: i/o ti?meout_"
L2: " "
```
🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __ab0cf318-0a19-4370-9534-b1156f1db5ac__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.76.118:22: i/o t?imeout_"
L2: " "
```
🟢 ok **cl.ignition.v2.noop**; Succeeded: stackit (1)
🟢 ok **cl.install.cloudinit**; Succeeded: stackit (1)
🟢 ok **cl.internet**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __1248a787-0816-42f7-af4f-77b30bda6c12__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.112.125:22: i/o ?timeout_"
L2: " "
```
🟢 ok **cl.network.initramfs.second-boot**; Succeeded: stackit (1)
🟢 ok **coreos.ignition.once**; Succeeded: stackit (1)
🟢 ok **coreos.ignition.resource.local**; Succeeded: stackit (1)
🟢 ok **coreos.ignition.resource.remote**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __d5b6889c-c5e6-4767-b8ed-6395b74d5e99__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.124.190:22: i/o ?timeout_"
L2: " "
```
🟢 ok **coreos.ignition.security.tls**; Succeeded: stackit (1)
🟢 ok **coreos.ignition.sethostname**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __dca22263-d98f-4781-b6af-4d8a3e727a35__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.115.89:22: i/o t?imeout_"
L2: " "
```
🟢 ok **coreos.ignition.ssh.key**; Succeeded: stackit (1)
🟢 ok **docker.network-openbsd-nc**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _harness.go:651: Cluster failed starting machines: machine __7e058f56-5b09-4499-958e-a6b6716d8b7f__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.124.34:22: i/o t?imeout_"
L2: " "
```
🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: stackit (1)
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine __e8f5c6ab-7a64-4ea4-a86a-4e8eeed08d6b__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.?34.127.89:22: i/o timeout_"
L2: " "
```
🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine __68067690-cb47-4b0a-b83e-3206ae3077a2__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.?34.112.153:22: i/o timeout_"
L2: " "
```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _cluster.go:125: I1027 11:05:01.902039 2152 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
L9: "cluster.go:125: I1027 11:05:10.562609 2386 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757-2-3-9-50d1070855__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4757-2-3-9-50d1070855__: lookup ci-4757-2-3-9-50d1070855 on 1.1.1.1:53: no such host"
L14: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
L15: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
L16: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
L17: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
L18: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757-2-3-9-50d1070855 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.3.159]"
L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 797.003??s"
L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.3.159:6443/livez"
L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 9.729163ms"
L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 11.623811ms"
L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.501175166s"
L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4757-2-3-9-50d1070855 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4757-2-3-9-50d1070855 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L61: "cluster.go:125: [bootstrap-token] Using token: k5ajjw.mz11tc8hs4cv1ltw"
L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L64: "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"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L67: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
L68: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L69: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L70: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L71: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L72: "cluster.go:125: "
L73: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L74: "cluster.go:125: "
L75: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L76: "cluster.go:125: "
L77: "cluster.go:125: mkdir -p $HOME/.kube"
L78: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L79: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L80: "cluster.go:125: "
L81: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L82: "cluster.go:125: "
L83: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L84: "cluster.go:125: "
L85: "cluster.go:125: You should now deploy a pod network to the cluster."
L86: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L87: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L88: "cluster.go:125: "
L89: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L90: "cluster.go:125: "
L91: "cluster.go:125: kubeadm join 10.0.3.159:6443 --token k5ajjw.mz11tc8hs4cv1ltw _"
L92: "cluster.go:125: --discovery-token-ca-cert-hash sha256:c49327f98b551e77d1491ffe16d3b97689a6e40332286a4f7b3847a6a9fc0aed "
L93: "cluster.go:125: namespace/tigera-operator created"
L94: "cluster.go:125: serviceaccount/tigera-operator created"
L95: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created"
L96: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created"
L97: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created"
L98: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created"
L99: "cluster.go:125: deployment.apps/tigera-operator created"
L100: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
L102: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L103: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
L104: "cluster.go:125: installation.operator.tigera.io/default created"
L105: "cluster.go:125: apiserver.operator.tigera.io/default created"
L106: "cluster.go:125: goldmane.operator.tigera.io/default created"
L107: "cluster.go:125: whisker.operator.tigera.io/default created"
L108: "kubeadm.go:197: unable to setup cluster: unable to create worker node: machine __db5ff39a-a259-4cb8-a42d-8a7205c0dc01__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.127?.89:22: i/o timeout_"
L109: " "
```
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine __c738418f-3efb-4fc3-8245-3fd7cd73ef1b__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.?34.115.246:22: i/o timeout_"
L2: " "
```
🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: stackit (1)
🟢 ok **kubeadm.v1.37.0.calico.base**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: machine __1f8d0990-4927-494a-ad59-7bbf6339dbf0__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 18?8.34.113.116:22: i/o timeout_"
L2: " "
```
🟢 ok **kubeadm.v1.37.0.cilium.base**; Succeeded: stackit (1)
🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: machine __4fa9deb3-fcdf-41a8-bd8a-1a4e782aac3d__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.?34.114.19:22: i/o timeout_"
L2: " "
```
🟢 ok **linux.nfs.v3**; Succeeded: stackit (1)
🟢 ok **linux.nfs.v4**; Succeeded: stackit (2); Failed: stackit (1)
Diagnostic output for stackit, run 1
```
L1: " Error: _nfs.go:77: Cluster.NewMachine: machine __b76a8675-109b-4e0b-b545-98787cb08464__ failed to start: ssh journalctl failed: time limit exceeded: dial tcp 188.34.112.131:22: i/o timeout_"
L2: " "
```