This job view page is being replaced by Spyglass soon. Check out the new job view.
PRgliptak: Allow override for csi-provisioner image
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-11-08 15:05
Elapsed17m59s
Revisionbe7140f71c302b36f2a35edeff21c814f406d4bb
Refs 401

No Test Failures!


Error lines from build-log.txt

... skipping 1360 lines ...

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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local


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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 7 lines ...
KIND	NAME			MESSAGE
Machine	i-014608c9fb625d962	machine "i-014608c9fb625d962" has not yet joined cluster
Machine	i-024ced1ce33a9ead2	machine "i-024ced1ce33a9ead2" has not yet joined cluster
Machine	i-02f6fbc6bb60ee711	machine "i-02f6fbc6bb60ee711" has not yet joined cluster
Machine	i-0f1484c4cf85b2754	machine "i-0f1484c4cf85b2754" has not yet joined cluster

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 7 lines ...
KIND	NAME			MESSAGE
Machine	i-014608c9fb625d962	machine "i-014608c9fb625d962" has not yet joined cluster
Machine	i-024ced1ce33a9ead2	machine "i-024ced1ce33a9ead2" has not yet joined cluster
Machine	i-02f6fbc6bb60ee711	machine "i-02f6fbc6bb60ee711" has not yet joined cluster
Machine	i-0f1484c4cf85b2754	machine "i-0f1484c4cf85b2754" has not yet joined cluster

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 12 lines ...
Node	ip-172-20-50-247.us-west-2.compute.internal		master "ip-172-20-50-247.us-west-2.compute.internal" is not ready
Pod	kube-system/aws-node-6t7k2				kube-system pod "aws-node-6t7k2" is pending
Pod	kube-system/dns-controller-56455df565-5c4vj		kube-system pod "dns-controller-56455df565-5c4vj" is pending
Pod	kube-system/kube-dns-66b6848cf6-kk6k7			kube-system pod "kube-dns-66b6848cf6-kk6k7" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-ktbbl	kube-system pod "kube-dns-autoscaler-577b4774b5-ktbbl" is pending

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 10 lines ...
Machine	i-02f6fbc6bb60ee711					machine "i-02f6fbc6bb60ee711" has not yet joined cluster
Machine	i-0f1484c4cf85b2754					machine "i-0f1484c4cf85b2754" has not yet joined cluster
Pod	kube-system/dns-controller-56455df565-5c4vj		kube-system pod "dns-controller-56455df565-5c4vj" is pending
Pod	kube-system/kube-dns-66b6848cf6-kk6k7			kube-system pod "kube-dns-66b6848cf6-kk6k7" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-ktbbl	kube-system pod "kube-dns-autoscaler-577b4774b5-ktbbl" is pending

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 11 lines ...
Machine	i-0f1484c4cf85b2754							machine "i-0f1484c4cf85b2754" has not yet joined cluster
Pod	kube-system/kube-dns-66b6848cf6-kk6k7					kube-system pod "kube-dns-66b6848cf6-kk6k7" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-ktbbl			kube-system pod "kube-dns-autoscaler-577b4774b5-ktbbl" is pending
Pod	kube-system/kube-proxy-ip-172-20-50-247.us-west-2.compute.internal	kube-system pod "kube-proxy-ip-172-20-50-247.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-50-247.us-west-2.compute.internal	kube-system pod "kube-scheduler-ip-172-20-50-247.us-west-2.compute.internal" is pending

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 9 lines ...

VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/kube-dns-66b6848cf6-kk6k7			kube-system pod "kube-dns-66b6848cf6-kk6k7" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-ktbbl	kube-system pod "kube-dns-autoscaler-577b4774b5-ktbbl" is pending

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 8 lines ...
ip-172-20-77-101.us-west-2.compute.internal	node	True

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

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

Validating cluster test-cluster-5737.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 578 lines ...
kube-proxy-ip-172-20-104-195.us-west-2.compute.internal               1/1     Running   0          60s
kube-proxy-ip-172-20-50-247.us-west-2.compute.internal                1/1     Running   0          2m6s
kube-proxy-ip-172-20-61-181.us-west-2.compute.internal                1/1     Running   0          53s
kube-proxy-ip-172-20-77-101.us-west-2.compute.internal                1/1     Running   0          51s
kube-scheduler-ip-172-20-50-247.us-west-2.compute.internal            1/1     Running   0          2m4s
tiller-deploy-5648cc8b79-6zq9k                                        1/1     Running   0          12s
Error: YAML parse error on aws-ebs-csi-driver/templates/manifest.yaml: error converting YAML to JSON: yaml: line 66: mapping values are not allowed in this context
2019/11/08 15:22:07 Deleting cluster test-cluster-5737.k8s.local
TYPE			NAME											ID
autoscaling-config	master-us-west-2a.masters.test-cluster-5737.k8s.local-20191108151216			master-us-west-2a.masters.test-cluster-5737.k8s.local-20191108151216
autoscaling-config	nodes.test-cluster-5737.k8s.local-20191108151216					nodes.test-cluster-5737.k8s.local-20191108151216
autoscaling-group	master-us-west-2a.masters.test-cluster-5737.k8s.local					master-us-west-2a.masters.test-cluster-5737.k8s.local
autoscaling-group	nodes.test-cluster-5737.k8s.local							nodes.test-cluster-5737.k8s.local
... skipping 172 lines ...
dhcp-options:dopt-0323abb4bff7b4732	ok
Deleted kubectl config for test-cluster-5737.k8s.local

Deleted cluster: "test-cluster-5737.k8s.local"
2019/11/08 15:23:38 exit status 1
exit status 1
make: *** [Makefile:54: test-e2e-multi-az] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
[Barnacle] 2019/11/08 15:23:38 Cleaning up Docker data root...
[Barnacle] 2019/11/08 15:23:38 Removing all containers.
... skipping 16 lines ...