This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 1 succeeded
Started2023-03-23 23:21
Elapsed51m10s
Revisionmaster

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 205 lines ...
I0323 23:22:14.941219    6350 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/467fbb7a-c9d1-11ed-8be2-1221e2764aa1"
I0323 23:22:14.946972    6350 app.go:128] ID for this run: "467fbb7a-c9d1-11ed-8be2-1221e2764aa1"
I0323 23:22:14.947209    6350 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-9b8b75964a-36844.test-cncf-aws.k8s.io/id_ed25519
I0323 23:22:14.959229    6350 dumplogs.go:45] /tmp/kops.SP779Xgx0 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
I0323 23:22:14.959370    6350 local.go:42] ⚙️ /tmp/kops.SP779Xgx0 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
I0323 23:22:14.992109    6360 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag"
Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found
W0323 23:22:15.491642    6350 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0323 23:22:15.491674    6350 down.go:48] /tmp/kops.SP779Xgx0 delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes
I0323 23:22:15.491685    6350 local.go:42] ⚙️ /tmp/kops.SP779Xgx0 delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes
I0323 23:22:15.532087    6370 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-492-gf2f28e4cde
... skipping 15 lines ...
I0323 23:22:17.491774    6407 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/467fbb7a-c9d1-11ed-8be2-1221e2764aa1"
I0323 23:22:17.494577    6407 app.go:128] ID for this run: "467fbb7a-c9d1-11ed-8be2-1221e2764aa1"
I0323 23:22:17.494722    6407 up.go:44] Cleaning up any leaked resources from previous cluster
I0323 23:22:17.494796    6407 dumplogs.go:45] /tmp/kops.tjQvC7xmG 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
I0323 23:22:17.494853    6407 local.go:42] ⚙️ /tmp/kops.tjQvC7xmG 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
I0323 23:22:17.527953    6416 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag"
Error: Cluster.kops.k8s.io "e2e-9b8b75964a-36844.test-cncf-aws.k8s.io" not found
W0323 23:22:18.027217    6407 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0323 23:22:18.027293    6407 down.go:48] /tmp/kops.tjQvC7xmG delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes
I0323 23:22:18.027305    6407 local.go:42] ⚙️ /tmp/kops.tjQvC7xmG delete cluster --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io --yes
I0323 23:22:18.059255    6423 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
I0323 23:22:18.506365    6407 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2023/03/23 23:22: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
I0323 23:22:18.518559    6407 http.go:37] curl https://ip.jsb.workers.dev
I0323 23:22:18.632075    6407 template.go:58] /tmp/kops.tjQvC7xmG toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template2580191187/manifest.yaml --values /tmp/kops-template2580191187/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io
I0323 23:22:18.632428    6407 local.go:42] ⚙️ /tmp/kops.tjQvC7xmG toolbox template --template tests/e2e/templates/many-addons.yaml.tmpl --output /tmp/kops-template2580191187/manifest.yaml --values /tmp/kops-template2580191187/values.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io
I0323 23:22:18.664309    6437 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag"
I0323 23:22:18.838600    6407 create.go:33] /tmp/kops.tjQvC7xmG create --filename /tmp/kops-template2580191187/manifest.yaml --name e2e-9b8b75964a-36844.test-cncf-aws.k8s.io
I0323 23:22:18.838658    6407 local.go:42] ⚙️ /tmp/kops.tjQvC7xmG create --filename /tmp/kops-template2580191187/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
W0323 23:22:54.161475    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:23:04.214089    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:23:14.259882    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:23:24.293509    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:23:34.350078    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:23:44.397934    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:23:54.442529    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:24:04.477057    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:24:14.524312    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:24:24.585380    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:24:34.616836    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:24:44.655312    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:24:54.685414    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:25:04.719936    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:25:14.749742    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:25:24.785503    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:25:34.820173    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:25:44.867907    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:25:54.899212    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:26:04.928170    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:26:14.986714    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:26:25.016032    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:26:35.045598    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:26:45.078107    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:26:55.109454    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:27:05.158395    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:27:15.192403    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:27:25.225887    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... 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
W0323 23:27:35.257080    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
W0323 23:28:15.303351    6474 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-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1a	Node		t3.medium	4	4	eu-central-1a
... skipping 40 lines ...
Pod	kube-system/node-local-dns-8nh5q				system-node-critical pod "node-local-dns-8nh5q" is pending
Pod	kube-system/node-local-dns-g9psk				system-node-critical pod "node-local-dns-g9psk" is pending
Pod	kube-system/node-local-dns-ltwr4				system-node-critical pod "node-local-dns-ltwr4" is pending
Pod	kube-system/pod-identity-webhook-57f4f9bd45-jjdwg		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-jjdwg" is pending
Pod	kube-system/pod-identity-webhook-57f4f9bd45-nm5z5		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-nm5z5" is pending

