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

No Test Failures!


Error lines from build-log.txt

... skipping 129 lines ...
I1019 08:40:47.532129    4703 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I1019 08:40:47.533625    4703 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.1+v1.22.0-5-gc97d172d26/linux/amd64/kops
I1019 08:40:48.256476    4703 up.go:43] Cleaning up any leaked resources from previous cluster
I1019 08:40:48.256508    4703 dumplogs.go:40] /logs/artifacts/12c85675-30b8-11ec-a761-46851535a78f/kops toolbox dump --name e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1019 08:40:48.275144    4723 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1019 08:40:48.275784    4723 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io" not found
W1019 08:40:48.809674    4703 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1019 08:40:48.809718    4703 down.go:48] /logs/artifacts/12c85675-30b8-11ec-a761-46851535a78f/kops delete cluster --name e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io --yes
I1019 08:40:48.827622    4733 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1019 08:40:48.827711    4733 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io" not found
I1019 08:40:49.322661    4703 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/19 08:40:49 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
I1019 08:40:49.329498    4703 http.go:37] curl https://ip.jsb.workers.dev
I1019 08:40:49.429796    4703 up.go:144] /logs/artifacts/12c85675-30b8-11ec-a761-46851535a78f/kops create cluster --name e2e-0799fb0cb3-ec357.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=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=docker --admin-access 35.194.23.235/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I1019 08:40:49.447388    4743 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1019 08:40:49.447495    4743 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1019 08:40:49.470687    4743 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1019 08:40:50.129704    4743 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 41 lines ...

I1019 08:41:18.494778    4703 up.go:181] /logs/artifacts/12c85675-30b8-11ec-a761-46851535a78f/kops validate cluster --name e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1019 08:41:18.511847    4762 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1019 08:41:18.511929    4762 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io

W1019 08:41:20.037368    4762 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1019 08:41:30.070051    4762 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0799fb0cb3-ec357.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
W1019 08:41:40.116113    4762 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
W1019 08:41:50.189631    4762 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
W1019 08:42:00.231056    4762 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
W1019 08:42:10.261432    4762 validate_cluster.go:232] (will retry): cluster not yet healthy
W1019 08:42:20.293245    4762 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0799fb0cb3-ec357.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
W1019 08:42:30.341587    4762 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
W1019 08:42:40.379349    4762 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
W1019 08:42:50.413689    4762 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
W1019 08:43:00.448314    4762 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
W1019 08:43:10.481646    4762 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
W1019 08:43:20.518175    4762 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
W1019 08:43:30.549241    4762 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
W1019 08:43:40.583215    4762 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
W1019 08:43:50.645532    4762 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
W1019 08:44:00.676427    4762 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
W1019 08:44:10.704295    4762 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
W1019 08:44:20.747225    4762 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
W1019 08:44:30.777125    4762 validate_cluster.go:232] (will retry): cluster not yet healthy
W1019 08:44:40.798373    4762 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0799fb0cb3-ec357.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
W1019 08:44:50.866618    4762 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
W1019 08:45:00.895851    4762 validate_cluster.go:232] (will retry): cluster not yet healthy
W1019 08:45:10.918181    4762 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0799fb0cb3-ec357.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
W1019 08:45:20.950187    4762 validate_cluster.go:232] (will retry): cluster not yet healthy
W1019 08:45:30.973918    4762 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0799fb0cb3-ec357.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
W1019 08:45:41.003132    4762 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
W1019 08:45:51.032705    4762 validate_cluster.go:232] (will retry): cluster not yet healthy
W1019 08:46:31.065071    4762 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
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
... skipping 10 lines ...
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-lbj8g				system-node-critical pod "calico-node-lbj8g" is pending
Pod	kube-system/calico-node-xp8gw				system-node-critical pod "calico-node-xp8gw" is pending
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:46:45.129085    4762 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 10 lines ...
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-lbj8g				system-node-critical pod "calico-node-lbj8g" is not ready (calico-node)
Pod	kube-system/calico-node-xp8gw				system-node-critical pod "calico-node-xp8gw" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:46:57.846444    4762 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 10 lines ...
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54			system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-lbj8g						system-node-critical pod "calico-node-lbj8g" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-9d2n2					system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq					system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-50-26.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-50-26.ap-northeast-2.compute.internal" is pending

Validation Failed
W1019 08:47:10.586836    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:47:23.496501    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:47:36.031792    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:47:48.731160    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:48:01.431359    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:48:14.044053    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:48:26.712443    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:48:39.375709    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:48:52.073208    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:49:04.737155    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:49:17.419927    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:49:30.191666    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:49:42.848609    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:49:55.549187    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:50:08.357216    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:50:21.108366    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:50:34.439536    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:50:47.115511    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:50:59.781944    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:51:12.427799    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:51:25.206126    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:51:37.882160    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:51:50.560149    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:52:03.292589    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:52:15.998612    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:52:28.809494    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:52:41.628352    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:52:54.317878    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:53:07.187968    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:53:19.865580    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:53:32.543994    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:53:45.233139    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:53:57.845078    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:54:10.451131    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:54:23.114977    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:54:36.329093    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:54:48.887526    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:55:01.617545    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:55:14.300240    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:55:26.995800    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:55:39.706620    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:55:52.340903    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:56:05.017794    4762 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 ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-t8q54	system-cluster-critical pod "calico-kube-controllers-659bd7879c-t8q54" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-9d2n2			system-cluster-critical pod "coredns-64497985bd-9d2n2" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-h98fq			system-cluster-critical pod "coredns-64497985bd-h98fq" is not ready (coredns)

Validation Failed
W1019 08:56:17.695449    4762 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I1019 08:56:27.703267    4703 dumplogs.go:40] /logs/artifacts/12c85675-30b8-11ec-a761-46851535a78f/kops toolbox dump --name e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1019 08:56:27.723682    4772 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1019 08:56:27.723776    4772 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/10/19 08:56:39 Dumping node ip-172-20-34-99.ap-northeast-2.compute.internal
2021/10/19 08:56:48 Dumping node ip-172-20-38-110.ap-northeast-2.compute.internal
2021/10/19 08:56:54 Dumping node ip-172-20-39-52.ap-northeast-2.compute.internal
... skipping 1231 lines ...
route-table:rtb-09cdebc66e36305d5	ok
vpc:vpc-0ae4406d4c5a168e9	ok
dhcp-options:dopt-0b00cb3ae68668027	ok
Deleted kubectl config for e2e-0799fb0cb3-ec357.test-cncf-aws.k8s.io

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