This job view page is being replaced by Spyglass soon. Check out the new job view.
PRleakingtapan: Update to use kubernetes 1.15 as dependency
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-08-15 01:55
Elapsed29m43s
Revision76833a3233163f43c9e8085dd861ca4b20e3021b
Refs 345

No Test Failures!


Error lines from build-log.txt

... skipping 1853 lines ...

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

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-4706-k8s-1c25uf-899760802.us-west-2.elb.amazonaws.com/api/v1/nodes: EOF
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local

INSTANCE GROUPS
... skipping 11 lines ...
Machine	i-00db387e44c2561b1					machine "i-00db387e44c2561b1" has not yet joined cluster
Machine	i-078e144df1ed020d0					machine "i-078e144df1ed020d0" has not yet joined cluster
Pod	kube-system/dns-controller-67d566c9b4-g9txb		kube-system pod "dns-controller-67d566c9b4-g9txb" is pending
Pod	kube-system/kube-dns-autoscaler-6567f59ccb-87c4g	kube-system pod "kube-dns-autoscaler-6567f59ccb-87c4g" is pending
Pod	kube-system/kube-dns-bdf859cdc-wt8c5			kube-system pod "kube-dns-bdf859cdc-wt8c5" is pending

Validation Failed
Waiting cluster to be created
Using cluster from kubectl context: test-cluster-4706.k8s.local

Validating cluster test-cluster-4706.k8s.local

INSTANCE GROUPS
... skipping 26 lines ...

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
error: timed out waiting for the condition on deployments/tiller-deploy
NAME                                                                 READY   STATUS    RESTARTS   AGE
dns-controller-67d566c9b4-g9txb                                      1/1     Running   0          11m
etcd-manager-events-ip-172-20-50-63.us-west-2.compute.internal       1/1     Running   0          11m
etcd-manager-main-ip-172-20-50-63.us-west-2.compute.internal         1/1     Running   0          10m
kube-apiserver-ip-172-20-50-63.us-west-2.compute.internal            1/1     Running   3          11m
kube-controller-manager-ip-172-20-50-63.us-west-2.compute.internal   1/1     Running   0          11m
... skipping 444 lines ...
go: downloading gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
go: downloading gopkg.in/fsnotify.v1 v1.4.7
go: extracting gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
go: extracting gopkg.in/fsnotify.v1 v1.4.7
go: downloading golang.org/x/sys v0.0.0-20190509141414-a5b02f93d862
go: extracting golang.org/x/sys v0.0.0-20190509141414-a5b02f93d862
Failed to compile e2e:

# github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/testsuites
tests/e2e/testsuites/testsuites.go:73:2: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:142:2: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:301:2: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:412:8: undefined: framework.WaitForDeploymentComplete
tests/e2e/testsuites/testsuites.go:414:15: undefined: framework.GetPodsForDeployment
tests/e2e/testsuites/testsuites.go:421:15: undefined: framework.GetPodsForDeployment
tests/e2e/testsuites/testsuites.go:436:2: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:444:2: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:454:2: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:457:3: undefined: framework.Logf
tests/e2e/testsuites/testsuites.go:457:3: too many errors

Ginkgo ran 1 suite in 2m28.319647682s
Test Suite Failed
Removing driver
release "aws-ebs-csi-driver" deleted
Deleting cluster test-cluster-4706
TYPE			NAME											ID
autoscaling-config	master-us-west-2a.masters.test-cluster-4706.k8s.local-20190815020239			master-us-west-2a.masters.test-cluster-4706.k8s.local-20190815020239
autoscaling-config	nodes.test-cluster-4706.k8s.local-20190815020239					nodes.test-cluster-4706.k8s.local-20190815020239
... skipping 98 lines ...
route-table:rtb-0dbaa335301805698	ok
vpc:vpc-0ae27b3026bdcd03f	ok
dhcp-options:dopt-056c4b0d747f0ef5c	ok
Deleted kubectl config for test-cluster-4706.k8s.local

Deleted cluster: "test-cluster-4706.k8s.local"
Makefile:49: recipe for target 'test-e2e-single-az' failed
make: *** [test-e2e-single-az] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
[Barnacle] 2019/08/15 02:25:21 Cleaning up Docker data root...
[Barnacle] 2019/08/15 02:25:21 Removing all containers.
... skipping 25 lines ...