This job view page is being replaced by Spyglass soon. Check out the new job view.
PRvdhanan: instance metadata issue fix
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-04-27 22:04
Elapsed8m41s
Revisiona90f84ef397d4a4c12a04d1cec2ecd5594710f4b
Refs 855

No Test Failures!


Error lines from build-log.txt

... skipping 784 lines ...
## Validating cluster test-cluster-1076.k8s.local
#
Using cluster from kubectl context: test-cluster-1076.k8s.local

Validating cluster test-cluster-1076.k8s.local

W0427 22:08:09.722924    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:08:19.759744    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:08:29.808913    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:08:39.843132    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:08:49.876567    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-1076-k8s-3vniba-924895374.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:09:11.566241    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:09:33.184470    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:09:54.797488    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:10:16.464998    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:10:38.115135    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:10:59.739645    9284 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

NODE STATUS
... skipping 9 lines ...
Pod	kube-system/etcd-manager-events-ip-172-20-57-147.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-57-147.us-west-2.compute.internal" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-57-147.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-57-147.us-west-2.compute.internal" is pending
Pod	kube-system/kube-apiserver-ip-172-20-57-147.us-west-2.compute.internal		system-cluster-critical pod "kube-apiserver-ip-172-20-57-147.us-west-2.compute.internal" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-57-147.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-57-147.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-147.us-west-2.compute.internal		system-node-critical pod "kube-proxy-ip-172-20-57-147.us-west-2.compute.internal" is pending

Validation Failed
W0427 22:11:11.540078    9284 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 5 lines ...
KIND	NAME						MESSAGE
Machine	i-0396b8a860850c308				machine "i-0396b8a860850c308" has not yet joined cluster
Machine	i-08a2ff342e5949470				machine "i-08a2ff342e5949470" has not yet joined cluster
Machine	i-0ed4679f852649acd				machine "i-0ed4679f852649acd" has not yet joined cluster
Node	ip-172-20-57-147.us-west-2.compute.internal	master "ip-172-20-57-147.us-west-2.compute.internal" is not ready

Validation Failed
W0427 22:11:22.631223    9284 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 4 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0396b8a860850c308	machine "i-0396b8a860850c308" has not yet joined cluster
Machine	i-08a2ff342e5949470	machine "i-08a2ff342e5949470" has not yet joined cluster
Machine	i-0ed4679f852649acd	machine "i-0ed4679f852649acd" has not yet joined cluster

Validation Failed
W0427 22:11:33.840408    9284 validate_cluster.go:221] (will retry): cluster not yet healthy