This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-03-26 19:00
Elapsed4h2m
Revisionrelease-0.4
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/7684f84c-c89e-457f-8365-073c25c06dea/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/7684f84c-c89e-457f-8365-073c25c06dea/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 709 lines ...
STEP: Deploying CNI to created Cluster
STEP: Creating the second Control Plane Machine
Creating AWSMachine test-d9svr2/test-infra-t9y1ge-1
Creating Join KubeadmConfig test-d9svr2/test-boot-4xw2mk-1
Creating Machine test-d9svr2/test-pbwtfp-1
Ensuring Machine test-d9svr2/test-pbwtfp-1 has bootstrapReady
Error retrieving node: etcdserver: leader changedSTEP: Creating the third Control Plane Machine
Creating AWSMachine test-d9svr2/test-infra-t9y1ge-2
Creating Join KubeadmConfig test-d9svr2/test-boot-4xw2mk-2
Creating Machine test-d9svr2/test-pbwtfp-2
Ensuring Machine test-d9svr2/test-pbwtfp-2 has bootstrapReady
STEP: Creating the MachineDeployment
Creating MachineDeployment in namespace test-d9svr2 with name test-capa-md1zwz0v
... skipping 148 lines ...
Creating AWSMachineTemplate test-z1zfgp/test-infra-capa-mtcgi54b-2
Creating Join KubeadmConfigTemplate test-z1zfgp/test-boot-md4ko630-2
Creating MachineDeployment test-z1zfgp/test-capa-mditajkt-2
STEP: Ensuring MachineDeployments are not in running state
Verifying MachineDeployment test-z1zfgp/test-capa-mditajkt-1 is running..
Verifying MachineDeployment test-z1zfgp/test-capa-mditajkt-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-z1zfgp/test-infra-capa-mtcgi54b-3
Ensuring Machine count matched to 2 
Verifying MachineDeployment test-z1zfgp/test-capa-mditajkt-1 is running..
STEP: Deleting the cluster
Deleting Cluster test-z1zfgp/test-2fqzko
... skipping 383 lines ...
golang.org/x/net/http2.(*clientConnReadLoop).run(0xc0006e2fb8, 0xc000906fa8, 0xc14018)
	/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(0xc00057db00)
	/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.038s
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 ...