This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 19 succeeded
Started2022-11-12 05:43
Elapsed29m46s
Revisionmaster
job-versionv1.26.0-beta.0.61+bd878fe5b31e37
kubetest-versionv20221109-489d560851
revisionv1.26.0-beta.0.61+bd878fe5b31e37

Test Failures


kubetest ClusterLoaderV2 3m0s

error during /home/prow/go/src/k8s.io/perf-tests/run-e2e.sh cluster-loader2 --nodes=600 --provider=kubemark --report-dir=/logs/artifacts --testconfig=testing/density/high-density-config.yaml --testoverrides=./testing/experiments/use_simple_latency_query.yaml --testoverrides=./testing/overrides/600_nodes_high_density.yaml: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 19 Passed Tests

Error lines from build-log.txt

... skipping 350 lines ...
NAME                     ZONE        MACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  EXTERNAL_IP     STATUS
kubemark-100pods-master  us-east1-b  n1-standard-2               10.40.0.3    35.190.185.235  RUNNING
Setting kubemark-100pods-master's aliases to 'pods-default:10.64.0.0/24;10.40.0.2/32' (added 10.40.0.2)
Updating network interface [nic0] of instance [kubemark-100pods-master]...
.........done.
Updated [https://www.googleapis.com/compute/v1/projects/k8s-infra-e2e-boskos-scale-28/zones/us-east1-b/instances/kubemark-100pods-master].
Failed to execute 'sudo /bin/bash /home/kubernetes/bin/kube-master-internal-route.sh' on kubemark-100pods-master despite 5 attempts
Last attempt failed with: /bin/bash: /home/kubernetes/bin/kube-master-internal-route.sh: No such file or directory
Creating nodes.
/home/prow/go/src/k8s.io/kubernetes/kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 1551: WINDOWS_CONTAINER_RUNTIME: unbound variable
/home/prow/go/src/k8s.io/kubernetes/kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 1551: WINDOWS_ENABLE_HYPERV: unbound variable
/home/prow/go/src/k8s.io/kubernetes/kubernetes/cluster/../cluster/../cluster/gce/util.sh: line 1551: ENABLE_AUTH_PROVIDER_GCP: unbound variable
Using subnet kubemark-100pods-custom-subnet
Attempt 1 to create kubemark-100pods-minion-template
... skipping 18 lines ...
Looking for address 'kubemark-100pods-master-ip'
Looking for address 'kubemark-100pods-master-internal-ip'
Using master: kubemark-100pods-master (external IP: 35.190.185.235; internal IP: 10.40.0.2)
Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

Kubernetes cluster created.
Cluster "k8s-infra-e2e-boskos-scale-28_kubemark-100pods" set.
User "k8s-infra-e2e-boskos-scale-28_kubemark-100pods" set.
Context "k8s-infra-e2e-boskos-scale-28_kubemark-100pods" created.
Switched to context "k8s-infra-e2e-boskos-scale-28_kubemark-100pods".
... skipping 65 lines ...
kubemark-100pods-minion-group-r9p2   Ready                         <none>   48s   v1.26.0-beta.0.61+bd878fe5b31e37
kubemark-100pods-minion-group-rhfv   Ready                         <none>   47s   v1.26.0-beta.0.61+bd878fe5b31e37
kubemark-100pods-minion-group-zf13   Ready                         <none>   47s   v1.26.0-beta.0.61+bd878fe5b31e37
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
etcd-1               Healthy   {"health":"true","reason":""}   
etcd-0               Healthy   {"health":"true","reason":""}   
scheduler            Healthy   ok                              
controller-manager   Healthy   ok                              
Cluster validation encountered some problems, but cluster should be in working order
...ignoring non-fatal errors in validate-cluster
Done, listing cluster services:

Kubernetes control plane is running at https://35.190.185.235
GLBCDefaultBackend is running at https://35.190.185.235/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://35.190.185.235/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://35.190.185.235/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
... skipping 225 lines ...
Looking for address 'kubemark-100pods-kubemark-master-ip'
Looking for address 'kubemark-100pods-kubemark-master-internal-ip'
Using master: kubemark-100pods-kubemark-master (external IP: 34.75.28.56; internal IP: 10.40.0.13)
Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

Kubernetes cluster created.
Cluster "k8s-infra-e2e-boskos-scale-28_kubemark-100pods-kubemark" set.
User "k8s-infra-e2e-boskos-scale-28_kubemark-100pods-kubemark" set.
Context "k8s-infra-e2e-boskos-scale-28_kubemark-100pods-kubemark" created.
Switched to context "k8s-infra-e2e-boskos-scale-28_kubemark-100pods-kubemark".
... skipping 20 lines ...
Found 1 node(s).
NAME                               STATUS                     ROLES    AGE   VERSION
kubemark-100pods-kubemark-master   Ready,SchedulingDisabled   <none>   18s   v1.26.0-beta.0.61+bd878fe5b31e37
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
etcd-1               Healthy   {"health":"true","reason":""}   
etcd-0               Healthy   {"health":"true","reason":""}   
controller-manager   Healthy   ok                              
scheduler            Healthy   ok                              
Cluster validation succeeded
Done, listing cluster services:
... skipping 849 lines ...
I1112 05:59:34.519802   57232 cluster.go:86] Name: hollow-node-zv2wx, clusterIP: 10.64.6.23, externalIP: , isSchedulable: false
I1112 05:59:34.519808   57232 cluster.go:86] Name: hollow-node-zv6f6, clusterIP: 10.64.1.42, externalIP: , isSchedulable: false
I1112 05:59:34.519814   57232 cluster.go:86] Name: hollow-node-zvp6p, clusterIP: 10.64.5.65, externalIP: , isSchedulable: false
I1112 05:59:34.519820   57232 cluster.go:86] Name: hollow-node-zvt25, clusterIP: 10.64.8.15, externalIP: , isSchedulable: false
I1112 05:59:34.519827   57232 cluster.go:86] Name: hollow-node-zvvdz, clusterIP: 10.64.4.31, externalIP: , isSchedulable: false
I1112 05:59:34.519834   57232 cluster.go:86] Name: kubemark-100pods-kubemark-master, clusterIP: 10.40.0.14, externalIP: 34.75.28.56, isSchedulable: false
F1112 05:59:34.729701   57232 clusterloader.go:303] Cluster verification error: no schedulable nodes in the cluster
2022/11/12 05:59:34 process.go:155: Step '/home/prow/go/src/k8s.io/perf-tests/run-e2e.sh cluster-loader2 --nodes=600 --provider=kubemark --report-dir=/logs/artifacts --testconfig=testing/density/high-density-config.yaml --testoverrides=./testing/experiments/use_simple_latency_query.yaml --testoverrides=./testing/overrides/600_nodes_high_density.yaml' finished in 3m0.592899952s
2022/11/12 05:59:34 e2e.go:781: Dumping logs for kubemark master to GCS directly at path: gs://k8s-infra-scalability-tests-logs/ci-kubernetes-kubemark-high-density-100-gce/1591305195407544320
2022/11/12 05:59:34 process.go:153: Running: /workspace/log-dump.sh /logs/artifacts gs://k8s-infra-scalability-tests-logs/ci-kubernetes-kubemark-high-density-100-gce/1591305195407544320
Checking for custom logdump instances, if any
Using gce provider, skipping check for LOG_DUMP_SSH_KEY and LOG_DUMP_SSH_USER
Project: k8s-infra-e2e-boskos-scale-28
... skipping 8 lines ...
scp: /var/log/glbc.log*: No such file or directory
scp: /var/log/cluster-autoscaler.log*: No such file or directory
scp: /var/log/konnectivity-server.log*: No such file or directory
scp: /var/log/fluentd.log*: No such file or directory
scp: /var/log/kubelet.cov*: No such file or directory
scp: /var/log/startupscript.log*: No such file or directory
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
Skipping dumping of node logs
Detecting nodes in the cluster
INSTANCE_GROUPS=kubemark-100pods-minion-group
NODE_NAMES=kubemark-100pods-minion-group-0bq4 kubemark-100pods-minion-group-0psj kubemark-100pods-minion-group-3pps kubemark-100pods-minion-group-4jxv kubemark-100pods-minion-group-bks5 kubemark-100pods-minion-group-j3f8 kubemark-100pods-minion-group-r9p2 kubemark-100pods-minion-group-rhfv kubemark-100pods-minion-group-zf13
WINDOWS_INSTANCE_GROUPS=
WINDOWS_NODE_NAMES=
... skipping 107 lines ...
Specify --start=71859 in the next get-serial-port-output invocation to get only the new output starting from here.
scp: /var/log/cluster-autoscaler.log*: No such file or directory
scp: /var/log/konnectivity-server.log*: No such file or directory
scp: /var/log/fluentd.log*: No such file or directory
scp: /var/log/kubelet.cov*: No such file or directory
scp: /var/log/startupscript.log*: No such file or directory
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
Dumping logs from nodes to GCS directly at 'gs://k8s-infra-scalability-tests-logs/ci-kubernetes-kubemark-high-density-100-gce/1591305195407544320' using logexporter
namespace/logexporter created
secret/google-service-account created
daemonset.apps/logexporter created
Listing marker files (gs://k8s-infra-scalability-tests-logs/ci-kubernetes-kubemark-high-density-100-gce/1591305195407544320/logexported-nodes-registry) for successful nodes...
CommandException: One or more URLs matched no objects.
... skipping 126 lines ...
W1112 06:12:54.268002   62083 loader.go:222] Config not found: /home/prow/go/src/k8s.io/kubernetes/kubernetes/test/kubemark/resources/kubeconfig.kubemark
Property "contexts.k8s-infra-e2e-boskos-scale-28_kubemark-100pods" unset.
Cleared config for k8s-infra-e2e-boskos-scale-28_kubemark-100pods from /home/prow/go/src/k8s.io/kubernetes/kubernetes/test/kubemark/resources/kubeconfig.kubemark
Done
2022/11/12 06:12:54 process.go:155: Step './hack/e2e-internal/e2e-down.sh' finished in 6m10.634814813s
2022/11/12 06:12:54 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2022/11/12 06:12:54 main.go:328: Something went wrong: encountered 1 errors: [error during /home/prow/go/src/k8s.io/perf-tests/run-e2e.sh cluster-loader2 --nodes=600 --provider=kubemark --report-dir=/logs/artifacts --testconfig=testing/density/high-density-config.yaml --testoverrides=./testing/experiments/use_simple_latency_query.yaml --testoverrides=./testing/overrides/600_nodes_high_density.yaml: exit status 1]
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 723, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 569, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 15 lines ...