This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-02-18 13:32
Elapsed6m27s
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/d4c9a1e1-b867-4b09-a030-a9fe459afe19/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/d4c9a1e1-b867-4b09-a030-a9fe459afe19/targets/test

No Test Failures!


Error lines from build-log.txt

... skipping 774 lines ...
vsphere_virtual_machine.controller.0: Still creating... (5m20s elapsed)
vsphere_virtual_machine.worker.1: Still creating... (5m20s elapsed)
vsphere_virtual_machine.controller.1: Still creating... (5m30s elapsed)
vsphere_virtual_machine.controller.0: Still creating... (5m30s elapsed)
vsphere_virtual_machine.controller.1: Still creating... (5m40s elapsed)

Error: Error applying plan:

5 error(s) occurred:

* vsphere_virtual_machine.worker[2]: 1 error(s) occurred:

* vsphere_virtual_machine.worker.2: timeout waiting for an available IP address
* vsphere_virtual_machine.controller[1]: 1 error(s) occurred:

* vsphere_virtual_machine.controller.1: timeout waiting for an available IP address
* vsphere_virtual_machine.worker[0]: 1 error(s) occurred:

* vsphere_virtual_machine.worker.0: error powering on virtual machine: The total number of virtual CPUs present or requested in virtual machines' configuration has exceeded the limit on the host: 1,152.
* vsphere_virtual_machine.worker[1]: 1 error(s) occurred:

* vsphere_virtual_machine.worker.1: timeout waiting for an available IP address
* vsphere_virtual_machine.controller[0]: 1 error(s) occurred:

* vsphere_virtual_machine.controller.0: timeout waiting for an available IP address

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.


ERROR [1] - failed to turn up cluster

# deleting AWS load balancer(s)
aws elbv2 delete-listener --listener-arn arn:aws:elasticloadbalancing:us-west-2:571501312763:listener/net/sk8lb-fe2958d/59522d0ce77cea27/1ba24e3a649c3fdf
aws elbv2 delete-listener --listener-arn arn:aws:elasticloadbalancing:us-west-2:571501312763:listener/net/sk8lb-fe2958d/59522d0ce77cea27/cf3f08b48d8ed290
aws elbv2 delete-load-balancer --load-balancer-arn arn:aws:elasticloadbalancing:us-west-2:571501312763:loadbalancer/net/sk8lb-fe2958d/59522d0ce77cea27

... skipping 18 lines ...
govc pool.destroy '//SDDC-Datacenter/host/Cluster-1/Resources/Compute-ResourcePool/sk8e2e/prow-22feaf8.fe2958d'

# deleting Terraform state
rm -fr data/prow-22feaf8

So long and thanks for all the fish.
make: *** [Makefile:229: conformance-test] Error 1