This job view page is being replaced by Spyglass soon. Check out the new job view.
PRleakingtapan: Fix the bug by passing fstype correctly
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-08-14 18:19
Elapsed30m32s
Revision009ab2b9c4ac59a9f4ab5f65f17d6a358c847139
Refs 335

No Test Failures!


Error lines from build-log.txt

... skipping 1634 lines ...

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

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


unexpected error during validation: error listing nodes: Get https://api-test-cluster-16250-k8-g3ro8m-1233072641.us-west-2.elb.amazonaws.com/api/v1/nodes: dial tcp: lookup api-test-cluster-16250-k8-g3ro8m-1233072641.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-16250.k8s.local

Validating cluster test-cluster-16250.k8s.local


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

Validating cluster test-cluster-16250.k8s.local


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

Validating cluster test-cluster-16250.k8s.local

INSTANCE GROUPS
... skipping 8 lines ...
KIND	NAME			MESSAGE
Machine	i-02a3cae73165f1419	machine "i-02a3cae73165f1419" has not yet joined cluster
Machine	i-070d0e889924a2bb6	machine "i-070d0e889924a2bb6" has not yet joined cluster
Machine	i-0a6e3169fd6b50142	machine "i-0a6e3169fd6b50142" has not yet joined cluster
Machine	i-0bf1f7257c98364a1	machine "i-0bf1f7257c98364a1" has not yet joined cluster

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

Validating cluster test-cluster-16250.k8s.local

INSTANCE GROUPS
... skipping 11 lines ...
Machine	i-070d0e889924a2bb6								machine "i-070d0e889924a2bb6" has not yet joined cluster
Machine	i-0a6e3169fd6b50142								machine "i-0a6e3169fd6b50142" has not yet joined cluster
Pod	kube-system/etcd-manager-main-ip-172-20-46-179.us-west-2.compute.internal	kube-system pod "etcd-manager-main-ip-172-20-46-179.us-west-2.compute.internal" is pending
Pod	kube-system/kube-dns-autoscaler-6567f59ccb-4vp7c				kube-system pod "kube-dns-autoscaler-6567f59ccb-4vp7c" is pending
Pod	kube-system/kube-dns-bdf859cdc-5nsmw						kube-system pod "kube-dns-bdf859cdc-5nsmw" is pending

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

Validating cluster test-cluster-16250.k8s.local

INSTANCE GROUPS
... skipping 10 lines ...
Machine	i-02a3cae73165f1419					machine "i-02a3cae73165f1419" has not yet joined cluster
Machine	i-070d0e889924a2bb6					machine "i-070d0e889924a2bb6" has not yet joined cluster
Machine	i-0a6e3169fd6b50142					machine "i-0a6e3169fd6b50142" has not yet joined cluster
Pod	kube-system/kube-dns-autoscaler-6567f59ccb-4vp7c	kube-system pod "kube-dns-autoscaler-6567f59ccb-4vp7c" is pending
Pod	kube-system/kube-dns-bdf859cdc-5nsmw			kube-system pod "kube-dns-bdf859cdc-5nsmw" is pending

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

Validating cluster test-cluster-16250.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-xqvjq                                       1/1     Running   0          11m
etcd-manager-events-ip-172-20-46-179.us-west-2.compute.internal       1/1     Running   0          10m
etcd-manager-main-ip-172-20-46-179.us-west-2.compute.internal         1/1     Running   0          11m
kube-apiserver-ip-172-20-46-179.us-west-2.compute.internal            1/1     Running   2          10m
kube-controller-manager-ip-172-20-46-179.us-west-2.compute.internal   1/1     Running   0          10m
... skipping 226 lines ...
go: downloading gopkg.in/fsnotify.v1 v1.4.7
go: downloading gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
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
{"component":"entrypoint","file":"prow/entrypoint/run.go:163","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","time":"2019-08-14T18:50:06Z"}