This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-13 07:12
Elapsed18m12s
Revision
job-versionv1.23.0-alpha.3.296+e054181e517b48
kubetest-version
revisionv1.23.0-alpha.3.296+e054181e517b48

Test Failures


kubetest Up 15m34s

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

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

2021/10/13 07:13:55 process.go:155: Step '/tmp/kops4281809166/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.296+e054181e517b48 --admin-access 34.123.127.27/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.105879455s
2021/10/13 07:13:55 process.go:153: Running: /tmp/kops4281809166/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1013 07:13:55.813788    1007 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1013 07:13:57.185670    1007 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
W1013 07:14:07.249852    1007 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
W1013 07:14:17.298054    1007 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
W1013 07:14:27.338599    1007 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
W1013 07:14:37.370187    1007 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
W1013 07:14:47.404714    1007 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
W1013 07:14:57.448916    1007 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
W1013 07:15:07.481360    1007 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
W1013 07:15:17.528194    1007 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
W1013 07:15:27.569956    1007 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
W1013 07:15:37.814194    1007 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
W1013 07:15:47.845777    1007 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
W1013 07:15:57.885144    1007 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
W1013 07:16:07.919909    1007 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
W1013 07:16:17.952315    1007 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
W1013 07:16:27.993639    1007 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
W1013 07:16:38.022488    1007 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
W1013 07:16:48.110721    1007 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
W1013 07:16:58.142775    1007 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
W1013 07:17:08.175864    1007 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
W1013 07:17:18.207211    1007 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
W1013 07:17:28.238059    1007 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
W1013 07:17:38.282753    1007 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
W1013 07:17:48.312960    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
W1013 07:18:28.359334    1007 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
W1013 07:18:38.405178    1007 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
... skipping 6 lines ...
Machine	i-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:18:52.143068    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:19:04.599255    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:19:17.035089    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:19:29.811874    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:19:42.280915    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:19:54.723506    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:20:07.169956    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:20:19.589368    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:20:32.180102    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:20:44.670899    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:20:57.079795    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:21:09.569052    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:21:22.031736    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:21:34.542493    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:21:46.990897    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:21:59.427440    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:22:11.959742    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:22:24.368731    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:22:37.346256    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:22:50.235728    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:23:02.589223    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:23:15.010061    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:23:27.435401    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:23:39.815629    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:23:52.287918    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:24:04.747478    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:24:17.243129    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:24:29.728624    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:24:42.100549    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:24:54.539333    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:25:07.103784    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:25:19.614535    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:25:32.119430    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:25:44.531241    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:25:56.973821    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:26:09.486696    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:26:21.901712    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:26:34.400754    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:26:47.495243    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:27:00.058362    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:27:12.428591    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:27:24.895333    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:27:37.427572    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:27:49.835301    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:28:02.295790    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:28:14.813033    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:28:27.288114    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:28:39.733873    1007 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-0b9413e081c8bc1b5				machine "i-0b9413e081c8bc1b5" has not yet joined cluster
Machine	i-0f5337f95036b31de				machine "i-0f5337f95036b31de" has not yet joined cluster
Machine	i-0f5390a127f5f81aa				machine "i-0f5390a127f5f81aa" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-fjtnj		system-cluster-critical pod "coredns-6c8944dbdc-fjtnj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-qgmlx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-qgmlx" is pending

Validation Failed
W1013 07:28:52.148060    1007 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/13 07:29:02 process.go:155: Step '/tmp/kops4281809166/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m6.364549111s
2021/10/13 07:29:02 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/13 07:29:02 process.go:153: Running: /tmp/kops4281809166/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1013 07:29:02.180139    1019 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/13 07:29:03 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.471101519s
2021/10/13 07:29:03 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-fjtnj
... skipping 40 lines ...
2021/10/13 07:29:21 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/13 07:29:21 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/13 07:29:22 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/13 07:29:22 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/13 07:29:22 dump.go:129: dumping node not registered in kubernetes: 18.228.188.30
2021/10/13 07:29:22 dump.go:163: Dumping node 18.228.188.30
2021/10/13 07:29:23 dump.go:132: error dumping node 18.228.188.30: could not connect: unable to SSH to "18.228.188.30": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 07:29:23 dump.go:129: dumping node not registered in kubernetes: 18.228.43.14
2021/10/13 07:29:23 dump.go:163: Dumping node 18.228.43.14
2021/10/13 07:29:25 dump.go:132: error dumping node 18.228.43.14: could not connect: unable to SSH to "18.228.43.14": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 07:29:25 dump.go:129: dumping node not registered in kubernetes: 18.230.65.84
2021/10/13 07:29:25 dump.go:163: Dumping node 18.230.65.84
2021/10/13 07:29:26 dump.go:132: error dumping node 18.230.65.84: could not connect: unable to SSH to "18.230.65.84": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 07:29:26 dump.go:129: dumping node not registered in kubernetes: 18.228.172.35
2021/10/13 07:29:26 dump.go:163: Dumping node 18.228.172.35
2021/10/13 07:29:27 dump.go:132: error dumping node 18.228.172.35: could not connect: unable to SSH to "18.228.172.35": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/13 07:29:27 process.go:153: Running: /tmp/kops4281809166/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1013 07:29:27.494110    1163 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/13 07:29:27 process.go:155: Step '/tmp/kops4281809166/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 487.469818ms
2021/10/13 07:29:27 process.go:153: Running: /tmp/kops4281809166/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 212 lines ...
dhcp-options:dopt-0060ae01eb448310e	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/13 07:31:03 process.go:155: Step '/tmp/kops4281809166/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m35.099690497s
2021/10/13 07:31:03 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/13 07:31:03 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops4281809166/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 ...