This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-04 07:05
Elapsed18m3s
Revision
job-versionv1.23.0-alpha.3.105+0ac956ff2bef9c
kubetest-version
revisionv1.23.0-alpha.3.105+0ac956ff2bef9c

Test Failures


kubetest Up 15m40s

kops validate cluster failed: error during /tmp/kops1486382208/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=32
+ wait 32
+ /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)=cdcc1eb1e90b1ff8178cfe58f02d625d
sha512sum(kubernetes-test-linux-amd64.tar.gz)=c094022cb2d8ca582c816ea790fae0bd86726125dfed4a60d148c657afa9cbdec511b0f960a72028532a99b2983c10a4babc2f49b514ec749bafb2c83f5e7a4d

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/04 07:05:35 process.go:155: Step './get-kube.sh' finished in 27.947271821s
2021/10/04 07:05:35 process.go:153: Running: /tmp/kops1486382208/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/04 07:05:36 process.go:155: Step '/tmp/kops1486382208/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 483.720249ms
2021/10/04 07:05:36 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/04 07:05:36 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/04 07:05:36 util.go:68: curl https://ip.jsb.workers.dev
2021/10/04 07:05:36 kops.go:439: Using external IP for admin access: 34.69.216.97/32
2021/10/04 07:05:36 process.go:153: Running: /tmp/kops1486382208/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-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.105+0ac956ff2bef9c --admin-access 34.69.216.97/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
I1004 07:05:36.134292     988 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1004 07:05:36.157432     988 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1004 07:05:36.628258     988 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/04 07:06:04 process.go:155: Step '/tmp/kops1486382208/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-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.105+0ac956ff2bef9c --admin-access 34.69.216.97/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 28.652107456s
2021/10/04 07:06:04 process.go:153: Running: /tmp/kops1486382208/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1004 07:06:04.788005    1008 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1004 07:06:06.221182    1008 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-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:06:16.252559    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:06:26.297147    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:06:36.333175    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:06:46.370983    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:06:56.407065    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:07:06.453561    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:07:16.487353    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:07:26.522583    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:07:36.560014    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:07:46.590115    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:07:56.653958    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:08:06.698517    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:08:16.726593    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:08:26.760249    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:08:36.786768    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:08:46.824079    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:08:56.889549    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:09:06.920854    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:09:16.972376    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:09:27.003703    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:09:37.034198    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:09:47.066291    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:09:57.112117    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:10:07.143220    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1004 07:10:17.201216    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 8 lines ...
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Node	ip-172-20-62-168.sa-east-1.compute.internal	master "ip-172-20-62-168.sa-east-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:10:30.756785    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:10:43.507245    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:10:55.925377    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:11:08.398057    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:11:20.755929    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:11:33.276065    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:11:45.673719    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:11:58.089928    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:12:10.563266    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:12:22.978798    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:12:35.441858    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:12:47.891237    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:13:00.343052    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:13:12.870296    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:13:25.285510    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:13:37.682730    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:13:50.129529    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:14:02.623990    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:14:15.006642    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:14:27.893359    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:14:40.324380    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:14:52.764430    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:15:05.193321    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:15:17.708255    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:15:30.169741    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:15:42.580906    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:15:55.034781    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:16:07.504469    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:16:19.969172    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:16:32.403503    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:16:44.819785    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:16:57.297946    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:17:09.787606    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:17:22.242746    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:17:34.627407    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:17:47.009535    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:17:59.351299    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:18:11.845447    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:18:24.720493    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:18:37.303888    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:18:49.757879    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:19:02.247928    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:19:14.656030    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:19:27.128832    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:19:39.513803    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:19:51.922894    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:20:04.411419    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:20:16.777435    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:20:29.189811    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:20:41.613694    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:20:54.110378    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-099c8fdd74cc01062				machine "i-099c8fdd74cc01062" has not yet joined cluster
Machine	i-0dbda1b7027e59ebe				machine "i-0dbda1b7027e59ebe" has not yet joined cluster
Machine	i-0e7aff0e3019eee58				machine "i-0e7aff0e3019eee58" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wsnc5		system-cluster-critical pod "coredns-5dc785954d-wsnc5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-ck7xb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-ck7xb" is pending

Validation Failed
W1004 07:21:06.573456    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/04 07:21:16 process.go:155: Step '/tmp/kops1486382208/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m11.815690246s
2021/10/04 07:21:16 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/04 07:21:16 process.go:153: Running: /tmp/kops1486382208/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1004 07:21:16.603898    1022 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/04 07:21:18 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.477896614s
2021/10/04 07:21:18 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-wsnc5
... skipping 40 lines ...
2021/10/04 07:21:35 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/04 07:21:35 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/04 07:21:35 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/04 07:21:36 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/04 07:21:36 dump.go:129: dumping node not registered in kubernetes: 18.230.122.219
2021/10/04 07:21:36 dump.go:163: Dumping node 18.230.122.219
2021/10/04 07:21:37 dump.go:132: error dumping node 18.230.122.219: could not connect: unable to SSH to "18.230.122.219": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/04 07:21:37 dump.go:129: dumping node not registered in kubernetes: 54.232.54.184
2021/10/04 07:21:37 dump.go:163: Dumping node 54.232.54.184
2021/10/04 07:21:38 dump.go:132: error dumping node 54.232.54.184: could not connect: unable to SSH to "54.232.54.184": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/04 07:21:38 dump.go:129: dumping node not registered in kubernetes: 18.231.98.246
2021/10/04 07:21:38 dump.go:163: Dumping node 18.231.98.246
2021/10/04 07:21:39 dump.go:132: error dumping node 18.231.98.246: could not connect: unable to SSH to "18.231.98.246": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/04 07:21:39 dump.go:129: dumping node not registered in kubernetes: 18.229.150.124
2021/10/04 07:21:39 dump.go:163: Dumping node 18.229.150.124
2021/10/04 07:21:40 dump.go:132: error dumping node 18.229.150.124: could not connect: unable to SSH to "18.229.150.124": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/04 07:21:40 process.go:153: Running: /tmp/kops1486382208/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1004 07:21:40.937446    1171 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	sa-east-1a
2021/10/04 07:21:41 process.go:155: Step '/tmp/kops1486382208/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 484.512081ms
2021/10/04 07:21:41 process.go:153: Running: /tmp/kops1486382208/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 166 lines ...
dhcp-options:dopt-0c91844e31880fce0	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/04 07:23:04 process.go:155: Step '/tmp/kops1486382208/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m23.284526383s
2021/10/04 07:23:04 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/04 07:23:04 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops1486382208/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 ...