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

Test Failures


kubetest Up 15m38s

kops validate cluster failed: error during /tmp/kops2408859421/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 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=bc51261349f4b9542019fa9d48becab3
sha512sum(kubernetes-test-linux-amd64.tar.gz)=9ca138655f4870608d66a918bced5dd2144954813071cce3d908aefe181cbc9b12e47a07a4352503c7f91a6ed2d03f45cf2ac518df56049a0110fb897239fc74

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/14 07:14:56 process.go:155: Step './get-kube.sh' finished in 25.772246806s
2021/10/14 07:14:56 process.go:153: Running: /tmp/kops2408859421/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/14 07:14:56 process.go:155: Step '/tmp/kops2408859421/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 484.751402ms
2021/10/14 07:14:56 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/14 07:14: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/14 07:14:56 util.go:68: curl https://ip.jsb.workers.dev
2021/10/14 07:14:56 kops.go:439: Using external IP for admin access: 23.251.147.183/32
2021/10/14 07:14:56 process.go:153: Running: /tmp/kops2408859421/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.312+a8bda48abeccf3 --admin-access 23.251.147.183/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
I1014 07:14:57.010069     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1014 07:14:57.031900     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1014 07:14:57.528519     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/14 07:15:24 process.go:155: Step '/tmp/kops2408859421/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.312+a8bda48abeccf3 --admin-access 23.251.147.183/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.099833874s
2021/10/14 07:15:24 process.go:153: Running: /tmp/kops2408859421/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1014 07:15:24.109080    1004 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1014 07:15:25.344301    1004 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
W1014 07:15:35.387186    1004 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
W1014 07:15:45.415533    1004 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
W1014 07:15:55.443437    1004 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
W1014 07:16:05.470472    1004 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
W1014 07:16:15.509290    1004 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
W1014 07:16:25.554414    1004 validate_cluster.go:232] (will retry): cluster not yet healthy
W1014 07:16:35.573469    1004 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
W1014 07:16:45.603909    1004 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
W1014 07:16:55.632896    1004 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
W1014 07:17:05.666817    1004 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
W1014 07:17:15.702256    1004 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
W1014 07:17:25.731079    1004 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
W1014 07:17:35.762204    1004 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
W1014 07:17:45.806298    1004 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
W1014 07:17:55.850103    1004 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
W1014 07:18:05.885382    1004 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
W1014 07:18:15.929807    1004 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
W1014 07:18:25.959357    1004 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
W1014 07:18:35.990260    1004 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
W1014 07:18:46.026435    1004 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
W1014 07:18:56.056965    1004 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
W1014 07:19:06.103836    1004 validate_cluster.go:232] (will retry): cluster not yet healthy
W1014 07:19:46.136536    1004 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1c	Master	c5.large	1	1	eu-west-1c
nodes-eu-west-1c	Node	t3.medium	4	4	eu-west-1c

NODE STATUS
... skipping 6 lines ...
Machine	i-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:19:58.935691    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:20:10.959359    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:20:23.071048    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:20:35.090248    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:20:47.000116    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:20:58.969378    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:21:10.945472    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:21:22.890986    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:21:34.916772    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:21:46.951803    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:21:58.998302    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:22:11.087718    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:22:23.082960    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:22:35.327037    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:22:47.460377    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:22:59.346637    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:23:11.292819    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:23:23.272625    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:23:35.536690    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:23:47.507328    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:23:59.939483    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:24:11.947508    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:24:23.991480    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:24:36.112523    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:24:47.985835    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:24:59.947495    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:25:12.086408    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:25:24.015942    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:25:36.027761    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:25:48.014039    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:25:59.930295    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:26:12.151007    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:26:24.212881    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:26:36.266679    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:26:48.304396    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:27:00.240761    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:27:12.292775    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:27:24.658562    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:27:36.609917    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:27:48.787439    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:28:01.212896    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:28:13.277562    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:28:25.275691    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:28:37.312931    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:28:49.437663    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:29:01.385386    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:29:13.438510    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:29:25.432565    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:29:37.405060    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:29:49.418470    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:30:01.475960    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:30:13.691141    1004 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-093d4ef1f7a72bbe3				machine "i-093d4ef1f7a72bbe3" has not yet joined cluster
Machine	i-0ba12b80cdfc3ac34				machine "i-0ba12b80cdfc3ac34" has not yet joined cluster
Machine	i-0f6053b30e8df07c9				machine "i-0f6053b30e8df07c9" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-wpn6m		system-cluster-critical pod "coredns-6c8944dbdc-wpn6m" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g7cnr	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g7cnr" is pending

Validation Failed
W1014 07:30:25.906612    1004 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/14 07:30:35 process.go:155: Step '/tmp/kops2408859421/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m11.821770387s
2021/10/14 07:30:35 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/14 07:30:35 process.go:153: Running: /tmp/kops2408859421/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1014 07:30:35.935352    1016 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/14 07:30:37 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.184580617s
2021/10/14 07:30:37 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-wpn6m
... skipping 40 lines ...
2021/10/14 07:30:51 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/14 07:30:51 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/14 07:30:51 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/14 07:30:52 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/14 07:30:52 dump.go:129: dumping node not registered in kubernetes: 54.229.215.142
2021/10/14 07:30:52 dump.go:163: Dumping node 54.229.215.142
2021/10/14 07:30:53 dump.go:132: error dumping node 54.229.215.142: could not connect: unable to SSH to "54.229.215.142": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/14 07:30:53 dump.go:129: dumping node not registered in kubernetes: 34.241.68.248
2021/10/14 07:30:53 dump.go:163: Dumping node 34.241.68.248
2021/10/14 07:30:53 dump.go:132: error dumping node 34.241.68.248: could not connect: unable to SSH to "34.241.68.248": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/14 07:30:53 dump.go:129: dumping node not registered in kubernetes: 34.243.91.97
2021/10/14 07:30:53 dump.go:163: Dumping node 34.243.91.97
2021/10/14 07:30:54 dump.go:132: error dumping node 34.243.91.97: could not connect: unable to SSH to "34.243.91.97": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/14 07:30:54 dump.go:129: dumping node not registered in kubernetes: 34.254.225.93
2021/10/14 07:30:54 dump.go:163: Dumping node 34.254.225.93
2021/10/14 07:30:55 dump.go:132: error dumping node 34.254.225.93: could not connect: unable to SSH to "34.254.225.93": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/14 07:30:55 process.go:153: Running: /tmp/kops2408859421/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1014 07:30:55.558462    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/14 07:30:56 process.go:155: Step '/tmp/kops2408859421/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 510.581141ms
2021/10/14 07:30:56 process.go:153: Running: /tmp/kops2408859421/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 194 lines ...
dhcp-options:dopt-05ea23516b535b9de	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/14 07:32:18 process.go:155: Step '/tmp/kops2408859421/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m21.964941528s
2021/10/14 07:32:18 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/14 07:32:18 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2408859421/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 ...