Validation Failed
W0323 23:28:30.314223    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 64 lines ...
Pod	kube-system/node-local-dns-cvvgs				system-node-critical pod "node-local-dns-cvvgs" is pending
Pod	kube-system/node-local-dns-h89w9				system-node-critical pod "node-local-dns-h89w9" is pending
Pod	kube-system/node-local-dns-qfcpk				system-node-critical pod "node-local-dns-qfcpk" is pending
Pod	kube-system/pod-identity-webhook-57f4f9bd45-jjdwg		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-jjdwg" is pending
Pod	kube-system/pod-identity-webhook-57f4f9bd45-nm5z5		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-nm5z5" is pending

Validation Failed
W0323 23:28:44.329446    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 54 lines ...
Pod	kube-system/metrics-server-db468d46c-qgfr5			system-cluster-critical pod "metrics-server-db468d46c-qgfr5" is not ready (metrics-server)
Pod	kube-system/node-local-dns-fxhhx				system-node-critical pod "node-local-dns-fxhhx" is pending
Pod	kube-system/node-local-dns-g5f7p				system-node-critical pod "node-local-dns-g5f7p" is pending
Pod	kube-system/pod-identity-webhook-57f4f9bd45-jjdwg		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-jjdwg" is pending
Pod	kube-system/pod-identity-webhook-57f4f9bd45-nm5z5		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-nm5z5" is not ready (pod-identity-webhook)

Validation Failed
W0323 23:28:58.287653    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 34 lines ...
Pod	kube-system/ebs-csi-node-8qxkq					system-node-critical pod "ebs-csi-node-8qxkq" is pending
Pod	kube-system/kube-scheduler-i-08bfe64398056354b			system-cluster-critical pod "kube-scheduler-i-08bfe64398056354b" is pending
Pod	kube-system/metrics-server-db468d46c-4zks5			system-cluster-critical pod "metrics-server-db468d46c-4zks5" is not ready (metrics-server)
Pod	kube-system/metrics-server-db468d46c-qgfr5			system-cluster-critical pod "metrics-server-db468d46c-qgfr5" is not ready (metrics-server)
Pod	kube-system/pod-identity-webhook-57f4f9bd45-jjdwg		system-cluster-critical pod "pod-identity-webhook-57f4f9bd45-jjdwg" is not ready (pod-identity-webhook)

Validation Failed
W0323 23:29:12.257161    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 24 lines ...
Node	i-08bfe64398056354b						control-plane node "i-08bfe64398056354b" is missing kube-controller-manager pod
Node	i-09ad4f1418057d6e3						control-plane node "i-09ad4f1418057d6e3" is missing kube-controller-manager pod
Node	i-0bd980b390f2091f9						control-plane node "i-0bd980b390f2091f9" is missing kube-scheduler pod
Pod	kube-system/aws-load-balancer-controller-cd678467f-hlrbv	system-cluster-critical pod "aws-load-balancer-controller-cd678467f-hlrbv" is pending
Pod	kube-system/aws-load-balancer-controller-cd678467f-w49p2	system-cluster-critical pod "aws-load-balancer-controller-cd678467f-w49p2" is pending

