This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-10 07:10
Elapsed17m45s
Revision
job-versionv1.23.0-alpha.3.249+80056f73a614b2
kubetest-version
revisionv1.23.0-alpha.3.249+80056f73a614b2

Test Failures


kubetest Up 15m27s

kops validate cluster failed: error during /tmp/kops2199515826/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=30
+ wait 30
+ /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 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=f94333404bad0f981b14ecdee09cf682
sha512sum(kubernetes-test-linux-amd64.tar.gz)=f4a8b8b91044ed753e57bcfa93cf37c0426b62267c72868ec0f73e705152a097abefdc1790a8cde4ff240cc2c6d31ba64766660416aab65c6a830b4c28effdfb

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/10 07:11:03 process.go:155: Step './get-kube.sh' finished in 28.350616899s
2021/10/10 07:11:03 process.go:153: Running: /tmp/kops2199515826/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/10 07:11:04 process.go:155: Step '/tmp/kops2199515826/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 599.862152ms
2021/10/10 07:11:04 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/10 07:11:04 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/10 07:11:04 util.go:68: curl https://ip.jsb.workers.dev
2021/10/10 07:11:04 kops.go:439: Using external IP for admin access: 35.184.196.110/32
2021/10/10 07:11:04 process.go:153: Running: /tmp/kops2199515826/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.184.196.110/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
I1010 07:11:04.200242     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1010 07:11:04.224655     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1010 07:11:08.449730     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 30 lines ...

2021/10/10 07:11:28 process.go:155: Step '/tmp/kops2199515826/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.249+80056f73a614b2 --admin-access 35.184.196.110/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 24.559850541s
2021/10/10 07:11:28 process.go:153: Running: /tmp/kops2199515826/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1010 07:11:28.764396    1006 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1010 07:11:30.214395    1006 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-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:11:40.257114    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:11:50.304733    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:12:00.337834    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:12:10.380410    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:12:20.422400    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:12:30.469401    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:12:40.514477    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:12:50.582482    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:13:00.613711    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:13:10.643830    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:13:20.673128    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:13:30.712470    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:13:40.744364    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:13:50.789631    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:14:00.819729    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:14:10.865702    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:14:20.900029    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:14:30.929770    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:14:40.974071    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:14:51.008626    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:15:01.040247    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:15:11.084159    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

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
W1010 07:15:21.115400    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 8 lines ...
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Node	ip-172-20-35-212.eu-west-1.compute.internal	master "ip-172-20-35-212.eu-west-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:15:34.078233    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:15:46.129232    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:15:58.033862    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:16:09.968231    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:16:21.923236    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:16:33.925665    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:16:45.936583    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:16:57.852360    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:17:09.877932    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:17:21.847516    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:17:33.783514    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:17:45.675962    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:17:57.546765    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:18:09.675671    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:18:21.613863    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:18:33.484603    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:18:45.677718    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:18:57.736006    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:19:09.613921    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:19:21.535017    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:19:33.914623    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:19:46.022679    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:19:58.003431    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:20:09.890619    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:20:21.862350    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:20:33.886314    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:20:45.932544    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:20:57.838853    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:21:09.767111    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:21:21.644736    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:21:33.588629    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:21:45.602006    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:21:57.520445    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:22:09.568806    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:22:21.781671    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:22:33.754283    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:22:45.732033    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:22:57.740164    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:23:09.609206    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:23:21.624240    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:23:33.995134    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:23:45.991866    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:23:57.986516    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:24:09.954668    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:24:21.958884    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:24:33.931345    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:24:45.918246    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:24:57.860212    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:25:09.829428    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:25:21.711751    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:25:33.687751    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:25:45.565836    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:25:57.618637    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:26:09.724510    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

... skipping 7 lines ...
Machine	i-0248532f820e6190a				machine "i-0248532f820e6190a" has not yet joined cluster
Machine	i-05a33a82740920f96				machine "i-05a33a82740920f96" has not yet joined cluster
Machine	i-0fa045dc5739276a5				machine "i-0fa045dc5739276a5" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-vw5vg		system-cluster-critical pod "coredns-5dc785954d-vw5vg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-gfhxs	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-gfhxs" is pending

Validation Failed
W1010 07:26:21.787504    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/10 07:26:31 process.go:155: Step '/tmp/kops2199515826/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m3.059138952s
2021/10/10 07:26:31 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/10 07:26:31 process.go:153: Running: /tmp/kops2199515826/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1010 07:26:31.826865    1020 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/10 07:26:33 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.238308997s
2021/10/10 07:26:33 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-vw5vg
... skipping 40 lines ...
2021/10/10 07:26:47 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/10 07:26:47 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/10 07:26:47 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/10 07:26:47 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/10 07:26:48 dump.go:129: dumping node not registered in kubernetes: 52.211.170.65
2021/10/10 07:26:48 dump.go:163: Dumping node 52.211.170.65
2021/10/10 07:26:48 dump.go:132: error dumping node 52.211.170.65: could not connect: unable to SSH to "52.211.170.65": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 07:26:48 dump.go:129: dumping node not registered in kubernetes: 54.216.116.225
2021/10/10 07:26:48 dump.go:163: Dumping node 54.216.116.225
2021/10/10 07:26:49 dump.go:132: error dumping node 54.216.116.225: could not connect: unable to SSH to "54.216.116.225": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 07:26:49 dump.go:129: dumping node not registered in kubernetes: 34.255.205.190
2021/10/10 07:26:49 dump.go:163: Dumping node 34.255.205.190
2021/10/10 07:26:50 dump.go:132: error dumping node 34.255.205.190: could not connect: unable to SSH to "34.255.205.190": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 07:26:50 dump.go:129: dumping node not registered in kubernetes: 54.195.153.127
2021/10/10 07:26:50 dump.go:163: Dumping node 54.195.153.127
2021/10/10 07:26:51 dump.go:132: error dumping node 54.195.153.127: could not connect: unable to SSH to "54.195.153.127": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/10 07:26:51 process.go:153: Running: /tmp/kops2199515826/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1010 07:26:51.339159    1167 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	eu-west-1c
2021/10/10 07:26:51 process.go:155: Step '/tmp/kops2199515826/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 475.802568ms
2021/10/10 07:26:51 process.go:153: Running: /tmp/kops2199515826/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 184 lines ...
dhcp-options:dopt-06f748a4cc0f476f3	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/10 07:28:13 process.go:155: Step '/tmp/kops2199515826/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m21.459477462s
2021/10/10 07:28:13 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/10 07:28:13 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2199515826/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 ...