This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-03-29 13:12
Elapsed4h3m
Revisionrelease-0.4
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/1fc1d746-66a3-4d0b-b221-9005f60a2317/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/1fc1d746-66a3-4d0b-b221-9005f60a2317/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 874 lines ...
Creating AWSMachineTemplate test-x1bzt6/test-infra-capa-mt97y68z-2
Creating Join KubeadmConfigTemplate test-x1bzt6/test-boot-mdvk7ilo-2
Creating MachineDeployment test-x1bzt6/test-capa-md3mnv16-2
STEP: Ensuring MachineDeployments are not in running state
Verifying MachineDeployment test-x1bzt6/test-capa-md3mnv16-1 is running..
Verifying MachineDeployment test-x1bzt6/test-capa-md3mnv16-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-x1bzt6/test-infra-capa-mt97y68z-3
Ensuring Machine count matched to 2 
Verifying MachineDeployment test-x1bzt6/test-capa-md3mnv16-1 is running..
STEP: Deleting the cluster
Deleting Cluster test-x1bzt6/test-nncubz
... skipping 216 lines ...
STEP: Deploying CNI to created Cluster
STEP: Creating the second Control Plane Machine in second AZ
Creating AWSMachine test-wurpu2/test-infra-ufrg1p-1
Creating Join KubeadmConfig test-wurpu2/test-boot-uuyfdt-1
Creating Machine test-wurpu2/test-wjv45m-1
Ensuring Machine test-wurpu2/test-wjv45m-1 has bootstrapReady
Error retrieving node: etcdserver: leader changedSTEP: Creating the third Control Plane Machine using SubnetID in third AZ
Creating AWSMachine test-wurpu2/test-infra-ufrg1p-2
Creating Join KubeadmConfig test-wurpu2/test-boot-uuyfdt-2
Creating Machine test-wurpu2/test-wjv45m-2
Ensuring Machine test-wurpu2/test-wjv45m-2 has bootstrapReady
STEP: Creating the MachineDeployment in second AZ
Creating MachineDeployment in namespace test-wurpu2 with name test-capa-md887s32
... skipping 45 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-n0gviv"
STEP: Creating a workload cluster with single control plane
STEP: Creating an AWSCluster
Creating AWSCluster test-n0gviv/test-infra-iji135
STEP: Creating a Cluster
... skipping 122 lines ...
golang.org/x/net/http2.(*clientConnReadLoop).run(0xc0002c9fb8, 0xc0002787a8, 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(0xc00026c180)
	/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.120s
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 ...