This job view page is being replaced by Spyglass soon. Check out the new job view.
PRleakingtapan: Switch to use new test framework
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-09-04 23:13
Elapsed22m26s
Revisionb326a5aeeb380a21c9928d9a310658799e0d6110
Refs 1009

No Test Failures!


Error lines from build-log.txt

... skipping 1109 lines ...

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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local


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

Validating cluster test-cluster-7187.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 7 lines ...
KIND	NAME			MESSAGE
Machine	i-0702d713ec1e2730d	machine "i-0702d713ec1e2730d" has not yet joined cluster
Machine	i-099578b841939bf77	machine "i-099578b841939bf77" has not yet joined cluster
Machine	i-0ae5bc437b2e0f368	machine "i-0ae5bc437b2e0f368" has not yet joined cluster
Machine	i-0d2cc711ea6c651f2	machine "i-0d2cc711ea6c651f2" has not yet joined cluster

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

Validating cluster test-cluster-7187.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 10 lines ...
Machine	i-0ae5bc437b2e0f368					machine "i-0ae5bc437b2e0f368" has not yet joined cluster
Machine	i-0d2cc711ea6c651f2					machine "i-0d2cc711ea6c651f2" has not yet joined cluster
Pod	kube-system/dns-controller-56455df565-dwc42		kube-system pod "dns-controller-56455df565-dwc42" is pending
Pod	kube-system/kube-dns-66b6848cf6-4v7q4			kube-system pod "kube-dns-66b6848cf6-4v7q4" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-mjm9s	kube-system pod "kube-dns-autoscaler-577b4774b5-mjm9s" is pending

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

Validating cluster test-cluster-7187.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 10 lines ...
Machine	i-0702d713ec1e2730d								machine "i-0702d713ec1e2730d" has not yet joined cluster
Machine	i-099578b841939bf77								machine "i-099578b841939bf77" has not yet joined cluster
Pod	kube-system/etcd-manager-main-ip-172-20-32-252.us-west-2.compute.internal	kube-system pod "etcd-manager-main-ip-172-20-32-252.us-west-2.compute.internal" is pending
Pod	kube-system/kube-dns-66b6848cf6-4v7q4						kube-system pod "kube-dns-66b6848cf6-4v7q4" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-mjm9s				kube-system pod "kube-dns-autoscaler-577b4774b5-mjm9s" is pending

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

Validating cluster test-cluster-7187.k8s.local

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

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

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

Validating cluster test-cluster-7187.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 291 lines ...
Ingress with multi-path echo backend
/home/prow/go/src/github.com/kubernetes-sigs/aws-alb-ingress-controller/test/e2e/ingress/multi_path_echo.go:190
  [mod-ip] should work [It]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-alb-ingress-controller/test/e2e/ingress/multi_path_echo.go:212

  all targets in arn:aws:elasticloadbalancing:us-west-2:607362164682:targetgroup/866babdb-062bf613d398493cdb2/52cbf7312e3b8a39 should be healthy
  Expected error:
      <*awserr.baseError | 0xc000930140>: {
          code: "RequestCanceled",
          message: "request context canceled",
          errs: [{}],
      }
      RequestCanceled: request context canceled
... skipping 4 lines ...
------------------------------
Sep  4 23:34:23.530: INFO: Running AfterSuite actions on all nodes


Summarizing 1 Failure:

[Fail] Ingress with multi-path echo backend [It] [mod-ip] should work 
/home/prow/go/src/github.com/kubernetes-sigs/aws-alb-ingress-controller/test/e2e/ingress/shared/targets.go:36

Ran 2 of 2 Specs in 417.465 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestE2E (417.47s)
FAIL

Ginkgo ran 1 suite in 7m49.635479957s
Test Suite Failed
2019/09/04 23:34:23 Deleting cluster test-cluster-7187.k8s.local
TYPE			NAME											ID
autoscaling-config	master-us-west-2a.masters.test-cluster-7187.k8s.local-20190904231811			master-us-west-2a.masters.test-cluster-7187.k8s.local-20190904231811
autoscaling-config	nodes.test-cluster-7187.k8s.local-20190904231811					nodes.test-cluster-7187.k8s.local-20190904231811
autoscaling-group	master-us-west-2a.masters.test-cluster-7187.k8s.local					master-us-west-2a.masters.test-cluster-7187.k8s.local
autoscaling-group	nodes.test-cluster-7187.k8s.local							nodes.test-cluster-7187.k8s.local
... skipping 188 lines ...
dhcp-options:dopt-0e5bc14a121ddb7c8	ok
Deleted kubectl config for test-cluster-7187.k8s.local

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