This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-09-20 21:59
Elapsed20m34s
Revisionmaster

Test Failures


kubetest2 Up 16m2s

exit status 1
				from junit_runner.xml

Filter through log files


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 166 lines ...
I0920 22:00:48.267725    6114 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0920 22:00:48.269994    6114 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-beta.2+v1.25.0-beta.1-110-g7595f0b6e5/linux/amd64/kops
I0920 22:00:48.995856    6114 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519
I0920 22:00:49.003303    6114 up.go:44] Cleaning up any leaked resources from previous cluster
I0920 22:00:49.003423    6114 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0920 22:00:49.003457    6114 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0920 22:00:49.544789    6114 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0920 22:00:49.544847    6114 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --yes
I0920 22:00:49.544862    6114 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --yes
I0920 22:00:49.575718    6147 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io" not found
I0920 22:00:50.040382    6114 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/20 22:00:50 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
I0920 22:00:50.055394    6114 http.go:37] curl https://ip.jsb.workers.dev
I0920 22:00:50.167856    6114 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.5 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220912 --channel=alpha --networking=cilium-etcd --container-runtime=containerd --admin-access 104.155.166.231/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0920 22:00:50.167901    6114 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.5 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220912 --channel=alpha --networking=cilium-etcd --container-runtime=containerd --admin-access 104.155.166.231/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0920 22:00:50.205318    6156 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true
I0920 22:00:50.227031    6156 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0920 22:00:50.764159    6156 new_cluster.go:1277]  Cloud Provider ID = aws
... skipping 593 lines ...

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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
W0920 22:05:16.328536    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
W0920 22:05:56.375204    6197 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.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-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is pending
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is pending
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is pending
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is pending
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is pending

Validation Failed
W0920 22:06:10.014185    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:06:22.599281    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:06:35.397112    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:06:47.904398    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:08:03.366081    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:08:15.929366    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:08:29.292712    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:08:41.924691    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:08:54.593765    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:09:07.189177    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:09:19.849341    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:09:32.397565    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:09:44.904043    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:09:57.451414    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:10:10.424710    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:10:22.880774    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:10:35.401149    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)

Validation Failed
W0920 22:10:47.947782    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:11:00.509367    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

Validation Failed
W0920 22:11:13.099499    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:11:25.562493    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:11:38.260444    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:11:50.821007    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:12:03.321636    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:12:15.870781    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:12:28.428590    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:12:40.941543    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:12:53.579096    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:13:06.297929    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:13:18.893840    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:13:31.427475    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:13:43.948306    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:13:56.638583    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-6498r		system-cluster-critical pod "coredns-5c44b6cf7d-6498r" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)

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

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-s2fb9	system-cluster-critical pod "ebs-csi-controller-5b9566744f-s2fb9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

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

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:15:00.218146    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:15:12.768835    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:15:25.431125    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:15:38.177720    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:15:50.890186    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:16:03.626180    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:16:16.218885    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:16:28.648261    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-dhmlm			system-node-critical pod "ebs-csi-node-dhmlm" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kqf2l			system-node-critical pod "ebs-csi-node-kqf2l" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-lsdz9			system-node-critical pod "ebs-csi-node-lsdz9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-q87vw			system-node-critical pod "ebs-csi-node-q87vw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xcrbg			system-node-critical pod "ebs-csi-node-xcrbg" is not ready (ebs-plugin)

Validation Failed
W0920 22:16:41.117347    6197 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0920 22:16:51.129254    6114 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0920 22:16:51.129346    6114 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0920 22:17:55.575124    6114 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0920 22:17:55.575176    6114 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0920 22:17:56.099864    6114 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0920 22:17:56.099903    6114 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/700bc433-392f-11ed-b62f-a2c655ae1569/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 291 lines ...
route-table:rtb-079662edf4ba979e5	ok
vpc:vpc-0234a5b13f39d1cdb	ok
dhcp-options:dopt-03d10c603b6ee0560	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace