This job view page is being replaced by Spyglass soon. Check out the new job view.
PRReillyBrogan: Add bidirectional BPF mount for Cilium >= 1.9.10 or >= 1.10.4
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-24 13:36
Elapsed25m52s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 557 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0924 13:43:20.914942    4852 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/5ab138b1-1d3c-11ec-bbe6-dab681da360c/kops
I0924 13:43:21.129819    4852 up.go:43] Cleaning up any leaked resources from previous cluster
I0924 13:43:21.129860    4852 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0924 13:43:21.150994   12432 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 13:43:21.151127   12432 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0924 13:43:21.640407    4852 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0924 13:43:21.640460    4852 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --yes
I0924 13:43:21.672867   12442 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 13:43:21.672982   12442 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
I0924 13:43:22.424031    4852 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/24 13:43:22 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
I0924 13:43:22.451580    4852 http.go:37] curl https://ip.jsb.workers.dev
I0924 13:43:22.542398    4852 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.2 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210907 --channel=alpha --networking=weave --container-runtime=containerd --node-size=t3.large --admin-access 104.197.237.181/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0924 13:43:22.573452   12451 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 13:43:22.573667   12451 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0924 13:43:22.627763   12451 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0924 13:43:23.131696   12451 new_cluster.go:1074]  Cloud Provider ID = aws
... skipping 31 lines ...

I0924 13:43:48.868751    4852 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0924 13:43:48.895964   12471 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 13:43:48.896183   12471 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0924 13:43:50.004611   12471 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:44:00.049215   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:44:10.093142   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:44:20.127339   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:44:30.178071   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:44:40.216516   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:44:50.254109   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:45:00.284063   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:45:10.329812   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:45:20.361434   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:45:30.396644   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:45:40.431061   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:45:50.477657   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:46:00.536796   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:46:10.573618   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:46:20.605708   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:46:30.651313   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:46:40.681277   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:46:50.733293   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:47:00.769768   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:47:10.801397   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:47:20.837603   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:47:30.874180   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-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
W0924 13:47:40.912376   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 13 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wxfx7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wxfx7" is pending
Pod	kube-system/ebs-csi-node-n64jz			system-node-critical pod "ebs-csi-node-n64jz" is pending
Pod	kube-system/ebs-csi-node-s2mtz			system-node-critical pod "ebs-csi-node-s2mtz" is pending
Pod	kube-system/weave-net-92sc8			system-node-critical pod "weave-net-92sc8" is pending
Pod	kube-system/weave-net-lz2jk			system-node-critical pod "weave-net-lz2jk" is pending

Validation Failed
W0924 13:47:52.931785   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 15 lines ...
Pod	kube-system/ebs-csi-node-jz58k			system-node-critical pod "ebs-csi-node-jz58k" is pending
Pod	kube-system/ebs-csi-node-n64jz			system-node-critical pod "ebs-csi-node-n64jz" is pending
Pod	kube-system/ebs-csi-node-s2mtz			system-node-critical pod "ebs-csi-node-s2mtz" is pending
Pod	kube-system/weave-net-6vz6d			system-node-critical pod "weave-net-6vz6d" is pending
Pod	kube-system/weave-net-l9k2p			system-node-critical pod "weave-net-l9k2p" is pending

Validation Failed
W0924 13:48:04.379957   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is pending
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is pending

Validation Failed
W0924 13:48:15.784780   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:48:27.218470   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:48:38.598795   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
W0924 13:48:48.634051   12471 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

NODE STATUS
... skipping 6 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh					system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-47-226.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-47-226.us-west-2.compute.internal" is pending

Validation Failed
W0924 13:48:59.985393   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:49:11.422407   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:49:22.860714   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:49:34.263380   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:49:45.889556   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:49:57.256673   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:50:08.799462   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)

Validation Failed
W0924 13:50:20.328832   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:50:31.988921   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:50:43.535102   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:50:54.936916   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:51:06.328468   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)

Validation Failed
W0924 13:51:17.912935   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:51:29.444136   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:51:40.782205   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:51:52.485934   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:52:04.202368   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:52:15.802571   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:52:27.393849   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:52:38.852300   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:52:50.231861   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)

Validation Failed
W0924 13:53:02.428199   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)

Validation Failed
W0924 13:53:13.794297   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:53:25.248326   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:53:36.644162   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:53:48.082713   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:53:59.510363   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:54:11.057578   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:54:22.452107   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:54:33.979285   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:54:45.690211   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:54:57.167136   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:55:08.855374   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:55:20.412280   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:55:31.810600   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:55:43.492462   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:55:55.406650   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)

Validation Failed
W0924 13:56:06.919690   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:56:18.304439   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 6 lines ...
ip-172-20-53-19.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)

Validation Failed
W0924 13:56:29.669678   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:56:41.086493   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:56:52.569940   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:57:04.192429   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:57:15.694732   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:57:27.236749   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:57:38.793707   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:57:50.199646   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:58:01.632249   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:58:13.016900   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:58:24.403566   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:58:35.856815   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.large	4	4	us-west-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-m9gdh	system-cluster-critical pod "coredns-5dc785954d-m9gdh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-5hf4v		system-node-critical pod "ebs-csi-node-5hf4v" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-jz58k		system-node-critical pod "ebs-csi-node-jz58k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-n64jz		system-node-critical pod "ebs-csi-node-n64jz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-s2mtz		system-node-critical pod "ebs-csi-node-s2mtz" is not ready (ebs-plugin)

Validation Failed
W0924 13:58:47.363103   12471 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0924 13:58:57.376119    4852 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0924 13:58:57.396653   12485 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 13:58:57.396988   12485 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/24 13:59:05 Dumping node ip-172-20-44-139.us-west-2.compute.internal
2021/09/24 13:59:09 Dumping node ip-172-20-44-84.us-west-2.compute.internal
2021/09/24 13:59:12 Dumping node ip-172-20-47-226.us-west-2.compute.internal
... skipping 1453 lines ...
route-table:rtb-06e2a4a6827042d83	ok
vpc:vpc-09050257450a92077	ok
dhcp-options:dopt-04ea4616ec224cc4b	ok
Deleted kubectl config for e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

Deleted cluster: "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...