e2e-kops-aws-upgrade-kstable-kolatest-to-kci-kolatest-many-addons #1637957191342231552
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 49m7s |
| Revision | master |
kubetest2 Down
... skipping 205 lines ... I0320 23:21:49.683613 6336 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/bca46336-c775-11ed-9e5f-baf334638f51" I0320 23:21:49.688388 6336 app.go:128] ID for this run: "bca46336-c775-11ed-9e5f-baf334638f51" I0320 23:21:49.688599 6336 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519 I0320 23:21:49.699092 6336 dumplogs.go:45] /tmp/kops.YgvH17naG 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 I0320 23:21:49.699252 6336 local.go:42] ⚙️ /tmp/kops.YgvH17naG 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 I0320 23:21:49.729256 6346 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found W0320 23:21:50.226166 6336 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0320 23:21:50.226213 6336 down.go:48] /tmp/kops.YgvH17naG delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0320 23:21:50.226227 6336 local.go:42] ⚙️ /tmp/kops.YgvH17naG delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0320 23:21:50.255344 6356 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 ... I0320 23:21:52.137977 6393 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/bca46336-c775-11ed-9e5f-baf334638f51" I0320 23:21:52.204408 6393 app.go:128] ID for this run: "bca46336-c775-11ed-9e5f-baf334638f51" I0320 23:21:52.204503 6393 up.go:44] Cleaning up any leaked resources from previous cluster I0320 23:21:52.204543 6393 dumplogs.go:45] /tmp/kops.wmu0Mxnbu 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 I0320 23:21:52.204580 6393 local.go:42] ⚙️ /tmp/kops.wmu0Mxnbu 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 I0320 23:21:52.237118 6404 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found W0320 23:21:52.732036 6393 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0320 23:21:52.732119 6393 down.go:48] /tmp/kops.wmu0Mxnbu delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0320 23:21:52.732132 6393 local.go:42] ⚙️ /tmp/kops.wmu0Mxnbu delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes I0320 23:21:52.761882 6414 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 I0320 23:21:53.229608 6393 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/03/20 23:21:53 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 I0320 23:21:53.243166 6393 http.go:37] curl https://ip.jsb.workers.dev I0320 23:21:53.347475 6393 template.go:58] /tmp/kops.wmu0Mxnbu toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template4220592342/manifest.yaml --values /tmp/kops-template4220592342/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0320 23:21:53.347526 6393 local.go:42] ⚙️ /tmp/kops.wmu0Mxnbu toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template4220592342/manifest.yaml --values /tmp/kops-template4220592342/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0320 23:21:53.377649 6424 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0320 23:21:53.543571 6393 create.go:33] /tmp/kops.wmu0Mxnbu create --filename /tmp/kops-template4220592342/manifest.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io I0320 23:21:53.543628 6393 local.go:42] ⚙️ /tmp/kops.wmu0Mxnbu create --filename /tmp/kops-template4220592342/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 W0320 23:22:31.278504 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:22:41.309707 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:22:51.342700 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:23:01.375154 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:23:11.420179 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:23:21.463215 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:23:31.522475 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:23:41.554156 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:23:51.585018 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:24:01.614723 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:24:11.646522 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:24:21.677302 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:24:31.707797 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:24:41.741838 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:24:51.805062 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:25:01.834829 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:25:11.887297 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:25:21.916307 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:25:31.961097 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:25:41.992632 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:25:52.033942 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:26:02.076383 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:26:12.122143 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:26:22.178562 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:26:32.212942 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:26:42.243281 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:26:52.289297 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:27:02.385447 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:27:12.417433 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:27:22.450424 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... 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 W0320 23:27:32.479976 6465 validate_cluster.go:232] (will retry): cluster not yet healthy W0320 23:28:12.554765 6465 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d nodes-ca-central-1a Node t3.medium 4 4 ca-central-1a ... skipping 33 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-cqdx5 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-cqdx5" is pending Pod kube-system/metrics-server-db468d46c-kkhlq system-cluster-critical pod "metrics-server-db468d46c-kkhlq" is pending Pod kube-system/metrics-server-db468d46c-n9b75 system-cluster-critical pod "metrics-server-db468d46c-n9b75" is pending Pod kube-system/pod-identity-webhook-df88d966c-fnnvf system-cluster-critical pod "pod-identity-webhook-df88d966c-fnnvf" is pending Pod kube-system/pod-identity-webhook-df88d966c-sgbts system-cluster-critical pod "pod-identity-webhook-df88d966c-sgbts" is pending Validation Failed W0320 23:28:25.015959 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 31 lines ... Pod kube-system/coredns-autoscaler-7cb5c5b969-cqdx5 system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-cqdx5" is pending Pod kube-system/metrics-server-db468d46c-kkhlq system-cluster-critical pod "metrics-server-db468d46c-kkhlq" is pending Pod kube-system/metrics-server-db468d46c-n9b75 system-cluster-critical pod "metrics-server-db468d46c-n9b75" is pending Pod kube-system/pod-identity-webhook-df88d966c-fnnvf system-cluster-critical pod "pod-identity-webhook-df88d966c-fnnvf" is pending Pod kube-system/pod-identity-webhook-df88d966c-sgbts system-cluster-critical pod "pod-identity-webhook-df88d966c-sgbts" is pending Validation Failed W0320 23:28:36.934241 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 67 lines ... Pod kube-system/node-local-dns-pkpp2 system-node-critical pod "node-local-dns-pkpp2" is pending Pod kube-system/node-local-dns-qwz9r system-node-critical pod "node-local-dns-qwz9r" is pending Pod kube-system/node-local-dns-rzcx6 system-node-critical pod "node-local-dns-rzcx6" is pending Pod kube-system/pod-identity-webhook-df88d966c-fnnvf system-cluster-critical pod "pod-identity-webhook-df88d966c-fnnvf" is pending Pod kube-system/pod-identity-webhook-df88d966c-sgbts system-cluster-critical pod "pod-identity-webhook-df88d966c-sgbts" is pending Validation Failed W0320 23:28:48.909352 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 62 lines ... Pod kube-system/node-local-dns-bfrkc system-node-critical pod "node-local-dns-bfrkc" is pending Pod kube-system/node-local-dns-g956l system-node-critical pod "node-local-dns-g956l" is pending Pod kube-system/node-local-dns-zhqj6 system-node-critical pod "node-local-dns-zhqj6" is pending Pod kube-system/pod-identity-webhook-df88d966c-fnnvf system-cluster-critical pod "pod-identity-webhook-df88d966c-fnnvf" is pending Pod kube-system/pod-identity-webhook-df88d966c-sgbts system-cluster-critical pod "pod-identity-webhook-df88d966c-sgbts" is pending Validation Failed W0320 23:29:00.870549 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 37 lines ... Pod kube-system/ebs-csi-node-xlttx system-node-critical pod "ebs-csi-node-xlttx" is pending Pod kube-system/ebs-csi-node-zt5f7 system-node-critical pod "ebs-csi-node-zt5f7" is pending Pod kube-system/metrics-server-db468d46c-kkhlq system-cluster-critical pod "metrics-server-db468d46c-kkhlq" is not ready (metrics-server) Pod kube-system/metrics-server-db468d46c-n9b75 system-cluster-critical pod "metrics-server-db468d46c-n9b75" is not ready (metrics-server) Pod kube-system/pod-identity-webhook-df88d966c-fnnvf system-cluster-critical pod "pod-identity-webhook-df88d966c-fnnvf" is not ready (pod-identity-webhook) Validation Failed W0320 23:29:13.830773 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 27 lines ... Node i-058a716431873bd6c control-plane node "i-058a716431873bd6c" is missing kube-scheduler pod Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-controller-manager pod Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-scheduler pod Pod kube-system/metrics-server-db468d46c-kkhlq system-cluster-critical pod "metrics-server-db468d46c-kkhlq" is not ready (metrics-server) Pod kube-system/metrics-server-db468d46c-n9b75 system-cluster-critical pod "metrics-server-db468d46c-n9b75" is not ready (metrics-server) Validation Failed W0320 23:29:25.941207 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 26 lines ... Node i-058a716431873bd6c control-plane node "i-058a716431873bd6c" is missing kube-controller-manager pod Node i-058a716431873bd6c control-plane node "i-058a716431873bd6c" is missing kube-scheduler pod Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-controller-manager pod Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-scheduler pod Pod kube-system/etcd-manager-main-i-058a716431873bd6c system-cluster-critical pod "etcd-manager-main-i-058a716431873bd6c" is pending Validation Failed W0320 23:29:37.913913 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 24 lines ... Node i-00ad7295d509e878d control-plane node "i-00ad7295d509e878d" is missing kube-controller-manager pod Node i-058a716431873bd6c control-plane node "i-058a716431873bd6c" is missing kube-scheduler pod Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-scheduler pod Pod kube-system/etcd-manager-events-i-00ad7295d509e878d system-cluster-critical pod "etcd-manager-events-i-00ad7295d509e878d" is pending Pod kube-system/etcd-manager-events-i-0c8f8c5bd74678bd9 system-cluster-critical pod "etcd-manager-events-i-0c8f8c5bd74678bd9" is pending Validation Failed W0320 23:29:49.821126 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 25 lines ... Node i-058a716431873bd6c control-plane node "i-058a716431873bd6c" is missing kube-scheduler pod Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-scheduler pod Pod kube-system/etcd-manager-main-i-0c8f8c5bd74678bd9 system-cluster-critical pod "etcd-manager-main-i-0c8f8c5bd74678bd9" is pending Pod kube-system/kube-proxy-i-01228484d30dbc684 system-node-critical pod "kube-proxy-i-01228484d30dbc684" is pending Pod kube-system/kube-proxy-i-0c8f8c5bd74678bd9 system-node-critical pod "kube-proxy-i-0c8f8c5bd74678bd9" is pending Validation Failed W0320 23:30:02.105188 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 26 lines ... Node i-0c8f8c5bd74678bd9 control-plane node "i-0c8f8c5bd74678bd9" is missing kube-scheduler pod Pod kube-system/kube-proxy-i-00a69aa9de5a1c9b0 system-node-critical pod "kube-proxy-i-00a69aa9de5a1c9b0" is pending Pod kube-system/kube-proxy-i-07e06fba7b79f3b93 system-node-critical pod "kube-proxy-i-07e06fba7b79f3b93" is pending Pod kube-system/kube-proxy-i-0f77771886670046a system-node-critical pod "kube-proxy-i-0f77771886670046a" is pending Pod kube-system/kube-scheduler-i-0c8f8c5bd74678bd9 system-cluster-critical pod "kube-scheduler-i-0c8f8c5bd74678bd9" is pending Validation Failed W0320 23:30:14.101106 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 20 lines ... i-0f77771886670046a node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/kube-proxy-i-0a03753cd9a206225 system-node-critical pod "kube-proxy-i-0a03753cd9a206225" is pending Validation Failed W0320 23:30:26.056554 6465 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ca-central-1a ControlPlane c5.large 1 1 ca-central-1a master-ca-central-1b ControlPlane c5.large 1 1 ca-central-1b master-ca-central-1d ControlPlane c5.large 1 1 ca-central-1d ... skipping 1243 lines ... I0321 00:04:15.365048 6582 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-092b6f4d6cf9b3ec6" has not yet joined cluster. I0321 00:04:47.467184 6582 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-092b6f4d6cf9b3ec6" has not yet joined cluster. I0321 00:05:19.579403 6582 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-092b6f4d6cf9b3ec6" has not yet joined cluster. I0321 00:05:51.663379 6582 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-092b6f4d6cf9b3ec6" has not yet joined cluster. I0321 00:06:23.587907 6582 instancegroups.go:557] Cluster did not pass validation within deadline: machine "i-092b6f4d6cf9b3ec6" has not yet joined cluster. E0321 00:06:23.587961 6582 instancegroups.go:506] Cluster did not validate within 30m0s Error: control-plane node not healthy after update, stopping rolling-update: "error validating cluster after terminating instance: cluster did not validate within a duration of \"30m0s\"" + 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.YgvH17naG --down I0321 00:06:23.615650 6601 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0321 00:06:23.616759 6601 app.go:61] The files in RunDir shall not be part of Artifacts I0321 00:06:23.616782 6601 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I0321 00:06:23.616814 6601 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/bca46336-c775-11ed-9e5f-baf334638f51" ... skipping 555 lines ...