e2e-kops-aws-upgrade-kstable-kolatest-to-kci-kolatest-many-addons #1638410357397524480
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 20m8s |
| Revision | master |
kubetest2 Down
... skipping 205 lines ... I0322 05:22:34.244499 6340 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/4b675ddc-c871-11ed-abe9-f26dd6892cca" I0322 05:22:34.247740 6340 app.go:128] ID for this run: "4b675ddc-c871-11ed-abe9-f26dd6892cca" I0322 05:22:34.247916 6340 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 I0322 05:22:34.254732 6340 dumplogs.go:45] /tmp/kops.kH71XeWfm 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 I0322 05:22:34.254765 6340 local.go:42] ⚙️ /tmp/kops.kH71XeWfm 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 I0322 05:22:34.284829 6351 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found W0322 05:22:34.733895 6340 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0322 05:22:34.733937 6340 down.go:48] /tmp/kops.kH71XeWfm delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0322 05:22:34.733950 6340 local.go:42] ⚙️ /tmp/kops.kH71XeWfm delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0322 05:22:34.763692 6361 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-488-gbccbdaccc6 ... skipping 15 lines ... I0322 05:22:37.262986 6396 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/4b675ddc-c871-11ed-abe9-f26dd6892cca" I0322 05:22:37.265708 6396 app.go:128] ID for this run: "4b675ddc-c871-11ed-abe9-f26dd6892cca" I0322 05:22:37.265758 6396 up.go:44] Cleaning up any leaked resources from previous cluster I0322 05:22:37.265824 6396 dumplogs.go:45] /tmp/kops.71SAMbsES 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 I0322 05:22:37.265923 6396 local.go:42] ⚙️ /tmp/kops.71SAMbsES 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 I0322 05:22:37.299976 6406 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found W0322 05:22:37.744515 6396 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0322 05:22:37.744556 6396 down.go:48] /tmp/kops.71SAMbsES delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0322 05:22:37.744567 6396 local.go:42] ⚙️ /tmp/kops.71SAMbsES delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0322 05:22:37.775405 6416 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 I0322 05:22:38.255947 6396 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/03/22 05:22:38 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 I0322 05:22:38.268440 6396 http.go:37] curl https://ip.jsb.workers.dev I0322 05:22:38.366814 6396 template.go:58] /tmp/kops.71SAMbsES toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template2437590756/manifest.yaml --values /tmp/kops-template2437590756/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0322 05:22:38.366860 6396 local.go:42] ⚙️ /tmp/kops.71SAMbsES toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template2437590756/manifest.yaml --values /tmp/kops-template2437590756/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0322 05:22:38.397070 6428 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0322 05:22:38.554697 6396 create.go:33] /tmp/kops.71SAMbsES create --filename /tmp/kops-template2437590756/manifest.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0322 05:22:38.554751 6396 local.go:42] ⚙️ /tmp/kops.71SAMbsES create --filename /tmp/kops-template2437590756/manifest.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io ... skipping 61 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 W0322 05:23:17.605169 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:23:27.649598 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:23:37.680588 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:23:47.716397 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:23:57.750145 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:24:07.779788 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:24:17.824540 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:24:27.856170 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:24:37.887018 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:24:47.916532 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:24:57.946188 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:25:08.006091 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:25:18.037585 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:25:28.067371 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:25:38.112137 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:25:48.156843 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:25:58.217613 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:26:08.248019 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:26:18.280380 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:26:28.312914 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:26:38.361841 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:26:48.395377 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:26:58.441360 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:27:08.472988 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:27:18.501803 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:27:28.558518 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:27:38.606371 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:27:48.651336 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:27:58.682685 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:28:08.713278 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:28:18.769656 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:28:28.801634 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:28:38.856078 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:28:48.889021 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:28:58.922270 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:29:08.985652 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:29:19.023200 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:29:29.053155 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 34 lines ... Pod kube-system/ebs-csi-node-zff7c system-node-critical pod "ebs-csi-node-zff7c" is pending Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is pending Pod kube-system/metrics-server-db468d46c-wpnxh system-cluster-critical pod "metrics-server-db468d46c-wpnxh" is pending Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is pending Pod kube-system/pod-identity-webhook-7c5858d967-r7xrf system-cluster-critical pod "pod-identity-webhook-7c5858d967-r7xrf" is pending Validation Failed W0322 05:29:41.751882 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 31 lines ... Pod kube-system/ebs-csi-node-zff7c system-node-critical pod "ebs-csi-node-zff7c" is pending Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is pending Pod kube-system/metrics-server-db468d46c-wpnxh system-cluster-critical pod "metrics-server-db468d46c-wpnxh" is pending Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is pending Pod kube-system/pod-identity-webhook-7c5858d967-r7xrf system-cluster-critical pod "pod-identity-webhook-7c5858d967-r7xrf" is pending Validation Failed W0322 05:29:53.818544 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 28 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-jfppw system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-jfppw" is pending Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is pending Pod kube-system/metrics-server-db468d46c-wpnxh system-cluster-critical pod "metrics-server-db468d46c-wpnxh" is pending Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is pending Pod kube-system/pod-identity-webhook-7c5858d967-r7xrf system-cluster-critical pod "pod-identity-webhook-7c5858d967-r7xrf" is pending Validation Failed W0322 05:30:06.073933 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 29 lines ... Pod kube-system/ebs-csi-node-n66nq system-node-critical pod "ebs-csi-node-n66nq" is pending Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is pending Pod kube-system/metrics-server-db468d46c-wpnxh system-cluster-critical pod "metrics-server-db468d46c-wpnxh" is pending Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is pending Pod kube-system/pod-identity-webhook-7c5858d967-r7xrf system-cluster-critical pod "pod-identity-webhook-7c5858d967-r7xrf" is pending Validation Failed W0322 05:30:18.244288 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 34 lines ... Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is pending Pod kube-system/metrics-server-db468d46c-wpnxh system-cluster-critical pod "metrics-server-db468d46c-wpnxh" is pending Pod kube-system/node-local-dns-9fxd7 system-node-critical pod "node-local-dns-9fxd7" is pending Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is pending Pod kube-system/pod-identity-webhook-7c5858d967-r7xrf system-cluster-critical pod "pod-identity-webhook-7c5858d967-r7xrf" is pending Validation Failed W0322 05:30:30.305315 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 46 lines ... Pod kube-system/node-local-dns-9ttl2 system-node-critical pod "node-local-dns-9ttl2" is pending Pod kube-system/node-local-dns-c8252 system-node-critical pod "node-local-dns-c8252" is pending Pod kube-system/node-local-dns-ldjtj system-node-critical pod "node-local-dns-ldjtj" is pending Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is pending Pod kube-system/pod-identity-webhook-7c5858d967-r7xrf system-cluster-critical pod "pod-identity-webhook-7c5858d967-r7xrf" is not ready (pod-identity-webhook) Validation Failed W0322 05:30:42.482233 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 31 lines ... Pod kube-system/ebs-csi-node-wg7m8 system-node-critical pod "ebs-csi-node-wg7m8" is pending Pod kube-system/etcd-manager-events-i-0e313cbd316649d77 system-cluster-critical pod "etcd-manager-events-i-0e313cbd316649d77" is pending Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is not ready (metrics-server) Pod kube-system/metrics-server-db468d46c-wpnxh system-cluster-critical pod "metrics-server-db468d46c-wpnxh" is not ready (metrics-server) Pod kube-system/pod-identity-webhook-7c5858d967-f6n55 system-cluster-critical pod "pod-identity-webhook-7c5858d967-f6n55" is not ready (pod-identity-webhook) Validation Failed W0322 05:30:54.749736 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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-015d29adb65048914 control-plane node "i-015d29adb65048914" is missing kube-controller-manager pod Pod kube-system/aws-load-balancer-controller-9c4f8f9df-28qmn system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-28qmn" is pending Pod kube-system/aws-load-balancer-controller-9c4f8f9df-n75jx system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-n75jx" is pending Pod kube-system/metrics-server-db468d46c-f8q62 system-cluster-critical pod "metrics-server-db468d46c-f8q62" is not ready (metrics-server) Validation Failed W0322 05:31:06.968399 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 19 lines ... 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-015d29adb65048914 control-plane node "i-015d29adb65048914" is missing kube-controller-manager pod Pod kube-system/aws-load-balancer-controller-9c4f8f9df-28qmn system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-28qmn" is pending Pod kube-system/aws-load-balancer-controller-9c4f8f9df-n75jx system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-n75jx" is pending Validation Failed W0322 05:31:19.501123 6468 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-1b ControlPlane c5.large 1 1 us-east-1b master-us-east-1e ControlPlane c5.large 1 1 us-east-1e ... skipping 21 lines ... Node i-015d29adb65048914 control-plane node "i-015d29adb65048914" is missing kube-controller-manager pod Pod kube-system/aws-load-balancer-controller-9c4f8f9df-28qmn system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-28qmn" is pending Pod kube-system/aws-load-balancer-controller-9c4f8f9df-n75jx system-cluster-critical pod "aws-load-balancer-controller-9c4f8f9df-n75jx" is pending Pod kube-system/etcd-manager-events-i-015d29adb65048914 system-cluster-critical pod "etcd-manager-events-i-015d29adb65048914" is pending Pod kube-system/kube-proxy-i-015d29adb65048914 system-node-critical pod "kube-proxy-i-015d29adb65048914" is pending Validation Failed W0322 05:31:31.698188 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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-015d29adb65048914 control-plane node "i-015d29adb65048914" is missing kube-controller-manager pod Validation Failed W0322 05:31:43.735936 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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-015d29adb65048914 control-plane node "i-015d29adb65048914" is missing kube-controller-manager pod Validation Failed W0322 05:31:55.882379 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 Pod kube-system/kube-proxy-i-0171c578f6a3fc57c system-node-critical pod "kube-proxy-i-0171c578f6a3fc57c" is pending Pod kube-system/kube-proxy-i-07c2de02b581e5075 system-node-critical pod "kube-proxy-i-07c2de02b581e5075" is pending Validation Failed W0322 05:32:07.988036 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:32:20.731840 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:32:32.933705 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:32:45.089127 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:32:57.336283 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:33:09.633008 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:33:21.818787 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:33:34.011422 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:33:46.209232 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:33:58.490137 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:34:10.856610 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:34:23.169364 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:34:35.847413 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:34:48.049121 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:35:00.339753 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:35:12.404535 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:35:24.435289 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:35:36.948165 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:35:49.120392 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:36:01.164362 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:36:13.244885 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:36:26.140080 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:36:38.306403 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:36:50.280008 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:37:02.729657 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:37:14.816193 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:37:26.881949 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:37:39.380495 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:37:51.674986 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:38:04.367332 6468 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-1b ControlPlane c5.large 1 1 us-east-1b 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 W0322 05:38:16.613231 6468 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.71SAMbsES --down I0322 05:38:26.647414 6488 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0322 05:38:26.648345 6488 app.go:61] The files in RunDir shall not be part of Artifacts I0322 05:38:26.648368 6488 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I0322 05:38:26.648390 6488 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/4b675ddc-c871-11ed-abe9-f26dd6892cca" ... skipping 477 lines ...