This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-03-30 01:14
Elapsed4h2m
Revisionrelease-0.4
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/ecde6b4a-a731-4e58-a13d-489bacd751d3/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/ecde6b4a-a731-4e58-a13d-489bacd751d3/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 870 lines ...
Creating AWSMachineTemplate test-j1bh41/test-infra-capa-mtawmemn-2
Creating Join KubeadmConfigTemplate test-j1bh41/test-boot-mdi7bhgi-2
Creating MachineDeployment test-j1bh41/test-capa-mdirbc0e-2
STEP: Ensuring MachineDeployments are not in running state
Verifying MachineDeployment test-j1bh41/test-capa-mdirbc0e-1 is running..
Verifying MachineDeployment test-j1bh41/test-capa-mdirbc0e-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-j1bh41/test-infra-capa-mtawmemn-3
Ensuring Machine count matched to 2 
Verifying MachineDeployment test-j1bh41/test-capa-mdirbc0e-1 is running..
STEP: Deleting the cluster
Deleting Cluster test-j1bh41/test-lwwnej
... 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-u08l9w"
STEP: Creating a workload cluster with single control plane
STEP: Creating an AWSCluster
Creating AWSCluster test-u08l9w/test-infra-vlsgqw
STEP: Creating a Cluster
... skipping 14 lines ...
Creating MachineDeployment test-u08l9w/test-capa-md87eyfh
Ensuring Machine count matched to 2 
Verifying MachineDeployment test-u08l9w/test-capa-md87eyfh is running..
STEP: Deleting node directly from infra cloud
Fetching the Machines of MachineDeployment test-capa-md87eyfh: 
Terminating EC2 instance with ID: aws:////i-02a780984bcd37e64 ... 
Ensuring machine test-capa-md87eyfh-78f4767f45-25r79's state is failed ... 
panic: test timed out after 4h0m0s

goroutine 5033 [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(0xc0006a6fb8, 0x0, 0x0)
	/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(0xc000590c00)
	/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.044s
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 ...