This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-18 14:40
Elapsed19m1s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0918 14:41:14.212110    4090 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0918 14:41:14.214243    4090 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-168-g8d49409d1f/linux/amd64/kops
I0918 14:41:14.950183    4090 up.go:43] Cleaning up any leaked resources from previous cluster
I0918 14:41:14.950218    4090 dumplogs.go:38] /logs/artifacts/4b21023b-188e-11ec-bfa0-9e8ae4027703/kops toolbox dump --name e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0918 14:41:14.967571    4110 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0918 14:41:14.967795    4110 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io" not found
W0918 14:41:15.482299    4090 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0918 14:41:15.482472    4090 down.go:48] /logs/artifacts/4b21023b-188e-11ec-bfa0-9e8ae4027703/kops delete cluster --name e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io --yes
I0918 14:41:15.501133    4121 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0918 14:41:15.501235    4121 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io" not found
I0918 14:41:16.175933    4090 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/18 14:41:16 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
I0918 14:41:16.185429    4090 http.go:37] curl https://ip.jsb.workers.dev
I0918 14:41:16.271655    4090 up.go:144] /logs/artifacts/4b21023b-188e-11ec-bfa0-9e8ae4027703/kops create cluster --name e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=amazon/amzn2-ami-hvm-2.0.20210813.1-x86_64-gp2 --channel=alpha --networking=kubenet --container-runtime=containerd --admin-access 35.224.171.180/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0918 14:41:16.291862    4131 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0918 14:41:16.292009    4131 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0918 14:41:16.324767    4131 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0918 14:41:16.910388    4131 new_cluster.go:1052]  Cloud Provider ID = aws
... skipping 41 lines ...

I0918 14:41:45.774757    4090 up.go:181] /logs/artifacts/4b21023b-188e-11ec-bfa0-9e8ae4027703/kops validate cluster --name e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0918 14:41:45.794115    4151 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0918 14:41:45.794904    4151 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io

W0918 14:41:47.337960    4151 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-f01ca39887-e2e4a.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-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:41:57.534276    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:42:07.565375    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:42:17.627193    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:42:27.709865    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:42:37.756797    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:42:47.822896    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:42:57.867817    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:43:07.916210    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:43:17.951669    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:43:27.979659    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:43:38.009045    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:43:48.040969    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:43:58.073226    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:44:08.167830    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:44:18.198550    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:44:28.243671    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:44:38.322366    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:44:48.500045    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:44:58.550826    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:45:08.609449    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:45:18.667711    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

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 14:45:28.715495    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
Machine	i-0c5ba2261c4cd86fe					machine "i-0c5ba2261c4cd86fe" has not yet joined cluster
Machine	i-0e238d1bd7d86611b					machine "i-0e238d1bd7d86611b" has not yet joined cluster
Node	ip-172-20-54-117.ap-northeast-2.compute.internal	master "ip-172-20-54-117.ap-northeast-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-64497985bd-m82rk			system-cluster-critical pod "coredns-64497985bd-m82rk" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-9zmvr		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-9zmvr" is pending

Validation Failed
W0918 14:45:43.399909    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
Machine	i-056370e05b81ee5df					machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b					machine "i-0e238d1bd7d86611b" has not yet joined cluster
Node	ip-172-20-54-117.ap-northeast-2.compute.internal	master "ip-172-20-54-117.ap-northeast-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-64497985bd-m82rk			system-cluster-critical pod "coredns-64497985bd-m82rk" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-9zmvr		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-9zmvr" is pending

Validation Failed
W0918 14:45:56.086728    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-039a2edd1e7eaf9c2			machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df			machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b			machine "i-0e238d1bd7d86611b" has not yet joined cluster
Pod	kube-system/coredns-64497985bd-99s56	system-cluster-critical pod "coredns-64497985bd-99s56" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-m82rk	system-cluster-critical pod "coredns-64497985bd-m82rk" is not ready (coredns)

Validation Failed
W0918 14:46:09.027152    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:46:21.641317    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:46:34.461760    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:46:47.271416    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:46:59.993631    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:47:12.951560    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:47:25.541093    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:47:38.168596    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:47:50.840458    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:48:03.607713    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:48:16.222737    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:48:28.849997    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:48:41.727367    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:48:54.398490    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:49:07.006275    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:49:19.908214    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:49:33.211815    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:49:45.904340    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Machine	i-056370e05b81ee5df	machine "i-056370e05b81ee5df" has not yet joined cluster
Machine	i-0e238d1bd7d86611b	machine "i-0e238d1bd7d86611b" has not yet joined cluster

Validation Failed
W0918 14:49:58.549789    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 8 lines ...
KIND	NAME									MESSAGE
Machine	i-039a2edd1e7eaf9c2							machine "i-039a2edd1e7eaf9c2" has not yet joined cluster
Node	ip-172-20-38-249.ap-northeast-2.compute.internal			node "ip-172-20-38-249.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-46-106.ap-northeast-2.compute.internal			node "ip-172-20-46-106.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/kube-proxy-ip-172-20-46-106.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-106.ap-northeast-2.compute.internal" is pending

Validation Failed
W0918 14:50:11.372688    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:50:24.242041    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:50:36.945659    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:50:49.700324    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:51:02.398150    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:51:15.341488    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:51:27.953755    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:51:40.669064    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:51:53.253077    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:52:06.058059    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:52:18.638294    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:52:31.393241    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:52:44.026313    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:52:56.775507    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:53:09.474427    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:53:22.044477    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:53:35.193777    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:53:47.877889    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:54:00.736454    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:54:13.382180    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:54:26.096889    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:54:38.858709    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:54:51.648147    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:55:04.514710    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:55:17.253541    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:55:29.990958    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:55:42.639679    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:55:55.216290    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:56:07.919002    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:56:20.629680    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:56:33.693251    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 5 lines ...
ip-172-20-55-240.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-039a2edd1e7eaf9c2	machine "i-039a2edd1e7eaf9c2" has not yet joined cluster

Validation Failed
W0918 14:56:46.434806    4151 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0918 14:56:56.447337    4090 dumplogs.go:38] /logs/artifacts/4b21023b-188e-11ec-bfa0-9e8ae4027703/kops toolbox dump --name e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0918 14:56:56.466225    4161 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0918 14:56:56.466323    4161 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/18 14:57:09 Dumping node ip-172-20-38-249.ap-northeast-2.compute.internal
2021/09/18 14:57:16 Dumping node ip-172-20-46-106.ap-northeast-2.compute.internal
2021/09/18 14:57:23 Dumping node ip-172-20-54-117.ap-northeast-2.compute.internal
... skipping 1260 lines ...
route-table:rtb-07f9da2a53f9bf215	ok
vpc:vpc-09fc85f3cef450d21	ok
dhcp-options:dopt-0517f31ad3df04d17	ok
Deleted kubectl config for e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io

Deleted cluster: "e2e-f01ca39887-e2e4a.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace