This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-09-18 19:37
Elapsed19m14s
Revision
job-versionv1.16.15
revisionv1.16.15

Test Failures


Up 15m46s

kops validate cluster failed: error during /tmp/kops172450782/kops validate cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files


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
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --deployment=kops --kops-ssh-user=ubuntu --env=KUBE_SSH_USER=ubuntu --env=KOPS_DEPLOY_LATEST_URL=https://storage.googleapis.com/kubernetes-release/release/stable-1.16.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/stable-1.16 --ginkgo-parallel --kops-args=--networking=calico --kops-image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20200528 --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort|Services.*rejected.*endpoints|Services.*affinity' --timeout=60m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
AWS_DEFAULT_PROFILE=default
AWS_PROFILE=default
... skipping 159 lines ...
route53-record:ZEMLNXIIWQ0RV/api.e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io.	ok
keypair:key-0e119a507935a0cde	ok

Deleted cluster: "e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io"
2020/09/18 19:38:37 process.go:155: Step '/tmp/kops172450782/kops delete cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --yes' finished in 15.800681671s
2020/09/18 19:38:37 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/09/18 19:38:37 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
2020/09/18 19:38:37 util.go:68: curl https://ip.jsb.workers.dev
2020/09/18 19:38:37 kops.go:439: Using external IP for admin access: 34.67.199.248/32
2020/09/18 19:38:37 process.go:153: Running: /tmp/kops172450782/kops create cluster --name e2e-kops-calico-u2004-k16.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/kubernetes-release/release/v1.16.15 --admin-access 34.67.199.248/32 --image 099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20200528 --cloud aws --networking=calico --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I0918 19:38:37.820158     166 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0918 19:38:38.007734     166 create_cluster.go:706] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I0918 19:38:39.375845     166 subnets.go:184] Assigned CIDR 172.20.32.0/19 to subnet ap-northeast-1c
... skipping 49 lines ...

2020/09/18 19:39:19 process.go:155: Step '/tmp/kops172450782/kops create cluster --name e2e-kops-calico-u2004-k16.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/kubernetes-release/release/v1.16.15 --admin-access 34.67.199.248/32 --image 099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20200528 --cloud aws --networking=calico --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 42.09289978s
2020/09/18 19:39:19 process.go:153: Running: /tmp/kops172450782/kops validate cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --wait 15m
I0918 19:39:19.913845     187 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io

