{"tests":[{"name":"cl.internet","result":"FAIL","duration":7228613790,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 60c7df79-2940-4653-8099-8ec6f72dfabe\n"},{"name":"cl.cloudinit.basic","result":"FAIL","duration":7394602793,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 7a9cc61b-8c63-4b40-85b2-f7bc73b79dd3\n"},{"name":"linux.nfs.v3","result":"FAIL","duration":10949045195,"output":"        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 your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: 7de1d705-e49c-49ed-9d34-5d2a9a7f73cc\n"},{"name":"cl.install.cloudinit","result":"FAIL","duration":11682008026,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 6e016111-7348-4187-9122-379a14596498\n"},{"name":"cl.etcd-member.discovery","result":"FAIL","duration":11994515346,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 6c73e1d2-4a0f-40d0-b70d-47e7a6b35e10\n"},{"name":"cl.ignition.kargs","result":"FAIL","duration":14885969796,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 91597def-206f-4a70-b96b-be0fd29ab044\n"},{"name":"kubeadm.v1.35.1.cilium.cgroupv1.base","result":"FAIL","duration":15047164399,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: c88edf25-e4c2-4034-8d2c-de94e612d8c8\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"FAIL","duration":15333797802,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: df8584f0-9e46-4297-9ecc-b32794fbef16\n"},{"name":"cl.flannel.vxlan","result":"FAIL","duration":16397150438,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: c6fb8532-f3b5-477d-a8df-dc2630a73e73\n"},{"name":"coreos.ignition.sethostname","result":"FAIL","duration":18344364883,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 0a6324ce-fc7e-4311-b2fa-d1c5817c8c18\n"},{"name":"coreos.ignition.resource.remote","result":"FAIL","duration":12290831465,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 2a2902af-ccab-4548-ba7a-a0f245541166\n"},{"name":"cl.metadata.aws","result":"FAIL","duration":19679798860,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 3b9f5879-910b-453a-a4ae-bd6ca5a19cc6\n"},{"name":"linux.nfs.v4","result":"FAIL","duration":19932741382,"output":"        nfs.go:77: Cluster.NewMachine: error running instances: RequestLimitExceeded: Request limit exceeded. Account 075585003325 has been throttled on ec2:RunInstances because it exceeded its request rate limit.\n\tstatus code: 503, request id: caecc0dd-3efa-4214-807c-4040975d3991\n"},{"name":"coreos.ignition.security.tls","result":"FAIL","duration":14375524012,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 5b0bedef-500d-46f0-8597-e71853fcd56e\n"},{"name":"kubeadm.v1.37.0.calico.base","result":"FAIL","duration":22358582781,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: 8d2c204d-cc0b-4f9d-aaf0-fee0c07b306c\n"},{"name":"kubeadm.v1.35.1.cilium.base","result":"FAIL","duration":23617710670,"output":"        kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: RequestLimitExceeded: Request limit exceeded. Account 075585003325 has been throttled on ec2:RunInstances because it exceeded its request rate limit.\n\tstatus code: 503, request id: 6f2a516c-2790-49d0-a05e-215e6e697766\n"},{"name":"kubeadm.v1.37.0.flannel.base","result":"FAIL","duration":12564405847,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: acdc8ae7-b435-4d51-9a1f-23f8ca9dc626\n"},{"name":"coreos.ignition.resource.s3","result":"FAIL","duration":13025334742,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 57c61c73-a12c-4dfd-96be-1cf17235fc64\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"FAIL","duration":15232496005,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: 3d7ba818-c444-4b48-871c-2355037fc0fe\n"},{"name":"cl.network.initramfs.second-boot","result":"FAIL","duration":12434621450,"output":"        harness.go:651: 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.\n\tstatus code: 400, request id: 20f22be7-0fa8-4787-86f1-6e7d570aa389\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"FAIL","duration":14973200712,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: ded869d7-beea-428c-9c8f-11e868edbe1e\n"},{"name":"docker.network-openbsd-nc","result":"FAIL","duration":54816372073,"output":"        harness.go:651: Cluster failed starting machines: error running instances: RequestLimitExceeded: Request limit exceeded. Account 075585003325 has been throttled on ec2:RunInstances because it exceeded its request rate limit.\n\tstatus code: 503, request id: 0afe360c-1a1d-426c-997e-5c5a623b99c5\n"},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":1873753899,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":1834579970,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":1875075177,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":1849084007,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":1888480417,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":2021881279,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":1842440576,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":1837462896,"output":""},{"name":"kubeadm.v1.35.1.calico.cgroupv1.base","result":"FAIL","duration":70986256017,"output":"        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 Availability Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c.\n\tstatus code: 400, request id: 0bac07a8-8ef9-40f1-97e5-5811d649e398\n"},{"name":"cl.basic/CloudConfig","result":"PASS","duration":2548114769,"output":""},{"name":"coreos.misc.aws.diskfriendlyname","result":"PASS","duration":72806455815,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":1945474428,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":1930344770,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":1834033669,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":1856923793,"output":""},{"name":"coreos.ignition.ssh.key","result":"PASS","duration":82704473213,"output":""},{"name":"cl.basic","result":"PASS","duration":95129354553,"output":"    --- PASS: cl.basic/UpdateEngineKeys (1.87s)\n    --- PASS: cl.basic/ReadOnly (1.83s)\n    --- PASS: cl.basic/RandomUUID (1.88s)\n    --- PASS: cl.basic/PortSSH (1.85s)\n    --- PASS: cl.basic/ServicesActive (1.89s)\n    --- PASS: cl.basic/Useradd (2.02s)\n    --- PASS: cl.basic/MachineID (1.84s)\n    --- PASS: cl.basic/Microcode (1.84s)\n    --- PASS: cl.basic/CloudConfig (2.55s)\n    --- PASS: cl.basic/Script (1.95s)\n    --- PASS: cl.basic/DbusPerms (1.93s)\n    --- PASS: cl.basic/Symlink (1.83s)\n    --- PASS: cl.basic/SymlinkFlatcar (1.86s)\n"},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":8875212567,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":10843060542,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":22547230831,"output":"        cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n        cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"PASS","duration":305661713668,"output":"        cluster.go:125: I1027 11:13:07.312300    2484 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: I1027 11:13:20.358195    2700 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 ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n        cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n        cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n        cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n        cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n        cluster.go:125: W1027 11:13:20.695135    2700 checks.go:906] detected that the sandbox image \"registry.k8s.io/pause:3.8\" of the container runtime is inconsistent with that used by kubeadm. It is recommended to use \"registry.k8s.io/pause:3.10.1\" as the CRI sandbox image.\n        cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n        cluster.go:125: [certs] Generating \"ca\" certificate and key\n        cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n        cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ip-172-31-31-38 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.31.31.38]\n        cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n        cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n        cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n        cluster.go:125: [certs] Generating \"sa\" key and public key\n        cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n        cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n        cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n        cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n        cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n        cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n        cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n        cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n        cluster.go:125: [kubelet-start] Starting the kubelet\n        cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n        cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n        cluster.go:125: [kubelet-check] The kubelet is healthy after 1.011288789s\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://172.31.31.38:6443/livez\n        cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n        cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n        cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 3.521051444s\n        cluster.go:125: [control-plane-check] kube-scheduler is healthy after 5.605923124s\n        cluster.go:125: [control-plane-check] kube-apiserver is healthy after 7.50251694s\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 ip-172-31-31-38 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 ip-172-31-31-38 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n        cluster.go:125: [bootstrap-token] Using token: smm6nw.zxefms9050q0nijp\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 172.31.31.38:6443 --token smm6nw.zxefms9050q0nijp \\\n        cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f2a6f9c9aa9329d9549ab21fbcc55c28a415b604d27de2a5e8d0750f9d58f4dd \n        cluster.go:125: namespace/kube-flannel created\n        cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n        cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n        cluster.go:125: serviceaccount/flannel created\n        cluster.go:125: configmap/kube-flannel-cfg created\n        cluster.go:125: daemonset.apps/kube-flannel-ds created\n        cluster.go:125: W1027 11:14:15.530868    2233 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n        cluster.go:125: \t[WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri\n        cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n    --- PASS: kubeadm.v1.35.1.flannel.base/node_readiness (8.88s)\n    --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (10.84s)\n    --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (22.55s)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n            cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"}],"result":"FAIL","platform":"aws","version":"4081.3.12"}