{"tests":[{"name":"linux.nfs.v3","result":"FAIL","duration":66236576496,"output":"        nfs.go:77: Cluster.NewMachine: 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":71534199522,"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.sethostname","result":"FAIL","duration":73401035860,"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":95946008102,"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.calico.base","result":"FAIL","duration":40180530000,"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.cilium.base","result":"FAIL","duration":116665207854,"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.flannel.vxlan","result":"FAIL","duration":120171842461,"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.internet","result":"FAIL","duration":37891321473,"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.35.1.cilium.base","result":"FAIL","duration":40480783345,"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.once","result":"FAIL","duration":23700500644,"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.misc.empty","result":"FAIL","duration":44192420792,"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":"coreos.ignition.resource.remote","result":"FAIL","duration":93481257540,"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.v2.noop","result":"FAIL","duration":103905712340,"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":179252868311,"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":"linux.nfs.v4","result":"FAIL","duration":35191862454,"output":"        nfs.go:77: Cluster.NewMachine: error creating IP address: 409 Conflict, status code 409, Body: {\"code\":409,\"msg\":\"conflict: Quota exceeded for resources: ['floatingip'].\"}\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":24143564094,"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":"coreos.ignition.ssh.key","result":"PASS","duration":215891784261,"output":""},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":219370802985,"output":""},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":60382891702,"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.basic/Script","result":"PASS","duration":639700883,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":298087449,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":361535125,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":312501477,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":354945215,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":306347462,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":408258015,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":431707721,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":316851250,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":320807464,"output":""},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":95546175750,"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.basic/Useradd","result":"PASS","duration":527449272,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":336078372,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":977756800,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":253852222499,"output":"        cluster.go:152: + cat /proc/cmdline\n"},{"name":"cl.install.cloudinit","result":"PASS","duration":254574578383,"output":""},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":258730394019,"output":"        resource.go:333: starting client: 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":258921726419,"output":"        kubeadm.go:197: unable to setup cluster: unable to create master node: error creating IP address: 409 Conflict, status code 409, Body: {\"code\":409,\"msg\":\"conflict: Quota exceeded for resources: ['floatingip'].\"}\n"},{"name":"cl.basic","result":"PASS","duration":261152695445,"output":"    --- PASS: cl.basic/Script (0.64s)\n    --- PASS: cl.basic/Symlink (0.30s)\n    --- PASS: cl.basic/ServicesActive (0.36s)\n    --- PASS: cl.basic/ReadOnly (0.31s)\n    --- PASS: cl.basic/RandomUUID (0.35s)\n    --- PASS: cl.basic/MachineID (0.31s)\n    --- PASS: cl.basic/PortSSH (0.41s)\n    --- PASS: cl.basic/DbusPerms (0.43s)\n    --- PASS: cl.basic/SymlinkFlatcar (0.32s)\n    --- PASS: cl.basic/UpdateEngineKeys (0.32s)\n    --- PASS: cl.basic/Useradd (0.53s)\n    --- PASS: cl.basic/Microcode (0.34s)\n    --- PASS: cl.basic/CloudConfig (0.98s)\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":276524187750,"output":""},{"name":"cl.cloudinit.basic","result":"PASS","duration":290742766601,"output":""},{"name":"coreos.ignition.security.tls","result":"PASS","duration":538415548893,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":11237534657,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":22559063300,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":13607312946,"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.36.1.flannel.base","result":"PASS","duration":822359058786,"output":"        cluster.go:125: I0908 23:43:14.184739    2163 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.4\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.4\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.4\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.4\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: I0908 23:43:24.128377    2397 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n        cluster.go:125: [init] Using Kubernetes version: v1.36.4\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4790-0-0-n-53900f10da\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4790-0-0-n-53900f10da\": lookup ci-4790-0-0-n-53900f10da 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-53900f10da kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.4.227]\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 2.145683ms\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.227: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 12.300297ms\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 21.306391ms\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.502393692s\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-53900f10da 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-53900f10da as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: kcgq18.2z39g5r2a3q1t6ca\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.227:6443 --token kcgq18.2z39g5r2a3q1t6ca \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:e0744a1794bbe43e79d3b961c32b8b5e61943f7ef33d24c87ee737dced5f2691 \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: W0908 23:47:38.108175    2001 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: W0908 23:47:38.471843    2001 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.flannel.base/node_readiness (11.24s)\n    --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (22.56s)\n    --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (13.61s)\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.36.1.cilium.base/node_readiness","result":"PASS","duration":22374787372,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/nginx_deployment","result":"PASS","duration":11899599225,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/NFS_deployment","result":"PASS","duration":19335698158,"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.36.1.cilium.base/IPSec_encryption","result":"PASS","duration":22819372702,"output":"        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"PASS","duration":778305090629,"output":"        cluster.go:125: I0908 23:45:55.915716    2282 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.4\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.4\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.4\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.4\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: I0908 23:46:05.552028    2514 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n        cluster.go:125: [init] Using Kubernetes version: v1.36.4\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4790-0-0-n-a7f2b2388d\" could not be reached\n        cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4790-0-0-n-a7f2b2388d\": lookup ci-4790-0-0-n-a7f2b2388d 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-a7f2b2388d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.6.198]\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 719.519µ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.6.198: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 13.568941ms\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 18.857334ms\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.502529287s\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-a7f2b2388d 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-a7f2b2388d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: blhex4.yqwnycilirl8dsag\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.6.198:6443 --token blhex4.yqwnycilirl8dsag \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:bf27340f21b572fe5fde15480f4e8d8a1a7fbecb1f89c3f48bb0cf783c88a9d5 \n        cluster.go:125: i  Using Cilium version 1.12.5\n        cluster.go:125: ? Auto-detected cluster name: kubernetes\n        cluster.go:125: ? Auto-detected datapath mode: tunnel\n        cluster.go:125: ? Auto-detected kube-proxy has been installed\n        cluster.go:125: i  helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n        cluster.go:125: i  Storing helm values file in kube-system/cilium-cli-helm-values Secret\n        cluster.go:125: ? Created CA in secret cilium-ca\n        cluster.go:125: ? Generating certificates for Hubble...\n        cluster.go:125: ? Creating Service accounts...\n        cluster.go:125: ? Creating Cluster roles...\n        cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n        cluster.go:125: i  Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n        cluster.go:125: i  Manual overwrite in ConfigMap: enable-endpoint-routes=true\n        cluster.go:125: ? Creating Agent DaemonSet...\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n        cluster.go:125: ? Creating Operator Deployment...\n        cluster.go:125: ? Waiting for Cilium to be installed and ready...\n        cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n        cluster.go:125: \u001b[33m    /??\\\n        cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m    Cilium:         \u001b[32mOK\u001b[0m\n        cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m    Operator:       \u001b[32mOK\u001b[0m\n        cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m    Hubble:         \u001b[36mdisabled\u001b[0m\n        cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m    ClusterMesh:    \u001b[36mdisabled\u001b[0m\n        cluster.go:125: \u001b[34m    \\__/\n        cluster.go:125: \u001b[0m\n        cluster.go:125: Deployment       cilium-operator    \n        cluster.go:125: DaemonSet        cilium             \n        cluster.go:125: Containers:      cilium             \n        cluster.go:125:                  cilium-operator    \n        cluster.go:125: Cluster Pods:    0/0 managed by Cilium\n        cluster.go:125: W0908 23:49:08.210522    1989 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: W0908 23:49:08.590051    1989 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.cilium.base/node_readiness (22.37s)\n    --- PASS: kubeadm.v1.36.1.cilium.base/nginx_deployment (11.90s)\n    --- PASS: kubeadm.v1.36.1.cilium.base/NFS_deployment (19.34s)\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    --- PASS: kubeadm.v1.36.1.cilium.base/IPSec_encryption (22.82s)\n            cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n            cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n            cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n            cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"}],"result":"FAIL","platform":"stackit","version":"4790.0.0"}