This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-17 07:16
Elapsed17m54s
Revision
job-versionv1.23.0-alpha.3.362+0cef26182cf830
kubetest-version
revisionv1.23.0-alpha.3.362+0cef26182cf830

Test Failures


kubetest Up 15m31s

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

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

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

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/17 07:17:11 process.go:155: Step './get-kube.sh' finished in 25.674512346s
2021/10/17 07:17:11 process.go:153: Running: /tmp/kops1130077126/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/17 07:17:11 process.go:155: Step '/tmp/kops1130077126/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 473.003587ms
2021/10/17 07:17:11 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/17 07:17:11 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/17 07:17:11 util.go:68: curl https://ip.jsb.workers.dev
2021/10/17 07:17:11 kops.go:439: Using external IP for admin access: 34.70.16.129/32
2021/10/17 07:17:11 process.go:153: Running: /tmp/kops1130077126/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-northeast-2c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.362+0cef26182cf830 --admin-access 34.70.16.129/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
I1017 07:17:11.767844     991 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1017 07:17:11.786899     991 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1017 07:17:12.326895     991 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/17 07:17:40 process.go:155: Step '/tmp/kops1130077126/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-northeast-2c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.362+0cef26182cf830 --admin-access 34.70.16.129/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.977030498s
2021/10/17 07:17:40 process.go:153: Running: /tmp/kops1130077126/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1017 07:17:40.744507    1011 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1017 07:17:42.275766    1011 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
W1017 07:17:52.306865    1011 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-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:18:02.349637    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:18:12.380685    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:18:22.420855    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:18:32.448127    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:18:42.483190    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:18:52.514911    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:19:02.548219    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:19:12.590940    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:19:22.617589    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:19:32.685196    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:19:42.750616    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1017 07:19:52.778362    1011 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-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:20:02.820738    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:20:12.850079    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:20:22.878672    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:20:32.912534    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1017 07:20:42.928882    1011 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-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:20:52.963732    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:21:02.993165    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:21:13.021783    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:21:23.051077    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:21:33.080422    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

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
W1017 07:21:43.110344    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 9 lines ...
Machine	i-0d62fd49e33c8c472									machine "i-0d62fd49e33c8c472" has not yet joined cluster
Node	ip-172-20-35-165.ap-northeast-2.compute.internal					master "ip-172-20-35-165.ap-northeast-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-6c8944dbdc-cq8dg							system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt						system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-35-165.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-35-165.ap-northeast-2.compute.internal" is pending

Validation Failed
W1017 07:21:57.188881    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:22:09.981398    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:22:22.605074    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:22:35.212139    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:22:47.750765    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:23:00.355010    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:23:12.927578    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:23:25.682877    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:23:38.672287    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:23:51.349215    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:24:03.936392    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:24:16.506002    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:24:29.288364    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:24:42.002664    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:24:54.669513    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:25:07.332996    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:25:20.068300    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:25:32.946779    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:25:46.358971    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:25:58.897575    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:26:11.454203    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:26:24.116876    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:26:36.812479    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:26:49.534046    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:27:02.180046    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:27:14.891910    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:27:27.569291    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:27:40.418587    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:27:52.997323    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:28:05.685606    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:28:18.344704    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:28:30.996750    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:28:43.662664    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:28:56.294471    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:29:08.959977    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:29:21.704709    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:29:34.361201    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:29:47.670432    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:30:00.239633    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:30:12.937682    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:30:25.611609    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:30:38.389733    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:30:51.044513    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:31:03.689828    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:31:16.446245    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:31:29.275820    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:31:41.933649    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:31:54.591255    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:32:07.472721    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:32:20.175497    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2c	Master	c5.large	1	1	ap-northeast-2c
nodes-ap-northeast-2c	Node	t3.medium	4	4	ap-northeast-2c

... skipping 7 lines ...
Machine	i-03ad5d2bab7541434				machine "i-03ad5d2bab7541434" has not yet joined cluster
Machine	i-06fb60a0d577c8d1d				machine "i-06fb60a0d577c8d1d" has not yet joined cluster
Machine	i-0d62fd49e33c8c472				machine "i-0d62fd49e33c8c472" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-cq8dg		system-cluster-critical pod "coredns-6c8944dbdc-cq8dg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-p7fzt	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-p7fzt" is pending

Validation Failed
W1017 07:32:33.031378    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/17 07:32:43 process.go:155: Step '/tmp/kops1130077126/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m2.309423555s
2021/10/17 07:32:43 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/17 07:32:43 process.go:153: Running: /tmp/kops1130077126/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1017 07:32:43.057475    1022 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/17 07:32:44 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.643334158s
2021/10/17 07:32:44 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-cq8dg
... skipping 40 lines ...
2021/10/17 07:33:02 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/17 07:33:02 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/17 07:33:03 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/17 07:33:03 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/17 07:33:03 dump.go:129: dumping node not registered in kubernetes: 15.164.165.116
2021/10/17 07:33:03 dump.go:163: Dumping node 15.164.165.116
2021/10/17 07:33:05 dump.go:132: error dumping node 15.164.165.116: could not connect: unable to SSH to "15.164.165.116": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/17 07:33:05 dump.go:129: dumping node not registered in kubernetes: 13.209.49.132
2021/10/17 07:33:05 dump.go:163: Dumping node 13.209.49.132
2021/10/17 07:33:06 dump.go:132: error dumping node 13.209.49.132: could not connect: unable to SSH to "13.209.49.132": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/17 07:33:06 dump.go:129: dumping node not registered in kubernetes: 3.34.47.140
2021/10/17 07:33:06 dump.go:163: Dumping node 3.34.47.140
2021/10/17 07:33:07 dump.go:132: error dumping node 3.34.47.140: could not connect: unable to SSH to "3.34.47.140": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/17 07:33:07 dump.go:129: dumping node not registered in kubernetes: 54.180.120.233
2021/10/17 07:33:07 dump.go:163: Dumping node 54.180.120.233
2021/10/17 07:33:08 dump.go:132: error dumping node 54.180.120.233: could not connect: unable to SSH to "54.180.120.233": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/17 07:33:08 process.go:153: Running: /tmp/kops1130077126/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1017 07:33:08.933032    1169 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-northeast-2c
2021/10/17 07:33:09 process.go:155: Step '/tmp/kops1130077126/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 482.554502ms
2021/10/17 07:33:09 process.go:153: Running: /tmp/kops1130077126/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 176 lines ...
dhcp-options:dopt-0ccd2d304e1b18a4c	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/17 07:34:34 process.go:155: Step '/tmp/kops1130077126/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m24.963981413s
2021/10/17 07:34:34 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/17 07:34:34 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops1130077126/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 ...