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

Test Failures


kubetest Up 15m42s

kops validate cluster failed: error during /tmp/kops997147212/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 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=b5efca210568ac210de92dba92d8806e
sha512sum(kubernetes-test-linux-amd64.tar.gz)=94e30ba2210c701f90ce4bafacabf8da54668036005eabcd7cb7c4d54921b5b1edeed2756b19d9f44119148a9fd42f041a18fa87f8e14e65ac8465e979a02da3

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

2021/10/05 19:06:51 process.go:155: Step '/tmp/kops997147212/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 ap-southeast-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.162+b28bf04cd054a2 --admin-access 34.136.128.196/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 29.758900019s
2021/10/05 19:06:51 process.go:153: Running: /tmp/kops997147212/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1005 19:06:51.378518    1010 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1005 19:06:53.018245    1010 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1005 19:07:03.065034    1010 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:07:13.118780    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:07:23.180751    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:07:33.214087    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:07:43.245270    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:07:53.292867    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:08:03.323574    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:08:13.362698    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:08:23.393699    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:08:33.428476    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:08:43.463000    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:08:53.495994    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:09:03.527980    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:09:13.580652    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:09:23.612810    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:09:33.641809    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:09:43.672716    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:09:53.705109    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:10:03.738285    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:10:13.775522    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:10:23.823264    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:10:33.870691    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:10:43.904252    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:10:53.938702    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:11:03.969430    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 19:11:14.027814    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:11:29.126167    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:11:42.482747    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:11:55.784823    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:12:08.928801    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:12:22.124718    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:12:35.248940    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:12:48.392959    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:13:01.593905    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:13:15.101296    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:13:28.193265    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:13:41.572447    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:13:54.725642    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:14:07.969171    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:14:21.161425    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:14:34.553441    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:14:47.878810    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:15:01.308132    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:15:14.680487    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:15:28.538066    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:15:41.628496    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:15:54.766051    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:16:08.139344    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:16:21.460220    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:16:34.531519    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:16:48.052122    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:17:01.268263    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:17:14.659464    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:17:27.800884    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:17:40.900842    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:17:54.234012    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:18:07.372244    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:18:20.645302    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:18:33.779068    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:18:46.902689    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

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

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

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

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

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

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

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

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

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

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:20:07.240826    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:20:20.530456    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:20:33.668021    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:20:46.850635    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:21:00.133130    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:21:13.618353    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:21:27.155309    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:21:40.609578    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

... skipping 7 lines ...
Machine	i-01e7aec8873bf0455				machine "i-01e7aec8873bf0455" has not yet joined cluster
Machine	i-0668b8839dd98d94f				machine "i-0668b8839dd98d94f" has not yet joined cluster
Machine	i-0ecd592a1246b5f97				machine "i-0ecd592a1246b5f97" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-8l6qf		system-cluster-critical pod "coredns-5dc785954d-8l6qf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f96m6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f96m6" is pending

Validation Failed
W1005 19:21:54.179127    1010 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/05 19:22:04 process.go:155: Step '/tmp/kops997147212/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m12.83446657s
2021/10/05 19:22:04 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/05 19:22:04 process.go:153: Running: /tmp/kops997147212/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1005 19:22:04.219656    1024 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/05 19:22:06 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.894388371s
2021/10/05 19:22:06 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-8l6qf
... skipping 40 lines ...
2021/10/05 19:22:27 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/05 19:22:27 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/05 19:22:28 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/05 19:22:28 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/05 19:22:28 dump.go:129: dumping node not registered in kubernetes: 13.212.131.140
2021/10/05 19:22:28 dump.go:163: Dumping node 13.212.131.140
2021/10/05 19:22:30 dump.go:132: error dumping node 13.212.131.140: could not connect: unable to SSH to "13.212.131.140": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/05 19:22:30 dump.go:129: dumping node not registered in kubernetes: 13.212.168.38
2021/10/05 19:22:30 dump.go:163: Dumping node 13.212.168.38
2021/10/05 19:22:32 dump.go:132: error dumping node 13.212.168.38: could not connect: unable to SSH to "13.212.168.38": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/05 19:22:32 dump.go:129: dumping node not registered in kubernetes: 13.251.45.208
2021/10/05 19:22:32 dump.go:163: Dumping node 13.251.45.208
2021/10/05 19:22:33 dump.go:132: error dumping node 13.251.45.208: could not connect: unable to SSH to "13.251.45.208": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/05 19:22:33 dump.go:129: dumping node not registered in kubernetes: 13.212.255.30
2021/10/05 19:22:33 dump.go:163: Dumping node 13.212.255.30
2021/10/05 19:22:35 dump.go:132: error dumping node 13.212.255.30: could not connect: unable to SSH to "13.212.255.30": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/05 19:22:35 process.go:153: Running: /tmp/kops997147212/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1005 19:22:35.484721    1175 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-southeast-1c
2021/10/05 19:22:35 process.go:155: Step '/tmp/kops997147212/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 502.282487ms
2021/10/05 19:22:35 process.go:153: Running: /tmp/kops997147212/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 196 lines ...
dhcp-options:dopt-08295ab0366a78c84	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/05 19:24:15 process.go:155: Step '/tmp/kops997147212/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m39.567073856s
2021/10/05 19:24:15 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/05 19:24:15 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops997147212/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 ...