e2e-kops-aws-upgrade-kstable-kolatest-to-kci-kolatest-many-addons #1636507826610245632
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 20m22s |
| Revision | master |
kubetest2 Down
... skipping 205 lines ... I0316 23:22:37.644716 6289 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/2d8679f7-c451-11ed-93d6-92b4ce3fddda" I0316 23:22:37.647896 6289 app.go:128] ID for this run: "2d8679f7-c451-11ed-93d6-92b4ce3fddda" I0316 23:22:37.648121 6289 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 I0316 23:22:37.655041 6289 dumplogs.go:45] /tmp/kops.XRFOsAONg toolbox dump --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0316 23:22:37.655073 6289 local.go:42] ⚙️ /tmp/kops.XRFOsAONg toolbox dump --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0316 23:22:37.686164 6300 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found W0316 23:22:38.157329 6289 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0316 23:22:38.157387 6289 down.go:48] /tmp/kops.XRFOsAONg delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0316 23:22:38.157399 6289 local.go:42] ⚙️ /tmp/kops.XRFOsAONg delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0316 23:22:38.188195 6308 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found Error: exit status 1 + echo 'kubetest2 down failed' kubetest2 down failed + [[ l == \v ]] ++ kops-base-from-marker latest ++ [[ latest =~ ^https: ]] ++ [[ latest == \l\a\t\e\s\t ]] ++ curl -fs https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt + KOPS_BASE_URL=https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-458-gedc5df1ee7 ... skipping 15 lines ... I0316 23:22:40.001936 6341 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/2d8679f7-c451-11ed-93d6-92b4ce3fddda" I0316 23:22:40.006414 6341 app.go:128] ID for this run: "2d8679f7-c451-11ed-93d6-92b4ce3fddda" I0316 23:22:40.006482 6341 up.go:44] Cleaning up any leaked resources from previous cluster I0316 23:22:40.006526 6341 dumplogs.go:45] /tmp/kops.cMKR9fcQN toolbox dump --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0316 23:22:40.006576 6341 local.go:42] ⚙️ /tmp/kops.cMKR9fcQN toolbox dump --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0316 23:22:40.038280 6350 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found W0316 23:22:40.509876 6341 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0316 23:22:40.509919 6341 down.go:48] /tmp/kops.cMKR9fcQN delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0316 23:22:40.509933 6341 local.go:42] ⚙️ /tmp/kops.cMKR9fcQN delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0316 23:22:40.541663 6359 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found I0316 23:22:41.009965 6341 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/03/16 23:22:41 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404 I0316 23:22:41.022635 6341 http.go:37] curl https://ip.jsb.workers.dev I0316 23:22:41.129608 6341 template.go:58] /tmp/kops.cMKR9fcQN toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template3173735234/manifest.yaml --values /tmp/kops-template3173735234/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0316 23:22:41.129653 6341 local.go:42] ⚙️ /tmp/kops.cMKR9fcQN toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template3173735234/manifest.yaml --values /tmp/kops-template3173735234/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0316 23:22:41.161649 6374 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0316 23:22:41.249769 6341 create.go:33] /tmp/kops.cMKR9fcQN create --filename /tmp/kops-template3173735234/manifest.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0316 23:22:41.249808 6341 local.go:42] ⚙️ /tmp/kops.cMKR9fcQN create --filename /tmp/kops-template3173735234/manifest.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io ... skipping 47 lines ... I0316 23:23:20.121254 6341 up.go:251] /tmp/kops.cMKR9fcQN validate cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --count 10 --wait 15m0s I0316 23:23:20.121330 6341 local.go:42] ⚙️ /tmp/kops.cMKR9fcQN validate cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --count 10 --wait 15m0s I0316 23:23:20.153292 6411 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Validating cluster e2e-9b8b75964a-36844.test-cncf-aws.k8s.io W0316 23:23:21.411102 6411 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-9b8b75964a-36844.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e nodes-us-east-1a Node t3.medium 4 4 us-east-1a ... skipping 2 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:23:31.452352 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:23:41.485093 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:23:51.524790 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:24:01.555833 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:24:11.598463 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:24:21.659105 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:24:31.716769 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:24:41.747431 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:24:51.780775 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:25:01.811662 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:25:11.849236 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:25:21.906378 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:25:31.968675 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:25:42.001402 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:25:52.034756 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:26:02.076602 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:26:12.108123 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:26:22.138889 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:26:32.170963 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:26:42.203188 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:26:52.263345 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:27:02.321830 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:27:12.368560 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:27:22.412350 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:27:32.442848 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:27:42.481755 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:27:52.519123 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:28:02.549606 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 3 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0316 23:28:12.577466 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 35 lines ... Pod kube-system/ebs-csi-node-xww5c system-node-critical pod "ebs-csi-node-xww5c" is pending Pod kube-system/metrics-server-db468d46c-24mf9 system-cluster-critical pod "metrics-server-db468d46c-24mf9" is pending Pod kube-system/metrics-server-db468d46c-cbgm8 system-cluster-critical pod "metrics-server-db468d46c-cbgm8" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:28:25.329508 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 35 lines ... Pod kube-system/ebs-csi-node-xww5c system-node-critical pod "ebs-csi-node-xww5c" is pending Pod kube-system/metrics-server-db468d46c-24mf9 system-cluster-critical pod "metrics-server-db468d46c-24mf9" is pending Pod kube-system/metrics-server-db468d46c-cbgm8 system-cluster-critical pod "metrics-server-db468d46c-cbgm8" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:28:37.447965 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 31 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-zqxx4 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-zqxx4" is pending Pod kube-system/metrics-server-db468d46c-24mf9 system-cluster-critical pod "metrics-server-db468d46c-24mf9" is pending Pod kube-system/metrics-server-db468d46c-cbgm8 system-cluster-critical pod "metrics-server-db468d46c-cbgm8" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:28:49.642399 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 44 lines ... Pod kube-system/node-local-dns-kmk92 system-node-critical pod "node-local-dns-kmk92" is pending Pod kube-system/node-local-dns-knrb2 system-node-critical pod "node-local-dns-knrb2" is pending Pod kube-system/node-local-dns-vhqgh system-node-critical pod "node-local-dns-vhqgh" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:29:01.841184 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 53 lines ... Pod kube-system/node-local-dns-8vkt8 system-node-critical pod "node-local-dns-8vkt8" is pending Pod kube-system/node-local-dns-jthdq system-node-critical pod "node-local-dns-jthdq" is pending Pod kube-system/node-local-dns-nwxks system-node-critical pod "node-local-dns-nwxks" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:29:14.907167 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 30 lines ... Pod kube-system/ebs-csi-node-z9d2g system-node-critical pod "ebs-csi-node-z9d2g" is pending Pod kube-system/metrics-server-db468d46c-24mf9 system-cluster-critical pod "metrics-server-db468d46c-24mf9" is not ready (metrics-server) Pod kube-system/metrics-server-db468d46c-cbgm8 system-cluster-critical pod "metrics-server-db468d46c-cbgm8" is not ready (metrics-server) Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:29:27.130599 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 26 lines ... Pod kube-system/aws-load-balancer-controller-9c4f8f9df-pp774 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-pp774" is pending Pod kube-system/metrics-server-db468d46c-24mf9 system-cluster-critical pod "metrics-server-db468d46c-24mf9" is not ready (metrics-server) Pod kube-system/metrics-server-db468d46c-cbgm8 system-cluster-critical pod "metrics-server-db468d46c-cbgm8" is not ready (metrics-server) Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is pending Validation Failed W0316 23:29:39.326461 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 24 lines ... Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-scheduler pod Pod kube-system/aws-load-balancer-controller-9c4f8f9df-cjxk5 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-cjxk5" is pending Pod kube-system/aws-load-balancer-controller-9c4f8f9df-pp774 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-pp774" is pending Pod kube-system/pod-identity-webhook-7c5858d967-ncqxv system-cluster-critical pod "pod-identity-webhook-7c5858d967-ncqxv" is not ready (pod-identity-webhook) Pod kube-system/pod-identity-webhook-7c5858d967-ss9ml system-cluster-critical pod "pod-identity-webhook-7c5858d967-ss9ml" is not ready (pod-identity-webhook) Validation Failed W0316 23:29:51.264106 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 22 lines ... Node i-068d4f6eb3cebc012 control-plane node "i-068d4f6eb3cebc012" is missing kube-scheduler pod Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-controller-manager pod Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-scheduler pod Pod kube-system/aws-load-balancer-controller-9c4f8f9df-cjxk5 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-cjxk5" is pending Pod kube-system/aws-load-balancer-controller-9c4f8f9df-pp774 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-pp774" is pending Validation Failed W0316 23:30:04.095307 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 25 lines ... Pod kube-system/aws-load-balancer-controller-9c4f8f9df-cjxk5 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-cjxk5" is pending Pod kube-system/aws-load-balancer-controller-9c4f8f9df-pp774 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-pp774" is pending Pod kube-system/kube-controller-manager-i-068d4f6eb3cebc012 system-cluster-critical pod "kube-controller-manager-i-068d4f6eb3cebc012" is pending Pod kube-system/kube-proxy-i-01d69c3fda8b95380 system-node-critical pod "kube-proxy-i-01d69c3fda8b95380" is pending Pod kube-system/kube-proxy-i-049a354b0e5c33422 system-node-critical pod "kube-proxy-i-049a354b0e5c33422" is pending Validation Failed W0316 23:30:16.487305 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 22 lines ... Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-controller-manager pod Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-scheduler pod Pod kube-system/aws-load-balancer-controller-9c4f8f9df-cjxk5 system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-cjxk5" is pending Pod kube-system/kube-proxy-i-008cb2c9a10fda912 system-node-critical pod "kube-proxy-i-008cb2c9a10fda912" is pending Pod kube-system/kube-proxy-i-04dc05ba493e914c6 system-node-critical pod "kube-proxy-i-04dc05ba493e914c6" is pending Validation Failed W0316 23:30:28.726477 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 20 lines ... InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-controller-manager pod Pod kube-system/etcd-manager-events-i-0cfc0ba8c958d5505 system-cluster-critical pod "etcd-manager-events-i-0cfc0ba8c958d5505" is pending Pod kube-system/etcd-manager-main-i-0cfc0ba8c958d5505 system-cluster-critical pod "etcd-manager-main-i-0cfc0ba8c958d5505" is pending Pod kube-system/kube-proxy-i-076b652da7a353b59 system-node-critical pod "kube-proxy-i-076b652da7a353b59" is pending Validation Failed W0316 23:30:40.839633 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 18 lines ... KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-controller-manager pod Pod kube-system/kube-proxy-i-0cfc0ba8c958d5505 system-node-critical pod "kube-proxy-i-0cfc0ba8c958d5505" is pending Validation Failed W0316 23:30:53.134060 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 17 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Node i-0cfc0ba8c958d5505 control-plane node "i-0cfc0ba8c958d5505" is missing kube-controller-manager pod Validation Failed W0316 23:31:05.475884 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:31:17.478756 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:31:30.468721 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:31:43.306410 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:31:55.457918 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:32:08.026434 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:32:20.923054 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:32:33.258830 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:32:45.614571 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:32:57.945848 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:33:10.143643 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:33:22.523842 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:33:34.795913 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:33:46.946481 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:33:59.256869 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:34:12.112904 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:34:24.630953 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:34:37.258887 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:34:49.487671 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:35:01.830886 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:35:14.394614 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:35:26.550281 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:35:38.895976 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:35:51.123017 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:36:03.342113 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:36:15.527677 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:36:27.646842 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:36:40.010432 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:36:52.581619 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:37:05.122392 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:37:18.616108 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:37:31.045643 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:37:43.364143 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:37:55.793984 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:38:08.198773 6411 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-1a ControlPlane c5.large 1 1 us-east-1a master-us-east-1c ControlPlane c5.large 1 1 us-east-1c master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 16 lines ... VALIDATION ERRORS KIND NAME MESSAGE InstanceGroup master-us-east-1e InstanceGroup "master-us-east-1e" did not have enough nodes 0 vs 1 InstanceGroup nodes-us-east-1e InstanceGroup "nodes-us-east-1e" did not have enough nodes 0 vs 4 Validation Failed W0316 23:38:20.649111 6411 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation Error: exit status 1 + kops-finish + kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --kops-binary-path=/tmp/kops.cMKR9fcQN --down I0316 23:38:30.691293 6432 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0316 23:38:30.692333 6432 app.go:61] The files in RunDir shall not be part of Artifacts I0316 23:38:30.692360 6432 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I0316 23:38:30.692385 6432 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/2d8679f7-c451-11ed-93d6-92b4ce3fddda" ... skipping 509 lines ...