### Test report for 4081.3.8+nightly-20260605-2100 / arm64 **Platforms tested** : aws 🟢 ok **cl.basic**; Succeeded: aws (1) 🟢 ok **cl.cloudinit.basic**; Succeeded: aws (1) 🟢 ok **cl.etcd-member.discovery**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: bf00fb13-8f0a-4fe0-b0cd-903d85b8873c_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 538b0c20-1a1f-4035-b9da-edeb06c20a0e_" L3: " " ```
🟢 ok **cl.flannel.vxlan**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: d4c8e631-6c68-4e0c-a7b3-ab552655a403_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: machine __i-06b7fdf83ef8fa560__ failed basic checks: ssh unreachable or system not ready: failure checking if machine is running: systemctl is?-system-running returned stdout: __starting__, stderr: ____, err: Process exited with status 1, systemctl list-jobs returned stdout: __JOB UNIT TYPE STATE_n604 flanneld.service? start waiting_n612 etcd-member.service start running_n501 multi-user.target start waiting_n605 flannel-docker-opts.service start waiting_n_n4 jobs listed.__, stderr: ____?, err: 🟢 ok **cl.ignition.kargs**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 9f926308-f5ff-4872-a065-1e1e952c2b29_" L3: " " ```
🟢 ok **cl.ignition.misc.empty**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 9491f3c8-1903-4c73-9279-2703d392a90e_" L3: " " ```
🟢 ok **cl.ignition.v1.noop**; Succeeded: aws (1) 🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: aws (1) 🟢 ok **cl.ignition.v2.noop**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: fbba192d-8663-4519-bba9-cd28ef6c9bd2_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: c4fa298b-767d-4f61-9adf-375e5f5f6eef_" L3: " " ```
🟢 ok **cl.install.cloudinit**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: cc5d69e1-d4ee-4d13-bc88-32a8dec44606_" L3: " " ```
🟢 ok **cl.internet**; Succeeded: aws (1) 🟢 ok **cl.metadata.aws**; Succeeded: aws (1) 🟢 ok **cl.network.initramfs.second-boot**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 8bcb7488-0c0f-4c8e-862c-9884901cc96a_" L3: " " ```
🟢 ok **coreos.ignition.once**; Succeeded: aws (1) 🟢 ok **coreos.ignition.resource.local**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 05706cd3-1708-4daa-8431-abc81e795e56_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 9c67d417-b7e4-48a4-ab10-b5187e6c3357_" L3: " " ```
🟢 ok **coreos.ignition.resource.remote**; Succeeded: aws (1) 🟢 ok **coreos.ignition.resource.s3**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 17eea67e-44f1-48d5-a82a-2449c1578fa5_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 95e9d5f2-d794-4599-b132-86178faaddd0_" L3: " " ```
🟢 ok **coreos.ignition.security.tls**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 0bf90cbe-9ba7-46d8-bc5b-1c1868cafbdc_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 482af17e-1939-4a6f-bc48-fa7ee8e197f4_" L3: " " ```
🟢 ok **coreos.ignition.sethostname**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: b0bdd7b9-7150-4d25-8324-26018f35ddb5_" L3: " " ```
🟢 ok **coreos.ignition.ssh.key**; Succeeded: aws (1) 🟢 ok **coreos.misc.aws.diskfriendlyname**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _harness.go:646: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: c29bb655-7ec4-4f59-8a58-0d80cfd22402_" L3: " " ```
🟢 ok **docker.network-openbsd-nc**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.34.4.calico.base**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: f71d02f7-3b40-4126-8b80-40d660030536_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 44319ec5-b727-43e8-b25a-18e52d47ed29_" L3: " " ```
🟢 ok **kubeadm.v1.34.4.calico.cgroupv1.base**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.34.4.cilium.base**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.34.4.cilium.cgroupv1.base**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.34.4.flannel.base**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.34.4.flannel.cgroupv1.base**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 79807b76-038e-41b6-abb7-4ef75bb4a734_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 561e41c3-56a9-4dc3-80ad-78f272a8b1fc_" L3: " " ```
🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: aws (1) 🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: aws (2); Failed: aws (1)
                Diagnostic output for aws, run 1 ``` L1: " Error: _cluster.go:125: I0605 23:35:36.080137 2452 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5" L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1" L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1" L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0" L9: "cluster.go:125: I0605 23:36:06.496052 2695 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35" L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.5" L11: "cluster.go:125: [preflight] Running pre-flight checks" L12: "cluster.go:125: [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet conf?ig will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri" L13: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_" L14: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster" L15: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection" L16: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_" L17: "cluster.go:125: W0605 23:36:06.836077 2695 checks.go:906] detected that the sandbox image __registry.k8s.io/pause:3.8__ of the container runtime is inconsistent with that used by kubeadm. It is rec?ommended to use __registry.k8s.io/pause:3.10.1__ as the CRI sandbox image." L18: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__" L19: "cluster.go:125: [certs] Generating __ca__ certificate and key" L20: "cluster.go:125: [certs] Generating __apiserver__ certificate and key" L21: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ip-172-31-29-200 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 1?72.31.29.200]" L22: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key" L23: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key" L24: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key" L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation" L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation" L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation" L28: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation" L29: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation" L30: "cluster.go:125: [certs] Generating __sa__ key and public key" L31: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__" L32: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file" L33: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file" L34: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file" L35: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file" L36: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file" L37: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__" L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__" L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__" L40: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__" L41: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__" L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__" L43: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__" L44: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__" L45: "cluster.go:125: [kubelet-start] Starting the kubelet" L46: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__" L47: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s" L48: "cluster.go:125: [kubelet-check] The kubelet is healthy after 1.001637881s" L49: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s" L50: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.31.29.200:6443/livez" L51: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz" L52: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez" L53: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.514614162s" L54: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 5.16873155s" L55: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.002002567s" L56: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace" L57: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster" L58: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs" L59: "cluster.go:125: [mark-control-plane] Marking the node ip-172-31-29-200 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balan?cers]" L60: "cluster.go:125: [mark-control-plane] Marking the node ip-172-31-29-200 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]" L61: "cluster.go:125: [bootstrap-token] Using token: ssr5j6.yexgzbjwrnv835bj" L62: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles" L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes" L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials" L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token" L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster" L67: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace" L68: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key" L69: "cluster.go:125: [addons] Applied essential addon: CoreDNS" L70: "cluster.go:125: [addons] Applied essential addon: kube-proxy" L71: "cluster.go:125: " L72: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!" L73: "cluster.go:125: " L74: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:" L75: "cluster.go:125: " L76: "cluster.go:125: mkdir -p $HOME/.kube" L77: "cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config" L78: "cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config" L79: "cluster.go:125: " L80: "cluster.go:125: Alternatively, if you are the root user, you can run:" L81: "cluster.go:125: " L82: "cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf" L83: "cluster.go:125: " L84: "cluster.go:125: You should now deploy a pod network to the cluster." L85: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:" L86: "cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/" L87: "cluster.go:125: " L88: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:" L89: "cluster.go:125: " L90: "cluster.go:125: kubeadm join 172.31.29.200:6443 --token ssr5j6.yexgzbjwrnv835bj _" L91: "cluster.go:125: --discovery-token-ca-cert-hash sha256:590ba6fe0558c8680aaafcf49a7eeb1315fe4b9f7d757002ec3e865943f495fc " L92: "cluster.go:125: namespace/kube-flannel created" L93: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created" L94: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created" L95: "cluster.go:125: serviceaccount/flannel created" L96: "cluster.go:125: configmap/kube-flannel-cfg created" L97: "cluster.go:125: daemonset.apps/kube-flannel-ds created" L98: "kubeadm.go:197: unable to setup cluster: unable to create worker node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zon?e (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L99: "status code: 400, request id: ff0103a6-aa56-49e6-995f-74a8844dc59c_" L100: " " ```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: e0090f11-2d5b-4f55-b19e-f0ee7c42bd8d_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 93fa4d39-942c-418d-9666-b17a65c68098_" L3: " " ```
🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: e0abc3ef-fb31-4d6b-b39c-a4977ccf7922_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 22d848e4-c273-4ef0-918d-60a50e69e6ad_" L3: " " ```
🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: aws (1) 🟢 ok **linux.nfs.v3**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _nfs.go:77: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry you?r request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 292c1ca1-3fac-4f53-879e-5d33234118e7_" L3: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _nfs.go:77: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry you?r request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: 8e14b0f5-c889-4b96-8401-6045dd0483b3_" L3: " " ```
🟢 ok **linux.nfs.v4**; Succeeded: aws (3); Failed: aws (1, 2)
                Diagnostic output for aws, run 2 ``` L1: " Error: _nfs.go:80: NFS server booted." L2: "nfs.go:85: Test file __/tmp/tmp.dWziSeA9sX__ created on server." L3: "nfs.go:122: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry your reque?st by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L4: "status code: 400, request id: 6b446f6e-56ab-42e6-87f7-bc13001ff246_" L5: " " ```                 Diagnostic output for aws, run 1 ``` L1: " Error: _nfs.go:77: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry you?r request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c." L2: "status code: 400, request id: c3ff6154-fe50-42e4-ae78-84c778655637_" L3: " " ```