This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-01-24 20:05
Elapsed28m23s
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/7ae15bd3-df9c-4d68-8936-07c473f1f8aa/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/7ae15bd3-df9c-4d68-8936-07c473f1f8aa/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 890 lines ...
STEP: creating control plane resource 1: Machine
STEP: waiting for the control plane to be initialized
STEP: creating a core MachineDeployment resource
STEP: creating a BootstrapConfigTemplate resource
STEP: creating an InfrastructureMachineTemplate resource
STEP: waiting for the workload nodes to exist
E0124 20:13:35.353680   11560 request.go:879] Unexpected error when reading response body: read tcp 10.8.0.7:50308->192.168.5.6:6443: read: connection reset by peer
E0124 20:13:35.353794   11560 request.go:879] Unexpected error when reading response body: read tcp 10.8.0.7:50308->192.168.5.6:6443: read: connection reset by peer
E0124 20:13:35.353814   11560 request.go:879] Unexpected error when reading response body: read tcp 10.8.0.7:50308->192.168.5.6:6443: read: connection reset by peer
E0124 20:13:35.353724   11560 request.go:879] Unexpected error when reading response body: read tcp 10.8.0.7:50308->192.168.5.6:6443: read: connection reset by peer
E0124 20:13:35.353773   11560 request.go:879] Unexpected error when reading response body: read tcp 10.8.0.7:50308->192.168.5.6:6443: read: connection reset by peer
STEP: cleaning up e2e resources
STEP: deleting cluster test-56d6538
STEP: ensuring all CAPI artifacts have been deleted
STEP: asserting all VSphereVM resources related to this test are eventually removed
STEP: asserting all VSphereMachine resources related to this test are eventually removed
STEP: asserting all VSphereCluster resources related to this test are eventually removed
... skipping 51 lines ...
------------------------------
STEP: tearing down the management cluster


Summarizing 1 Failure:

[Fail] CAPV Cluster Creation [AfterEach] Two-node control plane with one worker node should create a two-node control plane with one worker node 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test/framework@v0.0.0-20200119160935-412f6b3f1339/control_plane.go:210

Ran 2 of 2 Specs in 1509.791 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestCAPV (1509.79s)
FAIL

Ginkgo ran 1 suite in 25m54.866033884s
Test Suite Failed

real	25m54.874s
user	3m23.897s
sys	1m3.290s
make: *** [Makefile:75: e2e] Error 1
vpn
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
[Barnacle] 2020/01/24 20:34:19 Cleaning up Docker data root...
... skipping 19 lines ...