This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-26 09:23
Elapsed18m14s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I0926 09:24:40.656718    4688 up.go:43] Cleaning up any leaked resources from previous cluster
I0926 09:24:40.656755    4688 dumplogs.go:40] /logs/artifacts/62933833-1eab-11ec-aa51-d2836bccddff/kops toolbox dump --name e2e-f8797b4dae-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0926 09:24:40.672440    4708 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0926 09:24:40.672538    4708 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-f8797b4dae-53349.test-cncf-aws.k8s.io" not found
W0926 09:24:41.181718    4688 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0926 09:24:41.181765    4688 down.go:48] /logs/artifacts/62933833-1eab-11ec-aa51-d2836bccddff/kops delete cluster --name e2e-f8797b4dae-53349.test-cncf-aws.k8s.io --yes
I0926 09:24:41.203029    4718 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0926 09:24:41.203211    4718 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-f8797b4dae-53349.test-cncf-aws.k8s.io" not found
I0926 09:24:41.735604    4688 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/26 09:24:41 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0926 09:24:41.742899    4688 http.go:37] curl https://ip.jsb.workers.dev
I0926 09:24:41.826955    4688 up.go:144] /logs/artifacts/62933833-1eab-11ec-aa51-d2836bccddff/kops create cluster --name e2e-f8797b4dae-53349.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.2.0_HVM-20210907-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.225.74.23/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large
I0926 09:24:41.843436    4729 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0926 09:24:41.843674    4729 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0926 09:24:41.891437    4729 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0926 09:24:42.389249    4729 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I0926 09:25:07.961154    4688 up.go:181] /logs/artifacts/62933833-1eab-11ec-aa51-d2836bccddff/kops validate cluster --name e2e-f8797b4dae-53349.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0926 09:25:07.976287    4749 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0926 09:25:07.976386    4749 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f8797b4dae-53349.test-cncf-aws.k8s.io

W0926 09:25:09.144727    4749 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f8797b4dae-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:25:19.187613    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:25:29.219003    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:25:39.251648    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:25:49.284147    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:25:59.313447    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:26:09.402111    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:26:19.432483    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:26:29.466377    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:26:39.495039    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:26:49.525269    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:26:59.556009    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
W0926 09:27:09.595079    4749 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f8797b4dae-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:27:19.629306    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:27:29.658386    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:27:39.690957    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:27:49.719699    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:27:59.747854    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:28:09.782426    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:28:19.807655    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:28:29.836154    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:28:39.864350    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:28:49.893483    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
W0926 09:28:59.910054    4749 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f8797b4dae-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:29:09.953467    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:29:19.985510    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:29:30.012072    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:29:40.043891    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:29:50.074682    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
W0926 09:30:00.119802    4749 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f8797b4dae-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:30:10.166036    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

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 master 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
W0926 09:30:20.196497    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:30:32.803207    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:30:44.700640    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:30:56.466815    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:31:08.286673    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:31:20.049660    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:31:31.800217    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:31:43.814634    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:31:55.737499    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:32:07.544245    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:32:19.445945    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:32:31.221919    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:32:43.022423    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:32:54.839081    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:33:06.604361    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:33:18.517890    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:33:30.310254    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:33:42.098081    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:33:53.860312    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:34:05.733183    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:34:17.411345    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:34:29.662241    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:34:41.459862    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:34:53.194219    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:35:05.015918    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:35:16.847660    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:35:28.621438    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:35:40.382792    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:35:52.149560    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:36:04.041030    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:36:15.819458    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:36:27.671209    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:36:39.538631    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:36:51.347238    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:37:03.142848    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:37:15.186137    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:37:27.008272    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:37:38.837167    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:37:50.749622    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:38:02.531236    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:38:14.281977    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:38:26.545146    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:38:38.293604    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:38:50.074611    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:39:01.942996    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:39:13.720092    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:39:25.488212    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:39:37.282671    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:39:49.034075    4749 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-2a	Master	c5.large	1	1	eu-west-2a
nodes-eu-west-2a	Node	t3.medium	4	4	eu-west-2a

... skipping 9 lines ...
Machine	i-0f98b23ebb34345f6				machine "i-0f98b23ebb34345f6" has not yet joined cluster
Node	ip-172-20-56-139.eu-west-2.compute.internal	node "ip-172-20-56-139.eu-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-p8c4s			system-node-critical pod "cilium-p8c4s" is pending
Pod	kube-system/coredns-5dc785954d-22m22		system-cluster-critical pod "coredns-5dc785954d-22m22" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-r5ww9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-r5ww9" is pending

Validation Failed
W0926 09:40:00.806089    4749 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0926 09:40:10.815465    4688 dumplogs.go:40] /logs/artifacts/62933833-1eab-11ec-aa51-d2836bccddff/kops toolbox dump --name e2e-f8797b4dae-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0926 09:40:10.832999    4761 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0926 09:40:10.833208    4761 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/26 09:40:20 Dumping node ip-172-20-56-139.eu-west-2.compute.internal
2021/09/26 09:40:25 dumping node not registered in kubernetes: 35.177.84.243
2021/09/26 09:40:25 Dumping node 35.177.84.243
... skipping 1215 lines ...
route-table:rtb-04439c25d480a1d1c	ok
vpc:vpc-074b6013d30ff886a	ok
dhcp-options:dopt-03eb12ec64e21a516	ok
Deleted kubectl config for e2e-f8797b4dae-53349.test-cncf-aws.k8s.io

Deleted cluster: "e2e-f8797b4dae-53349.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace