{"tests":[{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":60539881698,"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":"coreos.ignition.resource.local","result":"FAIL","duration":63612582196,"output":"        harness.go:651: 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.v1.noop","result":"FAIL","duration":68972022072,"output":"        harness.go:651: 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":"kubeadm.v1.37.0.cilium.base","result":"FAIL","duration":75615854505,"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.35.1.calico.base","result":"FAIL","duration":80630268829,"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.35.1.cilium.base","result":"FAIL","duration":90711122937,"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.internet","result":"FAIL","duration":113599540849,"output":"        harness.go:651: 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":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":126482559366,"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.37.0.flannel.base","result":"FAIL","duration":130800502206,"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":"PASS","duration":220164104016,"output":""},{"name":"cl.ignition.misc.empty","result":"PASS","duration":224632392410,"output":""},{"name":"cl.flannel.vxlan","result":"FAIL","duration":293344650200,"output":"        harness.go:651: Cluster failed starting machines: machine \"373edc8f-09c9-4976-a856-65e2ca11e65c\" 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":"coreos.ignition.once","result":"PASS","duration":294084826377,"output":""},{"name":"linux.nfs.v4","result":"PASS","duration":430276721810,"output":"        nfs.go:80: NFS server booted.\n        nfs.go:85: Test file \"/tmp/tmp.qhRL217o0z\" created on server.\n        nfs.go:125: NFS client booted.\n        nfs.go:133: Got NFS mount.\n"},{"name":"linux.nfs.v3","result":"PASS","duration":430884935112,"output":"        nfs.go:80: NFS server booted.\n        nfs.go:85: Test file \"/tmp/tmp.SbnLx0BeZ4\" created on server.\n        nfs.go:125: NFS client booted.\n        nfs.go:133: Got NFS mount.\n"},{"name":"kubeadm.v1.37.0.calico.base/node_readiness","result":"PASS","duration":22322295256,"output":""},{"name":"kubeadm.v1.37.0.calico.base/nginx_deployment","result":"PASS","duration":11735954660,"output":""},{"name":"kubeadm.v1.37.0.calico.base/NFS_deployment","result":"PASS","duration":30325613768,"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":"kubeadm.v1.37.0.calico.base","result":"PASS","duration":813607790739,"output":"        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.0\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.0\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.0\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.0\n        cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\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.7.0-0\n        cluster.go:125: [init] Using Kubernetes version: v1.37.0\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4790-0-0-n-2e754677dd\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4790-0-0-n-2e754677dd\": lookup ci-4790-0-0-n-2e754677dd 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-4790-0-0-n-2e754677dd kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.4.61]\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 822.24µs\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.4.61: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-scheduler is healthy after 12.608079ms\n        cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 16.827679ms\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.505339237s\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-4790-0-0-n-2e754677dd 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-4790-0-0-n-2e754677dd as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: o2mq3p.u1itn7o0wjhxb2go\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.4.61:6443 --token o2mq3p.u1itn7o0wjhxb2go \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f8a2874944360d97102f6ef263e0c54669347443585ae03b8d92f8b635ebe15e \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: W0909 00:09:07.515460    2034 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.37.0.calico.base/node_readiness (22.32s)\n    --- PASS: kubeadm.v1.37.0.calico.base/nginx_deployment (11.74s)\n    --- PASS: kubeadm.v1.37.0.calico.base/NFS_deployment (30.33s)\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":"4790.0.0"}