{"tests":[{"name":"cl.cloudinit.script","result":"PASS","duration":94797071090,"output":""},{"name":"cl.ignition.v2.noop","result":"PASS","duration":95090716935,"output":""},{"name":"cl.swap_activation","result":"PASS","duration":95106120063,"output":""},{"name":"docker.enable-service.sysext","result":"PASS","duration":95299339817,"output":" cluster.go:152: + systemctl is-enabled docker\n"},{"name":"azure.nvme-friendly-naming","result":"SKIP","duration":95759586566,"output":" cluster.go:125: ls: cannot access '/dev/nvme0n1': No such file or directory\n nvme.go:47: no NVMe disk found on this instance\n"},{"name":"cl.ignition.v2.xfsroot","result":"PASS","duration":97433837080,"output":""},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":97998835875,"output":""},{"name":"coreos.ignition.groups","result":"PASS","duration":98413309314,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":1982908219,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":1560182244,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":1432308169,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":1399736230,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":1366902296,"output":""},{"name":"docker.userns","result":"PASS","duration":106919636687,"output":" cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \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: 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.19MB 0.0s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:e4eb599929c51ddc7bc75922c32faeab417298b0519dff74e9f835d2f7b16e66 done\n cluster.go:125: #5 naming to docker.io/library/userns-test done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"cl.basic/RandomUUID","result":"PASS","duration":1466873142,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":1893449357,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":1354368732,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":1311284773,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":1326389042,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":1403311855,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":1314237501,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":1332194937,"output":""},{"name":"cl.basic","result":"PASS","duration":120057824006,"output":" --- PASS: cl.basic/CloudConfig (1.98s)\n --- PASS: cl.basic/Script (1.56s)\n --- PASS: cl.basic/DbusPerms (1.43s)\n --- PASS: cl.basic/Symlink (1.40s)\n --- PASS: cl.basic/ReadOnly (1.37s)\n --- PASS: cl.basic/RandomUUID (1.47s)\n --- PASS: cl.basic/Useradd (1.89s)\n --- PASS: cl.basic/Microcode (1.35s)\n --- PASS: cl.basic/PortSSH (1.31s)\n --- PASS: cl.basic/SymlinkFlatcar (1.33s)\n --- PASS: cl.basic/UpdateEngineKeys (1.40s)\n --- PASS: cl.basic/ServicesActive (1.31s)\n --- PASS: cl.basic/MachineID (1.33s)\n"},{"name":"cl.network.iptables","result":"PASS","duration":125934008884,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"coreos.selinux.enforce","result":"PASS","duration":136520986210,"output":""},{"name":"coreos.locksmith.tls","result":"PASS","duration":141942566124,"output":""},{"name":"docker.containerd-restart","result":"PASS","duration":171081541797,"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: dbc3eadfebd7: Pulling fs layer\n cluster.go:125: dbc3eadfebd7: Verifying Checksum\n cluster.go:125: dbc3eadfebd7: Download complete\n cluster.go:125: dbc3eadfebd7: 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.ignition.v1.noop","result":"PASS","duration":95274113476,"output":""},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":95744150468,"output":""},{"name":"cl.ignition.v2.ext4root","result":"PASS","duration":96715587294,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":94197229390,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"sysext.disable-docker","result":"FAIL","duration":66223590755,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-04f138464c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/4869b1cd-c370-4e9e-913d-2723b978422e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:51:16.1327825+00:00\",\n \"endTime\": \"2026-10-21T14:51:21.7056146+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"4869b1cd-c370-4e9e-913d-2723b978422e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.cloudinit.basic","result":"PASS","duration":95781367291,"output":""},{"name":"cl.network.nftables","result":"PASS","duration":96162126629,"output":" cluster.go:152: + sudo nft --json list ruleset | jq '.nftables[] | select(.rule) | .rule.expr[0].match.right'\n"},{"name":"cl.ignition.translation","result":"PASS","duration":127913198460,"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":"cl.verity/verify","result":"PASS","duration":74163155708,"output":" cluster.go:125: Success\n"},{"name":"cl.ignition.v1.xfsroot","result":"PASS","duration":129076583033,"output":""},{"name":"cl.metadata.azure","result":"PASS","duration":94652579951,"output":""},{"name":"sysext.disable-containerd","result":"FAIL","duration":68724498228,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-474391c3de): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/b98900c9-88c5-44ca-a40d-3b8829e098e1\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:52:46.8877216+00:00\",\n \"endTime\": \"2026-10-21T14:52:50.6467282+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"b98900c9-88c5-44ca-a40d-3b8829e098e1\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"FAIL","duration":191152107873,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4757.2.2-a-dca1b5a882): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/462f0fea-c340-4004-8bf9-e77374fc291f\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:52:45.3295118+00:00\",\n \"endTime\": \"2026-10-21T14:52:49.9585549+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"462f0fea-c340-4004-8bf9-e77374fc291f\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"systemd.sysusers.gshadow","result":"PASS","duration":100386057546,"output":""},{"name":"sysext.simple","result":"PASS","duration":100552679223,"output":""},{"name":"coreos.tls.fetch-urls","result":"PASS","duration":103964219969,"output":""},{"name":"cl.ignition.v2.users","result":"PASS","duration":103634101265,"output":""},{"name":"docker.base","result":"FAIL","duration":68009444098,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-dd1f052885): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/eb9d9314-5efd-4b09-ad41-418dce49acb0\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:05.3294251+00:00\",\n \"endTime\": \"2026-10-21T14:53:09.5623345+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"eb9d9314-5efd-4b09-ad41-418dce49acb0\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"FAIL","duration":162164778702,"output":" kubeadm.go:197: unable to setup cluster: unable to create master node: PollUntilDone(ci-4757.2.2-a-f6572a734e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/179b245d-406e-461d-b43d-e8a22b40c02a\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:02.7015886+00:00\",\n \"endTime\": \"2026-10-21T14:53:06.5794435+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"179b245d-406e-461d-b43d-e8a22b40c02a\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.btrfs-storage","result":"PASS","duration":119711859292,"output":""},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":310456188556,"output":" cluster.go:125: I1021 14:52:43.972082 2680 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I1021 14:52:55.243053 3086 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-67b4a5a51d\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-67b4a5a51d\": lookup ci-4757.2.2-a-67b4a5a51d on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-67b4a5a51d kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.9]\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 688.944µ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.9: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 3.622089ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.053444ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002026409s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-67b4a5a51d as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-67b4a5a51d as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: na266k.mc9nalfs8piytk2e\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.9:6443 --token na266k.mc9nalfs8piytk2e \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:4cc5b3e9f5eff2b0387d5fd3fb50ca18f26cee796c07d19ce3f7246464abbce9 \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-ca34c5dd5f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/df581dc3-e1db-4b6d-8c0a-3ee758887e51\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:08.161515+00:00\",\n \"endTime\": \"2026-10-21T14:53:12.013674+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"df581dc3-e1db-4b6d-8c0a-3ee758887e51\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"FAIL","duration":313442123129,"output":" cluster.go:125: I1021 14:52:37.177095 2722 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: I1021 14:52:46.341259 3123 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36\n cluster.go:125: [init] Using Kubernetes version: v1.36.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-26a109c965\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-26a109c965\": lookup ci-4757.2.2-a-26a109c965 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-26a109c965 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] 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 555.118µ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.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 5.968759ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 8.394125ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.002402768s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-26a109c965 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-26a109c965 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 9bsbio.62868o5s2dtr65p2\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.6:6443 --token 9bsbio.62868o5s2dtr65p2 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:25fde63755a442665d7414ca87752f4604d0170473d75757cf5d5141fb766783 \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-66cdefb781): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/8276a5d5-6d78-4a09-aae8-2654ca2bc3cc\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:11.7940767+00:00\",\n \"endTime\": \"2026-10-21T14:53:15.7039393+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"8276a5d5-6d78-4a09-aae8-2654ca2bc3cc\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":322941739878,"output":" cluster.go:125: I1021 14:52:38.660825 2738 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I1021 14:52:47.787282 3109 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-cc4c460fd2\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-cc4c460fd2\": lookup ci-4757.2.2-a-cc4c460fd2 on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-cc4c460fd2 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.15]\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 502.318222ms\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.15: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.51480727s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.744279247s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.501815052s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-cc4c460fd2 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-cc4c460fd2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: mw5rem.ivfssnxw0lwb13x6\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.15:6443 --token mw5rem.ivfssnxw0lwb13x6 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:8389284b84f9892f5eeb6a749de1c9de64dea1300c4b2f0b260b1d0e81a7320a \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-b5e45eea45): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/b80767ab-7dda-4a2a-b32b-435aa91a8f7a\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:18.7798548+00:00\",\n \"endTime\": \"2026-10-21T14:53:25.1057755+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"b80767ab-7dda-4a2a-b32b-435aa91a8f7a\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"FAIL","duration":67695314113,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-83144e2f6d): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/f1c81233-f0a7-4a36-9887-766d4c6c4eec\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:35.6433359+00:00\",\n \"endTime\": \"2026-10-21T14:53:39.8161631+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"f1c81233-f0a7-4a36-9887-766d4c6c4eec\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.selinux","result":"FAIL","duration":67962931807,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-ed63d7141a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/467f18fc-389c-4eba-9c23-61654538654b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:35.9586847+00:00\",\n \"endTime\": \"2026-10-21T14:53:39.8085313+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"467f18fc-389c-4eba-9c23-61654538654b\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.etcd-member.etcdctlv3","result":"FAIL","duration":67959923193,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-bb79997cd7): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/73f92fee-17d4-4779-bd98-52cc74ec493c\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:55.7224526+00:00\",\n \"endTime\": \"2026-10-21T14:53:59.9299741+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"73f92fee-17d4-4779-bd98-52cc74ec493c\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.etcd-member.v2-backup-restore","result":"FAIL","duration":68490708482,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-8aca7cc558): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/b9631250-0f28-4ff1-84b8-51b095918851\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:53:56.7464436+00:00\",\n \"endTime\": \"2026-10-21T14:54:00.3699147+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"b9631250-0f28-4ff1-84b8-51b095918851\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.groups","result":"FAIL","duration":68164924441,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-35f269eeef): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/ed82392d-a90d-47e7-8b70-10e1c7099815\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:02.1835789+00:00\",\n \"endTime\": \"2026-10-21T14:54:05.7718562+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"ed82392d-a90d-47e7-8b70-10e1c7099815\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.osreset.ignition-rerun","result":"FAIL","duration":68162137843,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-136c71b4f9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/39ab5b42-8b0c-4ada-b191-b00e3e698324\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:02.2001654+00:00\",\n \"endTime\": \"2026-10-21T14:54:12.1114883+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"39ab5b42-8b0c-4ada-b191-b00e3e698324\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.luks","result":"FAIL","duration":67315078993,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-ddad7bd9c9): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/ac01070b-b28e-4f0c-9358-0af9d58bef50\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:05.5979081+00:00\",\n \"endTime\": \"2026-10-21T14:54:09.5829315+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"ac01070b-b28e-4f0c-9358-0af9d58bef50\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.locksmith.cluster","result":"FAIL","duration":68733414318,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-9d00f36617): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/58ababa4-c090-42f9-ae59-f97557250055\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:04.9193326+00:00\",\n \"endTime\": \"2026-10-21T14:54:08.5941346+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"58ababa4-c090-42f9-ae59-f97557250055\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":365052048172,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0\n cluster.go:125: [init] Using Kubernetes version: v1.37.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-f97d4e6e6c\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4757.2.2-a-f97d4e6e6c\": lookup ci-4757.2.2-a-f97d4e6e6c on 168.63.129.16:53: no such host\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ci-4757.2.2-a-f97d4e6e6c kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.21]\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 770.761µ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.21: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 4.172241ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.127152ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.50183742s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-f97d4e6e6c as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node ci-4757.2.2-a-f97d4e6e6c as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: v7p2zc.sumzi0ywrvfywv65\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.21:6443 --token v7p2zc.sumzi0ywrvfywv65 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:9a294a57ecfb73d9dcbd300f809801d97d02d79afee81051d0df591bc069e8ed \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 kubeadm.go:197: unable to setup cluster: unable to create worker node: PollUntilDone(ci-4757.2.2-a-db0296184f): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/2c7dc7f2-f242-44b9-a9f6-a2a72fef6c75\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:01.8106496+00:00\",\n \"endTime\": \"2026-10-21T14:54:06.4123093+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"2c7dc7f2-f242-44b9-a9f6-a2a72fef6c75\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":2458623016,"output":" harness.go:651: Cluster failed starting machines: creating nic: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/networkInterfaces/nic-987926d689\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.ssh.key","result":"FAIL","duration":208431759,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-3b8b8ca809\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.update.badusr","result":"FAIL","duration":205973454,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-5eb8b2f28a\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":335300378,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-88b2b011b5\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":202522598,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-de464a4e78\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.toolbox.dnf-install","result":"FAIL","duration":202902913,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-b6efbc5f53\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":2188837010,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-6c4a940b9d\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.internet","result":"FAIL","duration":68126797335,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-7db9a1e27b): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/f32cb0f6-d278-447a-a046-4868ea6fb29d\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:13.0655128+00:00\",\n \"endTime\": \"2026-10-21T14:54:16.9197444+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"f32cb0f6-d278-447a-a046-4868ea6fb29d\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.ext4root","result":"FAIL","duration":212809840,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-105b6a4420\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.users.shells","result":"FAIL","duration":200999766,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-3f68a32540\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"sysext.custom-docker.sysext","result":"FAIL","duration":196191585,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-385ecaca95\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2_1.ext4checkexisting","result":"FAIL","duration":191095511,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-769c3de443\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.resource.local","result":"FAIL","duration":216060714,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-ff946920ee\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.overlay.cleanup","result":"FAIL","duration":221057927,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-be63c6a9b6\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.symlink","result":"FAIL","duration":195415400,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-21c12976d1\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"bpf.ig/ig","result":"FAIL","duration":201322363,"output":" ig.go:57: creating node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-da2b2f17ec\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.systemd.enable-service","result":"FAIL","duration":220009638,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-55305f2c69\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.network.initramfs.second-boot","result":"FAIL","duration":207846185,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-c910e05905\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.ignition.once","result":"FAIL","duration":198149524,"output":" harness.go:651: Cluster failed starting machines: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-0660e03918\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.auth.verify","result":"FAIL","duration":68300456787,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-d5aeed7b1a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/4ff8950d-bafb-431f-9805-9b95d2b50346\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:14.4523316+00:00\",\n \"endTime\": \"2026-10-21T14:54:18.1530781+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"4ff8950d-bafb-431f-9805-9b95d2b50346\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"bpf.ig","result":"FAIL","duration":2202190500,"output":" --- FAIL: bpf.ig/ig (0.20s)\n ig.go:57: creating node: creating public ip: PUT https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Network/publicIPAddresses/ip-da2b2f17ec\n --------------------------------------------------------------------------------\n RESPONSE 409: 409 Conflict\n ERROR CODE: ResourceGroupBeingDeleted\n --------------------------------------------------------------------------------\n {\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'kola-cluster-image-ada2aa83e1' is in deprovisioning state and cannot perform this operation.\"\n }\n }\n --------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.37.0.cilium.base","result":"FAIL","duration":279155638603,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1\n kubeadm.go:197: unable to setup cluster: unable to run master script: wait: remote command exited without exit status or exit signal\n"},{"name":"systemd.journal.user","result":"FAIL","duration":67421105539,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-db2a1bd81a): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/f910fa74-94dd-4c91-87f4-3cea81954634\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:20.5255634+00:00\",\n \"endTime\": \"2026-10-21T14:54:25.3246418+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"f910fa74-94dd-4c91-87f4-3cea81954634\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.btrfsroot","result":"FAIL","duration":14549458341,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-17177447ad): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/71b3afe8-12ac-4d2f-8ac8-53655156e52b\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:55:13.6117248+00:00\",\n \"endTime\": \"2026-10-21T14:55:15.5581679+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'KOLA-CLUSTER-IMAGE-ADA2AA83E1' is in deprovisioning state and cannot perform this operation. Target: '/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Compute/disks/ci-4757.2.2-a-17177447ad_OsDisk_1_6e7dfb9d0dd94cd7bcd750982904b4b1'.\"\n },\n \"name\": \"71b3afe8-12ac-4d2f-8ac8-53655156e52b\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v2_1.vfat","result":"FAIL","duration":15394396513,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-1aab4a8809): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/fc494ac7-2f92-43e5-86c4-d8c2683578e2\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: ResourceGroupBeingDeleted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:55:13.9573807+00:00\",\n \"endTime\": \"2026-10-21T14:55:15.9517549+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"ResourceGroupBeingDeleted\",\n \"message\": \"The resource group 'KOLA-CLUSTER-IMAGE-ADA2AA83E1' is in deprovisioning state and cannot perform this operation. Target: '/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kola-cluster-image-ada2aa83e1/providers/Microsoft.Compute/disks/ci-4757.2.2-a-1aab4a8809_OsDisk_1_f1e99818dd3b45239cd894b8da994ab4'.\"\n },\n \"name\": \"fc494ac7-2f92-43e5-86c4-d8c2683578e2\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"coreos.selinux.boolean","result":"FAIL","duration":69138048483,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-43548a421e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/322d32e0-c080-453c-84a1-b44d60227aef\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:20.8499426+00:00\",\n \"endTime\": \"2026-10-21T14:54:25.2899257+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"322d32e0-c080-453c-84a1-b44d60227aef\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.network.wireguard","result":"FAIL","duration":68582602851,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-48e4778ddb): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/39ac5f00-9995-4194-bb70-d5f3b26f7819\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:23.7732526+00:00\",\n \"endTime\": \"2026-10-21T14:54:27.9941229+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"39ac5f00-9995-4194-bb70-d5f3b26f7819\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.users","result":"FAIL","duration":68493631784,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-548874e66e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/0eb2a78a-314c-4ef6-912e-80296d690f88\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: AllocationFailed\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:33.4841609+00:00\",\n \"endTime\": \"2026-10-21T14:54:38.290917+00:00\",\n \"status\": \"Failed\",\n \"error\": {\n \"code\": \"AllocationFailed\",\n \"message\": \"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"\n },\n \"name\": \"0eb2a78a-314c-4ef6-912e-80296d690f88\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":50729718988,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-bb28fa6214): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/9aba8875-91df-4dc8-be84-4259df9d66f1\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:55:05.278697+00:00\",\n \"endTime\": \"2026-10-21T14:55:32.8093845+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"9aba8875-91df-4dc8-be84-4259df9d66f1\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":52718112499,"output":" kubeadm.go:197: unable to setup cluster: unable to create etcd node: PollUntilDone(ci-4757.2.2-a-710c41162e): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/d6b95fc7-5c00-4562-aada-bf01bb6a8d3e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:55:03.6656462+00:00\",\n \"endTime\": \"2026-10-21T14:55:33.0352223+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"d6b95fc7-5c00-4562-aada-bf01bb6a8d3e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.cloudinit.multipart-mime","result":"FAIL","duration":50137736800,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-875a36269c): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/64d43e1c-5ab9-4c9e-8329-013a5af46e17\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:55:10.3084185+00:00\",\n \"endTime\": \"2026-10-21T14:55:32.9241441+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"64d43e1c-5ab9-4c9e-8329-013a5af46e17\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.misc.empty","result":"FAIL","duration":50398938174,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-aa5de34f06): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/285ed2d8-9cac-4551-8bd7-2a9e8c071a5e\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:55:11.1831268+00:00\",\n \"endTime\": \"2026-10-21T14:55:32.8093845+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"285ed2d8-9cac-4551-8bd7-2a9e8c071a5e\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.ignition.v1.once","result":"FAIL","duration":80279224802,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-eef6cc2575): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/6233c6ae-90c1-4158-b120-3cdc8369a54d\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:43.5317645+00:00\",\n \"endTime\": \"2026-10-21T14:55:39.5417814+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"6233c6ae-90c1-4158-b120-3cdc8369a54d\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.verity/corruption","result":"PASS","duration":174971638799,"output":""},{"name":"cl.verity","result":"PASS","duration":342047940316,"output":" --- PASS: cl.verity/verify (74.16s)\n cluster.go:125: Success\n --- PASS: cl.verity/corruption (174.97s)\n"},{"name":"cl.ignition.v2_1.swap","result":"FAIL","duration":142038392791,"output":" harness.go:651: Cluster failed starting machines: PollUntilDone(ci-4757.2.2-a-0fad9ab348): GET https://management.azure.com/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute/locations/westus2/operations/bd554aae-e1be-41d3-84ce-5a9ba4abf395\n--------------------------------------------------------------------------------\nRESPONSE 200: 200 OK\nERROR CODE: OperationPreempted\n--------------------------------------------------------------------------------\n{\n \"startTime\": \"2026-10-21T14:54:43.5941657+00:00\",\n \"endTime\": \"2026-10-21T14:57:00.0155577+00:00\",\n \"status\": \"Canceled\",\n \"error\": {\n \"code\": \"OperationPreempted\",\n \"message\": \"Operation execution has been preempted by a more recent operation.\"\n },\n \"name\": \"bd554aae-e1be-41d3-84ce-5a9ba4abf395\"\n}\n--------------------------------------------------------------------------------\n"},{"name":"cl.update.reboot","result":"FAIL","duration":778659028876,"output":" update.go:91: couldn't reboot: machine \"ci-4757.2.2-a-a0be03e32c\" failed to start: ssh journalctl failed: time limit exceeded: dial tcp 20.125.16.93:22: i/o timeout\n"},{"name":"coreos.locksmith.reboot","result":"FAIL","duration":1013495660345,"output":" locksmith.go:141: failed to check rebooted machine: ssh unreachable or system not ready: context deadline exceeded\n"},{"name":"cl.update.badverity","result":"FAIL","duration":5261515005157,"output":" update.go:168: ssh unreachable or system not ready: failure checking if machine is running: systemctl is-system-running returned stdout: \"\", stderr: \"\", err: dial tcp 20.98.90.104:22: i/o timeout, systemctl list-jobs returned stdout: \"\", stderr: \"\", err: dial tcp 20.98.90.104:22: i/o timeout\n"}],"result":"FAIL","platform":"azure","version":"4757.2.2"}