This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-21 19:19
Elapsed18m5s
Revision
job-versionv1.23.0-alpha.3.470+d3350f45e509b3
kubetest-version
revisionv1.23.0-alpha.3.470+d3350f45e509b3

Test Failures


kubetest Up 15m28s

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

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

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

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/21 19:20:10 process.go:155: Step './get-kube.sh' finished in 27.662438898s
2021/10/21 19:20:10 process.go:153: Running: /tmp/kops1665628035/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/21 19:20:10 process.go:155: Step '/tmp/kops1665628035/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 486.908783ms
2021/10/21 19:20:10 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/21 19:20:10 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/21 19:20:10 util.go:68: curl https://ip.jsb.workers.dev
2021/10/21 19:20:11 kops.go:439: Using external IP for admin access: 35.202.2.127/32
2021/10/21 19:20:11 process.go:153: Running: /tmp/kops1665628035/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 sa-east-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.470+d3350f45e509b3 --admin-access 35.202.2.127/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
I1021 19:20:11.072401     989 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1021 19:20:11.095719     989 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1021 19:20:11.677301     989 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 30 lines ...

2021/10/21 19:20:29 process.go:155: Step '/tmp/kops1665628035/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 sa-east-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.470+d3350f45e509b3 --admin-access 35.202.2.127/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 18.861424871s
2021/10/21 19:20:29 process.go:153: Running: /tmp/kops1665628035/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1021 19:20:29.936285    1010 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1021 19:20:31.273725    1010 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-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:20:41.307385    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:20:51.340112    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:21:01.384230    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:21:11.417412    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:21:21.482832    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:21:31.529626    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:21:41.558304    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:21:51.589893    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:22:01.633425    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:22:11.679468    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:22:21.745726    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:22:31.783561    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:22:41.813189    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
W1021 19:22:51.832402    1010 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-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:23:01.869560    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:23:11.901080    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
W1021 19:23:21.924329    1010 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-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:23:31.952865    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:23:41.983435    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:23:52.013306    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:24:02.054831    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:24:12.084612    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-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
W1021 19:24:22.117187    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 8 lines ...
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending
Pod	kube-system/ebs-csi-controller-69bd8fbf74-4fmz8	system-cluster-critical pod "ebs-csi-controller-69bd8fbf74-4fmz8" is pending

Validation Failed
W1021 19:24:36.007732    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:24:48.643072    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:25:01.181365    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:25:13.799395    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:25:26.474692    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:25:39.092369    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:25:51.546981    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:26:04.164113    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:26:16.706736    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:26:29.245403    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:26:41.729054    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:26:54.199039    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:27:06.803562    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:27:19.196338    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:27:31.803547    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:27:44.390737    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:27:56.922653    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:28:09.612761    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:28:22.140709    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:28:35.267870    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:28:47.676443    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:29:00.248211    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:29:12.807224    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:29:25.428325    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:29:37.901424    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:29:50.405034    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:30:03.102396    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:30:15.788678    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:30:28.317798    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:30:40.786268    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:30:53.373438    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:31:05.913162    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:31:18.481235    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:31:31.029126    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:31:43.501852    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:31:56.061431    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:32:08.542366    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:32:21.025001    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:32:34.073689    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:32:46.640438    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:32:59.267427    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:33:11.891675    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:33:24.308174    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:33:36.739635    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:33:49.399353    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:34:02.010265    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:34:14.390658    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:34:26.795859    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:34:39.301786    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:34:51.867459    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:35:04.447279    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:35:16.968457    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1c	Master	c5.large	1	1	sa-east-1c
nodes-sa-east-1c	Node	t3.medium	4	4	sa-east-1c

... skipping 7 lines ...
Machine	i-038e2d078f9ea8411				machine "i-038e2d078f9ea8411" has not yet joined cluster
Machine	i-04dd829b2da600fcf				machine "i-04dd829b2da600fcf" has not yet joined cluster
Machine	i-0b4088d418be56443				machine "i-0b4088d418be56443" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-b8wbr		system-cluster-critical pod "coredns-6c8944dbdc-b8wbr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-26f67	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-26f67" is pending

Validation Failed
W1021 19:35:29.693020    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/21 19:35:39 process.go:155: Step '/tmp/kops1665628035/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m9.790168726s
2021/10/21 19:35:39 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/21 19:35:39 process.go:153: Running: /tmp/kops1665628035/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1021 19:35:39.733669    1022 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/21 19:35:41 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.517470375s
2021/10/21 19:35:41 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-b8wbr
... skipping 40 lines ...
2021/10/21 19:35:58 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/21 19:35:58 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/21 19:35:59 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/21 19:35:59 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/21 19:35:59 dump.go:129: dumping node not registered in kubernetes: 15.228.15.217
2021/10/21 19:35:59 dump.go:163: Dumping node 15.228.15.217
2021/10/21 19:36:00 dump.go:132: error dumping node 15.228.15.217: could not connect: unable to SSH to "15.228.15.217": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 19:36:00 dump.go:129: dumping node not registered in kubernetes: 18.231.195.8
2021/10/21 19:36:00 dump.go:163: Dumping node 18.231.195.8
2021/10/21 19:36:01 dump.go:132: error dumping node 18.231.195.8: could not connect: unable to SSH to "18.231.195.8": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 19:36:01 dump.go:129: dumping node not registered in kubernetes: 54.207.151.47
2021/10/21 19:36:01 dump.go:163: Dumping node 54.207.151.47
2021/10/21 19:36:03 dump.go:132: error dumping node 54.207.151.47: could not connect: unable to SSH to "54.207.151.47": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 19:36:03 dump.go:129: dumping node not registered in kubernetes: 15.228.128.98
2021/10/21 19:36:03 dump.go:163: Dumping node 15.228.128.98
2021/10/21 19:36:04 dump.go:132: error dumping node 15.228.128.98: could not connect: unable to SSH to "15.228.128.98": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/21 19:36:04 process.go:153: Running: /tmp/kops1665628035/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1021 19:36:04.167415    1171 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	sa-east-1c
2021/10/21 19:36:04 process.go:155: Step '/tmp/kops1665628035/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 508.421059ms
2021/10/21 19:36:04 process.go:153: Running: /tmp/kops1665628035/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 176 lines ...
dhcp-options:dopt-09160eb0ede1a94c2	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/21 19:37:40 process.go:155: Step '/tmp/kops1665628035/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m35.989624757s
2021/10/21 19:37:40 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/21 19:37:40 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops1665628035/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 ...