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-07 00:28
Elapsed23m26s
Revisiona84377d8fac4dcf014eb911a04476967c873b218
Refs 1009

No Test Failures!


Error lines from build-log.txt

... skipping 1108 lines ...

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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local


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

Validating cluster test-cluster-3997.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 7 lines ...
KIND	NAME			MESSAGE
Machine	i-089ecff7e9632b1d7	machine "i-089ecff7e9632b1d7" has not yet joined cluster
Machine	i-0b5832495ae3f48b1	machine "i-0b5832495ae3f48b1" has not yet joined cluster
Machine	i-0d0994f8a7c1fc315	machine "i-0d0994f8a7c1fc315" has not yet joined cluster
Machine	i-0f45765005b6f4190	machine "i-0f45765005b6f4190" has not yet joined cluster

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

Validating cluster test-cluster-3997.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 10 lines ...
Machine	i-0b5832495ae3f48b1								machine "i-0b5832495ae3f48b1" has not yet joined cluster
Machine	i-0d0994f8a7c1fc315								machine "i-0d0994f8a7c1fc315" has not yet joined cluster
Pod	kube-system/etcd-manager-events-ip-172-20-43-68.us-west-2.compute.internal	kube-system pod "etcd-manager-events-ip-172-20-43-68.us-west-2.compute.internal" is pending
Pod	kube-system/kube-dns-66b6848cf6-5blpj						kube-system pod "kube-dns-66b6848cf6-5blpj" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-krf2p				kube-system pod "kube-dns-autoscaler-577b4774b5-krf2p" is pending

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

Validating cluster test-cluster-3997.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 10 lines ...
VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-controller-manager-ip-172-20-43-68.us-west-2.compute.internal	kube-system pod "kube-controller-manager-ip-172-20-43-68.us-west-2.compute.internal" is pending
Pod	kube-system/kube-dns-66b6848cf6-5blpj						kube-system pod "kube-dns-66b6848cf6-5blpj" is pending
Pod	kube-system/kube-dns-autoscaler-577b4774b5-krf2p				kube-system pod "kube-dns-autoscaler-577b4774b5-krf2p" is pending

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

Validating cluster test-cluster-3997.k8s.local

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

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

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

Validating cluster test-cluster-3997.k8s.local

INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
... skipping 294 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/5e61bbc2-0e376ae4358e3e58da6/0392a6fda9277e27 should be healthy
  Expected error:
      <*awserr.baseError | 0xc000880d00>: {
          code: "RequestCanceled",
          message: "request context canceled",
          errs: [{}],
      }
      RequestCanceled: request context canceled
... skipping 4 lines ...
------------------------------
Sep  7 00:49:00.807: 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 431.010 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestE2E (431.01s)
FAIL

Ginkgo ran 1 suite in 8m1.910288608s
Test Suite Failed
2019/09/07 00:49:00 Deleting cluster test-cluster-3997.k8s.local
TYPE			NAME											ID
autoscaling-config	master-us-west-2a.masters.test-cluster-3997.k8s.local-20190907003338			master-us-west-2a.masters.test-cluster-3997.k8s.local-20190907003338
autoscaling-config	nodes.test-cluster-3997.k8s.local-20190907003338					nodes.test-cluster-3997.k8s.local-20190907003338
autoscaling-group	master-us-west-2a.masters.test-cluster-3997.k8s.local					master-us-west-2a.masters.test-cluster-3997.k8s.local
autoscaling-group	nodes.test-cluster-3997.k8s.local							nodes.test-cluster-3997.k8s.local
... skipping 290 lines ...
dhcp-options:dopt-01a7547c97f8da1fe	ok
Deleted kubectl config for test-cluster-3997.k8s.local

Deleted cluster: "test-cluster-3997.k8s.local"
2019/09/07 00:52: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/07 00:52:15 Cleaning up Docker data root...
[Barnacle] 2019/09/07 00:52:15 Removing all containers.
... skipping 25 lines ...