{"tests":[{"name":"kubeadm.v1.36.1.calico.base/node_readiness","result":"PASS","duration":21098729096,"output":""},{"name":"kubeadm.v1.36.1.calico.base/nginx_deployment","result":"PASS","duration":5443976903,"output":""},{"name":"kubeadm.v1.36.1.calico.base/NFS_deployment","result":"PASS","duration":16688772014,"output":"        cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n        cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"PASS","duration":137368548480,"output":"        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\n        cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n        cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n        cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n        cluster.go:125: [init] Using Kubernetes version: v1.36.1\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n        cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n        cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n        cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n        cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n        cluster.go:125: [certs] Generating \"ca\" certificate and key\n        cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n        cluster.go:125: [certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.5]\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 993.655µ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.5: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.257846ms\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 3.880404ms\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.501340214s\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: gl4oku.hivlwtmsoaph9zew\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.5:6443 --token gl4oku.hivlwtmsoaph9zew \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f4c72498f2d9380de1b9cd2fc7af584b1b9e239b0ce33a04f007a9195611bef5 \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: W0603 19:56:01.758394    1855 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n        cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n        cluster.go:125: W0603 19:56:02.363246    1855 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 (21.10s)\n    --- PASS: kubeadm.v1.36.1.calico.base/nginx_deployment (5.44s)\n    --- PASS: kubeadm.v1.36.1.calico.base/NFS_deployment (16.69s)\n            cluster.go:125: jq: error (at \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.base/node_readiness","result":"PASS","duration":21056376144,"output":""},{"name":"kubeadm.v1.35.1.calico.base/nginx_deployment","result":"PASS","duration":10608607815,"output":""},{"name":"kubeadm.v1.35.1.calico.base/NFS_deployment","result":"PASS","duration":11341070529,"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.base","result":"PASS","duration":140944054317,"output":"        cluster.go:125: I0603 19:57:37.798308    2075 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n        cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\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: I0603 19:57:43.349943    2274 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n        cluster.go:125: [init] Using Kubernetes version: v1.35.5\n        cluster.go:125: [preflight] Running pre-flight checks\n        cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n        cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n        cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n        cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n        cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n        cluster.go:125: [certs] Generating \"ca\" certificate and key\n        cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n        cluster.go:125: [certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 10.0.0.8]\n        cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n        cluster.go:125: [certs] Generating \"sa\" key and public key\n        cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n        cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n        cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n        cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n        cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n        cluster.go:125: [kubelet-start] Starting the kubelet\n        cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n        cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n        cluster.go:125: [kubelet-check] The kubelet is healthy after 501.40703ms\n        cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n        cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.8:6443/livez\n        cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n        cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.45212298s\n        cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.503243852s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.000923287s\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: aaj8vr.y64aj0d5nbp6vkjd\n        cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n        cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n        cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n        cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n        cluster.go:125: [addons] Applied essential addon: CoreDNS\n        cluster.go:125: [addons] Applied essential addon: kube-proxy\n        cluster.go:125: \n        cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n        cluster.go:125: \n        cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n        cluster.go:125: \n        cluster.go:125:   mkdir -p $HOME/.kube\n        cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n        cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config\n        cluster.go:125: \n        cluster.go:125: Alternatively, if you are the root user, you can run:\n        cluster.go:125: \n        cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf\n        cluster.go:125: \n        cluster.go:125: You should now deploy a pod network to the cluster.\n        cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n        cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/\n        cluster.go:125: \n        cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n        cluster.go:125: \n        cluster.go:125: kubeadm join 10.0.0.8:6443 --token aaj8vr.y64aj0d5nbp6vkjd \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:06b79188ffefd03954fcddd5cd05f234b1c49c699aebe4ab5b05197ffc8a85bc \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: W0603 19:58:23.086916    1852 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n        cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n    --- PASS: kubeadm.v1.35.1.calico.base/node_readiness (21.06s)\n    --- PASS: kubeadm.v1.35.1.calico.base/nginx_deployment (10.61s)\n    --- PASS: kubeadm.v1.35.1.calico.base/NFS_deployment (11.34s)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"linux.nfs.v3","result":"FAIL","duration":20873443325,"output":"        nfs.go:77: Cluster.NewMachine: machine \"514f976f-c6d5-4acc-ae21-2c53a08f7abf\" failed basic checks: some systemd units failed:\n● systemd-hostnamed.service loaded failed failed Hostname Service\nstatus: \njournal:-- No entries --\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine 514f976f-c6d5-4acc-ae21-2c53a08f7abf console\n"},{"name":"coreos.ignition.sethostname","result":"FAIL","duration":18944475672,"output":"        harness.go:646: Cluster failed starting machines: machine \"a7a3f916-e421-44e5-bce7-711fd7b1aef0\" failed basic checks: some systemd units failed:\n● systemd-hostnamed.service loaded failed failed Hostname Service\nstatus: \njournal:-- No entries --\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine a7a3f916-e421-44e5-bce7-711fd7b1aef0 console\n"},{"name":"systemd.journal.remote","result":"FAIL","duration":20971150550,"output":"        journald.go:143: Cluster.NewMachine: machine \"38f08e99-7596-492b-9fe5-ae449c2321b8\" failed basic checks: some systemd units failed:\n● systemd-hostnamed.service loaded failed failed Hostname Service\nstatus: \njournal:-- No entries --\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine 38f08e99-7596-492b-9fe5-ae449c2321b8 console\n"},{"name":"cl.install.cloudinit","result":"FAIL","duration":618345605544,"output":"        harness.go:646: Cluster failed starting machines: machine \"242f819d-c23b-49f5-8a39-431c6a2a23db\" failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"starting\", stderr: \"\", err: Process exited with status 1, systemctl list-jobs returned stdout: \"JOB   UNIT                                                        TYPE  STATE\\n35700 user-cloudinit@var-lib-flatcar\\\\x2dinstall-user_data.service start running\\n669   multi-user.target                                           start waiting\\n834   user-config.target                                          start waiting\\n\\n3 jobs listed.\", stderr: \"\", err: \u003cnil\u003e\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine 242f819d-c23b-49f5-8a39-431c6a2a23db console\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":19909889271,"output":"        nfs.go:77: Cluster.NewMachine: machine \"f4f4f36a-b7f3-4f48-b5b1-adef13ffe836\" failed basic checks: some systemd units failed:\n● systemd-hostnamed.service loaded failed failed Hostname Service\nstatus: \njournal:-- No entries --\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine f4f4f36a-b7f3-4f48-b5b1-adef13ffe836 console\n"},{"name":"cl.cloudinit.basic","result":"FAIL","duration":639295416245,"output":"        harness.go:646: Cluster failed starting machines: machine \"e3541dd5-c355-45b0-aae5-15b1406576db\" failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"starting\", stderr: \"\", err: Process exited with status 1, systemctl list-jobs returned stdout: \"JOB   UNIT                      TYPE  STATE\\n814   user-config.target        start waiting\\n669   multi-user.target         start waiting\\n36259 user-configvirtfs.service start running\\n\\n3 jobs listed.\", stderr: \"\", err: \u003cnil\u003e\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine e3541dd5-c355-45b0-aae5-15b1406576db console\n"},{"name":"cl.ignition.v1.sethostname","result":"FAIL","duration":18904381909,"output":"        harness.go:646: Cluster failed starting machines: machine \"55328aef-ff8d-4374-9a64-b944fa023a84\" failed basic checks: some systemd units failed:\n● systemd-hostnamed.service loaded failed failed Hostname Service\nstatus: \njournal:-- No entries --\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine 55328aef-ff8d-4374-9a64-b944fa023a84 console\n"},{"name":"cl.basic/PortSSH","result":"PASS","duration":102578366,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":95788101,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":96940844,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":96889156,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":107993074,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":198921162,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":348991955,"output":""},{"name":"cl.basic/DbusPerms","result":"FAIL","duration":25151294446,"output":"        cluster.go:85: kolet: Process exited with status 1\n"},{"name":"cl.basic/Symlink","result":"PASS","duration":107490982,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":114155435,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":90528748,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":107160026,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":25158043788,"output":""},{"name":"cl.basic","result":"FAIL","duration":72326018692,"output":"    --- PASS: cl.basic/PortSSH (0.10s)\n    --- PASS: cl.basic/SymlinkFlatcar (0.10s)\n    --- PASS: cl.basic/UpdateEngineKeys (0.10s)\n    --- PASS: cl.basic/ReadOnly (0.10s)\n    --- PASS: cl.basic/RandomUUID (0.11s)\n    --- PASS: cl.basic/Useradd (0.20s)\n    --- PASS: cl.basic/CloudConfig (0.35s)\n        cluster.go:82: kolet:\n2026-06-03T20:05:55Z kolet: exit status 1\n    --- FAIL: cl.basic/DbusPerms (25.15s)\n            cluster.go:85: kolet: Process exited with status 1\n    --- PASS: cl.basic/Symlink (0.11s)\n    --- PASS: cl.basic/ServicesActive (0.11s)\n    --- PASS: cl.basic/MachineID (0.09s)\n    --- PASS: cl.basic/Microcode (0.11s)\n    --- PASS: cl.basic/Script (25.16s)\n"},{"name":"cl.cloudinit.multipart-mime","result":"FAIL","duration":637344087255,"output":"        harness.go:646: Cluster failed starting machines: machine \"0468d343-13ad-44d3-8ee0-c0d25f426619\" failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"starting\", stderr: \"\", err: Process exited with status 1, systemctl list-jobs returned stdout: \"JOB   UNIT                      TYPE  STATE\\n34972 user-configvirtfs.service start running\\n816   user-config.target        start waiting\\n669   multi-user.target         start waiting\\n\\n3 jobs listed.\", stderr: \"\", err: \u003cnil\u003e\n        harness.go:616: Found systemd unit failed to start (\u001b[0;1;39msystemd-hostnamed.service\u001b[0m - Hostname Service.\r\r) on machine 0468d343-13ad-44d3-8ee0-c0d25f426619 console\n"}],"result":"FAIL","platform":"qemu","version":"4593.2.100"}