e2e-kops-aws-upgrade-k121-ko1260-beta1-to-k122-ko126-many-addons #1619431205785047040
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 1h35m |
| Revision | master |
kubetest2 Down
... skipping 192 lines ... I0128 20:26:14.956173 5740 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/bfbfde6c-9f49-11ed-9a0c-f25a29267a91" I0128 20:26:14.977485 5740 app.go:128] ID for this run: "bfbfde6c-9f49-11ed-9a0c-f25a29267a91" I0128 20:26:14.977752 5740 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-cab136efef-554b9.test-cncf-aws.k8s.io/id_ed25519 I0128 20:26:14.985359 5740 dumplogs.go:45] /tmp/kops.y7BWFRKCT toolbox dump --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-cab136efef-554b9.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0128 20:26:14.985413 5740 local.go:42] ⚙️ /tmp/kops.y7BWFRKCT toolbox dump --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-cab136efef-554b9.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0128 20:26:15.016418 5750 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: Cluster.kops.k8s.io "e2e-cab136efef-554b9.test-cncf-aws.k8s.io" not found W0128 20:26:15.469973 5740 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0128 20:26:15.470036 5740 down.go:48] /tmp/kops.y7BWFRKCT delete cluster --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --yes I0128 20:26:15.470046 5740 local.go:42] ⚙️ /tmp/kops.y7BWFRKCT delete cluster --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --yes I0128 20:26:15.501166 5757 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-cab136efef-554b9.test-cncf-aws.k8s.io" not found Error: exit status 1 + echo 'kubetest2 down failed' kubetest2 down failed + [[ v == \v ]] + KOPS_BASE_URL= ++ kops-download-release v1.26.0-beta.1 ++ local kops +++ mktemp -t kops.XXXXXXXXX ++ kops=/tmp/kops.cwOuuQlLD ... skipping 11 lines ... I0128 20:26:17.475308 5792 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/bfbfde6c-9f49-11ed-9a0c-f25a29267a91" I0128 20:26:17.482758 5792 app.go:128] ID for this run: "bfbfde6c-9f49-11ed-9a0c-f25a29267a91" I0128 20:26:17.482847 5792 up.go:44] Cleaning up any leaked resources from previous cluster I0128 20:26:17.482911 5792 dumplogs.go:45] /tmp/kops.cwOuuQlLD toolbox dump --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-cab136efef-554b9.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0128 20:26:17.482942 5792 local.go:42] ⚙️ /tmp/kops.cwOuuQlLD toolbox dump --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-cab136efef-554b9.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0128 20:26:17.514659 5799 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: Cluster.kops.k8s.io "e2e-cab136efef-554b9.test-cncf-aws.k8s.io" not found W0128 20:26:17.993783 5792 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0128 20:26:17.993818 5792 down.go:48] /tmp/kops.cwOuuQlLD delete cluster --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --yes I0128 20:26:17.993834 5792 local.go:42] ⚙️ /tmp/kops.cwOuuQlLD delete cluster --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io --yes I0128 20:26:18.025784 5812 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-cab136efef-554b9.test-cncf-aws.k8s.io" not found I0128 20:26:18.477643 5792 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/28 20:26:18 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 I0128 20:26:18.492496 5792 http.go:37] curl https://ip.jsb.workers.dev I0128 20:26:18.598774 5792 template.go:58] /tmp/kops.cwOuuQlLD toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template2493463652/manifest.yaml --values /tmp/kops-template2493463652/values.yaml --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io I0128 20:26:18.598812 5792 local.go:42] ⚙️ /tmp/kops.cwOuuQlLD toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template2493463652/manifest.yaml --values /tmp/kops-template2493463652/values.yaml --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io I0128 20:26:18.628929 5823 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true I0128 20:26:18.721501 5792 create.go:33] /tmp/kops.cwOuuQlLD create --filename /tmp/kops-template2493463652/manifest.yaml --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io I0128 20:26:18.721553 5792 local.go:42] ⚙️ /tmp/kops.cwOuuQlLD create --filename /tmp/kops-template2493463652/manifest.yaml --name e2e-cab136efef-554b9.test-cncf-aws.k8s.io ... skipping 72 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 W0128 20:27:05.020225 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:27:15.061310 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:27:25.107536 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:27:35.146939 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:27:45.185579 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:27:55.234762 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:28:05.267272 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:28:15.297176 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:28:25.329391 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:28:35.364225 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:28:45.411734 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:28:55.444452 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:29:05.478464 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:29:15.513558 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:29:25.546616 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:29:35.578343 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:29:45.617042 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:29:55.658312 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:30:05.696575 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:30:15.738158 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:30:25.777575 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:30:35.824215 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:30:45.871747 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:30:55.906913 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:31:05.940925 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... 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 W0128 20:31:15.988803 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 41 lines ... Pod kube-system/coredns-autoscaler-5b654cd776-xjfnt system-cluster-critical pod "coredns-autoscaler-5b654cd776-xjfnt" is pending Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is pending Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:31:30.943553 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 40 lines ... Pod kube-system/coredns-autoscaler-5b654cd776-xjfnt system-cluster-critical pod "coredns-autoscaler-5b654cd776-xjfnt" is pending Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is pending Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:31:44.841242 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 37 lines ... Pod kube-system/coredns-autoscaler-5b654cd776-xjfnt system-cluster-critical pod "coredns-autoscaler-5b654cd776-xjfnt" is pending Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is pending Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:31:58.584011 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 33 lines ... Pod kube-system/coredns-autoscaler-5b654cd776-xjfnt system-cluster-critical pod "coredns-autoscaler-5b654cd776-xjfnt" is pending Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is pending Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:32:12.497155 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 37 lines ... Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is pending Pod kube-system/node-local-dns-8nrrf system-node-critical pod "node-local-dns-8nrrf" is pending Pod kube-system/node-local-dns-99dcr system-node-critical pod "node-local-dns-99dcr" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:32:26.313625 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 64 lines ... Pod kube-system/node-local-dns-k49hh system-node-critical pod "node-local-dns-k49hh" is pending Pod kube-system/node-local-dns-xm8wf system-node-critical pod "node-local-dns-xm8wf" is pending Pod kube-system/node-local-dns-z6hcd system-node-critical pod "node-local-dns-z6hcd" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:32:40.307680 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 50 lines ... Pod kube-system/coredns-autoscaler-5b654cd776-xjfnt system-cluster-critical pod "coredns-autoscaler-5b654cd776-xjfnt" is pending Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is pending Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is pending Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:32:54.262929 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 38 lines ... Pod kube-system/coredns-67487c96bf-lf5l8 system-cluster-critical pod "coredns-67487c96bf-lf5l8" is not ready (coredns) Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is not ready (metrics-server) Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is not ready (metrics-server) Pod kube-system/pod-identity-webhook-5d89b87449-2tqbf system-cluster-critical pod "pod-identity-webhook-5d89b87449-2tqbf" is pending Pod kube-system/pod-identity-webhook-5d89b87449-6dchc system-cluster-critical pod "pod-identity-webhook-5d89b87449-6dchc" is pending Validation Failed W0128 20:33:08.562872 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 29 lines ... Node ip-172-20-2-187.eu-west-3.compute.internal control-plane node "ip-172-20-2-187.eu-west-3.compute.internal" is missing kube-scheduler pod Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Pod kube-system/metrics-server-76b7954c74-fljl9 system-cluster-critical pod "metrics-server-76b7954c74-fljl9" is not ready (metrics-server) Pod kube-system/metrics-server-76b7954c74-jbrj2 system-cluster-critical pod "metrics-server-76b7954c74-jbrj2" is not ready (metrics-server) Validation Failed W0128 20:33:22.770407 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 28 lines ... Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Pod kube-system/kube-proxy-ip-172-20-1-254.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-1-254.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-2-187.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-2-187.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-2-87.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-2-87.eu-west-3.compute.internal" is pending Validation Failed W0128 20:33:36.558306 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 30 lines ... Pod kube-system/etcd-manager-events-ip-172-20-0-87.eu-west-3.compute.internal system-cluster-critical pod "etcd-manager-events-ip-172-20-0-87.eu-west-3.compute.internal" is pending Pod kube-system/kube-controller-manager-ip-172-20-0-87.eu-west-3.compute.internal system-cluster-critical pod "kube-controller-manager-ip-172-20-0-87.eu-west-3.compute.internal" is pending Pod kube-system/kube-controller-manager-ip-172-20-1-254.eu-west-3.compute.internal system-cluster-critical pod "kube-controller-manager-ip-172-20-1-254.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-0-84.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-0-84.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-1-124.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-1-124.eu-west-3.compute.internal" is pending Validation Failed W0128 20:33:50.765860 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 25 lines ... Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Pod kube-system/kube-proxy-ip-172-20-0-83.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-0-83.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-1-15.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-1-15.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-2-22.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-2-22.eu-west-3.compute.internal" is pending Validation Failed W0128 20:34:04.810161 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 24 lines ... Node ip-172-20-2-187.eu-west-3.compute.internal control-plane node "ip-172-20-2-187.eu-west-3.compute.internal" is missing kube-scheduler pod Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Pod kube-system/etcd-manager-main-ip-172-20-1-254.eu-west-3.compute.internal system-cluster-critical pod "etcd-manager-main-ip-172-20-1-254.eu-west-3.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-0-87.eu-west-3.compute.internal system-node-critical pod "kube-proxy-ip-172-20-0-87.eu-west-3.compute.internal" is pending Validation Failed W0128 20:34:19.233509 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 22 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Pod kube-system/etcd-manager-events-ip-172-20-1-254.eu-west-3.compute.internal system-cluster-critical pod "etcd-manager-events-ip-172-20-1-254.eu-west-3.compute.internal" is pending Validation Failed W0128 20:34:33.059214 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 21 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Validation Failed W0128 20:34:46.894932 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 21 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/aws-load-balancer-controller-c88dcb4f7-l2pkx system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-l2pkx" is pending Pod kube-system/aws-load-balancer-controller-c88dcb4f7-lq26m system-cluster-critical pod "aws-load-balancer-controller-c88dcb4f7-lq26m" is pending Validation Failed W0128 20:35:00.871358 5862 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-3a ControlPlane c5.large 1 1 eu-west-3a master-eu-west-3b ControlPlane c5.large 1 1 eu-west-3b master-eu-west-3c ControlPlane c5.large 1 1 eu-west-3c ... skipping 2287 lines ... I0128 21:50:19.600082 5977 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "aws-load-balancer-controller-6c7fb54569-5kstj" is pending, system-cluster-critical pod "aws-node-termination-handler-75c77b9b57-4zzfv" is pending, system-cluster-critical pod "cluster-autoscaler-74bcc6769c-hg9r9" is pending. I0128 21:50:53.864201 5977 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "aws-load-balancer-controller-6c7fb54569-5kstj" is pending, system-cluster-critical pod "aws-node-termination-handler-75c77b9b57-4zzfv" is pending, system-cluster-critical pod "cluster-autoscaler-74bcc6769c-hg9r9" is pending. I0128 21:51:27.627820 5977 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "aws-load-balancer-controller-6c7fb54569-5kstj" is pending, system-cluster-critical pod "aws-node-termination-handler-75c77b9b57-4zzfv" is pending, system-cluster-critical pod "cluster-autoscaler-74bcc6769c-hg9r9" is pending. I0128 21:52:02.344546 5977 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": system-cluster-critical pod "aws-load-balancer-controller-6c7fb54569-5kstj" is pending, system-cluster-critical pod "aws-node-termination-handler-75c77b9b57-4zzfv" is pending, system-cluster-critical pod "cluster-autoscaler-74bcc6769c-hg9r9" is pending. I0128 21:52:36.473819 5977 instancegroups.go:557] Cluster did not pass validation within deadline: system-cluster-critical pod "aws-load-balancer-controller-6c7fb54569-5kstj" is pending, system-cluster-critical pod "aws-node-termination-handler-75c77b9b57-4zzfv" is pending, system-cluster-critical pod "cluster-autoscaler-74bcc6769c-hg9r9" is pending. E0128 21:52:36.473874 5977 instancegroups.go:506] Cluster did not validate within 30m0s E0128 21:52:36.473889 5977 rollingupdate.go:218] failed to roll InstanceGroup "nodes-eu-west-3c": error validating cluster after detaching instance: cluster did not validate within a duration of "30m0s" Error: error validating cluster after detaching instance: cluster did not validate within a duration of "30m0s" + kops-finish + kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-cab136efef-554b9.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.y7BWFRKCT --down I0128 21:52:36.500517 5995 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag" I0128 21:52:36.501300 5995 app.go:61] The files in RunDir shall not be part of Artifacts I0128 21:52:36.501321 5995 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I0128 21:52:36.501341 5995 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/bfbfde6c-9f49-11ed-9a0c-f25a29267a91" ... skipping 1140 lines ...