This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Implement Windows NodePublish/Unpublish
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-04-26 20:35
Elapsed14m1s
Revisione5075f8eeed44900c6721657821d548957a0da81
Refs 823

No Test Failures!


Error lines from build-log.txt

... skipping 788 lines ...
## Validating cluster test-cluster-21013.k8s.local
#
Using cluster from kubectl context: test-cluster-21013.k8s.local

Validating cluster test-cluster-21013.k8s.local

W0426 20:43:37.408275    9229 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0426 20:43:47.469667    9229 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0426 20:43:57.562475    9229 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0426 20:44:07.599503    9229 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0426 20:44:17.668564    9229 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0426 20:44:31.237289    9229 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-21013-k8-rne91k-134662388.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0426 20:44:54.095789    9229 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)
W0426 20:45:15.906897    9229 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)
W0426 20:45:37.718882    9229 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)
W0426 20:45:59.502400    9229 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)
W0426 20:46:21.328538    9229 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 8 lines ...
Node	ip-172-20-44-196.us-west-2.compute.internal					master "ip-172-20-44-196.us-west-2.compute.internal" is not ready
Pod	kube-system/etcd-manager-events-ip-172-20-44-196.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-44-196.us-west-2.compute.internal" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-44-196.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-44-196.us-west-2.compute.internal" is pending
Pod	kube-system/kube-apiserver-ip-172-20-44-196.us-west-2.compute.internal		system-cluster-critical pod "kube-apiserver-ip-172-20-44-196.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-44-196.us-west-2.compute.internal		system-cluster-critical pod "kube-scheduler-ip-172-20-44-196.us-west-2.compute.internal" is pending

Validation Failed
W0426 20:46:33.060900    9229 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 8 lines ...
Machine	i-0f58af58a0f8355de				machine "i-0f58af58a0f8355de" has not yet joined cluster
Node	ip-172-20-44-196.us-west-2.compute.internal	master "ip-172-20-44-196.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending
Pod	kube-system/dns-controller-cd496f988-wkz2f	system-cluster-critical pod "dns-controller-cd496f988-wkz2f" is pending

Validation Failed
W0426 20:46:44.360215    9229 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 7 lines ...
Machine	i-096a274196ce2da75				machine "i-096a274196ce2da75" has not yet joined cluster
Machine	i-0f58af58a0f8355de				machine "i-0f58af58a0f8355de" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending
Pod	kube-system/dns-controller-cd496f988-wkz2f	system-cluster-critical pod "dns-controller-cd496f988-wkz2f" is pending

Validation Failed
W0426 20:46:55.523361    9229 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 7 lines ...
Machine	i-096a274196ce2da75				machine "i-096a274196ce2da75" has not yet joined cluster
Machine	i-0f58af58a0f8355de				machine "i-0f58af58a0f8355de" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending
Pod	kube-system/dns-controller-cd496f988-wkz2f	system-cluster-critical pod "dns-controller-cd496f988-wkz2f" is pending

Validation Failed
W0426 20:47:06.614733    9229 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 7 lines ...
Machine	i-096a274196ce2da75				machine "i-096a274196ce2da75" has not yet joined cluster
Machine	i-0f58af58a0f8355de				machine "i-0f58af58a0f8355de" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending
Pod	kube-system/dns-controller-cd496f988-wkz2f	system-cluster-critical pod "dns-controller-cd496f988-wkz2f" is pending

Validation Failed
W0426 20:47:17.735938    9229 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 7 lines ...
Machine	i-096a274196ce2da75				machine "i-096a274196ce2da75" has not yet joined cluster
Machine	i-0f58af58a0f8355de				machine "i-0f58af58a0f8355de" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending
Pod	kube-system/dns-controller-cd496f988-wkz2f	system-cluster-critical pod "dns-controller-cd496f988-wkz2f" is pending

Validation Failed
W0426 20:47:28.838910    9229 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 6 lines ...
Machine	i-01651df812fc764a2				machine "i-01651df812fc764a2" has not yet joined cluster
Machine	i-096a274196ce2da75				machine "i-096a274196ce2da75" has not yet joined cluster
Machine	i-0f58af58a0f8355de				machine "i-0f58af58a0f8355de" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending

Validation Failed
W0426 20:47:40.002782    9229 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 10 lines ...
Node	ip-172-20-60-56.us-west-2.compute.internal				node "ip-172-20-60-56.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-v2zst					system-cluster-critical pod "coredns-5489b75945-v2zst" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-wqnbh				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-wqnbh" is pending
Pod	kube-system/kube-proxy-ip-172-20-36-153.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-36-153.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-60-56.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-60-56.us-west-2.compute.internal" is pending

Validation Failed
W0426 20:47:51.079881    9229 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 7 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-45-196.us-west-2.compute.internal	node "ip-172-20-45-196.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-l6fp6		system-cluster-critical pod "coredns-5489b75945-l6fp6" is pending
Pod	kube-system/coredns-5489b75945-v2zst		system-cluster-critical pod "coredns-5489b75945-v2zst" is not ready (coredns)

Validation Failed
W0426 20:48:02.362925    9229 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 37 lines ...