This job view page is being replaced by Spyglass soon. Check out the new job view.
PRleakingtapan: Add e2e tests
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-10-10 04:02
Elapsed17m39s
Revisionf3752e40fdf9628cbdc62380e6a1f2f5ca29624b
Refs 103

No Test Failures!


Error lines from build-log.txt

... skipping 2262 lines ...

Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-255-k8s--59ch44-1757512280.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 11 lines ...
Machine	i-0e28fe57e02ff0ae3					machine "i-0e28fe57e02ff0ae3" has not yet joined cluster
Node	ip-172-20-59-87.us-west-2.compute.internal		master "ip-172-20-59-87.us-west-2.compute.internal" is not ready
Pod	kube-system/aws-node-66j8b				kube-system pod "aws-node-66j8b" is pending
Pod	kube-system/dns-controller-56455df565-kvmdv		kube-system pod "dns-controller-56455df565-kvmdv" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-mg676	kube-system pod "kube-dns-autoscaler-577b4774b5-mg676" is pending

Validation Failed
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 10 lines ...
Machine	i-0800a1a4f7a58c271							machine "i-0800a1a4f7a58c271" has not yet joined cluster
Machine	i-0e28fe57e02ff0ae3							machine "i-0e28fe57e02ff0ae3" has not yet joined cluster
Pod	kube-system/dns-controller-56455df565-kvmdv				kube-system pod "dns-controller-56455df565-kvmdv" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-mg676			kube-system pod "kube-dns-autoscaler-577b4774b5-mg676" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-87.us-west-2.compute.internal	kube-system pod "kube-proxy-ip-172-20-59-87.us-west-2.compute.internal" is pending

Validation Failed
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 11 lines ...
KIND	NAME							MESSAGE
Node	ip-172-20-48-67.us-west-2.compute.internal		node "ip-172-20-48-67.us-west-2.compute.internal" is not ready
Node	ip-172-20-52-181.us-west-2.compute.internal		node "ip-172-20-52-181.us-west-2.compute.internal" is not ready
Node	ip-172-20-52-190.us-west-2.compute.internal		node "ip-172-20-52-190.us-west-2.compute.internal" is not ready
Pod	kube-system/kube-dns-autoscaler-577b4774b5-mg676	kube-system pod "kube-dns-autoscaler-577b4774b5-mg676" is pending

Validation Failed
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 8 lines ...
ip-172-20-59-87.us-west-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-proxy-ip-172-20-48-67.us-west-2.compute.internal	kube-system pod "kube-proxy-ip-172-20-48-67.us-west-2.compute.internal" is pending

Validation Failed
Using cluster from kubectl context: test-cluster-255.k8s.local

Validating cluster test-cluster-255.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 287 lines ...
dhcp-options:dopt-0043e65d5414717f4	ok
Deleted kubectl config for test-cluster-255.k8s.local

Deleted cluster: "test-cluster-255.k8s.local"
2019/10/10 04:20:04 exit status 1
exit status 1
Makefile:42: recipe for target 'test-e2e' failed
make: *** [test-e2e] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
[Barnacle] 2019/10/10 04:20:04 Cleaning up Docker data root...
[Barnacle] 2019/10/10 04:20:04 Removing all containers.
... skipping 25 lines ...