This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-20 19:18
Elapsed17m54s
Revision
job-versionv1.23.0-alpha.3.434+18104ecf1f5736
kubetest-version
revisionv1.23.0-alpha.3.434+18104ecf1f5736

Test Failures


kubetest Up 15m29s

kops validate cluster failed: error during /tmp/kops177365719/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ WRAPPED_COMMAND_PID=31
+ wait 31
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --deployment=kops --env=KOPS_ARCH=amd64 --env=KUBE_SSH_USER=ec2-user --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=ci/latest --ginkgo-parallel --kops-image=309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --kops-args=--master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --kops-overrides=spec.docker.selinuxEnabled=true --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-ssh-user=ec2-user --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.focus=\[sig-storage\].*\[Slow\] --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8' --timeout=120m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=436f1fc01e29ba9b9faa513419323ae4
sha512sum(kubernetes-test-linux-amd64.tar.gz)=4312c4526f3a821f7dd5519462abd8d1c1d8916dc64ae55b4dd96200c7861d226aec82dc9226f371791632840a1cc6150dbc55c6d6c47017d2b963241debee5c

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/20 19:18:56 process.go:155: Step './get-kube.sh' finished in 25.274364502s
2021/10/20 19:18:56 process.go:153: Running: /tmp/kops177365719/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
Error: cluster not found "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/20 19:18:56 process.go:155: Step '/tmp/kops177365719/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 536.049717ms
2021/10/20 19:18:56 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/20 19:18:56 kops.go:514: 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
2021/10/20 19:18:56 util.go:68: curl https://ip.jsb.workers.dev
2021/10/20 19:18:56 kops.go:439: Using external IP for admin access: 35.188.65.11/32
2021/10/20 19:18:56 process.go:153: Running: /tmp/kops177365719/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-west-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.434+18104ecf1f5736 --admin-access 35.188.65.11/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1020 19:18:56.743349     989 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1020 19:18:56.762028     989 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1020 19:18:57.258007     989 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/20 19:19:23 process.go:155: Step '/tmp/kops177365719/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-west-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.434+18104ecf1f5736 --admin-access 35.188.65.11/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 27.040362404s
2021/10/20 19:19:23 process.go:153: Running: /tmp/kops177365719/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1020 19:19:23.791705    1009 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1020 19:19:25.109271    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:19:35.154048    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:19:45.189832    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:19:55.227072    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:20:05.303101    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:20:15.352313    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:20:25.390336    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:20:35.435015    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:20:45.507804    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:20:55.542498    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:21:05.578183    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:21:15.610067    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:21:25.647400    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:21:35.699106    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:21:45.747093    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:21:55.780648    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:22:05.849008    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:22:15.885164    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:22:25.921845    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:22:35.958273    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:22:46.008086    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:22:56.044639    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:23:06.080889    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:23:16.126161    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:23:26.164321    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

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
W1020 19:23:36.219470    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:23:49.322081    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:24:01.199511    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:24:13.227982    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:24:25.315883    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:24:37.321627    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:24:49.258291    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:25:01.229964    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:25:13.301762    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:25:25.235618    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:25:37.143449    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:25:49.072052    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:26:01.133371    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:26:13.144793    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:26:25.313699    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:26:37.276231    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:26:49.230416    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:27:01.321743    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:27:13.319900    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:27:25.355190    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:27:37.330912    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:27:49.673439    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:28:01.592729    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:28:13.743980    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:28:26.256535    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:28:38.167963    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:28:50.217487    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:29:02.391184    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:29:14.516129    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:29:26.544822    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:29:38.589678    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:29:50.759600    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:30:02.970900    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:30:15.123492    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:30:27.109442    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:30:39.113369    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:30:51.042910    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:31:03.145048    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:31:15.482252    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:31:27.475436    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:31:39.943001    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:31:51.890565    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:32:03.834274    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:32:15.769441    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:32:27.749551    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:32:39.832109    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:32:51.905154    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:33:04.008561    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:33:15.894409    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:33:27.715167    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:33:39.792275    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:33:51.781265    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:34:03.828779    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 7 lines ...
Machine	i-02d40d7d2fdce3393				machine "i-02d40d7d2fdce3393" has not yet joined cluster
Machine	i-0a599e395886601b1				machine "i-0a599e395886601b1" has not yet joined cluster
Machine	i-0f07c7598b4f118cc				machine "i-0f07c7598b4f118cc" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-z9pj4		system-cluster-critical pod "coredns-6c8944dbdc-z9pj4" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vlvjs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vlvjs" is pending

Validation Failed
W1020 19:34:15.768262    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/20 19:34:25 process.go:155: Step '/tmp/kops177365719/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m2.006862182s
2021/10/20 19:34:25 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/20 19:34:25 process.go:153: Running: /tmp/kops177365719/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1020 19:34:25.791919    1021 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/20 19:34:26 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.128288074s
2021/10/20 19:34:26 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-z9pj4
... skipping 40 lines ...
2021/10/20 19:34:41 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/20 19:34:41 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/20 19:34:41 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/20 19:34:41 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/20 19:34:41 dump.go:129: dumping node not registered in kubernetes: 52.49.18.179
2021/10/20 19:34:41 dump.go:163: Dumping node 52.49.18.179
2021/10/20 19:34:42 dump.go:132: error dumping node 52.49.18.179: could not connect: unable to SSH to "52.49.18.179": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 19:34:42 dump.go:129: dumping node not registered in kubernetes: 34.245.67.246
2021/10/20 19:34:42 dump.go:163: Dumping node 34.245.67.246
2021/10/20 19:34:43 dump.go:132: error dumping node 34.245.67.246: could not connect: unable to SSH to "34.245.67.246": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 19:34:43 dump.go:129: dumping node not registered in kubernetes: 54.72.201.38
2021/10/20 19:34:43 dump.go:163: Dumping node 54.72.201.38
2021/10/20 19:34:44 dump.go:132: error dumping node 54.72.201.38: could not connect: unable to SSH to "54.72.201.38": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 19:34:44 dump.go:129: dumping node not registered in kubernetes: 18.202.230.182
2021/10/20 19:34:44 dump.go:163: Dumping node 18.202.230.182
2021/10/20 19:34:45 dump.go:132: error dumping node 18.202.230.182: could not connect: unable to SSH to "18.202.230.182": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 19:34:45 process.go:153: Running: /tmp/kops177365719/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1020 19:34:45.403257    1165 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	eu-west-1a
2021/10/20 19:34:45 process.go:155: Step '/tmp/kops177365719/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 575.431022ms
2021/10/20 19:34:45 process.go:153: Running: /tmp/kops177365719/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 204 lines ...
dhcp-options:dopt-029df72eac72e1a98	ok
Deleted kubectl config for e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/20 19:36:18 process.go:155: Step '/tmp/kops177365719/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m32.215453329s
2021/10/20 19:36:18 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/20 19:36:18 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops177365719/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 723, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 569, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...