This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-03-24 00:51
Elapsed4h3m
Revisionrelease-0.4
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/21e5a132-6221-45f9-b8a9-ec7d378e7df2/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/21e5a132-6221-45f9-b8a9-ec7d378e7df2/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 872 lines ...
Creating AWSMachineTemplate test-rqx3yd/test-infra-capa-mtyogf27-2
Creating Join KubeadmConfigTemplate test-rqx3yd/test-boot-mde9gy9k-2
Creating MachineDeployment test-rqx3yd/test-capa-md080nn2-2
STEP: Ensuring MachineDeployments are not in running state
Verifying MachineDeployment test-rqx3yd/test-capa-md080nn2-1 is running..
Verifying MachineDeployment test-rqx3yd/test-capa-md080nn2-2 is running..
Checking Error event with message Failed to create instance: failed to run instance: InvalidSubnetID.NotFound: The subnet ID 'notcreated' does not exist is present 
STEP: Create new AwsMachineTemplate with correct Subnet ID and update its name in MachineDeployment
Creating AWSMachineTemplate test-rqx3yd/test-infra-capa-mtyogf27-3
Ensuring Machine count matched to 2 
Verifying MachineDeployment test-rqx3yd/test-capa-md080nn2-1 is running..
STEP: Deleting the cluster
Deleting Cluster test-rqx3yd/test-a13jyj
... skipping 274 lines ...
  Creating cluster after reaching vpc maximum limit
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/aws_test.go:388
    Cluster created after reaching vpc limit should be in provisioning
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/aws_test.go:389
------------------------------
functional tests Delete infra node directly from infra provider 
  Machine referencing deleted infra node should come to failed state
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/aws_test.go:414
creating namespace "test-usvapc"
STEP: Creating a workload cluster with single control plane
STEP: Creating an AWSCluster
Creating AWSCluster test-usvapc/test-infra-3cpja2
STEP: Creating a Cluster
... skipping 14 lines ...
Creating MachineDeployment test-usvapc/test-capa-mduiim63
Ensuring Machine count matched to 2 
Verifying MachineDeployment test-usvapc/test-capa-mduiim63 is running..
STEP: Deleting node directly from infra cloud
Fetching the Machines of MachineDeployment test-capa-mduiim63: 
Terminating EC2 instance with ID: aws:////i-048e663eb40530efb ... 
Ensuring machine test-capa-mduiim63-5c4b74759d-2xfnk's state is failed ... 
panic: test timed out after 4h0m0s

goroutine 5057 [running]:
testing.(*M).startAlarm.func1()
	/usr/local/go/src/testing/testing.go:1377 +0xdf
created by time.goFunc
... skipping 109 lines ...
golang.org/x/net/http2.(*clientConnReadLoop).run(0xc00054ffb8, 0xc0004f47a8, 0xc13fa8)
	/home/prow/go/pkg/mod/golang.org/x/net@v0.0.0-20191021144547-ec77196f6094/http2/transport.go:1732 +0x8c
golang.org/x/net/http2.(*ClientConn).readLoop(0xc000575500)
	/home/prow/go/pkg/mod/golang.org/x/net@v0.0.0-20191021144547-ec77196f6094/http2/transport.go:1660 +0xa3
created by golang.org/x/net/http2.(*Transport).newClientConn
	/home/prow/go/pkg/mod/golang.org/x/net@v0.0.0-20191021144547-ec77196f6094/http2/transport.go:673 +0x62f
FAIL	sigs.k8s.io/cluster-api-provider-aws/test/e2e	14400.067s
FAIL
make: *** [Makefile:96: test-e2e] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up binfmt_misc ...
================================================================================
... skipping 2 lines ...