This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-08 19:09
Elapsed17m13s
Revision
job-versionv1.23.0-alpha.3.243+f6facec054611f
kubetest-version
revisionv1.23.0-alpha.3.243+f6facec054611f

Test Failures


kubetest Up 15m25s

kops validate cluster failed: error during /tmp/kops577338175/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)=c0b0402e66b31324fe01206b972a31ac
sha512sum(kubernetes-test-linux-amd64.tar.gz)=acbf250513a1a938aceed309ca9759b49babe24d768fe20d8c9a44aa441b974e0c0be2e2765112bbcd807483c641774618ece9925c3a8b1b113a71905dac27f8

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/08 19:09:50 process.go:155: Step './get-kube.sh' finished in 28.026868148s
2021/10/08 19:09:50 process.go:153: Running: /tmp/kops577338175/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/08 19:09:51 process.go:155: Step '/tmp/kops577338175/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 492.205585ms
2021/10/08 19:09:51 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/08 19:09:51 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/08 19:09:51 util.go:68: curl https://ip.jsb.workers.dev
2021/10/08 19:09:51 kops.go:439: Using external IP for admin access: 34.134.51.8/32
2021/10/08 19:09:51 process.go:153: Running: /tmp/kops577338175/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 ca-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.243+f6facec054611f --admin-access 34.134.51.8/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
I1008 19:09:51.267006     986 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1008 19:09:51.289042     986 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1008 19:09:51.768266     986 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/08 19:10:13 process.go:155: Step '/tmp/kops577338175/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 ca-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.243+f6facec054611f --admin-access 34.134.51.8/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 21.806501167s
2021/10/08 19:10:13 process.go:153: Running: /tmp/kops577338175/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1008 19:10:13.073537    1007 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1008 19:10:14.028937    1007 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
W1008 19:10:24.048113    1007 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-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:10:34.082531    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:10:44.125184    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:10:54.161163    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:11:04.197274    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:11:14.225234    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:11:24.257885    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:11:34.286109    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:11:44.319796    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
W1008 19:11:54.344772    1007 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-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:12:04.376859    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:12:14.423544    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:12:24.469574    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:12:34.533509    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:12:44.563242    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:12:54.601550    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:13:04.647385    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:13:14.677312    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:13:24.711283    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:13:34.743336    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:13:44.778244    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:13:54.807241    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:14:04.840646    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

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
W1008 19:14:14.879657    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
W1008 19:14:54.914652    1007 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-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

NODE STATUS
... skipping 6 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:15:06.191103    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:15:17.097851    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:15:28.036313    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:15:38.953260    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:15:49.848479    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:16:00.747784    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:16:11.647779    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:16:22.568482    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:16:33.561011    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:16:44.700181    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:16:55.596291    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:17:06.477571    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:17:17.374678    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:17:28.251834    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:17:39.101286    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:17:50.049448    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:18:01.025511    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:18:11.890737    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:18:22.751348    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:18:33.689809    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:18:44.546619    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:18:55.450622    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:19:06.387255    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:19:17.456827    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:19:28.291273    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:19:39.105840    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:19:49.999204    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:20:00.954367    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:20:11.774292    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:20:22.643063    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:20:33.508784    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:20:44.372689    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:20:55.195739    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:21:06.064240    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:21:16.936375    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:21:27.834315    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:21:38.662593    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:21:49.524368    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:22:00.474587    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:22:11.387461    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:22:22.198200    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:22:33.126166    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:22:44.059011    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:22:55.018231    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:23:06.091429    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:23:17.124781    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:23:28.053012    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:23:39.042104    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:23:50.022547    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:24:00.931943    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:24:11.910556    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:24:22.833370    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:24:33.743671    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:24:44.648154    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:24:55.552571    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1b	Master	c5.large	1	1	ca-central-1b
nodes-ca-central-1b	Node	t3.medium	4	4	ca-central-1b

... skipping 7 lines ...
Machine	i-072b52d89c625dcca				machine "i-072b52d89c625dcca" has not yet joined cluster
Machine	i-0d26cee42cb8e74ab				machine "i-0d26cee42cb8e74ab" has not yet joined cluster
Machine	i-0d6e82c4dc734a6da				machine "i-0d6e82c4dc734a6da" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-s6svs		system-cluster-critical pod "coredns-5dc785954d-s6svs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2498	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2498" is pending

Validation Failed
W1008 19:25:06.484147    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/08 19:25:16 process.go:155: Step '/tmp/kops577338175/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m3.439881933s
2021/10/08 19:25:16 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/08 19:25:16 process.go:153: Running: /tmp/kops577338175/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1008 19:25:16.514318    1022 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/08 19:25:16 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 493.966091ms
2021/10/08 19:25:16 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-s6svs
... skipping 40 lines ...
2021/10/08 19:25:24 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/08 19:25:24 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/08 19:25:24 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/08 19:25:24 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/08 19:25:24 dump.go:129: dumping node not registered in kubernetes: 3.98.95.41
2021/10/08 19:25:24 dump.go:163: Dumping node 3.98.95.41
2021/10/08 19:25:24 dump.go:132: error dumping node 3.98.95.41: could not connect: unable to SSH to "3.98.95.41": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/08 19:25:24 dump.go:129: dumping node not registered in kubernetes: 35.182.156.119
2021/10/08 19:25:24 dump.go:163: Dumping node 35.182.156.119
2021/10/08 19:25:25 dump.go:132: error dumping node 35.182.156.119: could not connect: unable to SSH to "35.182.156.119": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/08 19:25:25 dump.go:129: dumping node not registered in kubernetes: 99.79.59.67
2021/10/08 19:25:25 dump.go:163: Dumping node 99.79.59.67
2021/10/08 19:25:25 dump.go:132: error dumping node 99.79.59.67: could not connect: unable to SSH to "99.79.59.67": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/08 19:25:25 dump.go:129: dumping node not registered in kubernetes: 35.182.240.73
2021/10/08 19:25:25 dump.go:163: Dumping node 35.182.240.73
2021/10/08 19:25:25 dump.go:132: error dumping node 35.182.240.73: could not connect: unable to SSH to "35.182.240.73": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/08 19:25:25 process.go:153: Running: /tmp/kops577338175/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1008 19:25:25.780721    1169 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ca-central-1b
2021/10/08 19:25:26 process.go:155: Step '/tmp/kops577338175/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 453.765162ms
2021/10/08 19:25:26 process.go:153: Running: /tmp/kops577338175/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 166 lines ...
dhcp-options:dopt-0412618719fdfa36c	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/08 19:26:28 process.go:155: Step '/tmp/kops577338175/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m2.773856773s
2021/10/08 19:26:28 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/08 19:26:28 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops577338175/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 ...