W0918 19:39:21.816186     187 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0918 19:39:31.887461     187 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-calico-u2004-k16.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
W0918 19:39:41.933197     187 validate_cluster.go:221] (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
W0918 19:39:52.015444     187 validate_cluster.go:221] (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
W0918 19:40:02.067543     187 validate_cluster.go:221] (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
W0918 19:40:12.129831     187 validate_cluster.go:221] (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
W0918 19:40:22.179147     187 validate_cluster.go:221] (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
W0918 19:40:32.248625     187 validate_cluster.go:221] (will retry): cluster not yet healthy
W0918 19:40:42.303656     187 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-calico-u2004-k16.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
W0918 19:40:52.357054     187 validate_cluster.go:221] (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
W0918 19:41:02.420554     187 validate_cluster.go:221] (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
W0918 19:41:12.480122     187 validate_cluster.go:221] (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
W0918 19:41:22.521279     187 validate_cluster.go:221] (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
W0918 19:41:32.615090     187 validate_cluster.go:221] (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
W0918 19:41:42.692401     187 validate_cluster.go:221] (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
W0918 19:41:52.743625     187 validate_cluster.go:221] (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
W0918 19:42:02.785056     187 validate_cluster.go:221] (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
W0918 19:42:12.827874     187 validate_cluster.go:221] (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
W0918 19:42:22.865067     187 validate_cluster.go:221] (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
W0918 19:42:32.920528     187 validate_cluster.go:221] (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
W0918 19:42:42.995709     187 validate_cluster.go:221] (will retry): cluster not yet healthy
W0918 19:42:53.040999     187 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-calico-u2004-k16.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
W0918 19:43:03.108632     187 validate_cluster.go:221] (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
W0918 19:43:13.159678     187 validate_cluster.go:221] (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
W0918 19:43:23.209147     187 validate_cluster.go:221] (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
W0918 19:43:33.261360     187 validate_cluster.go:221] (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
W0918 19:43:43.307610     187 validate_cluster.go:221] (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
W0918 19:43:53.356470     187 validate_cluster.go:221] (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
W0918 19:44:03.411440     187 validate_cluster.go:221] (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
W0918 19:44:13.452366     187 validate_cluster.go:221] (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
W0918 19:44:23.495251     187 validate_cluster.go:221] (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
W0918 19:44:33.556990     187 validate_cluster.go:221] (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
W0918 19:44:43.609847     187 validate_cluster.go:221] (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
W0918 19:44:53.649955     187 validate_cluster.go:221] (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
W0918 19:45:03.708871     187 validate_cluster.go:221] (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
W0918 19:45:13.763252     187 validate_cluster.go:221] (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
W0918 19:45:23.817700     187 validate_cluster.go:221] (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
W0918 19:45:33.879361     187 validate_cluster.go:221] (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
W0918 19:45:43.924625     187 validate_cluster.go:221] (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
W0918 19:45:54.063424     187 validate_cluster.go:221] (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
W0918 19:46:04.105043     187 validate_cluster.go:221] (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
W0918 19:46:14.161258     187 validate_cluster.go:221] (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
W0918 19:46:24.215640     187 validate_cluster.go:221] (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
W0918 19:46:34.263658     187 validate_cluster.go:221] (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
W0918 19:46:44.340901     187 validate_cluster.go:221] (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-0d7ca924c1aaa0187								machine "i-0d7ca924c1aaa0187" has not yet joined cluster
Machine	i-0e925ed54f264fafa								machine "i-0e925ed54f264fafa" has not yet joined cluster
Pod	kube-system/etcd-manager-main-ip-172-20-50-252.ap-northeast-1.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-50-252.ap-northeast-1.compute.internal" is pending
Pod	kube-system/kube-dns-67689f84b-thdcq						system-cluster-critical pod "kube-dns-67689f84b-thdcq" is pending
Pod	kube-system/kube-dns-autoscaler-5b55dbf76d-rsnfg				system-cluster-critical pod "kube-dns-autoscaler-5b55dbf76d-rsnfg" is pending

Validation Failed
W0918 19:46:57.239395     187 validate_cluster.go:221] (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 13 lines ...
Pod	kube-system/calico-node-9m2sg				system-node-critical pod "calico-node-9m2sg" is pending
Pod	kube-system/calico-node-g7v5r				system-node-critical pod "calico-node-g7v5r" is pending
Pod	kube-system/calico-node-vx8s8				system-node-critical pod "calico-node-vx8s8" is pending
Pod	kube-system/kube-dns-67689f84b-thdcq			system-cluster-critical pod "kube-dns-67689f84b-thdcq" is pending
Pod	kube-system/kube-dns-autoscaler-5b55dbf76d-rsnfg	system-cluster-critical pod "kube-dns-autoscaler-5b55dbf76d-rsnfg" is pending

Validation Failed
W0918 19:47:09.433517     187 validate_cluster.go:221] (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 15 lines ...
Pod	kube-system/calico-node-vx8s8						system-node-critical pod "calico-node-vx8s8" is pending
Pod	kube-system/kube-dns-67689f84b-thdcq					system-cluster-critical pod "kube-dns-67689f84b-thdcq" is pending
Pod	kube-system/kube-dns-autoscaler-5b55dbf76d-rsnfg			system-cluster-critical pod "kube-dns-autoscaler-5b55dbf76d-rsnfg" is pending
Pod	kube-system/kube-proxy-ip-172-20-32-23.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-23.ap-northeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-42-78.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-78.ap-northeast-1.compute.internal" is pending

Validation Failed
W0918 19:47:21.253061     187 validate_cluster.go:221] (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 10 lines ...
Pod	kube-system/calico-node-9m2sg				system-node-critical pod "calico-node-9m2sg" is pending
Pod	kube-system/calico-node-g7v5r				system-node-critical pod "calico-node-g7v5r" is pending
Pod	kube-system/calico-node-vx8s8				system-node-critical pod "calico-node-vx8s8" is pending
Pod	kube-system/kube-dns-67689f84b-thdcq			system-cluster-critical pod "kube-dns-67689f84b-thdcq" is pending
Pod	kube-system/kube-dns-autoscaler-5b55dbf76d-rsnfg	system-cluster-critical pod "kube-dns-autoscaler-5b55dbf76d-rsnfg" is pending

Validation Failed
W0918 19:47:33.196337     187 validate_cluster.go:221] (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 10 lines ...
Pod	kube-system/calico-node-9m2sg		system-node-critical pod "calico-node-9m2sg" is not ready (calico-node)
Pod	kube-system/calico-node-g7v5r		system-node-critical pod "calico-node-g7v5r" is not ready (calico-node)
Pod	kube-system/calico-node-vx8s8		system-node-critical pod "calico-node-vx8s8" is not ready (calico-node)
Pod	kube-system/kube-dns-67689f84b-4k82d	system-cluster-critical pod "kube-dns-67689f84b-4k82d" is pending
Pod	kube-system/kube-dns-67689f84b-thdcq	system-cluster-critical pod "kube-dns-67689f84b-thdcq" is pending

Validation Failed
W0918 19:47:45.128112     187 validate_cluster.go:221] (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 ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Machine	i-0b8b064293f1b5515							machine "i-0b8b064293f1b5515" has not yet joined cluster
Pod	kube-system/kube-dns-67689f84b-4k82d					system-cluster-critical pod "kube-dns-67689f84b-4k82d" is not ready (kubedns)
Pod	kube-system/kube-proxy-ip-172-20-51-242.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-242.ap-northeast-1.compute.internal" is pending

Validation Failed
W0918 19:47:57.044050     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:48:08.874128     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:48:20.763240     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:48:32.610439     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:48:44.457813     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:48:56.153275     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:49:07.927927     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:49:19.759381     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:49:31.479054     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:49:43.391951     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:49:55.148715     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:50:06.889297     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:50:18.623013     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:50:30.353355     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:50:42.076047     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:50:54.328526     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:51:06.016098     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:51:17.768709     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:51:29.435311     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:51:41.105058     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:51:52.848097     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:52:04.643615     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:52:16.398380     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:52:28.275579     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:52:39.940635     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:52:51.615756     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:53:03.337046     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:53:15.069642     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:53:26.803557     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:53:38.716630     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:53:50.481252     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:54:02.424243     187 validate_cluster.go:221] (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 5 lines ...
ip-172-20-51-242.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0b8b064293f1b5515	machine "i-0b8b064293f1b5515" has not yet joined cluster

Validation Failed
W0918 19:54:14.353758     187 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/09/18 19:54:24 process.go:155: Step '/tmp/kops172450782/kops validate cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --wait 15m' finished in 15m4.637484546s
2020/09/18 19:54:24 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/09/18 19:54:24 process.go:153: Running: /tmp/kops172450782/kops toolbox dump --name e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io -ojson
I0918 19:54:24.545777     199 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
2020/09/18 19:54:26 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 1.584597663s
2020/09/18 19:54:26 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-9rszs
... skipping 203 lines ...
	volume:vol-0d7ed5f3d2ce93da6
	volume:vol-07425d22a793d1f7e
	security-group:sg-03fcff5952fbbc89b
	vpc:vpc-058a4ee98a9b348d5
	subnet:subnet-0ccb7c0a3de7d743c
subnet:subnet-0ccb7c0a3de7d743c	still has dependencies, will retry
I0918 19:55:56.037887     264 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-004bfbb871e8d4a8f	ok
I0918 19:55:56.044653     264 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-07425d22a793d1f7e	ok
volume:vol-0fbaa92d1ee23257f	still has dependencies, will retry
I0918 19:55:56.051888     264 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0d7ed5f3d2ce93da6	ok
volume:vol-0a1d2a7dad0880e2a	still has dependencies, will retry
volume:vol-0c4bd603806e10f60	still has dependencies, will retry
volume:vol-0e6c7710f600ff16b	still has dependencies, will retry
internet-gateway:igw-0d39ce18e7b05280b	still has dependencies, will retry
security-group:sg-03fcff5952fbbc89b	still has dependencies, will retry
... skipping 27 lines ...
	volume:vol-0fbaa92d1ee23257f
	route-table:rtb-052edd4233a6daa77
	volume:vol-0a1d2a7dad0880e2a
	dhcp-options:dopt-0beadffe640d0eb1b
	internet-gateway:igw-0d39ce18e7b05280b
	volume:vol-0c4bd603806e10f60
I0918 19:56:18.213326     264 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0c4bd603806e10f60	ok
I0918 19:56:18.215502     264 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0fbaa92d1ee23257f	ok
volume:vol-0e6c7710f600ff16b	ok
volume:vol-0a1d2a7dad0880e2a	ok
subnet:subnet-0ccb7c0a3de7d743c	ok
security-group:sg-09e4f56780bed4864	ok
security-group:sg-03fcff5952fbbc89b	ok
... skipping 3 lines ...
dhcp-options:dopt-0beadffe640d0eb1b	ok
Deleted kubectl config for e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io"
2020/09/18 19:56:26 process.go:155: Step '/tmp/kops172450782/kops delete cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --yes' finished in 1m14.196653547s
2020/09/18 19:56:26 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/09/18 19:56:26 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops172450782/kops validate cluster e2e-kops-calico-u2004-k16.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 720, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 570, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...