{"tests":[{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":39434648458,"output":""},{"name":"cl.network.listeners","result":"PASS","duration":39357485658,"output":""},{"name":"cl.flannel.vxlan","result":"PASS","duration":99379086377,"output":" flannel.go:121: ping from 52fae722-fcd3-4841-9fc5-53e46d54fba8(10.254.76.0) to 2ad5986b-e8bd-4bdd-b6f2-c371714249a5(10.254.90.0)\n"},{"name":"docker.lib-coreos-dockerd-compat/docker-info","result":"PASS","duration":4346733957,"output":""},{"name":"docker.lib-coreos-dockerd-compat/resources","result":"PASS","duration":13351724849,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.20MB 0.2s done\n cluster.go:125: #3 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:1bae92328514311738d00e448ed75cfa19281e70169dc2fcd67c0eeee3d4b1e9 done\n cluster.go:125: #5 naming to docker.io/library/sleep 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n"},{"name":"docker.network-openbsd-nc","result":"PASS","duration":39380834063,"output":" docker.go:411: creating netcat containers\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.45MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:f692f89204aa7fec44dea3cdcdb3460dd13972cf0843ff60d321d5541a39b0b5 done\n cluster.go:125: #5 naming to docker.io/library/netcat 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.45MB 0.3s done\n cluster.go:125: #3 DONE 0.3s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:f08b698e772d54ceedafcdc938e2023285a4a951bc9e50f1885c6aca79879f9f done\n cluster.go:125: #5 naming to docker.io/library/netcat 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":315134628454,"output":" cluster.go:125: E1022 23:50:47.787445 4453 memcache.go:265] \"Unhandled Error\" err=\"couldn't get current server API group list: Get \\\"https://10.0.0.8:6443/api?timeout=32s\\\": net/http: TLS handshake timeout\"\n cluster.go:125: E1022 23:51:19.815260 4453 request.go:1196] \"Unexpected error when reading response body\" err=\"net/http: request canceled (Client.Timeout or context cancellation while reading body)\"\n cluster.go:125: E1022 23:51:19.980499 4453 memcache.go:265] \"Unhandled Error\" err=\"couldn't get current server API group list: unexpected error when reading response body. Please retry. Original error: net/http: request canceled (Client.Timeout or context cancellation while reading body)\"\n cluster.go:125: E1022 23:51:52.133090 4453 memcache.go:265] \"Unhandled Error\" err=\"couldn't get current server API group list: Get \\\"https://10.0.0.8:6443/api?timeout=32s\\\": context deadline exceeded\"\n cluster.go:125: error: the server doesn't have a resource type \"nodes\"\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n"},{"name":"docker.lib-coreos-dockerd-compat/networks-reliably","result":"PASS","duration":700091317158,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.04MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:55c3eb39dee449711784f44b9829e647bebc6bcbe316f0c83076289d4e18afca done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/user-no-caps","result":"PASS","duration":72821306188,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile:\n cluster.go:125: #1 transferring dockerfile: 108B 0.5s done\n cluster.go:125: #1 DONE 0.8s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B 0.1s done\n cluster.go:125: #2 DONE 0.4s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.06MB 2.3s done\n cluster.go:125: #3 DONE 3.0s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.7s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 1.2s done\n cluster.go:125: #5 writing image sha256:5a6202f41954a809853a66d1be8eb668eef4a277f2ae20e9719210917da12545 0.1s done\n cluster.go:125: #5 naming to docker.io/library/captest\n cluster.go:125: #5 naming to docker.io/library/captest 0.2s done\n cluster.go:125: #5 DONE 1.8s\n"},{"name":"kubeadm.v1.35.1.cilium.cgroupv1.base","result":"FAIL","duration":898473575651,"output":" cluster.go:125: I1022 23:49:00.708802 2020 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\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: I1022 23:52:52.204547 2486 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: [preflight] The system verification failed. Printing the output from the verification:\n cluster.go:125: \u001b[0;37mKERNEL_VERSION\u001b[0m: \u001b[0;32m6.6.159-flatcar\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NAMESPACES\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NET_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_PID_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_IPC_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_UTS_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CPUSETS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_MEMCG\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_INET\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_EXT4_FS\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_PROC_FS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NETFILTER_XT_TARGET_REDIRECT\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NETFILTER_XT_MATCH_COMMENT\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_FAIR_GROUP_SCHED\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUPS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_CPUACCT\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_DEVICE\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_FREEZER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_PIDS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_SCHED\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_OVERLAY_FS\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_AUFS_FS\u001b[0m: \u001b[0;33mnot set - Required for aufs.\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_BLK_DEV_DM\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CFS_BANDWIDTH\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_SECCOMP\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_SECCOMP_FILTER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mOS\u001b[0m: \u001b[0;32mLinux\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPU\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPUACCT\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPUSET\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_DEVICES\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_FREEZER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_MEMORY\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_PIDS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_HUGETLB\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_BLKIO\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is deprecated and will be removed in a future release. Please migrate to cgroups v2. To explicitly enable cgroups v1 support for kubelet v1.35 or newer, you must set the kubelet configuration option 'FailCgroupV1' to 'false'. You must also explicitly skip this validation. For more information, see https://git.k8s.io/enhancements/keps/sig-node/5573-remove-cgroup-v1\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: W1022 23:52:53.911953 2486 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.14]\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 1.232094615s\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.14: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 4.113883564s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 10.284081772s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 21.614777411s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: mnflxh.13u3h4hs5z41j1tw\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.14:6443 --token mnflxh.13u3h4hs5z41j1tw \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:bb5ab6594f2bc51593640a57ea0aa8711b2bcabf63a4bf206176f899117f2d57 \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: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[31m1 errors\u001b[0m, \u001b[33m1 warnings\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: DaemonSet cilium Desired: 1, Unavailable: \u001b[31m1/1\u001b[0m\n cluster.go:125: Deployment cilium-operator Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: Containers: cilium Pending: \u001b[32m1\u001b[0m\n cluster.go:125: cilium-operator Running: \u001b[32m1\u001b[0m\n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: Image versions cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\n cluster.go:125: cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1\n cluster.go:125: Errors: cilium cilium 1 pods of DaemonSet cilium are not ready\n cluster.go:125: Warnings: cilium cilium-bxj5n pod is pending\n cluster.go:125: ? Rolling back installation...\n cluster.go:125: \n cluster.go:125: Error: Unable to install Cilium: timeout while waiting for status to become successful: context deadline exceeded\n kubeadm.go:197: unable to setup cluster: unable to run master script: Process exited with status 1\n"},{"name":"docker.lib-coreos-dockerd-compat/ownership","result":"PASS","duration":165720566685,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 304074f06047: Pulling fs layer\n cluster.go:125: dbc0d6a7f6cc: Pulling fs layer\n cluster.go:125: 9f58674a3b11: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Pulling fs layer\n cluster.go:125: ecbed8e15a4c: Pulling fs layer\n cluster.go:125: 8d826465457f: Pulling fs layer\n cluster.go:125: 761e07649c97: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Waiting\n cluster.go:125: ecbed8e15a4c: Waiting\n cluster.go:125: 8d826465457f: Waiting\n cluster.go:125: 761e07649c97: Waiting\n cluster.go:125: 9f58674a3b11: Verifying Checksum\n cluster.go:125: 9f58674a3b11: Download complete\n cluster.go:125: 6f3c77a91d70: Verifying Checksum\n cluster.go:125: 6f3c77a91d70: Download complete\n cluster.go:125: ecbed8e15a4c: Verifying Checksum\n cluster.go:125: ecbed8e15a4c: Download complete\n cluster.go:125: 8d826465457f: Verifying Checksum\n cluster.go:125: 8d826465457f: Download complete\n cluster.go:125: 304074f06047: Verifying Checksum\n cluster.go:125: 304074f06047: Download complete\n cluster.go:125: 761e07649c97: Verifying Checksum\n cluster.go:125: 761e07649c97: Download complete\n cluster.go:125: dbc0d6a7f6cc: Verifying Checksum\n cluster.go:125: dbc0d6a7f6cc: Download complete\n cluster.go:125: 304074f06047: Pull complete\n cluster.go:125: dbc0d6a7f6cc: Pull complete\n cluster.go:125: 9f58674a3b11: Pull complete\n cluster.go:125: 6f3c77a91d70: Pull complete\n cluster.go:125: ecbed8e15a4c: Pull complete\n cluster.go:125: 8d826465457f: Pull complete\n cluster.go:125: 761e07649c97: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"PASS","duration":984529082681,"output":" --- PASS: docker.lib-coreos-dockerd-compat/docker-info (4.35s)\n --- PASS: docker.lib-coreos-dockerd-compat/resources (13.35s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.20MB 0.2s done\n cluster.go:125: #3 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:1bae92328514311738d00e448ed75cfa19281e70169dc2fcd67c0eeee3d4b1e9 done\n cluster.go:125: #5 naming to docker.io/library/sleep 0.0s done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n --- PASS: docker.lib-coreos-dockerd-compat/networks-reliably (700.09s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.04MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:55c3eb39dee449711784f44b9829e647bebc6bcbe316f0c83076289d4e18afca done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.lib-coreos-dockerd-compat/user-no-caps (72.82s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile:\n cluster.go:125: #1 transferring dockerfile: 108B 0.5s done\n cluster.go:125: #1 DONE 0.8s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B 0.1s done\n cluster.go:125: #2 DONE 0.4s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.06MB 2.3s done\n cluster.go:125: #3 DONE 3.0s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.7s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 1.2s done\n cluster.go:125: #5 writing image sha256:5a6202f41954a809853a66d1be8eb668eef4a277f2ae20e9719210917da12545 0.1s done\n cluster.go:125: #5 naming to docker.io/library/captest\n cluster.go:125: #5 naming to docker.io/library/captest 0.2s done\n cluster.go:125: #5 DONE 1.8s\n --- PASS: docker.lib-coreos-dockerd-compat/ownership (165.72s)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 304074f06047: Pulling fs layer\n cluster.go:125: dbc0d6a7f6cc: Pulling fs layer\n cluster.go:125: 9f58674a3b11: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Pulling fs layer\n cluster.go:125: ecbed8e15a4c: Pulling fs layer\n cluster.go:125: 8d826465457f: Pulling fs layer\n cluster.go:125: 761e07649c97: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Waiting\n cluster.go:125: ecbed8e15a4c: Waiting\n cluster.go:125: 8d826465457f: Waiting\n cluster.go:125: 761e07649c97: Waiting\n cluster.go:125: 9f58674a3b11: Verifying Checksum\n cluster.go:125: 9f58674a3b11: Download complete\n cluster.go:125: 6f3c77a91d70: Verifying Checksum\n cluster.go:125: 6f3c77a91d70: Download complete\n cluster.go:125: ecbed8e15a4c: Verifying Checksum\n cluster.go:125: ecbed8e15a4c: Download complete\n cluster.go:125: 8d826465457f: Verifying Checksum\n cluster.go:125: 8d826465457f: Download complete\n cluster.go:125: 304074f06047: Verifying Checksum\n cluster.go:125: 304074f06047: Download complete\n cluster.go:125: 761e07649c97: Verifying Checksum\n cluster.go:125: 761e07649c97: Download complete\n cluster.go:125: dbc0d6a7f6cc: Verifying Checksum\n cluster.go:125: dbc0d6a7f6cc: Download complete\n cluster.go:125: 304074f06047: Pull complete\n cluster.go:125: dbc0d6a7f6cc: Pull complete\n cluster.go:125: 9f58674a3b11: Pull complete\n cluster.go:125: 6f3c77a91d70: Pull complete\n cluster.go:125: ecbed8e15a4c: Pull complete\n cluster.go:125: 8d826465457f: Pull complete\n cluster.go:125: 761e07649c97: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"cl.ignition.v2.users","result":"PASS","duration":31487876524,"output":""},{"name":"coreos.auth.verify","result":"PASS","duration":42674719492,"output":""},{"name":"cl.network.iptables","result":"PASS","duration":46655769642,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"cl.cloudinit.multipart-mime","result":"FAIL","duration":152428718023,"output":" harness.go:621: Found systemd unit failed to start (\u001b[0;1;39muser-configvirtfs.…\u001b[0mud-config from /media/configvirtfs.\r\r) on machine b20ca3f3-09de-4c94-9680-8e83e9cff99d console\n"},{"name":"cl.etcd-member.etcdctlv3","result":"PASS","duration":168078324770,"output":" cluster.go:125: {\"level\":\"info\",\"ts\":1792713784.6710181,\"caller\":\"snapshot/v3_snapshot.go:68\",\"msg\":\"created temporary db file\",\"path\":\"/tmp/tmp.nwBkSwjjUF/snapshot.db.part\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1792713784.6823723,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:211\",\"msg\":\"opened snapshot stream; downloading\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1792713784.682408,\"caller\":\"snapshot/v3_snapshot.go:76\",\"msg\":\"fetching snapshot\",\"endpoint\":\"127.0.0.1:2379\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1792713784.685323,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:219\",\"msg\":\"completed snapshot read; closing\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1792713784.6853774,\"caller\":\"snapshot/v3_snapshot.go:91\",\"msg\":\"fetched snapshot\",\"endpoint\":\"127.0.0.1:2379\",\"size\":\"20 kB\",\"took\":\"now\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1792713784.685444,\"caller\":\"snapshot/v3_snapshot.go:100\",\"msg\":\"saved\",\"path\":\"/tmp/tmp.nwBkSwjjUF/snapshot.db\"}\n cluster.go:125: Deprecated: Use `etcdutl snapshot status` instead.\n"},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":134523736873,"output":""},{"name":"cl.flannel.udp","result":"PASS","duration":537509606448,"output":" cluster.go:125: Timeout occurred while waiting for network connectivity.\n flannel.go:121: ping from 1577de19-8fbf-432c-b957-981e047ebaca(10.254.77.0) to 9a9deb22-9b4b-4b3c-a2fd-dceb2e08f447(10.254.20.1)\n"},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"FAIL","duration":1020285013933,"output":" cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Error from server (Forbidden): deployments.apps is forbidden: User \"kubernetes-admin\" cannot list resource \"deployments\" in API group \"apps\" in the namespace \"default\"\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n kubeadm.go:232: nginx is not deployed: ready replicas should be equal to 1: null\n"},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"FAIL","duration":110615684369,"output":" cluster.go:125: E1023 00:13:45.440496 9306 round_tripper.go:63] CancelRequest not implemented by *kube.RetryingRoundTripper\n cluster.go:125: E1023 00:14:18.062784 9306 round_tripper.go:63] CancelRequest not implemented by *kube.RetryingRoundTripper\n cluster.go:125: Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating \"\": error validating data: failed to download openapi: Get \"https://10.0.0.8:6443/openapi/v2?timeout=32s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)\n kubeadm.go:242: unable to install NFS Helm Chart: Process exited with status 1\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":1948501377817,"output":" cluster.go:125: I1022 23:43:23.920025 1764 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\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: I1022 23:43:47.467683 1996 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1022 23:43:49.175413 1996 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.8]\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 1.002942448s\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.8: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 4.120066937s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 7.572130412s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 15.004217904s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: gs9czc.3xmcb5l2xwnymlwm\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.8:6443 --token gs9czc.3xmcb5l2xwnymlwm \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:fb787ca665a9f64ebf95caf5e50ebea654afed7839aeb28f5d8e59fa9a90a585 \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: W1022 23:46:17.455956 1629 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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 (315.13s)\n cluster.go:125: E1022 23:50:47.787445 4453 memcache.go:265] \"Unhandled Error\" err=\"couldn't get current server API group list: Get \\\"https://10.0.0.8:6443/api?timeout=32s\\\": net/http: TLS handshake timeout\"\n cluster.go:125: E1022 23:51:19.815260 4453 request.go:1196] \"Unexpected error when reading response body\" err=\"net/http: request canceled (Client.Timeout or context cancellation while reading body)\"\n cluster.go:125: E1022 23:51:19.980499 4453 memcache.go:265] \"Unhandled Error\" err=\"couldn't get current server API group list: unexpected error when reading response body. Please retry. Original error: net/http: request canceled (Client.Timeout or context cancellation while reading body)\"\n cluster.go:125: E1022 23:51:52.133090 4453 memcache.go:265] \"Unhandled Error\" err=\"couldn't get current server API group list: Get \\\"https://10.0.0.8:6443/api?timeout=32s\\\": context deadline exceeded\"\n cluster.go:125: error: the server doesn't have a resource type \"nodes\"\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n --- FAIL: kubeadm.v1.35.1.flannel.base/nginx_deployment (1020.29s)\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Error from server (Forbidden): deployments.apps is forbidden: User \"kubernetes-admin\" cannot list resource \"deployments\" in API group \"apps\" in the namespace \"default\"\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.8:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n kubeadm.go:232: nginx is not deployed: ready replicas should be equal to 1: null\n --- FAIL: kubeadm.v1.35.1.flannel.base/NFS_deployment (110.62s)\n cluster.go:125: E1023 00:13:45.440496 9306 round_tripper.go:63] CancelRequest not implemented by *kube.RetryingRoundTripper\n cluster.go:125: E1023 00:14:18.062784 9306 round_tripper.go:63] CancelRequest not implemented by *kube.RetryingRoundTripper\n cluster.go:125: Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating \"\": error validating data: failed to download openapi: Get \"https://10.0.0.8:6443/openapi/v2?timeout=32s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)\n kubeadm.go:242: unable to install NFS Helm Chart: Process exited with status 1\n"},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":161344285375,"output":""},{"name":"cl.ignition.oem.wipe","result":"PASS","duration":27840323129,"output":""},{"name":"cl.users.shells","result":"PASS","duration":51962908408,"output":""},{"name":"cl.tpm.root-cryptenroll-pcr-withupdate","result":"PASS","duration":640721940029,"output":" cluster.go:125: New TPM2 token enrolled as key slot 1.\n cluster.go:125: Wiped slot 2.\n"},{"name":"cl.tpm.nonroot","result":"PASS","duration":281773261370,"output":""},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":459501473072,"output":" harness.go:651: Cluster failed starting machines: machine \"8837d88d-8434-4711-b550-efa349cc480d\" failed basic checks: some systemd units failed:\n● systemd-hwdb-update.service loaded failed failed Rebuild Hardware Database\nstatus: \njournal:-- No entries --\n harness.go:621: Found systemd unit failed to start (\u001b[0;1;39msystemd-hwdb-updat…ervice\u001b[0m - Rebuild Hardware Database.\r\r) on machine 8837d88d-8434-4711-b550-efa349cc480d console\n harness.go:621: Found systemd dependency unit failed to start (\u001b[0;1;39msystemd-fsck…\u001b[0mem Check on /dev/disk/by-label/OEM.\r\r) on machine 8837d88d-8434-4711-b550-efa349cc480d console\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":482434576473,"output":" nfs.go:80: NFS server booted.\n nfs.go:85: Test file \"/tmp/tmp.4fMvszQvJA\" created on server.\n nfs.go:122: Cluster.NewMachine: machine \"80b8a108-7464-4b6d-b83b-5521f2937cac\" failed basic checks: some systemd units failed:\n● systemd-hwdb-update.service loaded failed failed Rebuild Hardware Database\nstatus: \njournal:-- No entries --\n harness.go:621: Found systemd unit failed to start (\u001b[0;1;39msystemd-hwdb-updat…ervice\u001b[0m - Rebuild Hardware Database.\r\r) on machine 80b8a108-7464-4b6d-b83b-5521f2937cac console\n harness.go:621: Found systemd dependency unit failed to start (\u001b[0;1;39msystemd-fsck…\u001b[0mem Check on /dev/disk/by-label/OEM.\r\r) on machine 80b8a108-7464-4b6d-b83b-5521f2937cac console\n"},{"name":"cl.sysext.boot","result":"PASS","duration":717112600984,"output":" cluster.go:125: + sudo systemctl mask --now ensure-sysext\n cluster.go:125: Created symlink /etc/systemd/system/ensure-sysext.service → /dev/null.\n cluster.go:125: + sudo systemctl mask --now systemd-sysext\n cluster.go:125: Created symlink /etc/systemd/system/systemd-sysext.service → /dev/null.\n cluster.go:125: + sudo mkdir -p /etc/flatcar/sysext /etc/flatcar/oem-sysext /oem/sysext /etc/extensions\n cluster.go:125: + sudo tee /oem/oem-release\n cluster.go:125: + echo ID=test\n cluster.go:125: + echo myext\n cluster.go:125: + sudo tee /etc/flatcar/enabled-sysext.conf\n cluster.go:125: + sudo touch /oem/sysext/active-oem-test /etc/flatcar/oem-sysext/oem-test-4081.3.10+nightly-20261022-2100.raw /etc/flatcar/oem-sysext/oem-test-1.2.3.raw /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw /etc/flatcar/sysext/flatcar-myext-1.2.3.raw\n cluster.go:125: + sudo ln -fs /etc/flatcar/oem-sysext/oem-test-1.2.3.raw /etc/extensions/oem-test.raw\n cluster.go:125: + sudo ln -fs /etc/flatcar/sysext/flatcar-myext-1.2.3.raw /etc/extensions/flatcar-myext.raw\n cluster.go:125: ++ readlink -f /etc/extensions/oem-test.raw\n cluster.go:125: + '[' /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw = /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw ']'\n cluster.go:125: ++ readlink -f /etc/extensions/flatcar-myext.raw\n cluster.go:125: + '[' /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw = /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw ']'\n cluster.go:125: + sudo mv /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw /etc/flatcar/oem-sysext/\n cluster.go:125: + sudo mv /etc/flatcar/oem-sysext/oem-test-1.2.3.raw /oem/sysext/\n cluster.go:125: + sudo ln -fs /oem/sysext/oem-test-1.2.3.raw /etc/extensions/oem-test.raw\n cluster.go:125: + sudo ln -fs /etc/flatcar/sysext/flatcar-myext-1.2.3.raw /etc/extensions/flatcar-myext.raw\n cluster.go:125: ++ readlink -f /etc/extensions/oem-test.raw\n cluster.go:125: + '[' /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw = /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw ']'\n cluster.go:125: ++ readlink -f /etc/extensions/flatcar-myext.raw\n cluster.go:125: + '[' /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw = /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw ']'\n cluster.go:125: + '[' -e /etc/flatcar/oem-sysext/oem-test-1.2.3.raw ']'\n cluster.go:125: ++ readlink -f /etc/extensions/oem-test.raw\n cluster.go:125: + '[' /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw = /oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw ']'\n cluster.go:125: ++ readlink -f /etc/extensions/flatcar-myext.raw\n cluster.go:125: + '[' /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw = /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20261022-2100.raw ']'\n"},{"name":"cl.ignition.oem.regular.new","result":"FAIL","duration":234964339749,"output":" harness.go:621: Found systemd unit failed to start (\u001b[0;1;39mldconfig.service\u001b[0m - Rebuild Dynamic Linker Cache.\r\r) on machine 98d2b990-b464-4f15-816f-02793311e334 console\n"},{"name":"cl.network.initramfs.second-boot","result":"FAIL","duration":564720825717,"output":" harness.go:621: Found systemd unit failed to start (\u001b[0;1;39mldconfig.service\u001b[0m - Rebuild Dynamic Linker Cache.\r\r) on machine cd898be9-fb5b-468e-ae1f-a4ab27586d74 console\n"},{"name":"docker.userns","result":"PASS","duration":277579750074,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B 0.1s done\n cluster.go:125: #1 DONE 0.6s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\n cluster.go:125: #2 transferring context: 2B 0.1s done\n cluster.go:125: #2 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.24MB 0.4s done\n cluster.go:125: #3 DONE 0.6s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.3s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.5s done\n cluster.go:125: #5 writing image sha256:a6c750108784458c373ff7071b829d50404091612d2c1bf0dbad5c48ff62e4a5 0.0s done\n cluster.go:125: #5 naming to docker.io/library/userns-test\n cluster.go:125: #5 naming to docker.io/library/userns-test 0.1s done\n cluster.go:125: #5 DONE 0.9s\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":710283695469,"output":" resource.go:333: starting client: machine \"69a5c042-e3dd-42db-9197-0e6d45bc5ab7\" failed basic checks: some systemd units failed:\n● systemd-hwdb-update.service loaded failed failed Rebuild Hardware Database\nstatus: \njournal:-- No entries --\n harness.go:621: Found systemd unit failed to start (\u001b[0;1;39msystemd-hwdb-updat…ervice\u001b[0m - Rebuild Hardware Database.\r\r) on machine 69a5c042-e3dd-42db-9197-0e6d45bc5ab7 console\n harness.go:621: Found systemd dependency unit failed to start (\u001b[0;1;39msystemd-fsck…\u001b[0mem Check on /dev/disk/by-label/OEM.\r\r) on machine 69a5c042-e3dd-42db-9197-0e6d45bc5ab7 console\n"},{"name":"cl.cgroupv1/CgroupMounts","result":"PASS","duration":2613009167,"output":""},{"name":"cl.cgroupv1","result":"PASS","duration":57699049588,"output":" --- PASS: cl.cgroupv1/CgroupMounts (2.61s)\n"},{"name":"cl.ignition.v2_1.vfat","result":"PASS","duration":70948093224,"output":""},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":2227789381841,"output":" cluster.go:125: I1023 00:20:27.365700 1887 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\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: W1023 00:24:37.299975 2301 version.go:108] could not fetch a Kubernetes version from the internet: unable to get URL \"https://dl.k8s.io/release/stable-1.txt\": Get \"https://dl.k8s.io/release/stable-1.txt\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n cluster.go:125: W1023 00:24:37.309922 2301 version.go:109] falling back to the local client version: v1.35.1\n cluster.go:125: [init] Using Kubernetes version: v1.35.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 00:25:07.985840 2301 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.30]\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 18.700624276s\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.30: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 2m50.081354122s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 6m36.107190726s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 15m4.542239955s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 258oqx.7u15a8eonuxhnm06\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.30:6443 --token 258oqx.7u15a8eonuxhnm06 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:c5374ab550ffa5ffd269558d16307655d9bd6ad1d7b56566e91ecc673ac70239 \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: error: timed out waiting for the condition\n kubeadm.go:197: unable to setup cluster: unable to run master script: Process exited with status 1\n"},{"name":"coreos.locksmith.reboot","result":"PASS","duration":468742162311,"output":""},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":398618662828,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\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.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E1023 00:52:25.264459 2083 remote_runtime.go:1359] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.38. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 00:52:26.003165 2083 checks.go:920] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.47]\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 62.179364ms\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.47: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 213.54789ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 396.545291ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1m2.217353159s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 3vez0q.uzvmhzb4j1v6m1tn\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.0.47:6443 --token 3vez0q.uzvmhzb4j1v6m1tn \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:4a00e7b6b10bd49bd708d26beba17e966c23ace6e2f0340e66e63330fe81e673 \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: error: timed out waiting for the condition\n kubeadm.go:197: unable to setup cluster: unable to run master script: Process exited with status 1\n"},{"name":"cl.ignition.v1.sethostname","result":"PASS","duration":27921505674,"output":""},{"name":"coreos.ignition.resource.s3.versioned","result":"PASS","duration":67164786950,"output":""},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":110106421355,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":78023730215,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":545575790377,"output":" cluster.go:125: I1023 00:54:50.303110 1847 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\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: I1023 00:57:21.674152 2250 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E1023 00:57:22.388848 2250 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 00:57:23.696663 2250 checks.go:907] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.49]\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 1.880854505s\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.49: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 653.612135ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 721.14256ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 54.634425675s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: mz59yf.xk3mztnv0dyaur11\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.0.49:6443 --token mz59yf.xk3mztnv0dyaur11 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:d891eec7d670282f41c456ce73c9f30a442bc55360e6f1a8ab1d725d20cd9a8a \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: error: timed out waiting for the condition\n kubeadm.go:197: unable to setup cluster: unable to run master script: Process exited with status 1\n"},{"name":"cl.tpm.root-cryptenroll","result":"PASS","duration":124863989715,"output":""},{"name":"cl.tpm.root-cryptenroll-pcr-noupdate","result":"PASS","duration":175699607055,"output":""},{"name":"docker.base/docker-info","result":"PASS","duration":9255782516,"output":""},{"name":"docker.base/resources","result":"PASS","duration":13520081507,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.20MB 0.1s done\n cluster.go:125: #3 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 writing image sha256:0d7ec52fa63b4eb103049f713e624785e8ea41cc2226866c409f25a2450ce995 0.0s done\n cluster.go:125: #5 naming to docker.io/library/sleep\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.2s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n"},{"name":"cl.disk.raid0.data","result":"PASS","duration":91401801818,"output":""},{"name":"docker.base/networks-reliably","result":"PASS","duration":697609062515,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile:\n cluster.go:125: #1 transferring dockerfile: 108B 0.1s done\n cluster.go:125: #1 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B 0.0s done\n cluster.go:125: #2 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.04MB 0.2s done\n cluster.go:125: #3 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:11c7f8d5ae7aa4ad7c666a3bf657d337b83f6ca9818b528555d5f75fae045d6e done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.base/user-no-caps","result":"PASS","duration":24662879953,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile:\n cluster.go:125: #1 transferring dockerfile: 108B 0.1s done\n cluster.go:125: #1 DONE 0.4s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B 0.0s done\n cluster.go:125: #2 DONE 0.3s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.06MB 0.7s done\n cluster.go:125: #3 DONE 0.9s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.3s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.5s done\n cluster.go:125: #5 writing image sha256:6f34ceb459635525056560601552e8ef7621f35667f233a38599c56ec797f78f done\n cluster.go:125: #5 naming to docker.io/library/captest 0.1s done\n cluster.go:125: #5 DONE 0.9s\n"},{"name":"docker.base/ownership","result":"PASS","duration":154501758310,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 304074f06047: Pulling fs layer\n cluster.go:125: dbc0d6a7f6cc: Pulling fs layer\n cluster.go:125: 9f58674a3b11: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Pulling fs layer\n cluster.go:125: ecbed8e15a4c: Pulling fs layer\n cluster.go:125: 8d826465457f: Pulling fs layer\n cluster.go:125: 761e07649c97: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Waiting\n cluster.go:125: ecbed8e15a4c: Waiting\n cluster.go:125: 8d826465457f: Waiting\n cluster.go:125: 761e07649c97: Waiting\n cluster.go:125: 9f58674a3b11: Verifying Checksum\n cluster.go:125: 9f58674a3b11: Download complete\n cluster.go:125: 6f3c77a91d70: Verifying Checksum\n cluster.go:125: 6f3c77a91d70: Download complete\n cluster.go:125: ecbed8e15a4c: Verifying Checksum\n cluster.go:125: ecbed8e15a4c: Download complete\n cluster.go:125: 304074f06047: Verifying Checksum\n cluster.go:125: 304074f06047: Download complete\n cluster.go:125: dbc0d6a7f6cc: Verifying Checksum\n cluster.go:125: dbc0d6a7f6cc: Download complete\n cluster.go:125: 761e07649c97: Verifying Checksum\n cluster.go:125: 761e07649c97: Download complete\n cluster.go:125: 8d826465457f: Verifying Checksum\n cluster.go:125: 8d826465457f: Download complete\n cluster.go:125: 304074f06047: Pull complete\n cluster.go:125: dbc0d6a7f6cc: Pull complete\n cluster.go:125: 9f58674a3b11: Pull complete\n cluster.go:125: 6f3c77a91d70: Pull complete\n cluster.go:125: ecbed8e15a4c: Pull complete\n cluster.go:125: 8d826465457f: Pull complete\n cluster.go:125: 761e07649c97: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.base","result":"PASS","duration":940152276596,"output":" --- PASS: docker.base/docker-info (9.26s)\n --- PASS: docker.base/resources (13.52s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B 0.0s done\n cluster.go:125: #1 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 2.20MB 0.1s done\n cluster.go:125: #3 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.2s done\n cluster.go:125: #5 writing image sha256:0d7ec52fa63b4eb103049f713e624785e8ea41cc2226866c409f25a2450ce995 0.0s done\n cluster.go:125: #5 naming to docker.io/library/sleep\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.2s\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n --- PASS: docker.base/networks-reliably (697.61s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile:\n cluster.go:125: #1 transferring dockerfile: 108B 0.1s done\n cluster.go:125: #1 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B 0.0s done\n cluster.go:125: #2 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 4.04MB 0.2s done\n cluster.go:125: #3 DONE 0.2s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:11c7f8d5ae7aa4ad7c666a3bf657d337b83f6ca9818b528555d5f75fae045d6e done\n cluster.go:125: #5 naming to docker.io/library/ping done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.base/user-no-caps (24.66s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile:\n cluster.go:125: #1 transferring dockerfile: 108B 0.1s done\n cluster.go:125: #1 DONE 0.4s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B 0.0s done\n cluster.go:125: #2 DONE 0.3s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 5.06MB 0.7s done\n cluster.go:125: #3 DONE 0.9s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.3s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers\n cluster.go:125: #5 exporting layers 0.5s done\n cluster.go:125: #5 writing image sha256:6f34ceb459635525056560601552e8ef7621f35667f233a38599c56ec797f78f done\n cluster.go:125: #5 naming to docker.io/library/captest 0.1s done\n cluster.go:125: #5 DONE 0.9s\n --- PASS: docker.base/ownership (154.50s)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: 304074f06047: Pulling fs layer\n cluster.go:125: dbc0d6a7f6cc: Pulling fs layer\n cluster.go:125: 9f58674a3b11: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Pulling fs layer\n cluster.go:125: ecbed8e15a4c: Pulling fs layer\n cluster.go:125: 8d826465457f: Pulling fs layer\n cluster.go:125: 761e07649c97: Pulling fs layer\n cluster.go:125: 6f3c77a91d70: Waiting\n cluster.go:125: ecbed8e15a4c: Waiting\n cluster.go:125: 8d826465457f: Waiting\n cluster.go:125: 761e07649c97: Waiting\n cluster.go:125: 9f58674a3b11: Verifying Checksum\n cluster.go:125: 9f58674a3b11: Download complete\n cluster.go:125: 6f3c77a91d70: Verifying Checksum\n cluster.go:125: 6f3c77a91d70: Download complete\n cluster.go:125: ecbed8e15a4c: Verifying Checksum\n cluster.go:125: ecbed8e15a4c: Download complete\n cluster.go:125: 304074f06047: Verifying Checksum\n cluster.go:125: 304074f06047: Download complete\n cluster.go:125: dbc0d6a7f6cc: Verifying Checksum\n cluster.go:125: dbc0d6a7f6cc: Download complete\n cluster.go:125: 761e07649c97: Verifying Checksum\n cluster.go:125: 761e07649c97: Download complete\n cluster.go:125: 8d826465457f: Verifying Checksum\n cluster.go:125: 8d826465457f: Download complete\n cluster.go:125: 304074f06047: Pull complete\n cluster.go:125: dbc0d6a7f6cc: Pull complete\n cluster.go:125: 9f58674a3b11: Pull complete\n cluster.go:125: 6f3c77a91d70: Pull complete\n cluster.go:125: ecbed8e15a4c: Pull complete\n cluster.go:125: 8d826465457f: Pull complete\n cluster.go:125: 761e07649c97: Pull complete\n cluster.go:125: Digest: sha256:50dc40e9ed93d19d1cf11bdcc014f8db4f7cc6a927f22d7114bb6ddf4d19f92d\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.enable-service.sysext","result":"PASS","duration":45683078707,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"cl.disk.raid1.data","result":"PASS","duration":130388454757,"output":""},{"name":"systemd.journal.user","result":"PASS","duration":47063568225,"output":""},{"name":"coreos.locksmith.tls","result":"PASS","duration":144355928446,"output":""},{"name":"cl.ignition.v1.groups","result":"PASS","duration":69128288256,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":82825628638,"output":""},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base/node_readiness","result":"FAIL","duration":1681577344110,"output":" cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: The connection to the server 10.0.0.52:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.52:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n kubeadm.go:213: nodes are not ready: ready nodes should be equal to 2: 1\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":1544216627511,"output":" cluster.go:125: W1023 01:12:55.804638 1895 version.go:108] could not fetch a Kubernetes version from the internet: unable to get URL \"https://dl.k8s.io/release/stable-1.txt\": Get \"https://dl.k8s.io/release/stable-1.txt\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n cluster.go:125: W1023 01:12:55.815606 1895 version.go:109] falling back to the local client version: v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\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: I1023 01:23:57.553546 2437 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E1023 01:24:05.376487 2437 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 01:24:19.822304 2437 checks.go:907] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.62]\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: error: error execution phase wait-control-plane: cannot obtain client without bootstrap: could not bootstrap the admin user in file admin.conf: unable to create ClusterRoleBinding: Post \"https://10.0.0.62:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?timeout=10s\": dial tcp 10.0.0.62:6443: connect: connection refused\n cluster.go:125: To see the stack trace of this error execute with --v=5 or higher\n kubeadm.go:197: unable to setup cluster: unable to run master script: Process exited with status 1\n"},{"name":"cl.ignition.partition_on_boot_disk","result":"PASS","duration":44875919139,"output":" filesystem.go:487: lsblk -f:\nNAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS\nloop2 squashfs 4.0 \nloop3 squashfs 4.0 \nsr0 \nvda \n|-vda1 vfat FAT32 EFI-SYSTEM 3EB7-6CAA \n|-vda2 \n|-vda3 btrfs 1b5bcbcd-4944-4dd4-862d-01d1a4747bb3 \n| `-usr btrfs 1b5bcbcd-4944-4dd4-862d-01d1a4747bb3 /usr\n|-vda4 \n|-vda6 btrfs OEM d03d83a2-ea23-446b-b2cb-31c87cc915d4 123M 1% /oem\n|-vda7 \n|-vda9 ext4 1.0 ROOT bd001aeb-94b0-4611-97b5-20156d0e8933 5.9G 0% /\n`-vda10 xfs VAR 1f3cf0ca-4e73-4da0-b952-16365a9328f3 5.2G 3% /var\n filesystem.go:489: findmnt:\nTARGET SOURCE FSTYPE OPTIONS\n/ /dev/vda9 ext4 rw,relatime,seclabel\n|-/boot systemd-1 autofs rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=5282\n|-/media tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,seclabel\n|-/dev devtmpfs devtmpfs rw,nosuid,seclabel,size=4096k,nr_inodes=303979,mode=755\n| |-/dev/hugepages hugetlbfs hugetlbfs rw,nosuid,nodev,relatime,seclabel,pagesize=2M\n| |-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime,seclabel\n| |-/dev/shm tmpfs tmpfs rw,nosuid,nodev,seclabel\n| `-/dev/pts devpts devpts rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000\n|-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime,seclabel\n| |-/sys/fs/selinux selinuxfs selinuxfs rw,nosuid,noexec,relatime\n| |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime,seclabel\n| |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime,seclabel\n| |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime\n| |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate,memory_recursiveprot\n| |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime,seclabel\n| |-/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700\n| |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime\n| `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime\n|-/proc proc proc rw,nosuid,nodev,noexec,relatime\n| `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=5286\n|-/run tmpfs tmpfs rw,nosuid,nodev,seclabel,size=495316k,nr_inodes=819200,mode=755\n| `-/run/user/500 tmpfs tmpfs rw,nosuid,nodev,relatime,seclabel,size=247656k,nr_inodes=61914,mode=700,uid=500,gid=500\n|-/tmp tmpfs tmpfs rw,nosuid,nodev,seclabel,nr_inodes=1048576\n|-/var /dev/vda10 xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota\n|-/usr /dev/dm-0 btrfs ro,relatime,seclabel,rescue=nologreplay,space_cache=v2,subvolid=5,subvol=/\n| `-/usr sysext overlay ro,nodev,relatime,seclabel,lowerdir=/run/systemd/sysext/meta/usr:/run/systemd/sysext/extensions/docker-flatcar/usr:/run/systemd/sysext/extensions/containerd-flatcar/usr:/usr\n|-/etc overlay overlay rw,noatime,seclabel,lowerdir=/sysroot/usr/share/flatcar/etc,upperdir=/sysroot/etc,workdir=/sysroot/.etc-work,uuid=on,metacopy=off\n`-/oem /dev/vda6 btrfs rw,nodev,relatime,seclabel,discard=async,space_cache=v2,subvolid=5,subvol=/\n cluster.go:152: + findmnt /var\n cluster.go:152: + cat /var/hello\n"},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":269831715499,"output":""},{"name":"coreos.ignition.once","result":"PASS","duration":488085147913,"output":""},{"name":"kubeadm.v1.37.0.flannel.base","result":"FAIL","duration":570796388431,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node with large disk: machine \"47003ec4-0309-473a-8eb3-40213637c65a\" failed basic checks: some systemd units failed:\n● systemd-hwdb-update.service loaded failed failed Rebuild Hardware Database\nstatus: \njournal:-- No entries --\n harness.go:621: Found systemd unit failed to start (\u001b[0;1;39msystemd-hwdb-updat…ervice\u001b[0m - Rebuild Hardware Database.\r\r) on machine 47003ec4-0309-473a-8eb3-40213637c65a console\n harness.go:621: Found systemd dependency unit failed to start (\u001b[0;1;39msystemd-fsck…\u001b[0mem Check on /dev/disk/by-label/OEM.\r\r) on machine 47003ec4-0309-473a-8eb3-40213637c65a console\n"},{"name":"cl.cloudinit.script","result":"PASS","duration":106979483673,"output":""},{"name":"sysext.disable-containerd","result":"PASS","duration":55417159196,"output":""},{"name":"coreos.selinux.boolean","result":"PASS","duration":162524019613,"output":""},{"name":"cl.misc.falco","result":"FAIL","duration":171695926899,"output":" cluster.go:125: Unable to find image 'falcosecurity/falco-driver-loader:master' locally\n cluster.go:125: master: Pulling from falcosecurity/falco-driver-loader\n cluster.go:125: 56d14e8ac0f6: Pulling fs layer\n cluster.go:125: 9d13c9fb0067: Pulling fs layer\n cluster.go:125: fabcdb810cc4: Pulling fs layer\n cluster.go:125: 94474473290a: Pulling fs layer\n cluster.go:125: d475340682cc: Pulling fs layer\n cluster.go:125: b0cfbdbf0600: Pulling fs layer\n cluster.go:125: cdc0f9d545de: Pulling fs layer\n cluster.go:125: 410f90a307bd: Pulling fs layer\n cluster.go:125: 94474473290a: Waiting\n cluster.go:125: d475340682cc: Waiting\n cluster.go:125: b0cfbdbf0600: Waiting\n cluster.go:125: cdc0f9d545de: Waiting\n cluster.go:125: 410f90a307bd: Waiting\n cluster.go:125: 9d13c9fb0067: Verifying Checksum\n cluster.go:125: 9d13c9fb0067: Download complete\n cluster.go:125: 56d14e8ac0f6: Verifying Checksum\n cluster.go:125: 56d14e8ac0f6: Download complete\n cluster.go:125: fabcdb810cc4: Verifying Checksum\n cluster.go:125: fabcdb810cc4: Download complete\n cluster.go:125: 94474473290a: Verifying Checksum\n cluster.go:125: 94474473290a: Download complete\n cluster.go:125: d475340682cc: Download complete\n cluster.go:125: cdc0f9d545de: Verifying Checksum\n cluster.go:125: cdc0f9d545de: Download complete\n cluster.go:125: 410f90a307bd: Verifying Checksum\n cluster.go:125: 410f90a307bd: Download complete\n cluster.go:125: b0cfbdbf0600: Verifying Checksum\n cluster.go:125: b0cfbdbf0600: Download complete\n cluster.go:125: 56d14e8ac0f6: Pull complete\n cluster.go:125: 9d13c9fb0067: Pull complete\n cluster.go:125: fabcdb810cc4: Pull complete\n cluster.go:125: 94474473290a: Pull complete\n cluster.go:125: d475340682cc: Pull complete\n cluster.go:125: b0cfbdbf0600: Pull complete\n cluster.go:125: cdc0f9d545de: Pull complete\n cluster.go:125: 410f90a307bd: Pull complete\n cluster.go:125: Digest: sha256:824bf64ea1db34b089746b322cc09b1bf592bccb70f6454b6bdc43357caa64a1\n cluster.go:125: Status: Downloaded newer image for falcosecurity/falco-driver-loader:master\n cluster.go:145: \"docker run --rm --privileged -v /root/.falco:/root/.falco -v /proc:/host/proc:ro -v /boot:/host/boot:ro -v /lib/modules:/host/lib/modules:ro -v /usr:/host/usr:ro -v /etc:/host/etc:ro falcosecurity/falco-driver-loader:master kmod\" failed: output * Setting up /usr/src links from host\n2026-10-23 01:43:45 INFO Running falcoctl driver config\n ├ name: falco\n ├ version: 11.0.1+driver\n ├ type: kmod\n ├ host-root: /host\n └ repos: https://download.falco.org/driver\n2026-10-23 01:43:45 INFO Committing driver config to specialized configuration file under\n └ directory: /etc/falco/config.d\n2026-10-23 01:43:45 INFO Storing falcoctl driver config \n2026-10-23 01:43:46 INFO Running falcoctl driver install\n ├ driver version: 11.0.1+driver\n ├ driver type: kmod\n ├ driver name: falco\n ├ compile: true\n ├ download: true\n ├ target: flatcar\n ├ arch: x86_64\n ├ kernel release: 6.6.159-flatcar\n └ kernel version: #1 SMP PREEMPT_DYNAMIC Thu Oct 22 22:25:36 -00 2026\n2026-10-23 01:43:46 INFO Trying to download a driver.\n └ url: https://download.falco.org/driver/11.0.1%2Bdriver/x86_64/falco_flatcar_4081.3.10_1.ko\n2026-10-23 01:43:46 WARN Non-200 response from url. code: 404\n2026-10-23 01:43:46 WARN unable to find a prebuilt driver \n2026-10-23 01:43:46 INFO Trying to compile the requested driver \n2026-10-23 01:43:46 INFO Flatcar detected; relocating kernel tools.\n └ version: 4081.3.10\n2026-10-23 01:43:46 INFO Trying automatic kernel headers download. \n2026-10-23 01:43:46 WARN Failed to generate script.\n └ err: unexpected extraversion: flatcar\n2026-10-23 01:43:47 INFO Trying to dkms install module. gcc: /usr/bin/gcc\n2026-10-23 01:45:03 INFO kernel module available.\n └ path: /root/.falco/11.0.1+driver/x86_64/falco_flatcar_4081.3.10_1.ko\n2026-10-23 01:45:04 INFO Trying to load a pre existent system module, if present.\n2026-10-23 01:45:04 WARN Consider compiling your own driver and loading it or getting in touch with the Falco community.\n2026-10-23 01:45:04 ERROR failed: driver falco/11.0.1+driver is not installed in DKMS for kernel 6.6.159-flatcar: falco/11.0.1+driver, 6.6.159-flatcar, x86_64: installed (WARNING! Diff between built and installed module!), status Process exited with status 1\n"},{"name":"cl.ignition.oem.indirect","result":"PASS","duration":139166279656,"output":""},{"name":"cl.ignition.symlink","result":"PASS","duration":26202303151,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"cl.toolbox.dnf-install","result":"PASS","duration":130697100615,"output":""},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base/nginx_deployment","result":"PASS","duration":1010268581189,"output":""},{"name":"linux.nfs.v3","result":"PASS","duration":57073755743,"output":" nfs.go:80: NFS server booted.\n nfs.go:85: Test file \"/tmp/tmp.2eZtWkEklH\" created on server.\n nfs.go:125: NFS client booted.\n nfs.go:133: Got NFS mount.\n"},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base/NFS_deployment","result":"PASS","duration":75561676073,"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"},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base","result":"FAIL","duration":3272249640984,"output":" cluster.go:125: I1023 00:58:17.003468 1968 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\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: I1023 01:00:02.846159 2354 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: [preflight] The system verification failed. Printing the output from the verification:\n cluster.go:125: \u001b[0;37mKERNEL_VERSION\u001b[0m: \u001b[0;32m6.6.159-flatcar\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NAMESPACES\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NET_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_PID_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_IPC_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_UTS_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CPUSETS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_MEMCG\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_INET\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_EXT4_FS\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_PROC_FS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NETFILTER_XT_TARGET_REDIRECT\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NETFILTER_XT_MATCH_COMMENT\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_FAIR_GROUP_SCHED\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUPS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_CPUACCT\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_DEVICE\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_FREEZER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_PIDS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_SCHED\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_OVERLAY_FS\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_AUFS_FS\u001b[0m: \u001b[0;33mnot set - Required for aufs.\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_BLK_DEV_DM\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CFS_BANDWIDTH\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_SECCOMP\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_SECCOMP_FILTER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mOS\u001b[0m: \u001b[0;32mLinux\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPU\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPUACCT\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPUSET\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_DEVICES\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_FREEZER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_MEMORY\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_PIDS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_HUGETLB\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_BLKIO\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is deprecated and will be removed in a future release. Please migrate to cgroups v2. To explicitly enable cgroups v1 support for kubelet v1.35 or newer, you must set the kubelet configuration option 'FailCgroupV1' to 'false'. You must also explicitly skip this validation. For more information, see https://git.k8s.io/enhancements/keps/sig-node/5573-remove-cgroup-v1\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: W1023 01:00:06.635013 2354 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.52]\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 3.016507262s\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.52: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 8.333051494s\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 10.693975779s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 40.00655399s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 71ow82.ekzpf11kkxla76zu\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.52:6443 --token 71ow82.ekzpf11kkxla76zu \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:114954bb6a09c4aafd8f87204c94e2079919b01598befebd1870f252fbc8bdba \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: W1023 01:02:28.076304 1785 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is deprecated and will be removed in a future release. Please migrate to cgroups v2. To explicitly enable cgroups v1 support for kubelet v1.35 or newer, you must set the kubelet configuration option 'FailCgroupV1' to 'false'. You must also explicitly skip this validation. For more information, see https://git.k8s.io/enhancements/keps/sig-node/5573-remove-cgroup-v1\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- FAIL: kubeadm.v1.35.1.calico.cgroupv1.base/node_readiness (1681.58s)\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: The connection to the server 10.0.0.52:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.52:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n kubeadm.go:213: nodes are not ready: ready nodes should be equal to 2: 1\n --- PASS: kubeadm.v1.35.1.calico.cgroupv1.base/nginx_deployment (1010.27s)\n --- PASS: kubeadm.v1.35.1.calico.cgroupv1.base/NFS_deployment (75.56s)\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":"cl.ignition.oem.indirect.new","result":"PASS","duration":61341259533,"output":""},{"name":"misc.fips","result":"PASS","duration":42374296296,"output":" cluster.go:125: Error setting digest\n cluster.go:125: 40C7BC46FC7E0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../openssl-3.2.3/crypto/evp/evp_fetch.c:355:Global default library context, Algorithm (MD5 : 102), Properties ()\n cluster.go:125: 40C7BC46FC7E0000:error:03000086:digital envelope routines:evp_md_init_internal:initialization error:../openssl-3.2.3/crypto/evp/digest.c:272:\n cluster.go:152: + cat /proc/sys/crypto/fips_enabled\n"},{"name":"cl.etcd-member.v2-backup-restore","result":"PASS","duration":45855124479,"output":" cluster.go:125: 2026-10-23T01:49:58Z\tinfo\tetcdutl/backup_command.go:216\tignoring EntryConfChange raft entry\n cluster.go:125: 2026-10-23T01:49:58Z\tinfo\tetcdutl/backup_command.go:231\tignoring member attribute update on\t{\"entry\": \"Term:2 Index:3 Data:\\\"\\\\010\\\\201\\\\316\\\\264\\\\232\\\\347\\\\254\\\\250\\\\333\\\\036\\\\022\\\\003PUT\\\\032\u0026/0/members/5118857a62351eb6/attributes\\\\\\\"R{\\\\\\\"name\\\\\\\":\\\\\\\"7f3c9b509d5e435ea84013b9a83a56eb\\\\\\\",\\\\\\\"clientURLs\\\\\\\":[\\\\\\\"http://10.0.0.86:2379\\\\\\\"]}(\\\\0002\\\\0008\\\\000H\\\\000P\\\\000X\\\\000`\\\\000h\\\\000p\\\\000x\\\\000\\\\200\\\\001\\\\000\\\" \", \"v2Req.Path\": \"/0/members/5118857a62351eb6/attributes\"}\n cluster.go:125: 2026-10-23T01:49:58Z\tinfo\tetcdutl/backup_command.go:252\tignoring v3 raft entry\n cluster.go:125: 2026-10-23T01:49:58Z\tinfo\tmembership/store.go:119\tTrimming membership information from the backend...\n"},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"PASS","duration":56430842968,"output":""},{"name":"cl.internet/UpdateEngine","result":"PASS","duration":542166399,"output":""},{"name":"cl.internet/DockerPing","result":"PASS","duration":12687055794,"output":""},{"name":"cl.internet/DockerEcho","result":"PASS","duration":1018181351,"output":""},{"name":"cl.internet/NTPDate","result":"PASS","duration":6974716370,"output":""},{"name":"coreos.ignition.security.tls","result":"PASS","duration":67673900103,"output":""},{"name":"cl.internet","result":"PASS","duration":50037408675,"output":" --- PASS: cl.internet/UpdateEngine (0.54s)\n --- PASS: cl.internet/DockerPing (12.69s)\n --- PASS: cl.internet/DockerEcho (1.02s)\n --- PASS: cl.internet/NTPDate (6.97s)\n"},{"name":"cl.update.reboot","result":"FAIL","duration":73495199111,"output":" update.go:91: couldn't reboot: machine \"b70c3b04-303d-416e-bb44-47a8aede8594\" failed basic checks: some systemd units failed:\n● ldconfig.service loaded failed failed Rebuild Dynamic Linker Cache\nstatus: \njournal:-- No entries --\n harness.go:621: Found systemd unit failed to start (\u001b[0;1;39mldconfig.service\u001b[0m - Rebuild Dynamic Linker Cache.\r\r) on machine b70c3b04-303d-416e-bb44-47a8aede8594 console\n"},{"name":"cl.tang.nonroot","result":"PASS","duration":98974108489,"output":" tang.go:148: Started tang on 10.0.0.1:38541\n"},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":33139389572,"output":""},{"name":"docker.containerd-restart","result":"PASS","duration":95086169746,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Verifying Checksum\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n"},{"name":"coreos.ignition.groups","result":"PASS","duration":98377781415,"output":""},{"name":"packages/sys-cluster/ipvsadm","result":"PASS","duration":2706171588,"output":""},{"name":"cl.ignition.v1.ext4root","result":"PASS","duration":28286847605,"output":""},{"name":"linux.ntp","result":"PASS","duration":23957005685,"output":""},{"name":"cl.omaha.ping","result":"PASS","duration":26384941096,"output":""},{"name":"packages/sys-block/open-iscsi","result":"PASS","duration":62807335822,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/targetcli-fb:latest' locally\n cluster.go:125: latest: Pulling from flatcar/targetcli-fb\n cluster.go:125: a2318d6c47ec: Pulling fs layer\n cluster.go:125: 3d3086a1439f: Pulling fs layer\n cluster.go:125: a2318d6c47ec: Verifying Checksum\n cluster.go:125: a2318d6c47ec: Download complete\n cluster.go:125: 3d3086a1439f: Verifying Checksum\n cluster.go:125: 3d3086a1439f: Download complete\n cluster.go:125: a2318d6c47ec: Pull complete\n cluster.go:125: 3d3086a1439f: Pull complete\n cluster.go:125: Digest: sha256:b6cd65db981974e8b74938617218dd023775b969f9a059ced21e6ce6fa4763c1\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/targetcli-fb:latest\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: Created symlink /etc/systemd/system/remote-fs.target.wants/iscsi.service → /usr/lib/systemd/system/iscsi.service.\n"},{"name":"packages","result":"PASS","duration":145577317460,"output":" --- PASS: packages/sys-cluster/ipvsadm (2.71s)\n --- PASS: packages/sys-block/open-iscsi (62.81s)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/targetcli-fb:latest' locally\n cluster.go:125: latest: Pulling from flatcar/targetcli-fb\n cluster.go:125: a2318d6c47ec: Pulling fs layer\n cluster.go:125: 3d3086a1439f: Pulling fs layer\n cluster.go:125: a2318d6c47ec: Verifying Checksum\n cluster.go:125: a2318d6c47ec: Download complete\n cluster.go:125: 3d3086a1439f: Verifying Checksum\n cluster.go:125: 3d3086a1439f: Download complete\n cluster.go:125: a2318d6c47ec: Pull complete\n cluster.go:125: 3d3086a1439f: Pull complete\n cluster.go:125: Digest: sha256:b6cd65db981974e8b74938617218dd023775b969f9a059ced21e6ce6fa4763c1\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/targetcli-fb:latest\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: Created symlink /etc/systemd/system/remote-fs.target.wants/iscsi.service → /usr/lib/systemd/system/iscsi.service.\n"},{"name":"docker.selinux","result":"PASS","duration":32585857224,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: sh: can't create /opt/hello: Permission denied\n"},{"name":"coreos.selinux.enforce","result":"PASS","duration":58301048066,"output":""},{"name":"cl.ignition.oem.regular","result":"PASS","duration":50086472131,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/node_readiness","result":"PASS","duration":40445957400,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/nginx_deployment","result":"PASS","duration":29550401879,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/NFS_deployment","result":"PASS","duration":39498054895,"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":"devcontainer.systemd-nspawn","result":"PASS","duration":867204870326,"output":" cluster.go:125: + set -euo pipefail\n cluster.go:125: + source /home/core/download-library.sh\n cluster.go:125: + download_dev_container_image flatcar_developer_container.bin\n cluster.go:125: + local output_bin=flatcar_developer_container.bin\n cluster.go:125: + shift\n cluster.go:125: + local arch version image_url bzip2cat\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo amd64\n cluster.go:125: + arch=amd64\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo 4081.3.10+nightly-20261022-2100\n cluster.go:125: + version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2 amd64 4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ local template=http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ shift\n cluster.go:125: ++ local arch=amd64\n cluster.go:125: ++ shift\n cluster.go:125: ++ local version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ shift\n cluster.go:125: ++ local result=http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/images/amd64/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + image_url=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + echo 'Fetching developer container from http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2'\n cluster.go:125: + curl --fail --silent --show-error --location --retry-delay 1 --retry 60 --retry-connrefused --retry-max-time 60 --connect-timeout 20 --remote-name http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + bzip2cat=bzcat\n cluster.go:125: + command -v lbzcat\n cluster.go:125: + bzip2cat=lbzcat\n cluster.go:125: + cp --sparse=always /dev/fd/63 flatcar_developer_container.bin\n cluster.go:125: ++ lbzcat flatcar_developer_container.bin.bz2\n cluster.go:125: + source /usr/share/coreos/release\n cluster.go:125: ++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: ++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: + ARCH=amd64\n cluster.go:125: + VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs amd64 4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ local template=http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs\n cluster.go:125: ++ shift\n cluster.go:125: ++ local arch=amd64\n cluster.go:125: ++ shift\n cluster.go:125: ++ local version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ shift\n cluster.go:125: ++ local result=http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/boards/amd64-usr/@VERSION@/pkgs\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + EXPECTED_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: + workdir=/home/core/dev-container-workdir-6662\n cluster.go:125: + USR_SRC_DIR=/home/core/dev-container-workdir-6662/src\n cluster.go:125: + VAR_TMP_DIR=/home/core/dev-container-workdir-6662/tmp\n cluster.go:125: + mkdir -p /home/core/dev-container-workdir-6662/src /home/core/dev-container-workdir-6662/tmp\n cluster.go:125: + sudo systemd-nspawn --console=pipe --setenv=PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs --setenv=EXPECTED_VERSION=4081.3.10+nightly-20261022-2100 --bind-ro=/lib/modules --bind-ro=/home/core/dev-container-script --bind=/home/core/dev-container-workdir-6662/src:/usr/src --bind=/home/core/dev-container-workdir-6662/tmp:/var/tmp --image=flatcar_developer_container.bin --machine=flatcar-developer-container /bin/bash /home/core/dev-container-script\n cluster.go:125: + source /usr/share/coreos/release\n cluster.go:125: ++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: ++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: + [[ 4081.3.10+nightly-20261022-2100 != \\4\\0\\8\\1\\.\\3\\.\\1\\0\\+\\n\\i\\g\\h\\t\\l\\y\\-\\2\\0\\2\\6\\1\\0\\2\\2\\-\\2\\1\\0\\0 ]]\n cluster.go:125: + export PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + export 'FEATURES=-ipc-sandbox -network-sandbox'\n cluster.go:125: + FEATURES='-ipc-sandbox -network-sandbox'\n cluster.go:125: + emerge-gitclone\n cluster.go:125: Cloning into '/var/lib/portage/scripts'...\n cluster.go:125: Note: switching to 'lts-4081.3.10-nightly-20261022-2100'.\n cluster.go:125: \n cluster.go:125: You are in 'detached HEAD' state. You can look around, make experimental\n cluster.go:125: changes and commit them, and you can discard any commits you make in this\n cluster.go:125: state without impacting any branches by switching back to a branch.\n cluster.go:125: \n cluster.go:125: If you want to create a new branch to retain commits you create, you may\n cluster.go:125: do so (now or later) by using -c with the switch command. Example:\n cluster.go:125: \n cluster.go:125: git switch -c \u003cnew-branch-name\u003e\n cluster.go:125: \n cluster.go:125: Or undo this operation with:\n cluster.go:125: \n cluster.go:125: git switch -\n cluster.go:125: \n cluster.go:125: Turn off this advice by setting config variable advice.detachedHead to false\n cluster.go:125: \n cluster.go:125: HEAD is now at 41503d353d New version: lts-4081.3.10-nightly-20261022-2100\n cluster.go:125: + emerge --getbinpkg --verbose coreos-sources\n cluster.go:125: \n cluster.go:125: !!! Your current profile is deprecated and not supported anymore.\n cluster.go:125: !!! Use eselect profile to update your profile.\n cluster.go:125: !!! Please upgrade to the following profile if possible:\n cluster.go:125: \n cluster.go:125: default/linux/amd64/23.0/split-usr/no-multilib/hardened\n cluster.go:125: \n cluster.go:125: To upgrade do the following steps:\n cluster.go:125: \n cluster.go:125: A profile upgrade to version 23.0 is available for your architecture.\n cluster.go:125: The new 23.0 profiles enable some toolchain hardening features and \n cluster.go:125: performance enhancements by default, and standardize settings.\n cluster.go:125: You can find the list of changes on the wiki tracking page [1].\n cluster.go:125: \n cluster.go:125: Upgrade instructions\n cluster.go:125: \n cluster.go:125: Note 1: If you have manually changed your CHOST to a value different from \n cluster.go:125: what the stages and profiles set, you may have to do that in the future too.\n cluster.go:125: In that case you should know what you are doing, hopefully; please read the \n cluster.go:125: instructions with a critical eye then.\n cluster.go:125: \n cluster.go:125: Note 2: In case you are already familiar with binary packages, you should be\n cluster.go:125: able to add \"--getbinpkg\" to the emerge calls to speed things up.\n cluster.go:125: The use of binary packages is completely optional though, and also not\n cluster.go:125: as much tested as the source-based upgrade path yet.\n cluster.go:125: \n cluster.go:125: 1. Ensure your system backups are up to date. Please also update\n cluster.go:125: your system fully and depclean before proceeding.\n cluster.go:125: glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.\n cluster.go:125: \n cluster.go:125: 2. If you are still using one of the long-deprecated amd64 17.0 profiles \n cluster.go:125: (other than x32 or musl), then first complete the migration to the \n cluster.go:125: corresponding 17.1 profile. Instructions can be found at [3].\n cluster.go:125: \n cluster.go:125: 3. If you are currently using systemd in a split-usr configuration, then first \n cluster.go:125: complete the migration to the corresponding merged-usr profile of the \n cluster.go:125: same profile version. Details on how to do this can be found in the news \n cluster.go:125: item [4].\n cluster.go:125: If you are currently using openrc, migrate to 23.0 first, keeping your disk\n cluster.go:125: layout. If you want to move from split-usr to merged-usr, do that afterwards.\n cluster.go:125: \n cluster.go:125: 4. Run \"emerge --info\" and note down the value of the CHOST variable.\n cluster.go:125: \n cluster.go:125: 5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,\n cluster.go:125: remove it. Also delete all lines defining CHOST_... variables.\n cluster.go:125: \n cluster.go:125: 6. Select the 23.0 profile corresponding to your current profile, either using\n cluster.go:125: \"eselect profile\" or by manually setting the profile symlink.\n cluster.go:125: Note that old profiles are by default split-usr and the 23.0 profiles by\n cluster.go:125: default merged-usr. Do NOT change directory scheme now, since this will\n cluster.go:125: mess up your system! \n cluster.go:125: Instead, make sure that the new profile has the same property: for example, \n cluster.go:125: OLD default/linux/amd64/17.1 \n cluster.go:125: ==\u003e NEW default/linux/amd64/23.0/split-usr\n cluster.go:125: (added \"split-usr\")\n cluster.go:125: OLD default/linux/amd64/17.1/systemd/merged-usr \n cluster.go:125: ==\u003e NEW default/linux/amd64/23.0/systemd\n cluster.go:125: (removed \"merged-usr\")\n cluster.go:125: A detailed table of the upgrade paths can be found at [5]. Please consult it.\n cluster.go:125: In some cases (hppa, x86) the table will tell you to pick between two choices. \n cluster.go:125: What you need should be obvious from your *old* CHOST value (from step 4).\n cluster.go:125: \n cluster.go:125: 7. Delete the contents of your binary package cache at ${PKGDIR}\n cluster.go:125: rm -r /var/cache/binpkgs/*\n cluster.go:125: \n cluster.go:125: 8. In the file or directory /etc/portage/binrepos.conf (if existing), update\n cluster.go:125: the URI in all configuration such that they point to 23.0 profile binhost \n cluster.go:125: directories. The exact paths can be found in the table at [5], too.\n cluster.go:125: \n cluster.go:125: 9. Rebuild or reinstall from binary (if available) the following packages in\n cluster.go:125: this order, with the same version as already active:\n cluster.go:125: emerge --ask --oneshot sys-devel/binutils\n cluster.go:125: (you may have to run binutils-config and re-select your binutils now)\n cluster.go:125: emerge --ask --oneshot sys-devel/gcc\n cluster.go:125: (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do \n cluster.go:125: that; instead, abort and try again with --nodeps added to the command line.)\n cluster.go:125: (you may have to run gcc-config and re-select your gcc now)\n cluster.go:125: and the C library, i.e. for glibc-based systems\n cluster.go:125: emerge --ask --oneshot sys-libs/glibc\n cluster.go:125: or for musl-based systems\n cluster.go:125: emerge --ask --oneshot sys-libs/musl\n cluster.go:125: \n cluster.go:125: 10. Re-run \"emerge --info\" and check if CHOST has changed compared to step 4.\n cluster.go:125: \n cluster.go:125: If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, \n cluster.go:125: \n cluster.go:125: 11. Recheck with binutils-config and gcc-config that valid installed versions\n cluster.go:125: of binutils and gcc are selected.\n cluster.go:125: \n cluster.go:125: 12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that\n cluster.go:125: refer to the *OLD* CHOST value, and remove them. \n cluster.go:125: Examples how to do this can be found in the similar procedure at [6].\n cluster.go:125: \n cluster.go:125: 13. Run env-update \u0026\u0026 source /etc/profile\n cluster.go:125: \n cluster.go:125: 14. Re-emerge libtool:\n cluster.go:125: emerge --ask --oneshot libtool\n cluster.go:125: \n cluster.go:125: 15. Just for safety, delete the contents of your binary package cache at \n cluster.go:125: ${PKGDIR} again:\n cluster.go:125: rm -r /var/cache/binpkgs/*\n cluster.go:125: \n cluster.go:125: 16. Rebuild world:\n cluster.go:125: emerge --ask --emptytree @world\n cluster.go:125: \n cluster.go:125: [1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition\n cluster.go:125: [2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline\n cluster.go:125: [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html\n cluster.go:125: [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html\n cluster.go:125: [5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table\n cluster.go:125: [6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work\n cluster.go:125: \n cluster.go:125: \n cluster.go:125: + zcat /proc/config.gz\n cluster.go:125: ++ nproc\n cluster.go:125: + exec make -C /usr/src/linux -j4 modules_prepare V=1\n"},{"name":"kubeadm.v1.37.0.cilium.base/IPSec_encryption","result":"PASS","duration":70179230764,"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.37.0.cilium.base","result":"PASS","duration":329170399233,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\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.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E1023 01:57:54.490171 2020 remote_runtime.go:1359] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.38. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 01:57:54.697857 2020 checks.go:920] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.104]\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.489059ms\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.104: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.252223ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 39.100093ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.019435448s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: hu5djv.tyqk5fdkx4pzsuqw\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.0.104:6443 --token hu5djv.tyqk5fdkx4pzsuqw \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:252012203a5f1ada53037b04384047bcff3bfce43f291fed4432f8baf4cd1f38 \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: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\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-operator \n cluster.go:125: cilium \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W1023 01:58:45.444744 1647 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E1023 01:58:45.461674 1647 remote_runtime.go:1359] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.38. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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.cilium.base/node_readiness (40.45s)\n --- PASS: kubeadm.v1.37.0.cilium.base/nginx_deployment (29.55s)\n --- PASS: kubeadm.v1.37.0.cilium.base/NFS_deployment (39.50s)\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 --- PASS: kubeadm.v1.37.0.cilium.base/IPSec_encryption (70.18s)\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"},{"name":"bpf.ig/ig","result":"PASS","duration":38691328765,"output":" cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"bpf.ig","result":"PASS","duration":40836960721,"output":" --- PASS: bpf.ig/ig (38.69s)\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_exec:v0.50.0 --host --filter proc.comm=docker,args~ps --output json --verbose\n cluster.go:125: + docker info\n cluster.go:125: + docker ps\n cluster.go:125: + docker images\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.args == \"/usr/bin/docker\\u00a0ps\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0info\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.args == \"/usr/bin/docker\\u00a0images\"))' ig.json\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --help\n cluster.go:125: + trap 'kill %%' ERR\n cluster.go:125: + timeout 30 grep -F -m1 running...\n cluster.go:125: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + dig kinvolk.io\n cluster.go:125: + dig flatcar.org\n cluster.go:125: + dig stable.release.flatcar-linux.net\n cluster.go:125: + kill %%\n cluster.go:125: + wait\n cluster.go:125: + jq -s -e '.[] | select(.name == \"flatcar.org.\")' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"kinvolk.io.\"))' ig.json\n cluster.go:125: + jq -s -e 'isempty(.[] | select(.name == \"stable.release.flatcar-linux.net.\"))' ig.json\n"},{"name":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":13326838244,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":28081017001,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":33796094810,"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":304335015189,"output":" cluster.go:125: I1023 02:00:41.144881 1780 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\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: I1023 02:01:47.553696 2082 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E1023 02:01:47.903993 2082 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 02:01:49.061917 2082 checks.go:907] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.2\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.109]\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 50.192428ms\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.109: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 44.611261ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 45.986075ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.027331299s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: a8khzc.tr1u2eknpdvy629m\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.0.109:6443 --token a8khzc.tr1u2eknpdvy629m \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:a921db04b92f133695d49b0fa558d57db8520b7e2714459cb1af82f9211662ad \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: W1023 02:02:30.257428 1615 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E1023 02:02:30.274286 1615 remote_runtime.go:1177] \"RuntimeConfig from runtime service failed\" err=\"rpc error: code = Unimplemented desc = unknown method RuntimeConfig for service runtime.v1.RuntimeService\"\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.37. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W1023 02:02:30.545468 1615 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 (13.33s)\n --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (28.08s)\n --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (33.80s)\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.v1.once","result":"PASS","duration":53486291987,"output":""},{"name":"coreos.update.badusr","result":"PASS","duration":372411280910,"output":""},{"name":"cl.update.badverity","result":"PASS","duration":348146085116,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":25834714792,"output":""},{"name":"cl.sysext.fallbackdownload","result":"PASS","duration":48293278419,"output":" update.go:664: Rebooting test machine\n"},{"name":"cl.disk.raid0.root","result":"PASS","duration":85980001879,"output":""},{"name":"sysext.custom-oem","result":"PASS","duration":131796838363,"output":" cluster.go:125: + set -euo pipefail\n cluster.go:125: + source /home/core/download-library.sh\n cluster.go:125: + download_dev_container_image flatcar_developer_container.bin\n cluster.go:125: + local output_bin=flatcar_developer_container.bin\n cluster.go:125: + shift\n cluster.go:125: + local arch version image_url bzip2cat\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo amd64\n cluster.go:125: + arch=amd64\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo 4081.3.10+nightly-20261022-2100\n cluster.go:125: + version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2 amd64 4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ local template=http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ shift\n cluster.go:125: ++ local arch=amd64\n cluster.go:125: ++ shift\n cluster.go:125: ++ local version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ shift\n cluster.go:125: ++ local result=http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/images/amd64/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + image_url=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + echo 'Fetching developer container from http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2'\n cluster.go:125: + curl --fail --silent --show-error --location --retry-delay 1 --retry 60 --retry-connrefused --retry-max-time 60 --connect-timeout 20 --remote-name http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + bzip2cat=bzcat\n cluster.go:125: + command -v lbzcat\n cluster.go:125: + bzip2cat=lbzcat\n cluster.go:125: + cp --sparse=always /dev/fd/63 flatcar_developer_container.bin\n cluster.go:125: ++ lbzcat flatcar_developer_container.bin.bz2\n cluster.go:125: + workdir=/home/core/dev-container-workdir-9676\n cluster.go:125: + mkdir -p /home/core/dev-container-workdir-9676\n cluster.go:125: + sudo systemd-nspawn --console=pipe --bind-ro=/home/core/dev-container-script.sh --bind=/home/core/dev-container-workdir-9676:/work --image=flatcar_developer_container.bin --machine=flatcar-developer-container /bin/bash /home/core/dev-container-script.sh\n cluster.go:125: + set -euo pipefail\n cluster.go:125: ++ source /etc/os-release\n cluster.go:125: +++ NAME='Flatcar Container Linux by Kinvolk'\n cluster.go:125: +++ ID=flatcar\n cluster.go:125: +++ ID_LIKE=coreos\n cluster.go:125: +++ VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20261022-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20261022-2100 (LTS 2024)'\n cluster.go:125: +++ ANSI_COLOR='38;5;75'\n cluster.go:125: +++ HOME_URL=https://flatcar.org/\n cluster.go:125: +++ BUG_REPORT_URL=https://issues.flatcar.org\n cluster.go:125: +++ FLATCAR_BOARD=amd64-usr\n cluster.go:125: +++ CPE_NAME='cpe:2.3:o:flatcar-linux:flatcar_linux:4081.3.10+nightly-20261022-2100:*:*:*:*:*:*:*'\n cluster.go:125: ++ echo 4081.3.10+nightly-20261022-2100\n cluster.go:125: + version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ source /etc/os-release\n cluster.go:125: +++ NAME='Flatcar Container Linux by Kinvolk'\n cluster.go:125: +++ ID=flatcar\n cluster.go:125: +++ ID_LIKE=coreos\n cluster.go:125: +++ VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20261022-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20261022-2100 (LTS 2024)'\n cluster.go:125: +++ ANSI_COLOR='38;5;75'\n cluster.go:125: +++ HOME_URL=https://flatcar.org/\n cluster.go:125: +++ BUG_REPORT_URL=https://issues.flatcar.org\n cluster.go:125: +++ FLATCAR_BOARD=amd64-usr\n cluster.go:125: +++ CPE_NAME='cpe:2.3:o:flatcar-linux:flatcar_linux:4081.3.10+nightly-20261022-2100:*:*:*:*:*:*:*'\n cluster.go:125: ++ echo 4081.3.10\n cluster.go:125: + version_id=4081.3.10\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo amd64-usr\n cluster.go:125: + board=amd64-usr\n cluster.go:125: + mkdir -p /work/sysext_rootfs/usr/share/flatcar-sysext-kola-test\n cluster.go:125: + echo 4081.3.10\n cluster.go:125: + mkdir -p /work/sysext_rootfs/usr/lib/extension-release.d\n cluster.go:125: + sysext_arch=x86-64\n cluster.go:125: + [[ amd64-usr = \\a\\r\\m\\6\\4\\-\\u\\s\\r ]]\n cluster.go:125: + metadata=('ID=flatcar' \"VERSION_ID=${version_id}\" \"ARCHITECTURE=${sysext_arch}\")\n cluster.go:125: + metadata_file=/work/sysext_rootfs/usr/lib/extension-release.d/extension-release.oem-test\n cluster.go:125: + printf '%s\\n' ID=flatcar VERSION_ID=4081.3.10 ARCHITECTURE=x86-64\n cluster.go:125: + mksquashfs /work/sysext_rootfs /work/oem-test-4081.3.10+nightly-20261022-2100.raw -all-root\n cluster.go:125: ++ source /etc/os-release\n cluster.go:125: +++ NAME='Flatcar Container Linux by Kinvolk'\n cluster.go:125: +++ ID=flatcar\n cluster.go:125: +++ ID_LIKE=coreos\n cluster.go:125: +++ VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20261022-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20261022-2100 (LTS 2024)'\n cluster.go:125: +++ ANSI_COLOR='38;5;75'\n cluster.go:125: +++ HOME_URL=https://flatcar.org/\n cluster.go:125: +++ BUG_REPORT_URL=https://issues.flatcar.org\n cluster.go:125: +++ FLATCAR_BOARD=amd64-usr\n cluster.go:125: +++ CPE_NAME='cpe:2.3:o:flatcar-linux:flatcar_linux:4081.3.10+nightly-20261022-2100:*:*:*:*:*:*:*'\n cluster.go:125: ++ echo 4081.3.10+nightly-20261022-2100\n cluster.go:125: + version=4081.3.10+nightly-20261022-2100\n cluster.go:125: + sysext_file=/home/core/dev-container-workdir-9676/oem-test-4081.3.10+nightly-20261022-2100.raw\n cluster.go:125: + [[ ! -e /home/core/dev-container-workdir-9676/oem-test-4081.3.10+nightly-20261022-2100.raw ]]\n cluster.go:125: + [[ ! -e /oem/oem-release ]]\n cluster.go:125: + printf '%s\\n' ID=test VERSION_ID=1.0.0 'NAME=testing stuff'\n cluster.go:125: + sudo tee /oem/oem-release\n cluster.go:125: + sudo mkdir -p /oem/sysext\n cluster.go:125: + sudo mv /home/core/dev-container-workdir-9676/oem-test-4081.3.10+nightly-20261022-2100.raw /oem/sysext\n cluster.go:125: + sudo touch /oem/sysext/active-oem-test\n cluster.go:125: + sudo flatcar-reset --keep-machine-id --keep-paths /var/log\n cluster.go:125: + set -euo pipefail\n cluster.go:125: ++ systemd-sysext list --json=pretty\n cluster.go:125: + list_out='[\n cluster.go:125: \t{\n cluster.go:125: \t\t\"name\" : \"containerd-flatcar\",\n cluster.go:125: \t\t\"type\" : \"raw\",\n cluster.go:125: \t\t\"path\" : \"/etc/extensions/containerd-flatcar.raw\",\n cluster.go:125: \t\t\"time\" : 1792710123572110\n cluster.go:125: \t},\n cluster.go:125: \t{\n cluster.go:125: \t\t\"name\" : \"docker-flatcar\",\n cluster.go:125: \t\t\"type\" : \"raw\",\n cluster.go:125: \t\t\"path\" : \"/etc/extensions/docker-flatcar.raw\",\n cluster.go:125: \t\t\"time\" : 1792710150138028\n cluster.go:125: \t},\n cluster.go:125: \t{\n cluster.go:125: \t\t\"name\" : \"oem-test\",\n cluster.go:125: \t\t\"type\" : \"raw\",\n cluster.go:125: \t\t\"path\" : \"/etc/extensions/oem-test.raw\",\n cluster.go:125: \t\t\"time\" : 1792721416480286\n cluster.go:125: \t}\n cluster.go:125: ]'\n cluster.go:125: ++ systemd-sysext status --json=pretty\n cluster.go:125: + status_out='[\n cluster.go:125: \t{\n cluster.go:125: \t\t\"hierarchy\" : \"/opt\",\n cluster.go:125: \t\t\"extensions\" : \"none\",\n cluster.go:125: \t\t\"since\" : null\n cluster.go:125: \t},\n cluster.go:125: \t{\n cluster.go:125: \t\t\"hierarchy\" : \"/usr\",\n cluster.go:125: \t\t\"extensions\" : [\n cluster.go:125: \t\t\t\"containerd-flatcar\",\n cluster.go:125: \t\t\t\"docker-flatcar\",\n cluster.go:125: \t\t\t\"oem-test\"\n cluster.go:125: \t\t],\n cluster.go:125: \t\t\"since\" : 1792721441531000\n cluster.go:125: \t}\n cluster.go:125: ]'\n cluster.go:125: + printf 'sysext list:\\n%s\\nsysext status:\\n%s\\n' '[\n cluster.go:125: \t{\n cluster.go:125: \t\t\"name\" : \"containerd-flatcar\",\n cluster.go:125: \t\t\"type\" : \"raw\",\n cluster.go:125: \t\t\"path\" : \"/etc/extensions/containerd-flatcar.raw\",\n cluster.go:125: \t\t\"time\" : 1792710123572110\n cluster.go:125: \t},\n cluster.go:125: \t{\n cluster.go:125: \t\t\"name\" : \"docker-flatcar\",\n cluster.go:125: \t\t\"type\" : \"raw\",\n cluster.go:125: \t\t\"path\" : \"/etc/extensions/docker-flatcar.raw\",\n cluster.go:125: \t\t\"time\" : 1792710150138028\n cluster.go:125: \t},\n cluster.go:125: \t{\n cluster.go:125: \t\t\"name\" : \"oem-test\",\n cluster.go:125: \t\t\"type\" : \"raw\",\n cluster.go:125: \t\t\"path\" : \"/etc/extensions/oem-test.raw\",\n cluster.go:125: \t\t\"time\" : 1792721416480286\n cluster.go:125: \t}\n cluster.go:125: ]' '[\n cluster.go:125: \t{\n cluster.go:125: \t\t\"hierarchy\" : \"/opt\",\n cluster.go:125: \t\t\"extensions\" : \"none\",\n cluster.go:125: \t\t\"since\" : null\n cluster.go:125: \t},\n cluster.go:125: \t{\n cluster.go:125: \t\t\"hierarchy\" : \"/usr\",\n cluster.go:125: \t\t\"extensions\" : [\n cluster.go:125: \t\t\t\"containerd-flatcar\",\n cluster.go:125: \t\t\t\"docker-flatcar\",\n cluster.go:125: \t\t\t\"oem-test\"\n cluster.go:125: \t\t],\n cluster.go:125: \t\t\"since\" : 1792721441531000\n cluster.go:125: \t}\n cluster.go:125: ]'\n cluster.go:125: ++ jq '.[] | select(.name == \"oem-test\")'\n cluster.go:125: + list_oem_test='{\n cluster.go:125: \"name\": \"oem-test\",\n cluster.go:125: \"type\": \"raw\",\n cluster.go:125: \"path\": \"/etc/extensions/oem-test.raw\",\n cluster.go:125: \"time\": 1792721416480286\n cluster.go:125: }'\n cluster.go:125: + [[ -z {\n cluster.go:125: \"name\": \"oem-test\",\n cluster.go:125: \"type\": \"raw\",\n cluster.go:125: \"path\": \"/etc/extensions/oem-test.raw\",\n cluster.go:125: \"time\": 1792721416480286\n cluster.go:125: } ]]\n cluster.go:125: ++ jq --raw-output .type\n cluster.go:125: + oem_test_type=raw\n cluster.go:125: + [[ raw != \\r\\a\\w ]]\n cluster.go:125: ++ jq --raw-output .path\n cluster.go:125: + oem_test_path=/etc/extensions/oem-test.raw\n cluster.go:125: ++ readlink -f /etc/extensions/oem-test.raw\n cluster.go:125: + oem_test_real_path=/oem/sysext/oem-test-4081.3.10+nightly-20261022-2100.raw\n cluster.go:125: + [[ /etc/extensions/oem-test.raw != \\/\\o\\e\\m\\/\\s\\y\\s\\e\\x\\t\\/\\o\\e\\m\\-\\t\\e\\s\\t\\-\\4\\0\\8\\1\\.\\3\\.\\1\\0\\+\\n\\i\\g\\h\\t\\l\\y\\-\\2\\0\\2\\6\\1\\0\\2\\2\\-\\2\\1\\0\\0\\.\\r\\a\\w ]]\n cluster.go:125: + [[ /etc/extensions/oem-test.raw != \\/\\e\\t\\c\\/\\e\\x\\t\\e\\n\\s\\i\\o\\n\\s\\/\\o\\e\\m\\-\\t\\e\\s\\t\\.\\r\\a\\w ]]\n cluster.go:125: ++ jq '.[] | select(.hierarchy == \"/usr\")'\n cluster.go:125: + status_usr='{\n cluster.go:125: \"hierarchy\": \"/usr\",\n cluster.go:125: \"extensions\": [\n cluster.go:125: \"containerd-flatcar\",\n cluster.go:125: \"docker-flatcar\",\n cluster.go:125: \"oem-test\"\n cluster.go:125: ],\n cluster.go:125: \"since\": 1792721441531000\n cluster.go:125: }'\n cluster.go:125: + [[ -z {\n cluster.go:125: \"hierarchy\": \"/usr\",\n cluster.go:125: \"extensions\": [\n cluster.go:125: \"containerd-flatcar\",\n cluster.go:125: \"docker-flatcar\",\n cluster.go:125: \"oem-test\"\n cluster.go:125: ],\n cluster.go:125: \"since\": 1792721441531000\n cluster.go:125: } ]]\n cluster.go:125: ++ jq --raw-output '.extensions[] | select(. == \"oem-test\")'\n cluster.go:125: + status_usr_extensions_oem_test=oem-test\n cluster.go:125: + [[ oem-test != \\o\\e\\m\\-\\t\\e\\s\\t ]]\n cluster.go:125: + f=/usr/share/flatcar-sysext-kola-test/file\n cluster.go:125: + [[ ! -e /usr/share/flatcar-sysext-kola-test/file ]]\n cluster.go:125: ++ cat /usr/share/flatcar-sysext-kola-test/file\n cluster.go:125: + got=4081.3.10\n cluster.go:125: ++ source /etc/os-release\n cluster.go:125: +++ NAME='Flatcar Container Linux by Kinvolk'\n cluster.go:125: +++ ID=flatcar\n cluster.go:125: +++ ID_LIKE=coreos\n cluster.go:125: +++ VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20261022-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20261022-2100 (LTS 2024)'\n cluster.go:125: +++ ANSI_COLOR='38;5;75'\n cluster.go:125: +++ HOME_URL=https://flatcar.org/\n cluster.go:125: +++ BUG_REPORT_URL=https://issues.flatcar.org\n cluster.go:125: +++ FLATCAR_BOARD=amd64-usr\n cluster.go:125: +++ CPE_NAME='cpe:2.3:o:flatcar-linux:flatcar_linux:4081.3.10+nightly-20261022-2100:*:*:*:*:*:*:*'\n cluster.go:125: ++ echo 4081.3.10\n cluster.go:125: + ex=4081.3.10\n cluster.go:125: + [[ 4081.3.10 != \\4\\0\\8\\1\\.\\3\\.\\1\\0 ]]\n"},{"name":"cl.verity/verify","result":"PASS","duration":55898227376,"output":" cluster.go:125: Success\n"},{"name":"cl.network.wireguard","result":"PASS","duration":117444146662,"output":" cluster.go:152: + ip --json address show kv0 | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n"},{"name":"cl.locksmith.cluster","result":"PASS","duration":545712124056,"output":""},{"name":"cl.verity/corruption","result":"PASS","duration":180228984824,"output":""},{"name":"cl.verity","result":"PASS","duration":284792232734,"output":" --- PASS: cl.verity/verify (55.90s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (180.23s)\n"},{"name":"systemd.journal.remote","result":"PASS","duration":122679698828,"output":" cluster.go:125: Running as unit: systemd-journal-remote-client.service; invocation ID: 1a72d94ee13d4239b46b7f980491e607\n"},{"name":"cl.disk.raid1.root","result":"PASS","duration":177277040497,"output":""},{"name":"cl.cloudinit.basic","result":"PASS","duration":30711593223,"output":""},{"name":"cl.swap_activation","result":"PASS","duration":119813375875,"output":""},{"name":"coreos.ignition.sethostname","result":"PASS","duration":52067812476,"output":""},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":310904792578,"output":""},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":316040312688,"output":""},{"name":"cl.tang.root","result":"PASS","duration":80600586763,"output":" tang.go:148: Started tang on 10.0.0.1:40731\n"},{"name":"cl.ignition.instantiated.enable-unit","result":"PASS","duration":30864398894,"output":""},{"name":"cl.ignition.v1.users","result":"PASS","duration":249221902195,"output":""},{"name":"systemd.sysusers.gshadow","result":"PASS","duration":217704039415,"output":""},{"name":"cl.overlay.cleanup","result":"FAIL","duration":369564614086,"output":" harness.go:621: Found systemd dependency unit failed to start (\u001b[0;1;39mserial-getty…S0.service\u001b[0m - Serial Getty on ttyS0.\r\r) on machine 1936b86d-9a59-4531-8031-e831a584b8e2 console\n"},{"name":"cl.ignition.oem.reuse","result":"PASS","duration":405888942621,"output":""},{"name":"cl.ignition.luks","result":"PASS","duration":86705938135,"output":""},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base/node_readiness","result":"PASS","duration":154260599516,"output":""},{"name":"cl.tpm.root","result":"PASS","duration":239728451694,"output":""},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base/nginx_deployment","result":"PASS","duration":74868409637,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":200578372,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":300930471,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":351406305,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":506401043,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":543091567,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":351686659,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":586197661,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":259912546,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":397278926,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":440283580,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":512144920,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":305381035,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":297174284,"output":""},{"name":"cl.basic","result":"PASS","duration":50210906048,"output":" --- PASS: cl.basic/SymlinkFlatcar (0.20s)\n --- PASS: cl.basic/ReadOnly (0.30s)\n --- PASS: cl.basic/RandomUUID (0.35s)\n --- PASS: cl.basic/Useradd (0.51s)\n --- PASS: cl.basic/DbusPerms (0.54s)\n --- PASS: cl.basic/UpdateEngineKeys (0.35s)\n --- PASS: cl.basic/ServicesActive (0.59s)\n --- PASS: cl.basic/MachineID (0.26s)\n --- PASS: cl.basic/Microcode (0.40s)\n --- PASS: cl.basic/CloudConfig (0.44s)\n --- PASS: cl.basic/Script (0.51s)\n --- PASS: cl.basic/PortSSH (0.31s)\n --- PASS: cl.basic/Symlink (0.30s)\n"},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base/NFS_deployment","result":"PASS","duration":29920368169,"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"},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base","result":"PASS","duration":1713548157359,"output":" cluster.go:125: I1023 02:23:59.154824 1923 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\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: W1023 02:25:26.232363 2266 version.go:108] could not fetch a Kubernetes version from the internet: unable to get URL \"https://dl.k8s.io/release/stable-1.txt\": Get \"https://dl.k8s.io/release/stable-1.txt\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n cluster.go:125: W1023 02:25:26.242967 2266 version.go:109] falling back to the local client version: v1.35.1\n cluster.go:125: [init] Using Kubernetes version: v1.35.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: [preflight] The system verification failed. Printing the output from the verification:\n cluster.go:125: \u001b[0;37mKERNEL_VERSION\u001b[0m: \u001b[0;32m6.6.159-flatcar\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NAMESPACES\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NET_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_PID_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_IPC_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_UTS_NS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CPUSETS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_MEMCG\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_INET\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_EXT4_FS\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_PROC_FS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NETFILTER_XT_TARGET_REDIRECT\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_NETFILTER_XT_MATCH_COMMENT\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_FAIR_GROUP_SCHED\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUPS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_CPUACCT\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_DEVICE\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_FREEZER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_PIDS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CGROUP_SCHED\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_OVERLAY_FS\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_AUFS_FS\u001b[0m: \u001b[0;33mnot set - Required for aufs.\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_BLK_DEV_DM\u001b[0m: \u001b[0;32menabled (as module)\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_CFS_BANDWIDTH\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_SECCOMP\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCONFIG_SECCOMP_FILTER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mOS\u001b[0m: \u001b[0;32mLinux\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPU\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPUACCT\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_CPUSET\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_DEVICES\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_FREEZER\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_MEMORY\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_PIDS\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_HUGETLB\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \u001b[0;37mCGROUPS_BLKIO\u001b[0m: \u001b[0;32menabled\u001b[0m\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is deprecated and will be removed in a future release. Please migrate to cgroups v2. To explicitly enable cgroups v1 support for kubelet v1.35 or newer, you must set the kubelet configuration option 'FailCgroupV1' to 'false'. You must also explicitly skip this validation. For more information, see https://git.k8s.io/enhancements/keps/sig-node/5573-remove-cgroup-v1\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: W1023 02:25:35.159525 2266 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.135]\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 9.153936211s\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.135: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 27.129002019s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 43.343681698s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7m28.284676135s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: c7dkvt.kex6nnzhtdk5w0re\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.135:6443 --token c7dkvt.kex6nnzhtdk5w0re \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:e8cf5e9405452c13ef3e3bbacf4915f8153e31fbd648862d019b8385594e65ec \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: W1023 02:39:56.346310 1750 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n cluster.go:125: \t[WARNING SystemVerification]: cgroups v1 support is deprecated and will be removed in a future release. Please migrate to cgroups v2. To explicitly enable cgroups v1 support for kubelet v1.35 or newer, you must set the kubelet configuration option 'FailCgroupV1' to 'false'. You must also explicitly skip this validation. For more information, see https://git.k8s.io/enhancements/keps/sig-node/5573-remove-cgroup-v1\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.cgroupv1.base/node_readiness (154.26s)\n --- PASS: kubeadm.v1.35.1.flannel.cgroupv1.base/nginx_deployment (74.87s)\n --- PASS: kubeadm.v1.35.1.flannel.cgroupv1.base/NFS_deployment (29.92s)\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":"cl.install.cloudinit","result":"PASS","duration":27663389536,"output":""},{"name":"docker.btrfs-storage","result":"PASS","duration":28338962415,"output":""},{"name":"sysext.simple","result":"PASS","duration":31109868781,"output":""},{"name":"cl.ignition.translation","result":"PASS","duration":48615010535,"output":" cluster.go:152: + ip --json address show kola | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n cluster.go:152: + cat /etc/systemd/network/00-dummy.network\n"},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":137618174053,"output":""},{"name":"cl.filesystem/deadlinks","result":"PASS","duration":66560537318,"output":""},{"name":"cl.filesystem/suid","result":"PASS","duration":14779444950,"output":""},{"name":"cl.filesystem/sgid","result":"PASS","duration":15544056939,"output":""},{"name":"cl.filesystem/writablefiles","result":"PASS","duration":14172283341,"output":""},{"name":"cl.filesystem/writabledirs","result":"PASS","duration":13778259132,"output":""},{"name":"cl.filesystem/stickydirs","result":"PASS","duration":7741984302,"output":""},{"name":"cl.filesystem/blacklist","result":"PASS","duration":9912703412,"output":""},{"name":"cl.filesystem","result":"PASS","duration":224401694375,"output":" --- PASS: cl.filesystem/deadlinks (66.56s)\n --- PASS: cl.filesystem/suid (14.78s)\n --- PASS: cl.filesystem/sgid (15.54s)\n --- PASS: cl.filesystem/writablefiles (14.17s)\n --- PASS: cl.filesystem/writabledirs (13.78s)\n --- PASS: cl.filesystem/stickydirs (7.74s)\n --- PASS: cl.filesystem/blacklist (9.91s)\n"},{"name":"sysext.custom-docker.sysext","result":"PASS","duration":157500414141,"output":" cluster.go:125: bash: line 1: docker: command not found\n cluster.go:125: Cloning into 'sysext-bakery'...\n cluster.go:125: Note: switching to '9850ffd5b2353f45a9b3bf4fb84f8138a149e3e7'.\n cluster.go:125: \n cluster.go:125: You are in 'detached HEAD' state. You can look around, make experimental\n cluster.go:125: changes and commit them, and you can discard any commits you make in this\n cluster.go:125: state without impacting any branches by switching back to a branch.\n cluster.go:125: \n cluster.go:125: If you want to create a new branch to retain commits you create, you may\n cluster.go:125: do so (now or later) by using -c with the switch command. Example:\n cluster.go:125: \n cluster.go:125: git switch -c \u003cnew-branch-name\u003e\n cluster.go:125: \n cluster.go:125: Or undo this operation with:\n cluster.go:125: \n cluster.go:125: git switch -\n cluster.go:125: \n cluster.go:125: Turn off this advice by setting config variable advice.detachedHead to false\n cluster.go:125: \n cluster.go:125: HEAD is now at 9850ffd Merge pull request #31 from flatcar/t-lo/fix-docker-23-containerd-shim\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/busybox:latest' locally\n cluster.go:125: latest: Pulling from flatcar/busybox\n cluster.go:125: 4bf2067f7735: Pulling fs layer\n cluster.go:125: 4bf2067f7735: Download complete\n cluster.go:125: 4bf2067f7735: Pull complete\n cluster.go:125: Digest: sha256:93e8234eb9ca92b9aae20fd73d6c9447ac3d1cc741c6e80c737f821dca582a0e\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/busybox:latest\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n cluster.go:125: mke2fs 1.47.1 (20-May-2024)\n cluster.go:125: resize2fs 1.47.1 (20-May-2024)\n"},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":100169748873,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"FAIL","duration":458793678510,"output":" cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n kubeadm.go:232: nginx is not deployed: ready replicas should be equal to 1: null\n"},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"FAIL","duration":911517818930,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): 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 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 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 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: Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get pods test-pod-1)\n cluster.go:125: The connection to the server 10.0.0.149:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.149:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Error from server (Forbidden): pods \"test-pod-1\" is forbidden: User \"kubernetes-admin\" cannot get resource \"pods\" in API group \"\" in the namespace \"default\"\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 kubeadm.go:264: nginx pod with NFS is not deployed: getting container status: Process exited with status 5\n"},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"FAIL","duration":147259591161,"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 cluster.go:125: Error: Unable to determine status: timeout while waiting for status to become successful: context deadline exceeded\n cluster.go:145: \"/opt/bin/cilium status --wait --wait-duration 1m\" failed: output \u001b[33m /¯¯\\\n\u001b[36m /¯¯\u001b[33m\\__/\u001b[32m¯¯\\\u001b[0m Cilium: \u001b[31m2 errors\u001b[0m\n\u001b[36m \\__\u001b[31m/¯¯\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n\u001b[32m /¯¯\u001b[31m\\__/\u001b[35m¯¯\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n\u001b[32m \\__\u001b[34m/¯¯\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n\u001b[34m \\__/\n\u001b[0m\nDaemonSet cilium \nDeployment cilium-operator \nContainers: cilium-operator Running: \u001b[32m1\u001b[0m\n cilium Running: \u001b[32m2\u001b[0m\nCluster Pods: 3/4 managed by Cilium\nImage versions cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 2\n cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\nErrors: cilium cilium-j9wnr controller sync-to-k8s-ciliumendpoint (1073) is failing since 12s (8x): Unauthorized\n cilium cilium-j9wnr controller cilium-health-ep is failing since 2m30s (4x): Get \"http://192.168.0.226:4240/hello\": dial tcp 192.168.0.226:4240: connect: no route to host, status Process exited with status 1\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":2197255108332,"output":" cluster.go:125: I1023 02:52:42.759886 1815 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\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: I1023 02:52:55.718358 2031 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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: W1023 02:52:56.328672 2031 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.149]\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.538337044s\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.149: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 11.685707025s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 31.7144384s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1m45.583040777s\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 localhost 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 localhost as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: brvh1z.dh94sitn9og0mom1\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.149:6443 --token brvh1z.dh94sitn9og0mom1 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:6b21ffc52c591f7346f7384c958de2e413b96e87e3b361727c3508961a591094 \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: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\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: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \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: W1023 02:56:10.490592 1654 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\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.cilium.base/node_readiness (100.17s)\n --- FAIL: kubeadm.v1.35.1.cilium.base/nginx_deployment (458.79s)\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n kubeadm.go:232: nginx is not deployed: ready replicas should be equal to 1: null\n --- FAIL: kubeadm.v1.35.1.cilium.base/NFS_deployment (911.52s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:112): 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 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 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 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: Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get pods test-pod-1)\n cluster.go:125: The connection to the server 10.0.0.149:6443 was refused - did you specify the right host or port?\n cluster.go:125: The connection to the server 10.0.0.149:6443 was refused - did you specify the right host or port?\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Unable to connect to the server: net/http: TLS handshake timeout\n cluster.go:125: Error from server (Forbidden): pods \"test-pod-1\" is forbidden: User \"kubernetes-admin\" cannot get resource \"pods\" in API group \"\" in the namespace \"default\"\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 kubeadm.go:264: nginx pod with NFS is not deployed: getting container status: Process exited with status 5\n --- FAIL: kubeadm.v1.35.1.cilium.base/IPSec_encryption (147.26s)\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: Error: Unable to determine status: timeout while waiting for status to become successful: context deadline exceeded\n cluster.go:145: \"/opt/bin/cilium status --wait --wait-duration 1m\" failed: output \u001b[33m /¯¯\\\n \u001b[36m /¯¯\u001b[33m\\__/\u001b[32m¯¯\\\u001b[0m Cilium: \u001b[31m2 errors\u001b[0m\n \u001b[36m \\__\u001b[31m/¯¯\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n \u001b[32m /¯¯\u001b[31m\\__/\u001b[35m¯¯\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n \u001b[32m \\__\u001b[34m/¯¯\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n \u001b[34m \\__/\n \u001b[0m\n DaemonSet cilium \n Deployment cilium-operator \n Containers: cilium-operator Running: \u001b[32m1\u001b[0m\n cilium Running: \u001b[32m2\u001b[0m\n Cluster Pods: 3/4 managed by Cilium\n Image versions cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 2\n cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\n Errors: cilium cilium-j9wnr controller sync-to-k8s-ciliumendpoint (1073) is failing since 12s (8x): Unauthorized\n cilium cilium-j9wnr controller cilium-health-ep is failing since 2m30s (4x): Get \"http://192.168.0.226:4240/hello\": dial tcp 192.168.0.226:4240: connect: no route to host, status Process exited with status 1\n"},{"name":"devcontainer.docker","result":"PASS","duration":4501257450801,"output":" cluster.go:125: + set -euo pipefail\n cluster.go:125: + source /home/core/download-library.sh\n cluster.go:125: + download_dev_container_image flatcar_developer_container.bin\n cluster.go:125: + local output_bin=flatcar_developer_container.bin\n cluster.go:125: + shift\n cluster.go:125: + local arch version image_url bzip2cat\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo amd64\n cluster.go:125: + arch=amd64\n cluster.go:125: ++ source /usr/share/flatcar/release\n cluster.go:125: +++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: +++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: +++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: ++ echo 4081.3.10+nightly-20261022-2100\n cluster.go:125: + version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2 amd64 4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ local template=http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ shift\n cluster.go:125: ++ local arch=amd64\n cluster.go:125: ++ shift\n cluster.go:125: ++ local version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ shift\n cluster.go:125: ++ local result=http://bincache.flatcar-linux.net/images/@ARCH@/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/images/amd64/@VERSION@/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + image_url=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + echo 'Fetching developer container from http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2'\n cluster.go:125: + curl --fail --silent --show-error --location --retry-delay 1 --retry 60 --retry-connrefused --retry-max-time 60 --connect-timeout 20 --remote-name http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20261022-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + bzip2cat=bzcat\n cluster.go:125: + command -v lbzcat\n cluster.go:125: + bzip2cat=lbzcat\n cluster.go:125: + cp --sparse=always /dev/fd/63 flatcar_developer_container.bin\n cluster.go:125: ++ lbzcat flatcar_developer_container.bin.bz2\n cluster.go:125: + source /usr/share/coreos/release\n cluster.go:125: ++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: ++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: + ARCH=amd64\n cluster.go:125: + VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs amd64 4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ local template=http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs\n cluster.go:125: ++ shift\n cluster.go:125: ++ local arch=amd64\n cluster.go:125: ++ shift\n cluster.go:125: ++ local version=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ shift\n cluster.go:125: ++ local result=http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/boards/amd64-usr/@VERSION@/pkgs\n cluster.go:125: ++ result=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + EXPECTED_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: + workdir=/home/core/dev-container-workdir-4441\n cluster.go:125: + USR_SRC_DIR=/home/core/dev-container-workdir-4441/src\n cluster.go:125: + VAR_TMP_DIR=/home/core/dev-container-workdir-4441/tmp\n cluster.go:125: + mkdir -p /home/core/dev-container-workdir-4441/src /home/core/dev-container-workdir-4441/tmp\n cluster.go:125: ++ parted flatcar_developer_container.bin unit b print\n cluster.go:125: ++ grep Start --after-context=1\n cluster.go:125: ++ tail --lines=1\n cluster.go:125: ++ awk '{ print $2 }'\n cluster.go:125: ++ head --bytes=-2\n cluster.go:125: + offset=2097152\n cluster.go:125: + mkdir root\n cluster.go:125: + sudo mount -o loop,ro,offset=2097152 flatcar_developer_container.bin root\n cluster.go:125: + sudo tar -C root -czf dev-container-image.tar.gz .\n cluster.go:125: + sudo umount root\n cluster.go:125: + rm -f flatcar_developer_container.bin\n cluster.go:125: + docker import dev-container-image.tar.gz dev-container:42\n cluster.go:125: + sudo rm -f dev-container-image.tar.gz\n cluster.go:125: + restorecon /home/core/dev-container-script\n cluster.go:125: + docker run --log-driver=journald --env PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs --env EXPECTED_VERSION=4081.3.10+nightly-20261022-2100 --mount type=bind,source=/lib/modules,target=/lib/modules,readonly=true --mount type=bind,source=/home/core/dev-container-script,target=/home/core/dev-container-script,readonly=true --mount type=bind,source=/home/core/dev-container-workdir-4441/src,target=/usr/src --mount type=bind,source=/home/core/dev-container-workdir-4441/tmp,target=/var/tmp dev-container:42 /bin/bash /home/core/dev-container-script\n cluster.go:125: + source /usr/share/coreos/release\n cluster.go:125: ++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20261022-2100\n cluster.go:125: ++ FLATCAR_RELEASE_BOARD=amd64-usr\n cluster.go:125: ++ FLATCAR_RELEASE_APPID='{e96281a6-d1af-4bde-9a0a-97b76e56dc57}'\n cluster.go:125: + [[ 4081.3.10+nightly-20261022-2100 != \\4\\0\\8\\1\\.\\3\\.\\1\\0\\+\\n\\i\\g\\h\\t\\l\\y\\-\\2\\0\\2\\6\\1\\0\\2\\2\\-\\2\\1\\0\\0 ]]\n cluster.go:125: + export PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20261022-2100/pkgs\n cluster.go:125: + export 'FEATURES=-ipc-sandbox -network-sandbox'\n cluster.go:125: + FEATURES='-ipc-sandbox -network-sandbox'\n cluster.go:125: + emerge-gitclone\n cluster.go:125: Cloning into '/var/lib/portage/scripts'...\n cluster.go:125: Updating files: 7% (1051/13702)\rUpdating files: 8% (1097/13702)\rUpdating files: 9% (1234/13702)\rUpdating files: 10% (1371/13702)\rUpdating files: 11% (1508/13702)\rUpdating files: 12% (1645/13702)\rUpdating files: 13% (1782/13702)\rUpdating files: 14% (1919/13702)\rUpdating files: 15% (2056/13702)\rUpdating files: 15% (2112/13702)\rUpdating files: 16% (2193/13702)\rUpdating files: 17% (2330/13702)\rUpdating files: 18% (2467/13702)\rUpdating files: 18% (2489/13702)\rUpdating files: 19% (2604/13702)\rUpdating files: 19% (2719/13702)\rUpdating files: 20% (2741/13702)\rUpdating files: 21% (2878/13702)\rUpdating files: 21% (2914/13702)\rUpdating files: 22% (3015/13702)\rUpdating files: 22% (3090/13702)\rUpdating files: 23% (3152/13702)\rUpdating files: 23% (3280/13702)\rUpdating files: 24% (3289/13702)\rUpdating files: 25% (3426/13702)\rUpdating files: 25% (3471/13702)\rUpdating files: 26% (3563/13702)\rUpdating files: 26% (3610/13702)\rUpdating files: 27% (3700/13702)\rUpdating files: 27% (3741/13702)\rUpdating files: 27% (3821/13702)\rUpdating files: 28% (3837/13702)\rUpdating files: 29% (3974/13702)\rUpdating files: 29% (4029/13702)\rUpdating files: 30% (4111/13702)\rUpdating files: 31% (4248/13702)\rUpdating files: 31% (4364/13702)\rUpdating files: 32% (4385/13702)\rUpdating files: 33% (4522/13702)\rUpdating files: 34% (4659/13702)\rUpdating files: 35% (4796/13702)\rUpdating files: 35% (4875/13702)\rUpdating files: 36% (4933/13702)\rUpdating files: 37% (5070/13702)\rUpdating files: 38% (5207/13702)\rUpdating files: 39% (5344/13702)\rUpdating files: 40% (5481/13702)\rUpdating files: 41% (5618/13702)\rUpdating files: 42% (5755/13702)\rUpdating files: 42% (5873/13702)\rUpdating files: 43% (5892/13702)\rUpdating files: 44% (6029/13702)\rUpdating files: 45% (6166/13702)\rUpdating files: 46% (6303/13702)\rUpdating files: 47% (6440/13702)\rUpdating files: 48% (6577/13702)\rUpdating files: 49% (6714/13702)\rUpdating files: 50% (6851/13702)\rUpdating files: 51% (6989/13702)\rUpdating files: 52% (7126/13702)\rUpdating files: 53% (7263/13702)\rUpdating files: 54% (7400/13702)\rUpdating files: 55% (7537/13702)\rUpdating files: 56% (7674/13702)\rUpdating files: 57% (7811/13702)\rUpdating files: 58% (7948/13702)\rUpdating files: 59% (8085/13702)\rUpdating files: 60% (8222/13702)\rUpdating files: 61% (8359/13702)\rUpdating files: 62% (8496/13702)\rUpdating files: 63% (8633/13702)\rUpdating files: 64% (8770/13702)\rUpdating files: 65% (8907/13702)\rUpdating files: 66% (9044/13702)\rUpdating files: 67% (9181/13702)\rUpdating files: 67% (9219/13702)\rUpdating files: 68% (9318/13702)\rUpdating files: 69% (9455/13702)\rUpdating files: 70% (9592/13702)\rUpdating files: 71% (9729/13702)\rUpdating files: 72% (9866/13702)\rUpdating files: 73% (10003/13702)\rUpdating files: 74% (10140/13702)\rUpdating files: 75% (10277/13702)\rUpdating files: 76% (10414/13702)\rUpdating files: 77% (10551/13702)\rUpdating files: 78% (10688/13702)\rUpdating files: 79% (10825/13702)\rUpdating files: 80% (10962/13702)\rUpdating files: 81% (11099/13702)\rUpdating files: 82% (11236/13702)\rUpdating files: 83% (11373/13702)\rUpdating files: 84% (11510/13702)\rUpdating files: 84% (11546/13702)\rUpdating files: 85% (11647/13702)\rUpdating files: 86% (11784/13702)\rUpdating files: 87% (11921/13702)\rUpdating files: 88% (12058/13702)\rUpdating files: 88% (12174/13702)\rUpdating files: 89% (12195/13702)\rUpdating files: 90% (12332/13702)\rUpdating files: 91% (12469/13702)\rUpdating files: 92% (12606/13702)\rUpdating files: 92% (12731/13702)\rUpdating files: 93% (12743/13702)\rUpdating files: 94% (12880/13702)\rUpdating files: 95% (13017/13702)\rUpdating files: 95% (13114/13702)\rUpdating files: 96% (13154/13702)\rUpdating files: 97% (13291/13702)\rUpdating files: 98% (13428/13702)\rUpdating files: 99% (13565/13702)\rUpdating files: 100% (13702/13702)\rUpdating files: 100% (13702/13702), done.\n cluster.go:125: Note: switching to 'lts-4081.3.10-nightly-20261022-2100'.\n cluster.go:125: \n cluster.go:125: You are in 'detached HEAD' state. You can look around, make experimental\n cluster.go:125: changes and commit them, and you can discard any commits you make in this\n cluster.go:125: state without impacting any branches by switching back to a branch.\n cluster.go:125: \n cluster.go:125: If you want to create a new branch to retain commits you create, you may\n cluster.go:125: do so (now or later) by using -c with the switch command. Example:\n cluster.go:125: \n cluster.go:125: git switch -c \u003cnew-branch-name\u003e\n cluster.go:125: \n cluster.go:125: Or undo this operation with:\n cluster.go:125: \n cluster.go:125: git switch -\n cluster.go:125: \n cluster.go:125: Turn off this advice by setting config variable advice.detachedHead to false\n cluster.go:125: \n cluster.go:125: HEAD is now at 41503d353d New version: lts-4081.3.10-nightly-20261022-2100\n cluster.go:125: + emerge --getbinpkg --verbose coreos-sources\n cluster.go:125: \n cluster.go:125: !!! Your current profile is deprecated and not supported anymore.\n cluster.go:125: !!! Use eselect profile to update your profile.\n cluster.go:125: !!! Please upgrade to the following profile if possible:\n cluster.go:125: \n cluster.go:125: default/linux/amd64/23.0/split-usr/no-multilib/hardened\n cluster.go:125: \n cluster.go:125: To upgrade do the following steps:\n cluster.go:125: \n cluster.go:125: A profile upgrade to version 23.0 is available for your architecture.\n cluster.go:125: The new 23.0 profiles enable some toolchain hardening features and \n cluster.go:125: performance enhancements by default, and standardize settings.\n cluster.go:125: You can find the list of changes on the wiki tracking page [1].\n cluster.go:125: \n cluster.go:125: Upgrade instructions\n cluster.go:125: \n cluster.go:125: Note 1: If you have manually changed your CHOST to a value different from \n cluster.go:125: what the stages and profiles set, you may have to do that in the future too.\n cluster.go:125: In that case you should know what you are doing, hopefully; please read the \n cluster.go:125: instructions with a critical eye then.\n cluster.go:125: \n cluster.go:125: Note 2: In case you are already familiar with binary packages, you should be\n cluster.go:125: able to add \"--getbinpkg\" to the emerge calls to speed things up.\n cluster.go:125: The use of binary packages is completely optional though, and also not\n cluster.go:125: as much tested as the source-based upgrade path yet.\n cluster.go:125: \n cluster.go:125: 1. Ensure your system backups are up to date. Please also update\n cluster.go:125: your system fully and depclean before proceeding.\n cluster.go:125: glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.\n cluster.go:125: \n cluster.go:125: 2. If you are still using one of the long-deprecated amd64 17.0 profiles \n cluster.go:125: (other than x32 or musl), then first complete the migration to the \n cluster.go:125: corresponding 17.1 profile. Instructions can be found at [3].\n cluster.go:125: \n cluster.go:125: 3. If you are currently using systemd in a split-usr configuration, then first \n cluster.go:125: complete the migration to the corresponding merged-usr profile of the \n cluster.go:125: same profile version. Details on how to do this can be found in the news \n cluster.go:125: item [4].\n cluster.go:125: If you are currently using openrc, migrate to 23.0 first, keeping your disk\n cluster.go:125: layout. If you want to move from split-usr to merged-usr, do that afterwards.\n cluster.go:125: \n cluster.go:125: 4. Run \"emerge --info\" and note down the value of the CHOST variable.\n cluster.go:125: \n cluster.go:125: 5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,\n cluster.go:125: remove it. Also delete all lines defining CHOST_... variables.\n cluster.go:125: \n cluster.go:125: 6. Select the 23.0 profile corresponding to your current profile, either using\n cluster.go:125: \"eselect profile\" or by manually setting the profile symlink.\n cluster.go:125: Note that old profiles are by default split-usr and the 23.0 profiles by\n cluster.go:125: default merged-usr. Do NOT change directory scheme now, since this will\n cluster.go:125: mess up your system! \n cluster.go:125: Instead, make sure that the new profile has the same property: for example, \n cluster.go:125: OLD default/linux/amd64/17.1 \n cluster.go:125: ==\u003e NEW default/linux/amd64/23.0/split-usr\n cluster.go:125: (added \"split-usr\")\n cluster.go:125: OLD default/linux/amd64/17.1/systemd/merged-usr \n cluster.go:125: ==\u003e NEW default/linux/amd64/23.0/systemd\n cluster.go:125: (removed \"merged-usr\")\n cluster.go:125: A detailed table of the upgrade paths can be found at [5]. Please consult it.\n cluster.go:125: In some cases (hppa, x86) the table will tell you to pick between two choices. \n cluster.go:125: What you need should be obvious from your *old* CHOST value (from step 4).\n cluster.go:125: \n cluster.go:125: 7. Delete the contents of your binary package cache at ${PKGDIR}\n cluster.go:125: rm -r /var/cache/binpkgs/*\n cluster.go:125: \n cluster.go:125: 8. In the file or directory /etc/portage/binrepos.conf (if existing), update\n cluster.go:125: the URI in all configuration such that they point to 23.0 profile binhost \n cluster.go:125: directories. The exact paths can be found in the table at [5], too.\n cluster.go:125: \n cluster.go:125: 9. Rebuild or reinstall from binary (if available) the following packages in\n cluster.go:125: this order, with the same version as already active:\n cluster.go:125: emerge --ask --oneshot sys-devel/binutils\n cluster.go:125: (you may have to run binutils-config and re-select your binutils now)\n cluster.go:125: emerge --ask --oneshot sys-devel/gcc\n cluster.go:125: (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do \n cluster.go:125: that; instead, abort and try again with --nodeps added to the command line.)\n cluster.go:125: (you may have to run gcc-config and re-select your gcc now)\n cluster.go:125: and the C library, i.e. for glibc-based systems\n cluster.go:125: emerge --ask --oneshot sys-libs/glibc\n cluster.go:125: or for musl-based systems\n cluster.go:125: emerge --ask --oneshot sys-libs/musl\n cluster.go:125: \n cluster.go:125: 10. Re-run \"emerge --info\" and check if CHOST has changed compared to step 4.\n cluster.go:125: \n cluster.go:125: If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, \n cluster.go:125: \n cluster.go:125: 11. Recheck with binutils-config and gcc-config that valid installed versions\n cluster.go:125: of binutils and gcc are selected.\n cluster.go:125: \n cluster.go:125: 12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that\n cluster.go:125: refer to the *OLD* CHOST value, and remove them. \n cluster.go:125: Examples how to do this can be found in the similar procedure at [6].\n cluster.go:125: \n cluster.go:125: 13. Run env-update \u0026\u0026 source /etc/profile\n cluster.go:125: \n cluster.go:125: 14. Re-emerge libtool:\n cluster.go:125: emerge --ask --oneshot libtool\n cluster.go:125: \n cluster.go:125: 15. Just for safety, delete the contents of your binary package cache at \n cluster.go:125: ${PKGDIR} again:\n cluster.go:125: rm -r /var/cache/binpkgs/*\n cluster.go:125: \n cluster.go:125: 16. Rebuild world:\n cluster.go:125: emerge --ask --emptytree @world\n cluster.go:125: \n cluster.go:125: [1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition\n cluster.go:125: [2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline\n cluster.go:125: [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html\n cluster.go:125: [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html\n cluster.go:125: [5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table\n cluster.go:125: [6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work\n cluster.go:125: \n cluster.go:125: \n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: Unable to unshare: EPERM (for FEATURES=\"pid-sandbox\")\n cluster.go:125: + zcat /proc/config.gz\n cluster.go:125: ++ nproc\n cluster.go:125: + exec make -C /usr/src/linux -j4 modules_prepare V=1\n"}],"result":"FAIL","platform":"qemu","version":"4081.3.10"}