### Test report for 4868.0.0+nightly-20261029-2100 / arm64
**Platforms tested** : azure
🟢 ok **azure.nvme-friendly-naming # SKIP**; Succeeded: azure (1)
🟢 ok **bpf.ig**; Succeeded: azure (1)
🟢 ok **cl.basic**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.basic**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.multipart-mime**; Succeeded: azure (1)
🟢 ok **cl.cloudinit.script**; Succeeded: azure (1)
🟢 ok **cl.etcd-member.discovery**; Succeeded: azure (1)
🟢 ok **cl.etcd-member.etcdctlv3**; Succeeded: azure (1)
🟢 ok **cl.etcd-member.v2-backup-restore**; Succeeded: azure (1)
🟢 ok **cl.flannel.vxlan**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4868.0.0-n-0849c19d22__ failed basic checks: some systemd units failed:"
L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)"
L3: "status: "
L4: "journal:-- No entries --"
L5: "harness.go:669: Found systemd unit failed to start (?[0;1;39metcd-member.servic????[0mtcd (System Application Container). ) on machine ci-4868.0.0-n-0849c19d22 console"
L6: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mflannel-dock????[0mers (System Application Container). ) on machine ci-4868.0.0-n-0849c19d22 console_"
L7: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4868.0.0-n-583379c433__ failed basic checks: some systemd units failed:"
L2: "??? flanneld.service loaded failed failed flannel - Network fabric for containers (System Application Container)"
L3: "status: "
L4: "journal:-- No entries --_"
L5: " "
```
🟢 ok **cl.ignition.kargs**; Succeeded: azure (1)
🟢 ok **cl.ignition.luks**; Succeeded: azure (1)
🟢 ok **cl.ignition.misc.empty**; Succeeded: azure (1)
🟢 ok **cl.ignition.symlink**; Succeeded: azure (1)
🟢 ok **cl.ignition.translation**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.btrfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.ext4root**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.groups**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.once**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v1.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.ext4root**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.noop**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.users**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2.xfsroot**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.ext4checkexisting**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.swap**; Succeeded: azure (1)
🟢 ok **cl.ignition.v2_1.vfat**; Succeeded: azure (1)
🟢 ok **cl.internet**; Succeeded: azure (1)
🟢 ok **cl.locksmith.cluster**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4868.0.0-n-85c984df62__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: __starting__, stderr: ____, err: Process exited with status 1, systemctl list-jobs returned stdout: __JOB UNIT TYPE STATE_n860 multi-user.target? start waiting_n1048 etcd-member.service start running_n_n2 jobs listed.__, stderr: ____, err: Diagnostic output for azure, run 1
```
L1: " Error: _harness.go:699: Cluster failed starting machines: machine __ci-4868.0.0-n-d10c9ba723__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemc?tl is-system-running returned stdout: __starting__, stderr: ____, err: Process exited with status 1, systemctl list-jobs returned stdout: __JOB UNIT TYPE STATE_n858 multi-user.target? start waiting_n1041 etcd-member.service start running_n_n2 jobs listed.__, stderr: ____, err:
🟢 ok **cl.metadata.azure**; Succeeded: azure (1)
🟢 ok **cl.network.initramfs.second-boot**; Succeeded: azure (1)
🟢 ok **cl.network.iptables**; Succeeded: azure (1)
🟢 ok **cl.network.nftables**; Succeeded: azure (1)
🟢 ok **cl.network.wireguard**; Succeeded: azure (1)
🟢 ok **cl.osreset.ignition-rerun**; Succeeded: azure (1)
🟢 ok **cl.overlay.cleanup**; Succeeded: azure (1)
🟢 ok **cl.swap_activation**; Succeeded: azure (1)
🟢 ok **cl.toolbox.dnf-install**; Succeeded: azure (1)
🟢 ok **cl.update.badverity**; Succeeded: azure (1)
🟢 ok **cl.update.reboot**; Succeeded: azure (1)
🟢 ok **cl.users.shells**; Succeeded: azure (1)
🟢 ok **cl.verity**; Succeeded: azure (1)
🟢 ok **coreos.auth.verify**; Succeeded: azure (1)
🟢 ok **coreos.ignition.groups**; Succeeded: azure (1)
🟢 ok **coreos.ignition.once**; Succeeded: azure (1)
🟢 ok **coreos.ignition.resource.local**; Succeeded: azure (1)
🟢 ok **coreos.ignition.resource.remote**; Succeeded: azure (1)
🟢 ok **coreos.ignition.security.tls**; Succeeded: azure (1)
🟢 ok **coreos.ignition.ssh.key**; Succeeded: azure (1)
🟢 ok **coreos.ignition.systemd.enable-service**; Succeeded: azure (1)
🟢 ok **coreos.locksmith.reboot**; Succeeded: azure (1)
🟢 ok **coreos.locksmith.tls**; Succeeded: azure (1)
🟢 ok **coreos.selinux.boolean**; Succeeded: azure (1)
🟢 ok **coreos.selinux.enforce**; Succeeded: azure (1)
🟢 ok **coreos.tls.fetch-urls**; Succeeded: azure (1)
🟢 ok **coreos.update.badusr**; Succeeded: azure (1)
🟢 ok **docker.base**; Succeeded: azure (1)
🟢 ok **docker.btrfs-storage**; Succeeded: azure (1)
🟢 ok **docker.containerd-restart**; Succeeded: azure (1)
🟢 ok **docker.enable-service.sysext**; Succeeded: azure (1)
🟢 ok **docker.lib-coreos-dockerd-compat**; Succeeded: azure (1)
🟢 ok **docker.network-openbsd-nc**; Succeeded: azure (1)
🟢 ok **docker.selinux**; Succeeded: azure (1)
🟢 ok **docker.userns**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: azure (3); Failed: azure (1, 2)
Diagnostic output for azure, run 2
```
L1: " Error: _cluster.go:125: I1030 09:11:37.997158 2659 version.go:260] remote version is much newer: v1.37.2; falling back to: stable-1.35"
L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.10"
L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.10"
L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.10"
L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.10"
L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1"
L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1"
L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0"
L9: "cluster.go:125: I1030 09:11:47.071308 2873 version.go:260] remote version is much newer: v1.37.2; falling back to: stable-1.35"
L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.10"
L11: "cluster.go:125: [preflight] Running pre-flight checks"
L12: "cluster.go:125: [WARNING Hostname]: hostname __ci-4868.0.0-n-96fe95799d__ could not be reached"
L13: "cluster.go:125: [WARNING Hostname]: hostname __ci-4868.0.0-n-96fe95799d__: lookup ci-4868.0.0-n-96fe95799d on 168.63.129.16:53: no such host"
L14: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
L15: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
L16: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
L17: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
L18: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
L19: "cluster.go:125: [certs] Generating __ca__ certificate and key"
L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4868.0.0-n-96fe95799d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.?96.0.1 10.0.0.8]"
L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
L30: "cluster.go:125: [certs] Generating __sa__ key and public key"
L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
L45: "cluster.go:125: [kubelet-start] Starting the kubelet"
L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 1.001104248s"
L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://10.0.0.8:6443/livez"
L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.504711339s"
L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.764430699s"
L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.501855727s"
L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
L59: "cluster.go:125: [mark-control-plane] Marking the node ci-4868.0.0-n-96fe95799d as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-lo?ad-balancers]"
L60: "cluster.go:125: [mark-control-plane] Marking the node ci-4868.0.0-n-96fe95799d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
L61: "cluster.go:125: [bootstrap-token] Using token: 4d92ga.f6ik0cio78qbu9ji"
L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
L64: "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"
L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
L67: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
L68: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
L69: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
L70: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
L71: "cluster.go:125: "
L72: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
L73: "cluster.go:125: "
L74: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
L75: "cluster.go:125: "
L76: "cluster.go:125: mkdir -p $HOME/.kube"
L77: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
L78: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config"
L79: "cluster.go:125: "
L80: "cluster.go:125: Alternatively, if you are the root user, you can run:"
L81: "cluster.go:125: "
L82: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf"
L83: "cluster.go:125: "
L84: "cluster.go:125: You should now deploy a pod network to the cluster."
L85: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
L86: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/"
L87: "cluster.go:125: "
L88: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
L89: "cluster.go:125: "
L90: "cluster.go:125: kubeadm join 10.0.0.8:6443 --token 4d92ga.f6ik0cio78qbu9ji _"
L91: "cluster.go:125: --discovery-token-ca-cert-hash sha256:5a2060ac15cdd0704d8dc22dfa02ec80e78d9d662960bc11a9cf9a6b8cb72f91 "
L92: "cluster.go:125: i Using Cilium version 1.12.5"
L93: "cluster.go:125: ? Auto-detected cluster name: kubernetes"
L94: "cluster.go:125: ? Auto-detected datapath mode: tunnel"
L95: "cluster.go:125: ? Auto-detected kube-proxy has been installed"
L96: "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=vx?lan"
L97: "cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret"
L98: "cluster.go:125: ? Created CA in secret cilium-ca"
L99: "cluster.go:125: ? Generating certificates for Hubble..."
L100: "cluster.go:125: ? Creating Service accounts..."
L101: "cluster.go:125: ? Creating Cluster roles..."
L102: "cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5..."
L103: "cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true"
L104: "cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17"
L105: "cluster.go:125: ? Creating Agent DaemonSet..."
L106: "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"
L107: "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___ fi?eld instead__ subsys=klog"
L108: "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 i?nstead__ subsys=klog"
L109: "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"
L110: "cluster.go:125: ? Creating Operator Deployment..."
L111: "cluster.go:125: ? Waiting for Cilium to be installed and ready..."
L112: "cluster.go:125: ? Cilium was successfully installed! Run _cilium status_ to view installation health"
L113: "cluster.go:125: ?[33m /??_"
L114: "cluster.go:125: ?[36m /???[33m___/?[32m??_?[0m Cilium: ?[32mOK?[0m"
L115: "cluster.go:125: ?[36m ___?[31m/??_?[32m__/?[0m Operator: ?[32mOK?[0m"
L116: "cluster.go:125: ?[32m /???[31m___/?[35m??_?[0m Hubble: ?[36mdisabled?[0m"
L117: "cluster.go:125: ?[32m ___?[34m/??_?[35m__/?[0m ClusterMesh: ?[36mdisabled?[0m"
L118: "cluster.go:125: ?[34m ___/"
L119: "cluster.go:125: ?[0m"
L120: "cluster.go:125: DaemonSet cilium "
L121: "cluster.go:125: Deployment cilium-operator "
L122: "cluster.go:125: Containers: cilium "
L123: "cluster.go:125: cilium-operator "
L124: "cluster.go:125: Cluster Pods: 0/0 managed by Cilium"
L125: "cluster.go:125: W1030 09:14:29.280712 2622 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration"
L126: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
L127: "--- FAIL: kubeadm.v1.35.1.cilium.base/IPSec_encryption (77.15s)"
L128: "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"
L129: "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___ fi?eld instead__ subsys=klog"
L130: "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 i?nstead__ subsys=klog"
L131: "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"
L132: "cluster.go:125: Error: Unable to determine status: timeout while waiting for status to become successful: context deadline exceeded"
L133: "cluster.go:145: __/opt/bin/cilium status --wait --wait-duration 1m__ failed: output ?[33m /????_"
L134: "?[36m /?????[33m___/?[32m????_?[0m Cilium: ?[31m1 errors?[0m"
L135: "?[36m ___?[31m/????_?[32m__/?[0m Operator: ?[32mOK?[0m"
L136: "?[32m /?????[31m___/?[35m????_?[0m Hubble: ?[36mdisabled?[0m"
L137: "?[32m ___?[34m/????_?[35m__/?[0m ClusterMesh: ?[36mdisabled?[0m"
L138: "?[34m ___/"
L139: "?[0m"
L140: "Deployment cilium-operator Desired: 1, Ready: ?[32m1/1?[0m, Available: ?[32m1/1?[0m"
L141: "DaemonSet cilium Desired: 2, Ready: ?[32m2/2?[0m, Available: ?[32m2/2?[0m"
L142: "Containers: cilium Running: ?[32m2?[0m"
L143: "cilium-operator Running: ?[32m1?[0m"
L144: "Cluster Pods: 5/5 managed by Cilium"
L145: "Image versions cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 2"
L146: "cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1"
L147: "Errors: cilium cilium-jqv2t unable to retrieve cilium status: error dialing backend: dial tcp 10.10.10.10:10250: i/o timeout, status Process exited with status 1_"
L148: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to get etcd node health: health polling failed: Process exited with status 1:_"
L2: " "
```
🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.37.0.calico.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.37.0.cilium.base**; Succeeded: azure (1)
🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: azure (1)
🟢 ok **podman.base**; Succeeded: azure (1)
🟢 ok **podman.network-single**; Succeeded: azure (1)
🟢 ok **podman.workflow**; Succeeded: azure (1)
🟢 ok **sysext.custom-docker.sysext**; Succeeded: azure (1)
🟢 ok **sysext.disable-containerd**; Succeeded: azure (1)
🟢 ok **sysext.disable-docker**; Succeeded: azure (1)
🟢 ok **sysext.simple**; Succeeded: azure (1)
❌ not ok **sysext.zfs.docker**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-5cad755d2f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/a3c848a3-28cb-415a-89f8-46e619385ca2"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T10:07:22.2258252+00:00__,"
L8: "__endTime__: __2026-10-30T10:27:32.8015105+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-5cad755d2f_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __a3c848a3-28cb-415a-89f8-46e619385ca2__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-5cad755d2f console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-5cad755d2f console_"
L19: " "
```
Diagnostic output for azure, run 4
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-6f16c13730): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/df764e51-9c2f-401e-b159-7a7f3ce441af"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:57:24.7907614+00:00__,"
L8: "__endTime__: __2026-10-30T10:02:08.555255+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __df764e51-9c2f-401e-b159-7a7f3ce441af__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 3
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-52567ca2e3): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/0d98c281-7604-4b3b-a26b-d0360c5dff03"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:32:17.894578+00:00__,"
L8: "__endTime__: __2026-10-30T09:52:32.1834559+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-52567ca2e3_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __0d98c281-7604-4b3b-a26b-d0360c5dff03__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-52567ca2e3 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4868.0.0-n-52567ca2e3 console_"
L19: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-50dcae2875): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/7bf72ec6-5c44-4d11-9233-2e9ac2b28a81"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:07:09.8294329+00:00__,"
L8: "__endTime__: __2026-10-30T09:27:21.1017123+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-50dcae2875_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __7bf72ec6-5c44-4d11-9233-2e9ac2b28a81__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-50dcae2875 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4868.0.0-n-50dcae2875 console_"
L19: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-157cc02066): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/4ac1e61e-0f8a-46ab-b151-88ada224018d"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T08:32:39.3303636+00:00__,"
L8: "__endTime__: __2026-10-30T08:52:51.5404974+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-157cc02066_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __4ac1e61e-0f8a-46ab-b151-88ada224018d__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-157cc02066 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-157cc02066 console_"
L19: " "
```
❌ not ok **sysext.zfs.nfs**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-c63288d8f8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/49715c5e-0ec4-40b3-bbfc-649a1f2023bc"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T10:07:19.4454008+00:00__,"
L8: "__endTime__: __2026-10-30T10:27:30.9077609+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-c63288d8f8_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __49715c5e-0ec4-40b3-bbfc-649a1f2023bc__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-c63288d8f8 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-c63288d8f8 console_"
L19: " "
```
Diagnostic output for azure, run 4
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-592dfb6f46): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/6d8f61d3-e678-4f8c-b9d4-bb01dda9b72b"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:57:24.5991216+00:00__,"
L8: "__endTime__: __2026-10-30T10:02:26.4933315+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __6d8f61d3-e678-4f8c-b9d4-bb01dda9b72b__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 3
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-b4872a9077): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/436ccf2f-fc39-4f47-899a-7ab2ff26b91c"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:32:18.2171071+00:00__,"
L8: "__endTime__: __2026-10-30T09:52:30.7681045+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-b4872a9077_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __436ccf2f-fc39-4f47-899a-7ab2ff26b91c__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-b4872a9077 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-b4872a9077 console_"
L19: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-8dc4bb3ccc): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/a09a9950-9b8c-4dd6-bdfc-2b9b06839e18"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:07:10.5757736+00:00__,"
L8: "__endTime__: __2026-10-30T09:27:21.6225479+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-8dc4bb3ccc_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __a09a9950-9b8c-4dd6-bdfc-2b9b06839e18__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-8dc4bb3ccc console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-8dc4bb3ccc console_"
L19: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-39d16ba9a8): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/226490eb-fe64-45ec-bb86-c3bb32e9ea3d"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T08:45:23.7533832+00:00__,"
L8: "__endTime__: __2026-10-30T09:02:06.0271298+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __226490eb-fe64-45ec-bb86-c3bb32e9ea3d__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
❌ not ok **sysext.zfs.reboot**; Failed: azure (1, 2, 3, 4, 5)
Diagnostic output for azure, run 5
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-a36f0c8f15): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/15df833c-332a-4b68-a579-29b39ba9ec30"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T10:07:19.3229174+00:00__,"
L8: "__endTime__: __2026-10-30T10:27:31.7054156+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-a36f0c8f15_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __15df833c-332a-4b68-a579-29b39ba9ec30__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-a36f0c8f15 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-a36f0c8f15 console_"
L19: " "
```
Diagnostic output for azure, run 4
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-4f0ab48f94): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/3747de7e-a2ca-4b95-9707-501a061f4680"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OperationPreempted"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:57:24.4376609+00:00__,"
L8: "__endTime__: __2026-10-30T10:02:01.6643635+00:00__,"
L9: "__status__: __Canceled__,"
L10: "__error__: {"
L11: "__code__: __OperationPreempted__,"
L12: "__message__: __Operation execution has been preempted by a more recent operation.__"
L13: "},"
L14: "__name__: __3747de7e-a2ca-4b95-9707-501a061f4680__"
L15: "}"
L16: "--------------------------------------------------------------------------------_"
L17: " "
```
Diagnostic output for azure, run 3
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-58f2987753): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/5cbda9a5-4530-465a-b2d4-beb80f5c6d18"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:32:20.650289+00:00__,"
L8: "__endTime__: __2026-10-30T09:52:31.1708907+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-58f2987753_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __5cbda9a5-4530-465a-b2d4-beb80f5c6d18__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-58f2987753 console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4868.0.0-n-58f2987753 console_"
L19: " "
```
Diagnostic output for azure, run 2
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-cb61ca2eeb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/218e3f8a-ceb3-4da0-8e08-f3150ee0c605"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T09:07:10.3722852+00:00__,"
L8: "__endTime__: __2026-10-30T09:27:21.7685049+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-cb61ca2eeb_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __218e3f8a-ceb3-4da0-8e08-f3150ee0c605__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-cb61ca2eeb console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39mserial-getty???.service?[0m - Serial Getty on ttyAMA0. ) on machine ci-4868.0.0-n-cb61ca2eeb console_"
L19: " "
```
Diagnostic output for azure, run 1
```
L1: " Error: _zfs.go:172: creating a machine failed: PollUntilDone(ci-4868.0.0-n-646a38d23f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/?locations/westus2/operations/40edf6d0-8815-4119-979a-6fd46bccdbf7"
L2: "--------------------------------------------------------------------------------"
L3: "RESPONSE 200: 200 OK"
L4: "ERROR CODE: OSProvisioningTimedOut"
L5: "--------------------------------------------------------------------------------"
L6: "{"
L7: "__startTime__: __2026-10-30T08:32:39.8379748+00:00__,"
L8: "__endTime__: __2026-10-30T08:52:49.3211253+00:00__,"
L9: "__status__: __Failed__,"
L10: "__error__: {"
L11: "__code__: __OSProvisioningTimedOut__,"
L12: "__message__: __OS Provisioning for VM _ci-4868.0.0-n-646a38d23f_ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, ma?ke sure the image has been properly prepared (generalized)._r_n * Instructions for Windows: https://learn.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image_r_n * Instructions f?or Linux: https://learn.microsoft.com/azure/virtual-machines/linux/create-upload-generic_r_n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to sha?red image gallery. Please refer to https://aka.ms/movetosig for the same.__"
L13: "},"
L14: "__name__: __40edf6d0-8815-4119-979a-6fd46bccdbf7__"
L15: "}"
L16: "--------------------------------------------------------------------------------"
L17: "harness.go:669: Found systemd unit failed to start (?[0;1;39msystemd-udev-settl????[0m To Complete Device Initialization. ) on machine ci-4868.0.0-n-646a38d23f console"
L18: "harness.go:669: Found systemd dependency unit failed to start (?[0;1;39msystemd-fsck????[0mem Check on /dev/disk/by-label/OEM. ) on machine ci-4868.0.0-n-646a38d23f console_"
L19: " "
```
🟢 ok **systemd.journal.user**; Succeeded: azure (1)
🟢 ok **systemd.sysusers.gshadow**; Succeeded: azure (1)