Validation Failed
W0323 23:29:26.261772    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 26 lines ...
Node	i-0bd980b390f2091f9						control-plane node "i-0bd980b390f2091f9" is missing kube-scheduler pod
Pod	kube-system/aws-load-balancer-controller-cd678467f-hlrbv	system-cluster-critical pod "aws-load-balancer-controller-cd678467f-hlrbv" is pending
Pod	kube-system/aws-load-balancer-controller-cd678467f-w49p2	system-cluster-critical pod "aws-load-balancer-controller-cd678467f-w49p2" is pending
Pod	kube-system/kube-proxy-i-09ad4f1418057d6e3			system-node-critical pod "kube-proxy-i-09ad4f1418057d6e3" is pending
Pod	kube-system/kube-scheduler-i-0bd980b390f2091f9			system-cluster-critical pod "kube-scheduler-i-0bd980b390f2091f9" is pending

Validation Failed
W0323 23:29:40.071246    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 24 lines ...
Node	i-08bfe64398056354b				control-plane node "i-08bfe64398056354b" is missing kube-controller-manager pod
Node	i-09ad4f1418057d6e3				control-plane node "i-09ad4f1418057d6e3" is missing kube-controller-manager pod
Pod	kube-system/kube-proxy-i-00697b40342e74cce	system-node-critical pod "kube-proxy-i-00697b40342e74cce" is pending
Pod	kube-system/kube-proxy-i-0635fb2d3dd8854fa	system-node-critical pod "kube-proxy-i-0635fb2d3dd8854fa" is pending
Pod	kube-system/kube-proxy-i-070ae8a3a5c8659ff	system-node-critical pod "kube-proxy-i-070ae8a3a5c8659ff" is pending

Validation Failed
W0323 23:29:53.933732    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 22 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	i-09ad4f1418057d6e3				control-plane node "i-09ad4f1418057d6e3" is missing kube-controller-manager pod
Pod	kube-system/kube-proxy-i-0c45fecb566dd8b52	system-node-critical pod "kube-proxy-i-0c45fecb566dd8b52" is pending
Pod	kube-system/kube-proxy-i-0ea935a6c143cbb9c	system-node-critical pod "kube-proxy-i-0ea935a6c143cbb9c" is pending

Validation Failed
W0323 23:30:08.010718    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 23 lines ...
KIND	NAME							MESSAGE
Node	i-09ad4f1418057d6e3					control-plane node "i-09ad4f1418057d6e3" is missing kube-controller-manager pod
Pod	kube-system/kube-controller-manager-i-09ad4f1418057d6e3	system-cluster-critical pod "kube-controller-manager-i-09ad4f1418057d6e3" is pending
Pod	kube-system/kube-proxy-i-0b0ccf3fe9975c07d		system-node-critical pod "kube-proxy-i-0b0ccf3fe9975c07d" is pending
Pod	kube-system/kube-proxy-i-0bfb6f1225546480f		system-node-critical pod "kube-proxy-i-0bfb6f1225546480f" is pending

Validation Failed
W0323 23:30:22.494804    6474 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE		MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	ControlPlane	c5.large	1	1	eu-central-1a
master-eu-central-1b	ControlPlane	c5.large	1	1	eu-central-1b
master-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
... skipping 1238 lines ...
I0324 00:04:03.291138    6588 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-020fa94967dfce5e2" has not yet joined cluster.
I0324 00:04:37.476606    6588 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-020fa94967dfce5e2" has not yet joined cluster.
I0324 00:05:11.513351    6588 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-020fa94967dfce5e2" has not yet joined cluster.
I0324 00:05:45.921159    6588 instancegroups.go:560] Cluster did not pass validation, will retry in "30s": machine "i-020fa94967dfce5e2" has not yet joined cluster.
I0324 00:06:19.966731    6588 instancegroups.go:557] Cluster did not pass validation within deadline: machine "i-020fa94967dfce5e2" has not yet joined cluster.
E0324 00:06:19.966807    6588 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.SP779Xgx0 --down
I0324 00:06:20.009112    6606 featureflag.go:167] Unknown FeatureFlag "SpecOverrideFlag"
I0324 00:06:20.010397    6606 app.go:61] The files in RunDir shall not be part of Artifacts
I0324 00:06:20.010424    6606 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I0324 00:06:20.010451    6606 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/467fbb7a-c9d1-11ed-8be2-1221e2764aa1"
... skipping 671 lines ...