{"tests":[{"name":"docker.userns","result":"PASS","duration":54486536968,"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: 2.24MB 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.0s done\n cluster.go:125: #5 writing image sha256:2cd3cd1218c775939774d4b3c2e1ed2e4a45ec01027e86136b2a236a819518ac done\n cluster.go:125: #5 naming to docker.io/library/userns-test done\n cluster.go:125: #5 DONE 0.0s\n"},{"name":"cl.ignition.v1.once","result":"PASS","duration":71992160905,"output":""},{"name":"cl.swap_activation","result":"PASS","duration":30252867049,"output":""},{"name":"linux.ntp","result":"PASS","duration":24078724644,"output":""},{"name":"cl.network.iptables","result":"PASS","duration":23854440675,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base/node_readiness","result":"PASS","duration":11356263627,"output":""},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base/nginx_deployment","result":"PASS","duration":33260900377,"output":""},{"name":"cl.tang.root","result":"PASS","duration":131258107038,"output":" tang.go:148: Started tang on 10.0.0.1:40383\n"},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base/NFS_deployment","result":"PASS","duration":31186059491,"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"},{"name":"kubeadm.v1.35.1.flannel.cgroupv1.base","result":"PASS","duration":220732029459,"output":" cluster.go:125: I0909 00:12:57.037218 1903 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8\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: I0909 00:13:09.210871 2122 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.8\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.156-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: W0909 00:13:09.524316 2122 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.6]\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 506.724453ms\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.6: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 3.135684595s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.159764366s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 6.004105754s\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: jt20al.fgtscq4zww6rjm6x\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.6:6443 --token jt20al.fgtscq4zww6rjm6x \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:6f012a069e8daaa314c89aab91bf150417f86f4946186be7154cd54d13cf165b \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: W0909 00:13:46.373961 1752 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 (11.36s)\n --- PASS: kubeadm.v1.35.1.flannel.cgroupv1.base/nginx_deployment (33.26s)\n --- PASS: kubeadm.v1.35.1.flannel.cgroupv1.base/NFS_deployment (31.19s)\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":"docker.btrfs-storage","result":"PASS","duration":29584616473,"output":""},{"name":"cl.sysext.boot","result":"PASS","duration":133595203064,"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: + echo ID=test\n cluster.go:125: + sudo tee /oem/oem-release\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-20260908-2100.raw /etc/flatcar/oem-sysext/oem-test-1.2.3.raw /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20260908-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-20260908-2100.raw = /oem/sysext/oem-test-4081.3.10+nightly-20260908-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-20260908-2100.raw = /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20260908-2100.raw ']'\n cluster.go:125: + sudo mv /oem/sysext/oem-test-4081.3.10+nightly-20260908-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-20260908-2100.raw = /oem/sysext/oem-test-4081.3.10+nightly-20260908-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-20260908-2100.raw = /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20260908-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-20260908-2100.raw = /oem/sysext/oem-test-4081.3.10+nightly-20260908-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-20260908-2100.raw = /etc/flatcar/sysext/flatcar-myext-4081.3.10+nightly-20260908-2100.raw ']'\n"},{"name":"cl.tpm.root","result":"PASS","duration":100010424175,"output":""},{"name":"coreos.selinux.enforce","result":"PASS","duration":68295025248,"output":""},{"name":"sysext.custom-docker.sysext","result":"PASS","duration":61393355726,"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":"cl.install.cloudinit","result":"PASS","duration":26091541665,"output":""},{"name":"cl.network.wireguard","result":"PASS","duration":24205066275,"output":" cluster.go:152: + ip --json address show kv0 | jq -r '.[] | .addr_info | .[] | select( .family == \"inet\") | .local'\n"},{"name":"cl.disk.raid1.root","result":"PASS","duration":67812087665,"output":""},{"name":"cl.ignition.oem.regular.new","result":"PASS","duration":68195742292,"output":""},{"name":"sysext.custom-oem","result":"PASS","duration":123973719736,"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-20260908-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-20260908-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-20260908-2100\n cluster.go:125: + version=4081.3.10+nightly-20260908-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-20260908-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-20260908-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-20260908-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20260908-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + image_url=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20260908-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-20260908-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-20260908-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-23773\n cluster.go:125: + mkdir -p /home/core/dev-container-workdir-23773\n cluster.go:125: + sudo systemd-nspawn --console=pipe --bind-ro=/home/core/dev-container-script.sh --bind=/home/core/dev-container-workdir-23773:/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-20260908-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20260908-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20260908-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-20260908-2100:*:*:*:*:*:*:*'\n cluster.go:125: ++ echo 4081.3.10+nightly-20260908-2100\n cluster.go:125: + version=4081.3.10+nightly-20260908-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-20260908-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20260908-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20260908-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-20260908-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-20260908-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-20260908-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-20260908-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20260908-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20260908-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-20260908-2100:*:*:*:*:*:*:*'\n cluster.go:125: ++ echo 4081.3.10+nightly-20260908-2100\n cluster.go:125: + version=4081.3.10+nightly-20260908-2100\n cluster.go:125: + sysext_file=/home/core/dev-container-workdir-23773/oem-test-4081.3.10+nightly-20260908-2100.raw\n cluster.go:125: + [[ ! -e /home/core/dev-container-workdir-23773/oem-test-4081.3.10+nightly-20260908-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-23773/oem-test-4081.3.10+nightly-20260908-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\" : 1788909897324956\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\" : 1788909925868852\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\" : 1788913140154306\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\" : 1788913162426000\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\" : 1788909897324956\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\" : 1788909925868852\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\" : 1788913140154306\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\" : 1788913162426000\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\": 1788913140154306\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\": 1788913140154306\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-20260908-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\\0\\9\\0\\8\\-\\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\": 1788913162426000\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\": 1788913162426000\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-20260908-2100\n cluster.go:125: +++ VERSION_ID=4081.3.10\n cluster.go:125: +++ BUILD_ID=nightly-20260908-2100\n cluster.go:125: +++ SYSEXT_LEVEL=1.0\n cluster.go:125: +++ PRETTY_NAME='Flatcar Container Linux by Kinvolk 4081.3.10+nightly-20260908-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-20260908-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.ignition.oem.reuse","result":"PASS","duration":99351051827,"output":""},{"name":"cl.tpm.root-cryptenroll-pcr-noupdate","result":"PASS","duration":210629057469,"output":""},{"name":"coreos.selinux.boolean","result":"PASS","duration":206489090213,"output":""},{"name":"docker.enable-service.sysext","result":"PASS","duration":117953354321,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":118189316232,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/node_readiness","result":"PASS","duration":251048664627,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":188900373409,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/nginx_deployment","result":"PASS","duration":289146297533,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":139616419806,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/NFS_deployment","result":"PASS","duration":198433350437,"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 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:121): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.cilium.base/IPSec_encryption","result":"FAIL","duration":95041682557,"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, \u001b[33m1 warnings\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\nDeployment cilium-operator Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\nDaemonSet cilium Desired: 2, Unavailable: \u001b[31m2/2\u001b[0m\nContainers: cilium Running: \u001b[32m1\u001b[0m, Pending: \u001b[32m1\u001b[0m\n cilium-operator Running: \u001b[32m1\u001b[0m\nCluster Pods: 0/0 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-5jcvd unable to retrieve cilium status: command terminated with exit code 1\n cilium cilium 2 pods of DaemonSet cilium are not ready\nWarnings: cilium cilium-kl2hp pod is pending, status Process exited with status 1\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":1525589188537,"output":" cluster.go:125: I0909 00:21:42.188596 1829 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I0909 00:22:30.421114 2130 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.4\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0909 00:22:30.768236 2130 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: W0909 00:22:31.491364 2130 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.26]\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 81.429673ms\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.26: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 286.610514ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 392.302777ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 32.526734777s\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: fqxrkt.ugk6w69pdpg1hgsd\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.26:6443 --token fqxrkt.ugk6w69pdpg1hgsd \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:96fd3e88ce3a5dc88ed932e18102eb28b35c8e1afd5cdb63e11d9fb3e177e992 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/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 Running: \u001b[32m1\u001b[0m\n cluster.go:125: cilium-operator Running: \u001b[32m1\u001b[0m\n cluster.go:125: Cluster Pods: 2/2 managed by Cilium\n cluster.go:125: Image versions cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1\n cluster.go:125: cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\n cluster.go:125: W0909 00:30:38.643474 1705 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0909 00:30:39.453371 1705 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: W0909 00:30:43.439501 1705 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.cilium.base/node_readiness (251.05s)\n --- PASS: kubeadm.v1.36.1.cilium.base/nginx_deployment (289.15s)\n --- PASS: kubeadm.v1.36.1.cilium.base/NFS_deployment (198.43s)\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: 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:121): Cannot iterate over null (null)\n --- FAIL: kubeadm.v1.36.1.cilium.base/IPSec_encryption (95.04s)\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, \u001b[33m1 warnings\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 Deployment cilium-operator Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n DaemonSet cilium Desired: 2, Unavailable: \u001b[31m2/2\u001b[0m\n Containers: cilium Running: \u001b[32m1\u001b[0m, Pending: \u001b[32m1\u001b[0m\n cilium-operator Running: \u001b[32m1\u001b[0m\n Cluster Pods: 0/0 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-5jcvd unable to retrieve cilium status: command terminated with exit code 1\n cilium cilium 2 pods of DaemonSet cilium are not ready\n Warnings: cilium cilium-kl2hp pod is pending, status Process exited with status 1\n"},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":250419670422,"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 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"},{"name":"kubeadm.v1.35.1.flannel.base","result":"PASS","duration":1484957501529,"output":" cluster.go:125: I0909 00:25:30.827254 1794 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8\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: I0909 00:27:21.400429 2093 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.8\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: W0909 00:27:34.274586 2093 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.28]\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.038934908s\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.28: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 29.594047451s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 51.210787217s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2m55.668629447s\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: lye6ne.p4g91v4anjd3isi4\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.28:6443 --token lye6ne.p4g91v4anjd3isi4 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:3c8e2fbac327ad42f3bad9efbed4291b57d3b66c5037eb0f9259d913ed3e4361 \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: W0909 00:34:57.607633 1631 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 (188.90s)\n --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (139.62s)\n --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (250.42s)\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"},{"name":"packages/sys-cluster/ipvsadm","result":"PASS","duration":1866858572,"output":""},{"name":"cl.misc.falco","result":"PASS","duration":1152936959360,"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: dbaa5c62f0ed: Pulling fs layer\n cluster.go:125: 3a9e2cc66ed6: Pulling fs layer\n cluster.go:125: a877d6bc7973: Pulling fs layer\n cluster.go:125: 377af4312b2a: Pulling fs layer\n cluster.go:125: 1f4307240b49: Pulling fs layer\n cluster.go:125: 92a619a21102: Pulling fs layer\n cluster.go:125: e74027f1681c: Pulling fs layer\n cluster.go:125: 7c1ca9c00aa9: Pulling fs layer\n cluster.go:125: 1f4307240b49: Waiting\n cluster.go:125: 92a619a21102: Waiting\n cluster.go:125: e74027f1681c: Waiting\n cluster.go:125: 377af4312b2a: Waiting\n cluster.go:125: 7c1ca9c00aa9: Waiting\n cluster.go:125: 3a9e2cc66ed6: Verifying Checksum\n cluster.go:125: 3a9e2cc66ed6: Download complete\n cluster.go:125: dbaa5c62f0ed: Verifying Checksum\n cluster.go:125: dbaa5c62f0ed: Download complete\n cluster.go:125: 377af4312b2a: Verifying Checksum\n cluster.go:125: 377af4312b2a: Download complete\n cluster.go:125: 1f4307240b49: Verifying Checksum\n cluster.go:125: 1f4307240b49: Download complete\n cluster.go:125: e74027f1681c: Verifying Checksum\n cluster.go:125: e74027f1681c: Download complete\n cluster.go:125: 7c1ca9c00aa9: Verifying Checksum\n cluster.go:125: 7c1ca9c00aa9: Download complete\n cluster.go:125: a877d6bc7973: Verifying Checksum\n cluster.go:125: a877d6bc7973: Download complete\n cluster.go:125: 92a619a21102: Verifying Checksum\n cluster.go:125: 92a619a21102: Download complete\n cluster.go:125: dbaa5c62f0ed: Pull complete\n cluster.go:125: 3a9e2cc66ed6: Pull complete\n cluster.go:125: a877d6bc7973: Pull complete\n cluster.go:125: 377af4312b2a: Pull complete\n cluster.go:125: 1f4307240b49: Pull complete\n cluster.go:125: 92a619a21102: Pull complete\n cluster.go:125: e74027f1681c: Pull complete\n cluster.go:125: 7c1ca9c00aa9: Pull complete\n cluster.go:125: Digest: sha256:7c9c2cdde28df7fe6244eb25533420f9310a84db35109956962f8e9431ffe1e2\n cluster.go:125: Status: Downloaded newer image for falcosecurity/falco-driver-loader:master\n"},{"name":"cl.tpm.root-cryptenroll","result":"PASS","duration":95849550357,"output":""},{"name":"packages/sys-block/open-iscsi","result":"PASS","duration":65568437147,"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":109746493056,"output":" --- PASS: packages/sys-cluster/ipvsadm (1.87s)\n --- PASS: packages/sys-block/open-iscsi (65.57s)\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":"misc.fips","result":"PASS","duration":43466240607,"output":" cluster.go:125: Error setting digest\n cluster.go:125: 4087E4E6AB7F0000: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: 4087E4E6AB7F0000: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.sysext.fallbackdownload","result":"PASS","duration":55005580572,"output":" update.go:664: Rebooting test machine\n"},{"name":"coreos.ignition.groups","result":"PASS","duration":26445701224,"output":""},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":25967135568,"output":""},{"name":"cl.ignition.oem.regular","result":"FAIL","duration":63389297130,"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 aec687c4-80da-4935-b287-ac2256697246 console\n"},{"name":"cl.ignition.kargs","result":"PASS","duration":75218997088,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"cl.etcd-member.discovery","result":"PASS","duration":97494725368,"output":""},{"name":"cl.ignition.oem.wipe","result":"PASS","duration":34612986659,"output":""},{"name":"cl.ignition.v1.users","result":"PASS","duration":25905276239,"output":""},{"name":"cl.flannel.vxlan","result":"PASS","duration":199651417070,"output":" flannel.go:121: ping from ddd56f73-5980-4a84-8950-d4fdd898058e(10.254.84.0) to 9a735145-fa37-42b7-8dfd-643f00b887d3(10.254.17.0)\n"},{"name":"cl.overlay.cleanup","result":"PASS","duration":75513783219,"output":""},{"name":"coreos.ignition.resource.local","result":"PASS","duration":126604273911,"output":""},{"name":"cl.osreset.ignition-rerun","result":"PASS","duration":157541246829,"output":""},{"name":"cl.omaha.ping","result":"PASS","duration":64442133256,"output":""},{"name":"sysext.simple","result":"PASS","duration":212809574050,"output":""},{"name":"kubeadm.v1.35.1.calico.base/node_readiness","result":"PASS","duration":292138539876,"output":""},{"name":"systemd.sysusers.gshadow","result":"PASS","duration":226050728383,"output":""},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":402458315658,"output":""},{"name":"kubeadm.v1.35.1.calico.base/nginx_deployment","result":"FAIL","duration":648901865757,"output":" kubeadm.go:232: nginx is not deployed: ready replicas should be equal to 1: null\n"},{"name":"cl.disk.raid0.data","result":"PASS","duration":502218433069,"output":""},{"name":"kubeadm.v1.35.1.calico.base/NFS_deployment","result":"FAIL","duration":591133373185,"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 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: 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 kubeadm.go:264: nginx pod with NFS is not deployed: getting container status: Process exited with status 5\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":2094926059872,"output":" cluster.go:125: I0909 00:53:59.564800 1813 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8\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: I0909 00:54:49.432121 2092 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.8\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: W0909 00:54:51.046837 2092 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.53]\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.564076715s\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.53: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 16.651436443s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 32.433192054s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 58.054876556s\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: kjskmm.rjwwtjf9nisll3gj\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.53:6443 --token kjskmm.rjwwtjf9nisll3gj \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:604ed01ab5c188ccd9a8e75aef95e93909f4d9c8bdc5234dd741c142e55c6cb4 \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0909 00:58:53.155248 1690 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.calico.base/node_readiness (292.14s)\n --- FAIL: kubeadm.v1.35.1.calico.base/nginx_deployment (648.90s)\n kubeadm.go:232: nginx is not deployed: ready replicas should be equal to 1: null\n --- FAIL: kubeadm.v1.35.1.calico.base/NFS_deployment (591.13s)\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: 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 kubeadm.go:264: nginx pod with NFS is not deployed: getting container status: Process exited with status 5\n"},{"name":"devcontainer.docker","result":"PASS","duration":2325394622456,"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-20260908-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-20260908-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-20260908-2100\n cluster.go:125: + version=4081.3.10+nightly-20260908-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-20260908-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-20260908-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-20260908-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20260908-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + image_url=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20260908-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-20260908-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-20260908-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-20260908-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-20260908-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs amd64 4081.3.10+nightly-20260908-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-20260908-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-20260908-2100/pkgs\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-2100/pkgs\n cluster.go:125: + EXPECTED_VERSION=4081.3.10+nightly-20260908-2100\n cluster.go:125: + workdir=/home/core/dev-container-workdir-27361\n cluster.go:125: + USR_SRC_DIR=/home/core/dev-container-workdir-27361/src\n cluster.go:125: + VAR_TMP_DIR=/home/core/dev-container-workdir-27361/tmp\n cluster.go:125: + mkdir -p /home/core/dev-container-workdir-27361/src /home/core/dev-container-workdir-27361/tmp\n cluster.go:125: ++ parted flatcar_developer_container.bin unit b print\n cluster.go:125: ++ tail --lines=1\n cluster.go:125: ++ grep Start --after-context=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-20260908-2100/pkgs --env EXPECTED_VERSION=4081.3.10+nightly-20260908-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-27361/src,target=/usr/src --mount type=bind,source=/home/core/dev-container-workdir-27361/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-20260908-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-20260908-2100 != \\4\\0\\8\\1\\.\\3\\.\\1\\0\\+\\n\\i\\g\\h\\t\\l\\y\\-\\2\\0\\2\\6\\0\\9\\0\\8\\-\\2\\1\\0\\0 ]]\n cluster.go:125: + export PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-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: 44% (6076/13622)\rUpdating files: 45% (6130/13622)\rUpdating files: 46% (6267/13622)\rUpdating files: 47% (6403/13622)\rUpdating files: 48% (6539/13622)\rUpdating files: 49% (6675/13622)\rUpdating files: 50% (6811/13622)\rUpdating files: 51% (6948/13622)\rUpdating files: 52% (7084/13622)\rUpdating files: 53% (7220/13622)\rUpdating files: 54% (7356/13622)\rUpdating files: 55% (7493/13622)\rUpdating files: 56% (7629/13622)\rUpdating files: 57% (7765/13622)\rUpdating files: 58% (7901/13622)\rUpdating files: 59% (8037/13622)\rUpdating files: 60% (8174/13622)\rUpdating files: 61% (8310/13622)\rUpdating files: 62% (8446/13622)\rUpdating files: 63% (8582/13622)\rUpdating files: 64% (8719/13622)\rUpdating files: 65% (8855/13622)\rUpdating files: 66% (8991/13622)\rUpdating files: 67% (9127/13622)\rUpdating files: 68% (9263/13622)\rUpdating files: 69% (9400/13622)\rUpdating files: 70% (9536/13622)\rUpdating files: 71% (9672/13622)\rUpdating files: 72% (9808/13622)\rUpdating files: 73% (9945/13622)\rUpdating files: 73% (10006/13622)\rUpdating files: 74% (10081/13622)\rUpdating files: 75% (10217/13622)\rUpdating files: 76% (10353/13622)\rUpdating files: 77% (10489/13622)\rUpdating files: 78% (10626/13622)\rUpdating files: 79% (10762/13622)\rUpdating files: 80% (10898/13622)\rUpdating files: 81% (11034/13622)\rUpdating files: 82% (11171/13622)\rUpdating files: 83% (11307/13622)\rUpdating files: 84% (11443/13622)\rUpdating files: 85% (11579/13622)\rUpdating files: 86% (11715/13622)\rUpdating files: 87% (11852/13622)\rUpdating files: 88% (11988/13622)\rUpdating files: 89% (12124/13622)\rUpdating files: 90% (12260/13622)\rUpdating files: 91% (12397/13622)\rUpdating files: 92% (12533/13622)\rUpdating files: 93% (12669/13622)\rUpdating files: 94% (12805/13622)\rUpdating files: 95% (12941/13622)\rUpdating files: 96% (13078/13622)\rUpdating files: 97% (13214/13622)\rUpdating files: 98% (13350/13622)\rUpdating files: 99% (13486/13622)\rUpdating files: 100% (13622/13622)\rUpdating files: 100% (13622/13622), done.\n cluster.go:125: Note: switching to 'lts-4081.3.10-nightly-20260908-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 f39187863e New version: lts-4081.3.10-nightly-20260908-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"},{"name":"cl.tpm.root-cryptenroll-pcr-withupdate","result":"PASS","duration":194958689364,"output":" cluster.go:125: New TPM2 token enrolled as key slot 1.\n cluster.go:125: Wiped slot 2.\n"},{"name":"cl.update.reboot","result":"PASS","duration":49267435631,"output":""},{"name":"cl.filesystem/deadlinks","result":"PASS","duration":1539404963,"output":""},{"name":"cl.filesystem/suid","result":"PASS","duration":241024275,"output":""},{"name":"cl.filesystem/sgid","result":"PASS","duration":224250197,"output":""},{"name":"cl.filesystem/writablefiles","result":"PASS","duration":285263660,"output":""},{"name":"cl.filesystem/writabledirs","result":"PASS","duration":175941513,"output":""},{"name":"cl.filesystem/stickydirs","result":"PASS","duration":208827835,"output":""},{"name":"cl.filesystem/blacklist","result":"PASS","duration":238286125,"output":""},{"name":"cl.filesystem","result":"PASS","duration":25238719377,"output":" --- PASS: cl.filesystem/deadlinks (1.54s)\n --- PASS: cl.filesystem/suid (0.24s)\n --- PASS: cl.filesystem/sgid (0.22s)\n --- PASS: cl.filesystem/writablefiles (0.29s)\n --- PASS: cl.filesystem/writabledirs (0.18s)\n --- PASS: cl.filesystem/stickydirs (0.21s)\n --- PASS: cl.filesystem/blacklist (0.24s)\n"},{"name":"coreos.ignition.sethostname","result":"PASS","duration":23621171494,"output":""},{"name":"cl.verity/verify","result":"PASS","duration":3161670830,"output":" cluster.go:125: Success\n"},{"name":"coreos.ignition.systemd.enable-service","result":"PASS","duration":24853205741,"output":""},{"name":"cl.update.badverity","result":"PASS","duration":411308223881,"output":""},{"name":"cl.ignition.translation","result":"PASS","duration":25056734465,"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":"systemd.journal.user","result":"PASS","duration":23432584306,"output":""},{"name":"cl.tang.nonroot","result":"PASS","duration":66435869352,"output":" tang.go:148: Started tang on 10.0.0.1:38551\n"},{"name":"cl.ignition.oem.indirect","result":"PASS","duration":48349494421,"output":""},{"name":"cl.verity/corruption","result":"PASS","duration":169043190365,"output":""},{"name":"cl.verity","result":"PASS","duration":196697878770,"output":" --- PASS: cl.verity/verify (3.16s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (169.04s)\n"},{"name":"coreos.ignition.security.tls","result":"PASS","duration":54236703910,"output":""},{"name":"cl.ignition.oem.indirect.new","result":"PASS","duration":45141388780,"output":""},{"name":"sysext.disable-docker","result":"PASS","duration":23532374996,"output":""},{"name":"coreos.ignition.once","result":"PASS","duration":49029095417,"output":""},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":24925734615,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":26980296085,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"PASS","duration":21693192209,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"PASS","duration":25037640673,"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"},{"name":"cl.locksmith.cluster","result":"PASS","duration":384834298936,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"PASS","duration":49933118960,"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.35.1.cilium.base","result":"PASS","duration":211297199600,"output":" cluster.go:125: I0909 01:33:28.368398 1811 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8\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: I0909 01:33:34.622330 2025 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.8\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: W0909 01:33:34.767759 2025 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.84]\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 500.917169ms\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.84:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.504360055s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.809141173s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.501408733s\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: gblqrd.1fi3rj2wlendudkd\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.84:6443 --token gblqrd.1fi3rj2wlendudkd \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:54df23f53a2922d0a6a9e327895b355a3970d2d4410117538d870afc8bfeb908 \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: W0909 01:34:04.928512 1642 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 (26.98s)\n --- PASS: kubeadm.v1.35.1.cilium.base/nginx_deployment (21.69s)\n --- PASS: kubeadm.v1.35.1.cilium.base/NFS_deployment (25.04s)\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.35.1.cilium.base/IPSec_encryption (49.93s)\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":"cl.ignition.partition_on_boot_disk","result":"PASS","duration":31608547933,"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 6F4B-31DE \n|-vda2 \n|-vda3 btrfs 13432187-b880-4b47-bdce-be56db9cec0d \n| `-usr btrfs 13432187-b880-4b47-bdce-be56db9cec0d /usr\n|-vda4 \n|-vda6 btrfs OEM ed838769-4fc0-46de-b087-2dfda5f8d87e 123M 1% /oem\n|-vda7 \n|-vda9 ext4 1.0 ROOT d692b4dc-4932-4822-afe4-a8f6636b0737 5.9G 0% /\n`-vda10 xfs VAR faf2e0ac-c49a-4406-b77e-4000ca56916c 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=3029\n|-/media tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,seclabel\n|-/tmp tmpfs tmpfs rw,nosuid,nodev,seclabel,nr_inodes=1048576\n|-/dev devtmpfs devtmpfs rw,nosuid,seclabel,size=4096k,nr_inodes=299730,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/firmware/efi/efivars efivarfs efivarfs rw,nosuid,nodev,noexec,relatime\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=3033\n|-/run tmpfs tmpfs rw,nosuid,nodev,seclabel,size=494360k,nr_inodes=819200,mode=755\n| `-/run/user/500 tmpfs tmpfs rw,nosuid,nodev,relatime,seclabel,size=247180k,nr_inodes=61795,mode=700,uid=500,gid=500\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":"kubeadm.v1.35.1.cilium.cgroupv1.base/node_readiness","result":"PASS","duration":40694300759,"output":""},{"name":"kubeadm.v1.35.1.cilium.cgroupv1.base/nginx_deployment","result":"PASS","duration":39350428973,"output":""},{"name":"kubeadm.v1.35.1.cilium.cgroupv1.base/NFS_deployment","result":"PASS","duration":40551578184,"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":"cl.ignition.v2_1.ext4checkexisting","result":"PASS","duration":182590011205,"output":""},{"name":"kubeadm.v1.35.1.cilium.cgroupv1.base/IPSec_encryption","result":"PASS","duration":59513692355,"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":"cl.ignition.v1.xfsroot","result":"PASS","duration":35834917732,"output":""},{"name":"kubeadm.v1.35.1.cilium.cgroupv1.base","result":"PASS","duration":402542601035,"output":" cluster.go:125: I0909 01:34:34.727865 1953 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8\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: I0909 01:34:49.017137 2195 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.8\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.156-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: W0909 01:34:49.759864 2195 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.88]\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.00750671s\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.88: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 2.01179289s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.461920091s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 12.043148909s\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: gcpl7h.ccy2xps5cb7kzm52\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.88:6443 --token gcpl7h.ccy2xps5cb7kzm52 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:5270826d443086f886dd700be72d5a6fdee5121d8c854c24fbb19886f0a00194 \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: ? Restarting unmanaged pods...\n cluster.go:125: ? Restarted unmanaged pod kube-system/coredns-7d764666f9-fs7xv\n cluster.go:125: ? Restarted unmanaged pod kube-system/coredns-7d764666f9-tdhxx\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 Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: DaemonSet cilium Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: Containers: cilium Running: \u001b[32m1\u001b[0m\n cluster.go:125: cilium-operator Running: \u001b[32m1\u001b[0m\n cluster.go:125: Cluster Pods: 2/2 managed by Cilium\n cluster.go:125: Image versions cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1\n cluster.go:125: cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\n cluster.go:125: W0909 01:37:12.755074 1798 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.cilium.cgroupv1.base/node_readiness (40.69s)\n --- PASS: kubeadm.v1.35.1.cilium.cgroupv1.base/nginx_deployment (39.35s)\n --- PASS: kubeadm.v1.35.1.cilium.cgroupv1.base/NFS_deployment (40.55s)\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.35.1.cilium.cgroupv1.base/IPSec_encryption (59.51s)\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":"kubeadm.v1.37.0.flannel.base/node_readiness","result":"PASS","duration":30364328079,"output":""},{"name":"kubeadm.v1.37.0.flannel.base/nginx_deployment","result":"PASS","duration":11902927547,"output":""},{"name":"kubeadm.v1.37.0.flannel.base/NFS_deployment","result":"PASS","duration":12421855609,"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":"cl.ignition.symlink","result":"PASS","duration":25212629569,"output":" cluster.go:152: + readlink /etc/localtime\n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"PASS","duration":273549096333,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.0\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0909 01:38:23.475036 1959 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: W0909 01:38:24.084308 1959 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.93]\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.396381ms\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.93: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 15.324519ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 38.799095ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.027695483s\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: 0sipmf.fp2jwii9ulwfm5hc\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.93:6443 --token 0sipmf.fp2jwii9ulwfm5hc \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:14b3fa5d0192c426e7e85d73dc7456ca2d38bb701484be56e96a9cd2e2e3a6c4 \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: W0909 01:39:43.138987 1613 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0909 01:39:43.444960 1613 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.flannel.base/node_readiness (30.36s)\n --- PASS: kubeadm.v1.37.0.flannel.base/nginx_deployment (11.90s)\n --- PASS: kubeadm.v1.37.0.flannel.base/NFS_deployment (12.42s)\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.luks","result":"PASS","duration":32835359533,"output":""},{"name":"systemd.journal.remote","result":"PASS","duration":47981338843,"output":" cluster.go:125: Running as unit: systemd-journal-remote-client.service; invocation ID: 4f114b9daf154209b53a9dba45d3d428\n"},{"name":"docker.containerd-restart","result":"PASS","duration":81133700782,"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"},{"name":"cl.disk.raid1.data","result":"PASS","duration":47696672298,"output":""},{"name":"cl.tpm.nonroot","result":"PASS","duration":134901480926,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":34926292827,"output":""},{"name":"cl.cloudinit.multipart-mime","result":"PASS","duration":30876173829,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":111394436020,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":221314088126,"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 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: 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"},{"name":"kubeadm.v1.36.1.flannel.base","result":"PASS","duration":525170456622,"output":" cluster.go:125: I0909 01:42:29.473138 1802 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I0909 01:42:38.283188 2020 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.4\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0909 01:42:38.341629 2020 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: W0909 01:42:38.505856 2020 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.105]\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 7.345978ms\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.105: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 10.951789ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 13.2624ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.005642893s\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: a5ermy.dqpm9lo4beg7vw1z\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.105:6443 --token a5ermy.dqpm9lo4beg7vw1z \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:2ff5c6dddeace430b3f6a54f053065aeef98720bb1c94502a296696a2502dd7e \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: W0909 01:44:01.482129 1610 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0909 01:44:01.570527 1610 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: W0909 01:44:02.157840 1610 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 (34.93s)\n --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (111.39s)\n --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (221.31s)\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: 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"},{"name":"kubeadm.v1.36.1.calico.base/node_readiness","result":"PASS","duration":266344548652,"output":""},{"name":"cl.ignition.v1.btrfsroot","result":"PASS","duration":45413878056,"output":""},{"name":"kubeadm.v1.36.1.calico.base/nginx_deployment","result":"PASS","duration":81969084236,"output":""},{"name":"kubeadm.v1.36.1.calico.base/NFS_deployment","result":"PASS","duration":156245738211,"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 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"},{"name":"kubeadm.v1.36.1.calico.base","result":"PASS","duration":766983104277,"output":" cluster.go:125: I0909 01:42:40.274839 1804 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.4\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I0909 01:42:54.067891 2041 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.4\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0909 01:42:54.183943 2041 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: W0909 01:42:54.544482 2041 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.107]\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 5.128905ms\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.107: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 51.859459ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 57.982504ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 6.528584141s\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: p7zs89.ds6sbcanjdps2861\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.107:6443 --token p7zs89.ds6sbcanjdps2861 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:b539a2d19de65aba999669409a43683b49531cfa0dcefe3e0e71b94ae94a7442 \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0909 01:45:23.167119 1682 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0909 01:45:23.713913 1682 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: W0909 01:45:26.667575 1682 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.calico.base/node_readiness (266.34s)\n --- PASS: kubeadm.v1.36.1.calico.base/nginx_deployment (81.97s)\n --- PASS: kubeadm.v1.36.1.calico.base/NFS_deployment (156.25s)\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"},{"name":"cl.cloudinit.basic","result":"PASS","duration":31418329397,"output":""},{"name":"docker.lib-coreos-dockerd-compat/docker-info","result":"PASS","duration":1294077652,"output":""},{"name":"docker.lib-coreos-dockerd-compat/resources","result":"PASS","duration":3256364848,"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: 2.20MB 0.0s done\n cluster.go:125: #3 DONE 0.0s\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:4032ca0af55ad4e0f4cc83affd44df0e5c6566cfd880b697e7fe4762b881f97a done\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.0s\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":"kubeadm.v1.37.0.calico.base/node_readiness","result":"PASS","duration":24760106082,"output":""},{"name":"kubeadm.v1.37.0.calico.base/nginx_deployment","result":"PASS","duration":12409816460,"output":""},{"name":"kubeadm.v1.37.0.calico.base/NFS_deployment","result":"PASS","duration":33279884474,"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"},{"name":"kubeadm.v1.37.0.calico.base","result":"PASS","duration":409706705585,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.0\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0909 01:55:20.607110 1955 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: W0909 01:55:20.787019 1955 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.115]\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 867.461µs\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.115: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.244581ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 6.986253ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.502102067s\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: y0zc6d.2wkaugkfxngj1fwb\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.115:6443 --token y0zc6d.2wkaugkfxngj1fwb \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:121684a6279f407cc4fe441900db77f158170ce98868d2a962885f8a16878d2a \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0909 01:56:35.962354 1659 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0909 01:56:36.041134 1659 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.calico.base/node_readiness (24.76s)\n --- PASS: kubeadm.v1.37.0.calico.base/nginx_deployment (12.41s)\n --- PASS: kubeadm.v1.37.0.calico.base/NFS_deployment (33.28s)\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":"docker.base/docker-info","result":"PASS","duration":3246578963,"output":""},{"name":"docker.base/resources","result":"PASS","duration":6793647236,"output":" cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 78B 0.0s\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.20MB 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.1s done\n cluster.go:125: #5 writing image sha256:ee3e1d22c5ddf78664b4562b861e915b2d3e578fea230b338d2781a7562f8a4e 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.lib-coreos-dockerd-compat/networks-reliably","result":"PASS","duration":200353056713,"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.0s\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.0s done\n cluster.go:125: #5 writing image sha256:f84efc4223ffb06b48fbde433606acc0b3f4d4e8a7d6e5ee1156eb38ad2ee2d3 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":3130219979,"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:\n cluster.go:125: #2 transferring context: 2B 0.0s 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: 5.06MB 0.1s 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.1s done\n cluster.go:125: #5 writing image sha256:f9e7b913fb8ae45d24d768e246d4e18e0baccb8ce490df3f6e14e0cfec1f7363\n cluster.go:125: #5 writing image sha256:f9e7b913fb8ae45d24d768e246d4e18e0baccb8ce490df3f6e14e0cfec1f7363 done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/ownership","result":"PASS","duration":20836090767,"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: 2e19782d7109: Pulling fs layer\n cluster.go:125: 0b08cd0de4e0: Pulling fs layer\n cluster.go:125: 28c7fd8ab61c: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Pulling fs layer\n cluster.go:125: 7803ef1d418e: Pulling fs layer\n cluster.go:125: 0525b6a65f36: Pulling fs layer\n cluster.go:125: 887ef3017df6: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Waiting\n cluster.go:125: 7803ef1d418e: Waiting\n cluster.go:125: 0525b6a65f36: Waiting\n cluster.go:125: 887ef3017df6: Waiting\n cluster.go:125: 28c7fd8ab61c: Verifying Checksum\n cluster.go:125: 28c7fd8ab61c: Download complete\n cluster.go:125: c04b8fd1dd8d: Verifying Checksum\n cluster.go:125: c04b8fd1dd8d: Download complete\n cluster.go:125: 0b08cd0de4e0: Verifying Checksum\n cluster.go:125: 0b08cd0de4e0: Download complete\n cluster.go:125: 2e19782d7109: Verifying Checksum\n cluster.go:125: 2e19782d7109: Download complete\n cluster.go:125: 7803ef1d418e: Verifying Checksum\n cluster.go:125: 7803ef1d418e: Download complete\n cluster.go:125: 0525b6a65f36: Download complete\n cluster.go:125: 887ef3017df6: Verifying Checksum\n cluster.go:125: 887ef3017df6: Download complete\n cluster.go:125: 2e19782d7109: Pull complete\n cluster.go:125: 0b08cd0de4e0: Pull complete\n cluster.go:125: 28c7fd8ab61c: Pull complete\n cluster.go:125: c04b8fd1dd8d: Pull complete\n cluster.go:125: 7803ef1d418e: Pull complete\n cluster.go:125: 0525b6a65f36: Pull complete\n cluster.go:125: 887ef3017df6: Pull complete\n cluster.go:125: Digest: sha256:e68933b249335b5a57ee334d1d621e5e881d280ed29fdcadfbaa34b963a52a01\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"PASS","duration":254943979818,"output":" --- PASS: docker.lib-coreos-dockerd-compat/docker-info (1.29s)\n --- PASS: docker.lib-coreos-dockerd-compat/resources (3.26s)\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: 2.20MB 0.0s done\n cluster.go:125: #3 DONE 0.0s\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:4032ca0af55ad4e0f4cc83affd44df0e5c6566cfd880b697e7fe4762b881f97a done\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.0s\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 (200.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.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.0s\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.0s done\n cluster.go:125: #5 writing image sha256:f84efc4223ffb06b48fbde433606acc0b3f4d4e8a7d6e5ee1156eb38ad2ee2d3 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 (3.13s)\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 0.0s 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: 5.06MB 0.1s 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.1s done\n cluster.go:125: #5 writing image sha256:f9e7b913fb8ae45d24d768e246d4e18e0baccb8ce490df3f6e14e0cfec1f7363\n cluster.go:125: #5 writing image sha256:f9e7b913fb8ae45d24d768e246d4e18e0baccb8ce490df3f6e14e0cfec1f7363 done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.lib-coreos-dockerd-compat/ownership (20.84s)\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: 2e19782d7109: Pulling fs layer\n cluster.go:125: 0b08cd0de4e0: Pulling fs layer\n cluster.go:125: 28c7fd8ab61c: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Pulling fs layer\n cluster.go:125: 7803ef1d418e: Pulling fs layer\n cluster.go:125: 0525b6a65f36: Pulling fs layer\n cluster.go:125: 887ef3017df6: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Waiting\n cluster.go:125: 7803ef1d418e: Waiting\n cluster.go:125: 0525b6a65f36: Waiting\n cluster.go:125: 887ef3017df6: Waiting\n cluster.go:125: 28c7fd8ab61c: Verifying Checksum\n cluster.go:125: 28c7fd8ab61c: Download complete\n cluster.go:125: c04b8fd1dd8d: Verifying Checksum\n cluster.go:125: c04b8fd1dd8d: Download complete\n cluster.go:125: 0b08cd0de4e0: Verifying Checksum\n cluster.go:125: 0b08cd0de4e0: Download complete\n cluster.go:125: 2e19782d7109: Verifying Checksum\n cluster.go:125: 2e19782d7109: Download complete\n cluster.go:125: 7803ef1d418e: Verifying Checksum\n cluster.go:125: 7803ef1d418e: Download complete\n cluster.go:125: 0525b6a65f36: Download complete\n cluster.go:125: 887ef3017df6: Verifying Checksum\n cluster.go:125: 887ef3017df6: Download complete\n cluster.go:125: 2e19782d7109: Pull complete\n cluster.go:125: 0b08cd0de4e0: Pull complete\n cluster.go:125: 28c7fd8ab61c: Pull complete\n cluster.go:125: c04b8fd1dd8d: Pull complete\n cluster.go:125: 7803ef1d418e: Pull complete\n cluster.go:125: 0525b6a65f36: Pull complete\n cluster.go:125: 887ef3017df6: Pull complete\n cluster.go:125: Digest: sha256:e68933b249335b5a57ee334d1d621e5e881d280ed29fdcadfbaa34b963a52a01\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"cl.etcd-member.etcdctlv3","result":"PASS","duration":85939444980,"output":" cluster.go:125: {\"level\":\"info\",\"ts\":1788919235.7682786,\"caller\":\"snapshot/v3_snapshot.go:68\",\"msg\":\"created temporary db file\",\"path\":\"/tmp/tmp.M9plNR6nnG/snapshot.db.part\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1788919235.795265,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:211\",\"msg\":\"opened snapshot stream; downloading\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1788919235.79633,\"caller\":\"snapshot/v3_snapshot.go:76\",\"msg\":\"fetching snapshot\",\"endpoint\":\"127.0.0.1:2379\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1788919235.831356,\"logger\":\"client\",\"caller\":\"v3/maintenance.go:219\",\"msg\":\"completed snapshot read; closing\"}\n cluster.go:125: {\"level\":\"info\",\"ts\":1788919235.831878,\"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\":1788919235.8322427,\"caller\":\"snapshot/v3_snapshot.go:100\",\"msg\":\"saved\",\"path\":\"/tmp/tmp.M9plNR6nnG/snapshot.db\"}\n cluster.go:125: Deprecated: Use `etcdutl snapshot status` instead.\n"},{"name":"cl.ignition.v1.groups","result":"PASS","duration":91054609128,"output":""},{"name":"docker.base/networks-reliably","result":"PASS","duration":230873153604,"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 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.1s 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\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:206caaeeb4b14a4bb6e3aa13d2ef3b9430b6d1e9e5847baf8b274cf9ab074f48 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":3416855890,"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: 5.06MB 0.1s 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\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:828320a7b4074bfd585c5602a3d17828120d71407992cd7c8e1b4bacf451f3de done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.2s\n"},{"name":"docker.base/ownership","result":"PASS","duration":14725142535,"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: 2e19782d7109: Pulling fs layer\n cluster.go:125: 0b08cd0de4e0: Pulling fs layer\n cluster.go:125: 28c7fd8ab61c: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Pulling fs layer\n cluster.go:125: 7803ef1d418e: Pulling fs layer\n cluster.go:125: 0525b6a65f36: Pulling fs layer\n cluster.go:125: 887ef3017df6: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Waiting\n cluster.go:125: 7803ef1d418e: Waiting\n cluster.go:125: 0525b6a65f36: Waiting\n cluster.go:125: 887ef3017df6: Waiting\n cluster.go:125: 28c7fd8ab61c: Verifying Checksum\n cluster.go:125: 28c7fd8ab61c: Download complete\n cluster.go:125: 2e19782d7109: Verifying Checksum\n cluster.go:125: 2e19782d7109: Download complete\n cluster.go:125: c04b8fd1dd8d: Verifying Checksum\n cluster.go:125: c04b8fd1dd8d: Download complete\n cluster.go:125: 7803ef1d418e: Verifying Checksum\n cluster.go:125: 7803ef1d418e: Download complete\n cluster.go:125: 0525b6a65f36: Verifying Checksum\n cluster.go:125: 0525b6a65f36: Download complete\n cluster.go:125: 887ef3017df6: Verifying Checksum\n cluster.go:125: 887ef3017df6: Download complete\n cluster.go:125: 0b08cd0de4e0: Verifying Checksum\n cluster.go:125: 2e19782d7109: Pull complete\n cluster.go:125: 0b08cd0de4e0: Pull complete\n cluster.go:125: 28c7fd8ab61c: Pull complete\n cluster.go:125: c04b8fd1dd8d: Pull complete\n cluster.go:125: 7803ef1d418e: Pull complete\n cluster.go:125: 0525b6a65f36: Pull complete\n cluster.go:125: 887ef3017df6: Pull complete\n cluster.go:125: Digest: sha256:e68933b249335b5a57ee334d1d621e5e881d280ed29fdcadfbaa34b963a52a01\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"cl.ignition.v2.users","result":"PASS","duration":31707622266,"output":""},{"name":"docker.base","result":"PASS","duration":288811946935,"output":" --- PASS: docker.base/docker-info (3.25s)\n --- PASS: docker.base/resources (6.79s)\n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 78B 0.0s\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.20MB 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.1s done\n cluster.go:125: #5 writing image sha256:ee3e1d22c5ddf78664b4562b861e915b2d3e578fea230b338d2781a7562f8a4e 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.base/networks-reliably (230.87s)\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 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.1s 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\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:206caaeeb4b14a4bb6e3aa13d2ef3b9430b6d1e9e5847baf8b274cf9ab074f48 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 (3.42s)\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: 5.06MB 0.1s 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\n cluster.go:125: #5 exporting layers 0.1s done\n cluster.go:125: #5 writing image sha256:828320a7b4074bfd585c5602a3d17828120d71407992cd7c8e1b4bacf451f3de done\n cluster.go:125: #5 naming to docker.io/library/captest done\n cluster.go:125: #5 DONE 0.2s\n --- PASS: docker.base/ownership (14.73s)\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: 2e19782d7109: Pulling fs layer\n cluster.go:125: 0b08cd0de4e0: Pulling fs layer\n cluster.go:125: 28c7fd8ab61c: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Pulling fs layer\n cluster.go:125: 7803ef1d418e: Pulling fs layer\n cluster.go:125: 0525b6a65f36: Pulling fs layer\n cluster.go:125: 887ef3017df6: Pulling fs layer\n cluster.go:125: c04b8fd1dd8d: Waiting\n cluster.go:125: 7803ef1d418e: Waiting\n cluster.go:125: 0525b6a65f36: Waiting\n cluster.go:125: 887ef3017df6: Waiting\n cluster.go:125: 28c7fd8ab61c: Verifying Checksum\n cluster.go:125: 28c7fd8ab61c: Download complete\n cluster.go:125: 2e19782d7109: Verifying Checksum\n cluster.go:125: 2e19782d7109: Download complete\n cluster.go:125: c04b8fd1dd8d: Verifying Checksum\n cluster.go:125: c04b8fd1dd8d: Download complete\n cluster.go:125: 7803ef1d418e: Verifying Checksum\n cluster.go:125: 7803ef1d418e: Download complete\n cluster.go:125: 0525b6a65f36: Verifying Checksum\n cluster.go:125: 0525b6a65f36: Download complete\n cluster.go:125: 887ef3017df6: Verifying Checksum\n cluster.go:125: 887ef3017df6: Download complete\n cluster.go:125: 0b08cd0de4e0: Verifying Checksum\n cluster.go:125: 2e19782d7109: Pull complete\n cluster.go:125: 0b08cd0de4e0: Pull complete\n cluster.go:125: 28c7fd8ab61c: Pull complete\n cluster.go:125: c04b8fd1dd8d: Pull complete\n cluster.go:125: 7803ef1d418e: Pull complete\n cluster.go:125: 0525b6a65f36: Pull complete\n cluster.go:125: 887ef3017df6: Pull complete\n cluster.go:125: Digest: sha256:e68933b249335b5a57ee334d1d621e5e881d280ed29fdcadfbaa34b963a52a01\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"cl.ignition.v2_1.vfat","result":"PASS","duration":49527466415,"output":""},{"name":"linux.nfs.v3","result":"PASS","duration":149462035729,"output":" nfs.go:80: NFS server booted.\n nfs.go:85: Test file \"/tmp/tmp.Omp2MP4w0K\" created on server.\n nfs.go:125: NFS client booted.\n nfs.go:133: Got NFS mount.\n"},{"name":"cl.etcd-member.v2-backup-restore","result":"PASS","duration":208193402476,"output":" cluster.go:125: 2026-09-09T02:06:37Z\tinfo\tetcdutl/backup_command.go:216\tignoring EntryConfChange raft entry\n cluster.go:125: 2026-09-09T02:06:37Z\tinfo\tetcdutl/backup_command.go:231\tignoring member attribute update on\t{\"entry\": \"Term:2 Index:3 Data:\\\"\\\\010\\\\202\\\\320\\\\203\\\\324\\\\276\\\\220\\\\350\\\\205k\\\\022\\\\003PUT\\\\032\u0026/0/members/56b8603f35a36b0b/attributes\\\\\\\"S{\\\\\\\"name\\\\\\\":\\\\\\\"270aaa18fca84ba3a6c92e2635278618\\\\\\\",\\\\\\\"clientURLs\\\\\\\":[\\\\\\\"http://10.0.0.124:2379\\\\\\\"]}(\\\\0002\\\\0008\\\\000H\\\\000P\\\\000X\\\\000`\\\\000h\\\\000p\\\\000x\\\\000\\\\200\\\\001\\\\000\\\" \", \"v2Req.Path\": \"/0/members/56b8603f35a36b0b/attributes\"}\n cluster.go:125: 2026-09-09T02:06:37Z\tinfo\tetcdutl/backup_command.go:252\tignoring v3 raft entry\n cluster.go:125: 2026-09-09T02:06:37Z\tinfo\tmembership/store.go:119\tTrimming membership information from the backend...\n"},{"name":"cl.ignition.v2_1.swap","result":"PASS","duration":64262680573,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/node_readiness","result":"PASS","duration":51596428912,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/nginx_deployment","result":"PASS","duration":6216195826,"output":""},{"name":"kubeadm.v1.37.0.cilium.base/NFS_deployment","result":"PASS","duration":24648951857,"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"},{"name":"kubeadm.v1.37.0.cilium.base/IPSec_encryption","result":"PASS","duration":22745110457,"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":505609598209,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.0\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.0\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: E0909 02:09:13.683032 2074 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: W0909 02:09:17.936047 2074 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.127]\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 119.775498ms\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.127: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 246.172659ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 306.466615ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 46.614931108s\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: zelkl5.8e3lvwrfw3kzm18t\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.127:6443 --token zelkl5.8e3lvwrfw3kzm18t \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:e645a32f42282beb052de57c7f58b34c6fbac573b38478dec399321321e8789d \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 \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W0909 02:11:44.782243 1654 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: E0909 02:11:44.805141 1654 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 (51.60s)\n --- PASS: kubeadm.v1.37.0.cilium.base/nginx_deployment (6.22s)\n --- PASS: kubeadm.v1.37.0.cilium.base/NFS_deployment (24.65s)\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 (22.75s)\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":"coreos.locksmith.tls","result":"PASS","duration":46805104573,"output":""},{"name":"devcontainer.systemd-nspawn","result":"PASS","duration":1791798510024,"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-20260908-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-20260908-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-20260908-2100\n cluster.go:125: + version=4081.3.10+nightly-20260908-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-20260908-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-20260908-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-20260908-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20260908-2100/flatcar_developer_container.bin.bz2\n cluster.go:125: + image_url=http://bincache.flatcar-linux.net/images/amd64/4081.3.10+nightly-20260908-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-20260908-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-20260908-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: ++ lbzcat flatcar_developer_container.bin.bz2\n cluster.go:125: + cp --sparse=always /dev/fd/63 flatcar_developer_container.bin\n cluster.go:125: + source /usr/share/coreos/release\n cluster.go:125: ++ FLATCAR_RELEASE_VERSION=4081.3.10+nightly-20260908-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-20260908-2100\n cluster.go:125: ++ process_template http://bincache.flatcar-linux.net/boards/@ARCH@-usr/@VERSION@/pkgs amd64 4081.3.10+nightly-20260908-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-20260908-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-20260908-2100/pkgs\n cluster.go:125: ++ echo http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-2100/pkgs\n cluster.go:125: + EXPECTED_VERSION=4081.3.10+nightly-20260908-2100\n cluster.go:125: + workdir=/home/core/dev-container-workdir-28157\n cluster.go:125: + USR_SRC_DIR=/home/core/dev-container-workdir-28157/src\n cluster.go:125: + VAR_TMP_DIR=/home/core/dev-container-workdir-28157/tmp\n cluster.go:125: + mkdir -p /home/core/dev-container-workdir-28157/src /home/core/dev-container-workdir-28157/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-20260908-2100/pkgs --setenv=EXPECTED_VERSION=4081.3.10+nightly-20260908-2100 --bind-ro=/lib/modules --bind-ro=/home/core/dev-container-script --bind=/home/core/dev-container-workdir-28157/src:/usr/src --bind=/home/core/dev-container-workdir-28157/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-20260908-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-20260908-2100 != \\4\\0\\8\\1\\.\\3\\.\\1\\0\\+\\n\\i\\g\\h\\t\\l\\y\\-\\2\\0\\2\\6\\0\\9\\0\\8\\-\\2\\1\\0\\0 ]]\n cluster.go:125: + export PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-2100/pkgs\n cluster.go:125: + PORTAGE_BINHOST=http://bincache.flatcar-linux.net/boards/amd64-usr/4081.3.10+nightly-20260908-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-20260908-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 f39187863e New version: lts-4081.3.10-nightly-20260908-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":"cl.cloudinit.script","result":"PASS","duration":22496405729,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":22585269012,"output":""},{"name":"linux.nfs.v4","result":"PASS","duration":41903713653,"output":" nfs.go:80: NFS server booted.\n nfs.go:85: Test file \"/tmp/tmp.LV2fSzPNSs\" created on server.\n nfs.go:125: NFS client booted.\n nfs.go:133: Got NFS mount.\n"},{"name":"coreos.ignition.resource.s3.versioned","result":"PASS","duration":22528489305,"output":""},{"name":"sysext.disable-containerd","result":"PASS","duration":21359472866,"output":""},{"name":"cl.ignition.v1.ext4root","result":"PASS","duration":21579216153,"output":""},{"name":"cl.internet/UpdateEngine","result":"PASS","duration":131783774,"output":""},{"name":"cl.internet/DockerPing","result":"PASS","duration":5441751930,"output":""},{"name":"cl.internet/DockerEcho","result":"PASS","duration":527236377,"output":""},{"name":"cl.internet/NTPDate","result":"PASS","duration":6900524287,"output":""},{"name":"cl.internet","result":"PASS","duration":35842757267,"output":" --- PASS: cl.internet/UpdateEngine (0.13s)\n --- PASS: cl.internet/DockerPing (5.44s)\n --- PASS: cl.internet/DockerEcho (0.53s)\n --- PASS: cl.internet/NTPDate (6.90s)\n"},{"name":"cl.network.listeners","result":"PASS","duration":23527701474,"output":""},{"name":"coreos.update.badusr","result":"PASS","duration":558613266893,"output":""},{"name":"cl.disk.raid0.root","result":"PASS","duration":37661058605,"output":""},{"name":"coreos.auth.verify","result":"PASS","duration":22414526715,"output":""},{"name":"cl.flannel.udp","result":"PASS","duration":122904554869,"output":" cluster.go:125: Timeout occurred while waiting for network connectivity.\n flannel.go:121: ping from 3024c232-da66-4294-b093-c58b789abad0(10.254.72.0) to f4bd7b11-3dd3-4b06-823a-31534a92178a(10.254.18.1)\n"},{"name":"cl.cgroupv1/CgroupMounts","result":"PASS","duration":134346805,"output":""},{"name":"cl.cgroupv1","result":"PASS","duration":22768522687,"output":" --- PASS: cl.cgroupv1/CgroupMounts (0.13s)\n"},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":25605379325,"output":""},{"name":"cl.users.shells","result":"PASS","duration":22384337851,"output":""},{"name":"cl.ignition.instantiated.enable-unit","result":"PASS","duration":22990422680,"output":""},{"name":"docker.selinux","result":"PASS","duration":26059525722,"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 cluster.go:125: sh: can't create /opt/hello: Permission denied\n"},{"name":"docker.network-openbsd-nc","result":"PASS","duration":26816882717,"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: 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.0s\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:8524ca8127d8352814ad5ae287608e912d699c485a0913eae63202bf7a7a6e06 done\n cluster.go:125: #5 naming to docker.io/library/netcat done\n cluster.go:125: #5 DONE 0.0s\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: 2.45MB 0.0s done\n cluster.go:125: #3 DONE 0.0s\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:72e34333a1b60bd8a4e474e7fe2487dc3beb271713b7fc159e31732980abc93f done\n cluster.go:125: #5 naming to docker.io/library/netcat done\n cluster.go:125: #5 DONE 0.0s\n"},{"name":"cl.basic/Useradd","result":"PASS","duration":193165179,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":144489770,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":380591596,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":134365933,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":144350766,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":145691740,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":147944249,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":159310442,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":186950021,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":129432917,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":168446014,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":138101832,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":174124653,"output":""},{"name":"cl.basic","result":"PASS","duration":24956017149,"output":" --- PASS: cl.basic/Useradd (0.19s)\n --- PASS: cl.basic/MachineID (0.14s)\n --- PASS: cl.basic/CloudConfig (0.38s)\n --- PASS: cl.basic/Symlink (0.13s)\n --- PASS: cl.basic/SymlinkFlatcar (0.14s)\n --- PASS: cl.basic/ReadOnly (0.15s)\n --- PASS: cl.basic/RandomUUID (0.15s)\n --- PASS: cl.basic/Microcode (0.16s)\n --- PASS: cl.basic/Script (0.19s)\n --- PASS: cl.basic/PortSSH (0.13s)\n --- PASS: cl.basic/DbusPerms (0.17s)\n --- PASS: cl.basic/UpdateEngineKeys (0.14s)\n --- PASS: cl.basic/ServicesActive (0.17s)\n"},{"name":"bpf.ig/ig","result":"PASS","duration":29660564744,"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: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + timeout 30 grep -F -m1 running...\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":31764817179,"output":" --- PASS: bpf.ig/ig (29.66s)\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: + sudo ig run trace_dns:v0.50.0 --host --filter name=flatcar.org. --output json --verbose\n cluster.go:125: + timeout 30 grep -F -m1 running...\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":"cl.toolbox.dnf-install","result":"PASS","duration":39872209920,"output":""},{"name":"cl.ignition.v1.sethostname","result":"PASS","duration":22378712200,"output":""},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base/node_readiness","result":"PASS","duration":10941805221,"output":""},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base/nginx_deployment","result":"PASS","duration":6054121402,"output":""},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base/NFS_deployment","result":"PASS","duration":13224924382,"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.35.1.calico.cgroupv1.base","result":"PASS","duration":130667407690,"output":" cluster.go:125: I0909 02:20:10.507738 1944 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.8\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: I0909 02:20:19.287117 2164 version.go:260] remote version is much newer: v1.37.0; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.8\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.156-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: W0909 02:20:19.494848 2164 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.158]\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 504.823044ms\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.158: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 2.013343705s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.779693432s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.504074009s\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: i0cqge.7tk5zy8lx1k8fegf\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.158:6443 --token i0cqge.7tk5zy8lx1k8fegf \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:5d74e69c612d8d5cda0f20de9981b91669b12895566baf519cda54a2252d26ef \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0909 02:21:04.524066 1779 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.calico.cgroupv1.base/node_readiness (10.94s)\n --- PASS: kubeadm.v1.35.1.calico.cgroupv1.base/nginx_deployment (6.05s)\n --- PASS: kubeadm.v1.35.1.calico.cgroupv1.base/NFS_deployment (13.22s)\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":"coreos.locksmith.reboot","result":"PASS","duration":345542643548,"output":""}],"result":"FAIL","platform":"qemu","version":"4081.3.10"}