This job view page is being replaced by Spyglass soon. Check out the new job view.
Tests 1 failed / 8 succeeded
Started2022-08-12 14:35

Test Failures

kubetest Up 53s

error during ./hack/e2e-internal/ exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid

Show 8 Passed Tests

Error lines from build-log.txt

... skipping 282 lines ...
NAME                                REGION       NETWORK               RANGE         STACK_TYPE  IPV6_ACCESS_TYPE  INTERNAL_IPV6_PREFIX  EXTERNAL_IPV6_PREFIX
e2e-123350959e-5888a-custom-subnet  us-central1  e2e-123350959e-5888a  IPV4_ONLY
Created subnetwork e2e-123350959e-5888a-custom-subnet
Using subnet e2e-123350959e-5888a-custom-subnet
Starting master and configuring firewalls
Configuring firewall for apiserver konnectivity server
ERROR: (gcloud.compute.disks.create) Could not fetch resource:
 - The zone 'projects/k8s-infra-e2e-boskos-103/zones/us-central1-b' does not have enough resources available to fulfill the request.  Try a different zone, or try again later.

2022/08/12 14:37:45 process.go:155: Step './hack/e2e-internal/' finished in 53.873295943s
2022/08/12 14:37:45 e2e.go:571: Dumping logs from nodes to GCS directly at path: gs://sig-scalability-logs/ci-kubernetes-e2e-gce-node-containerd-throughput/1558099357847261184
2022/08/12 14:37:45 process.go:153: Running: ./cluster/log-dump/ /logs/artifacts gs://sig-scalability-logs/ci-kubernetes-e2e-gce-node-containerd-throughput/1558099357847261184
Checking for custom logdump instances, if any
... skipping 7 lines ...
Project: k8s-infra-e2e-boskos-103
Network Project: k8s-infra-e2e-boskos-103
Zone: us-central1-b
Dumping logs from master locally to '/logs/artifacts'
Trying to find master named 'e2e-123350959e-5888a-master'
Looking for address 'e2e-123350959e-5888a-master-ip'
ERROR: (gcloud.compute.addresses.describe) Could not fetch resource:
 - The resource 'projects/k8s-infra-e2e-boskos-103/regions/us-central1/addresses/e2e-123350959e-5888a-master-ip' was not found

Could not detect Kubernetes master node.  Make sure you've launched a cluster with ''
Master not detected. Is the cluster up?
Dumping logs from nodes to GCS directly at 'gs://sig-scalability-logs/ci-kubernetes-e2e-gce-node-containerd-throughput/1558099357847261184' using logexporter
Detecting nodes in the cluster
... skipping 60 lines ...
W0812 14:39:07.221621    5708 loader.go:223] Config not found: /workspace/.kube/config
Property "contexts.k8s-infra-e2e-boskos-103_e2e-123350959e-5888a" unset.
Cleared config for k8s-infra-e2e-boskos-103_e2e-123350959e-5888a from /workspace/.kube/config
2022/08/12 14:39:07 process.go:155: Step './hack/e2e-internal/' finished in 1m15.460757768s
2022/08/12 14:39:07 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2022/08/12 14:39:07 main.go:331: Something went wrong: starting e2e cluster: error during ./hack/e2e-internal/ exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/", line 723, in <module>
  File "/workspace/scenarios/", line 569, in main
  File "/workspace/scenarios/", line 228, in start
... skipping 9 lines ...