This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-18 07:16
Elapsed18m10s
Revision
job-versionv1.23.0-alpha.3.364+9804a83d8fd9ee
kubetest-version
revisionv1.23.0-alpha.3.364+9804a83d8fd9ee

Test Failures


kubetest Up 15m39s

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

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

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

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/18 07:17:12 process.go:155: Step './get-kube.sh' finished in 25.313239973s
2021/10/18 07:17:12 process.go:153: Running: /tmp/kops1566361955/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/18 07:17:13 process.go:155: Step '/tmp/kops1566361955/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 462.471981ms
2021/10/18 07:17:13 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/18 07:17:13 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/18 07:17:13 util.go:68: curl https://ip.jsb.workers.dev
2021/10/18 07:17:13 kops.go:439: Using external IP for admin access: 34.123.84.185/32
2021/10/18 07:17:13 process.go:153: Running: /tmp/kops1566361955/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.364+9804a83d8fd9ee --admin-access 34.123.84.185/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
I1018 07:17:13.221171     990 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1018 07:17:13.241626     990 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1018 07:17:13.754784     990 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/18 07:17:41 process.go:155: Step '/tmp/kops1566361955/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.364+9804a83d8fd9ee --admin-access 34.123.84.185/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.501494832s
2021/10/18 07:17:41 process.go:153: Running: /tmp/kops1566361955/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1018 07:17:41.723295    1011 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1018 07:17:43.111308    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-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:17:53.149543    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:18:03.186499    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:18:13.232831    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:18:23.271350    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:18:33.305303    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1018 07:18:43.343971    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-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:18:53.378297    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:19:03.428754    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:19:13.468912    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:19:23.504646    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:19:33.539288    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:19:43.610912    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:19:53.648436    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:20:03.697880    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:20:13.738496    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:20:23.778044    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:20:33.815689    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1018 07:20:43.879348    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-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:20:53.920476    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
W1018 07:21:03.946869    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-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:21:13.996898    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:21:24.032015    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:21:34.082415    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-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
W1018 07:21:44.124853    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1c	Master	c5.large	1	1	ap-northeast-1c
nodes-ap-northeast-1c	Node	t3.medium	4	4	ap-northeast-1c

... skipping 8 lines ...
Machine	i-06fd35bbc83aa5ad7					machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b					machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Node	ip-172-20-42-229.ap-northeast-1.compute.internal	master "ip-172-20-42-229.ap-northeast-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-6c8944dbdc-kh24f			system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 9 lines ...
Machine	i-0fd79a9d67ef8296b									machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Node	ip-172-20-42-229.ap-northeast-1.compute.internal					master "ip-172-20-42-229.ap-northeast-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-6c8944dbdc-kh24f							system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw						system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-42-229.ap-northeast-1.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-42-229.ap-northeast-1.compute.internal" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

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

... skipping 7 lines ...
Machine	i-054abebee2690d955				machine "i-054abebee2690d955" has not yet joined cluster
Machine	i-06fd35bbc83aa5ad7				machine "i-06fd35bbc83aa5ad7" has not yet joined cluster
Machine	i-0fd79a9d67ef8296b				machine "i-0fd79a9d67ef8296b" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-kh24f		system-cluster-critical pod "coredns-6c8944dbdc-kh24f" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tdtnw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tdtnw" is pending

Validation Failed
W1018 07:32:42.373280    1011 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/18 07:32:52 process.go:155: Step '/tmp/kops1566361955/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m10.6719675s
2021/10/18 07:32:52 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/18 07:32:52 process.go:153: Running: /tmp/kops1566361955/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1018 07:32:52.399280    1024 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/18 07:32:53 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.422480088s
2021/10/18 07:32:53 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-kh24f
... skipping 40 lines ...
2021/10/18 07:33:10 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/18 07:33:10 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/18 07:33:10 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/18 07:33:10 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/18 07:33:11 dump.go:129: dumping node not registered in kubernetes: 54.238.218.46
2021/10/18 07:33:11 dump.go:163: Dumping node 54.238.218.46
2021/10/18 07:33:12 dump.go:132: error dumping node 54.238.218.46: could not connect: unable to SSH to "54.238.218.46": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 07:33:12 dump.go:129: dumping node not registered in kubernetes: 3.115.11.5
2021/10/18 07:33:12 dump.go:163: Dumping node 3.115.11.5
2021/10/18 07:33:13 dump.go:132: error dumping node 3.115.11.5: could not connect: unable to SSH to "3.115.11.5": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 07:33:13 dump.go:129: dumping node not registered in kubernetes: 18.182.39.144
2021/10/18 07:33:13 dump.go:163: Dumping node 18.182.39.144
2021/10/18 07:33:14 dump.go:132: error dumping node 18.182.39.144: could not connect: unable to SSH to "18.182.39.144": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 07:33:14 dump.go:129: dumping node not registered in kubernetes: 52.192.234.79
2021/10/18 07:33:14 dump.go:163: Dumping node 52.192.234.79
2021/10/18 07:33:15 dump.go:132: error dumping node 52.192.234.79: could not connect: unable to SSH to "52.192.234.79": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/18 07:33:15 process.go:153: Running: /tmp/kops1566361955/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1018 07:33:15.513548    1171 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-northeast-1c
2021/10/18 07:33:16 process.go:155: Step '/tmp/kops1566361955/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 508.525541ms
2021/10/18 07:33:16 process.go:153: Running: /tmp/kops1566361955/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 204 lines ...
dhcp-options:dopt-0245f5a79a334ab45	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/18 07:34:51 process.go:155: Step '/tmp/kops1566361955/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m35.318037722s
2021/10/18 07:34:51 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/18 07:34:51 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops1566361955/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 ...