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-11 17:28
Elapsed29m38s
Revision8649833fb24596a9675000a773ca88e765840970
Refs 103

No Test Failures!


Error lines from build-log.txt

... skipping 2262 lines ...

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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local


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

Validating cluster test-cluster-5861.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 7 lines ...
KIND	NAME			MESSAGE
Machine	i-05b016a675f7f7fad	machine "i-05b016a675f7f7fad" has not yet joined cluster
Machine	i-09cabeed08cd32982	machine "i-09cabeed08cd32982" has not yet joined cluster
Machine	i-0eff5b9507c09f5f2	machine "i-0eff5b9507c09f5f2" has not yet joined cluster
Machine	i-0f0de707ab274e214	machine "i-0f0de707ab274e214" has not yet joined cluster

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

Validating cluster test-cluster-5861.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 11 lines ...
Machine	i-0f0de707ab274e214					machine "i-0f0de707ab274e214" has not yet joined cluster
Node	ip-172-20-35-120.us-west-2.compute.internal		master "ip-172-20-35-120.us-west-2.compute.internal" is not ready
Pod	kube-system/dns-controller-56455df565-5fn5n		kube-system pod "dns-controller-56455df565-5fn5n" is pending
Pod	kube-system/kube-dns-66b6848cf6-98xzp			kube-system pod "kube-dns-66b6848cf6-98xzp" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-4p2vt	kube-system pod "kube-dns-autoscaler-577b4774b5-4p2vt" is pending

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

Validating cluster test-cluster-5861.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 14 lines ...
Node	ip-172-20-44-126.us-west-2.compute.internal		node "ip-172-20-44-126.us-west-2.compute.internal" is not ready
Pod	kube-system/aws-node-2ltsz				kube-system pod "aws-node-2ltsz" is pending
Pod	kube-system/aws-node-lbq59				kube-system pod "aws-node-lbq59" is pending
Pod	kube-system/kube-dns-66b6848cf6-98xzp			kube-system pod "kube-dns-66b6848cf6-98xzp" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-4p2vt	kube-system pod "kube-dns-autoscaler-577b4774b5-4p2vt" is pending

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

Validating cluster test-cluster-5861.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 325 lines ...
Oct 11 17:49:53.625: INFO: PersistentVolumeClaim pvc-lcf76 found but phase is Pending instead of Bound.
Oct 11 17:49:55.682: INFO: PersistentVolumeClaim pvc-lcf76 found and phase=Bound (4m46.275185488s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Oct 11 17:49:55.855: INFO: Waiting up to 15m0s for pod "fsx-volume-tester-v5wtg" in namespace "fsx-8081" to be "success or failure"
Oct 11 17:49:55.913: INFO: Pod "fsx-volume-tester-v5wtg": Phase="Pending", Reason="", readiness=false. Elapsed: 57.519234ms
Oct 11 17:49:57.969: INFO: Pod "fsx-volume-tester-v5wtg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.114216444s
Oct 11 17:50:00.033: INFO: Pod "fsx-volume-tester-v5wtg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.178002182s
Oct 11 17:50:02.090: INFO: Pod "fsx-volume-tester-v5wtg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.235120009s
Oct 11 17:50:04.150: INFO: Pod "fsx-volume-tester-v5wtg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.295016238s
... skipping 342 lines ...
rip    0x460c23
rflags 0x202
cs     0x33
fs     0x0
gs     0x0
*** Test killed with quit: ran too long (10m0s).
FAIL	github.com/kubernetes-sigs/aws-fsx-csi-driver/tests/e2e	600.016s
Removing driver
daemonset.apps "fsx-csi-node" deleted
serviceaccount "fsx-csi-controller-sa" deleted
clusterrole.rbac.authorization.k8s.io "fsx-csi-external-provisioner-role" deleted
clusterrolebinding.rbac.authorization.k8s.io "fsx-csi-external-provisioner-binding" deleted
statefulset.apps "fsx-csi-controller" deleted
... skipping 209 lines ...
dhcp-options:dopt-0bbb8d780488e4f60	ok
Deleted kubectl config for test-cluster-5861.k8s.local

Deleted cluster: "test-cluster-5861.k8s.local"
2019/10/11 17:57:52 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/11 17:57:52 Cleaning up Docker data root...
[Barnacle] 2019/10/11 17:57:52 Removing all containers.
... skipping 25 lines ...