This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultfailure
Tests 1 failed / 1 succeeded
Started2022-09-04 16:28
Elapsed21m40s
Revision
uploadercrier
uploadercrier

Test Failures


kubetest2 Up 15m55s

exit status 1
				from junit_runner.xml

Filter through log files


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 166 lines ...
I0904 16:30:13.839395    6090 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0904 16:30:13.889528    6090 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-beta.2+v1.25.0-beta.1-13-g9faeb5b8a9/linux/amd64/kops
I0904 16:30:15.144299    6090 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519
I0904 16:30:15.159008    6090 up.go:44] Cleaning up any leaked resources from previous cluster
I0904 16:30:15.159164    6090 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0904 16:30:15.159195    6090 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0904 16:30:15.673136    6090 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0904 16:30:15.673191    6090 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops delete cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --yes
I0904 16:30:15.673203    6090 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops delete cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --yes
I0904 16:30:15.709255    6125 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io" not found
I0904 16:30:16.237303    6090 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/04 16:30:16 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0904 16:30:16.248609    6090 http.go:37] curl https://ip.jsb.workers.dev
I0904 16:30:16.356940    6090 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops create cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.13 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-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-focal-20.04-amd64-server-20220810 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.71.6.63/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0904 16:30:16.356982    6090 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops create cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.13 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-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-focal-20.04-amd64-server-20220810 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.71.6.63/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0904 16:30:16.392855    6132 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0904 16:30:16.413284    6132 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0904 16:30:17.025349    6132 new_cluster.go:1277]  Cloud Provider ID = aws
... skipping 545 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
W0904 16:31:00.559335    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:31:10.626748    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:31:20.677287    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:31:30.729505    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:31:40.772402    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:31:50.827180    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:32:00.875513    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:32:10.923760    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:32:20.972494    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:32:31.019606    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:32:41.066242    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:32:51.143194    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:33:01.190995    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:33:11.245692    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:33:21.302254    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:33:31.352543    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:33:41.413563    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:33:51.456757    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:34:01.500689    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:34:11.544032    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:34:21.606358    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-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
W0904 16:34:31.651250    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 10 lines ...
Node	ip-172-20-39-12.us-west-1.compute.internal	node "ip-172-20-39-12.us-west-1.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-sd2rt			system-node-critical pod "calico-node-sd2rt" is pending
Pod	kube-system/coredns-5fcc7b6498-ckpqx		system-cluster-critical pod "coredns-5fcc7b6498-ckpqx" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-zcrtr	system-cluster-critical pod "coredns-autoscaler-6658b4bf85-zcrtr" is pending
Pod	kube-system/ebs-csi-node-tc289			system-node-critical pod "ebs-csi-node-tc289" is pending

Validation Failed
W0904 16:34:43.309027    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 15 lines ...
Pod	kube-system/coredns-5fcc7b6498-ckpqx		system-cluster-critical pod "coredns-5fcc7b6498-ckpqx" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-zcrtr	system-cluster-critical pod "coredns-autoscaler-6658b4bf85-zcrtr" is pending
Pod	kube-system/ebs-csi-node-9sgqf			system-node-critical pod "ebs-csi-node-9sgqf" is pending
Pod	kube-system/ebs-csi-node-r8nx9			system-node-critical pod "ebs-csi-node-r8nx9" is pending
Pod	kube-system/ebs-csi-node-tc289			system-node-critical pod "ebs-csi-node-tc289" is pending

Validation Failed
W0904 16:34:54.468397    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 14 lines ...
Pod	kube-system/coredns-5fcc7b6498-ckpqx					system-cluster-critical pod "coredns-5fcc7b6498-ckpqx" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-zcrtr				system-cluster-critical pod "coredns-autoscaler-6658b4bf85-zcrtr" is pending
Pod	kube-system/ebs-csi-node-9sgqf						system-node-critical pod "ebs-csi-node-9sgqf" is pending
Pod	kube-system/ebs-csi-node-r8nx9						system-node-critical pod "ebs-csi-node-r8nx9" is pending
Pod	kube-system/kube-proxy-ip-172-20-48-237.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-48-237.us-west-1.compute.internal" is pending

Validation Failed
W0904 16:35:05.850119    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 10 lines ...
Pod	kube-system/calico-node-pdkld						system-node-critical pod "calico-node-pdkld" is not ready (calico-node)
Pod	kube-system/calico-node-xgtc4						system-node-critical pod "calico-node-xgtc4" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-9sgqf						system-node-critical pod "ebs-csi-node-9sgqf" is pending
Pod	kube-system/ebs-csi-node-r8nx9						system-node-critical pod "ebs-csi-node-r8nx9" is pending
Pod	kube-system/kube-proxy-ip-172-20-39-12.us-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-39-12.us-west-1.compute.internal" is pending

Validation Failed
W0904 16:35:17.165535    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:35:28.356547    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:35:39.628868    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:35:50.830658    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:36:02.300187    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:36:13.489161    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:36:24.591858    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:36:35.915830    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:36:47.213427    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:36:58.462748    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:37:09.640434    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:37:21.036400    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:37:32.282003    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:37:43.479145    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:37:54.648688    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:38:05.855951    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:38:17.050505    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:38:28.290715    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:38:39.657992    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:38:50.867654    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:39:02.071728    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:39:13.318186    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:39:24.636896    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:39:36.056070    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:39:47.282725    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:39:58.577339    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:40:09.782704    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:40:21.117543    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:40:32.341555    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:40:43.616917    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:40:54.782998    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:41:05.995405    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:41:17.260184    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:41:28.608393    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:41:39.996570    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:41:51.175878    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:42:02.460198    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:42:13.684244    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:42:24.982008    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:42:36.635366    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:42:47.894004    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:42:59.107391    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:43:10.327594    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:43:21.654229    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:43:32.897155    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:43:44.126433    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:43:55.447402    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:44:06.566698    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:44:17.838814    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:44:29.106510    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:44:40.310843    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:44:51.489858    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:45:02.827097    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:45:14.101329    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:45:25.314881    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:45:36.541380    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:45:47.879597    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 5 lines ...
ip-172-20-58-134.us-west-1.compute.internal	master	True

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

Validation Failed
W0904 16:45:59.109765    6173 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0904 16:46:09.121997    6090 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0904 16:46:09.122058    6090 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0904 16:46:48.186613    6090 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops get cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0904 16:46:48.186665    6090 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops get cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0904 16:46:48.737402    6090 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops get instancegroups --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0904 16:46:48.737446    6090 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/99e54729-2c6e-11ed-a329-1a5ef8605916/kops get instancegroups --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 407 lines ...
route-table:rtb-01b8024c27fa4bbb5	ok
vpc:vpc-03b8e53d4be77f240	ok
dhcp-options:dopt-0aa97d93afeb997fc	ok
Deleted kubectl config for e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace