This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 19 succeeded
Started2022-11-13 05:44
Elapsed30m29s
Revisionmaster
job-versionv1.26.0-beta.0.65+8e48df13531802
kubetest-versionv20221109-489d560851
revisionv1.26.0-beta.0.65+8e48df13531802

Test Failures


kubetest ClusterLoaderV2 2m50s

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    34.139.244.252  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-24/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 22 lines ...
Looking for address 'kubemark-100pods-master-ip'
Looking for address 'kubemark-100pods-master-internal-ip'
Using master: kubemark-100pods-master (external IP: 34.139.244.252; 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-24_kubemark-100pods" set.
User "k8s-infra-e2e-boskos-scale-24_kubemark-100pods" set.
Context "k8s-infra-e2e-boskos-scale-24_kubemark-100pods" created.
Switched to context "k8s-infra-e2e-boskos-scale-24_kubemark-100pods".
... skipping 52 lines ...
kubemark-100pods-minion-group-p3bp   Ready                         <none>   71s    v1.26.0-beta.0.65+8e48df13531802
kubemark-100pods-minion-group-q772   Ready                         <none>   40s    v1.26.0-beta.0.65+8e48df13531802
kubemark-100pods-minion-group-rl84   Ready                         <none>   74s    v1.26.0-beta.0.65+8e48df13531802
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":""}   
scheduler            Healthy   ok                              
etcd-0               Healthy   {"health":"true","reason":""}   
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://34.139.244.252
GLBCDefaultBackend is running at https://34.139.244.252/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
CoreDNS is running at https://34.139.244.252/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://34.139.244.252/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.23.233.10; 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-24_kubemark-100pods-kubemark" set.
User "k8s-infra-e2e-boskos-scale-24_kubemark-100pods-kubemark" set.
Context "k8s-infra-e2e-boskos-scale-24_kubemark-100pods-kubemark" created.
Switched to context "k8s-infra-e2e-boskos-scale-24_kubemark-100pods-kubemark".
... skipping 20 lines ...
Found 1 node(s).
NAME                               STATUS                     ROLES    AGE   VERSION
kubemark-100pods-kubemark-master   Ready,SchedulingDisabled   <none>   19s   v1.26.0-beta.0.65+8e48df13531802
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 succeeded
Done, listing cluster services:
... skipping 849 lines ...
I1113 06:00:23.839972   57009 cluster.go:86] Name: hollow-node-zwcbj, clusterIP: 10.64.7.62, externalIP: , isSchedulable: false
I1113 06:00:23.839977   57009 cluster.go:86] Name: hollow-node-zwp7t, clusterIP: 10.64.1.9, externalIP: , isSchedulable: false
I1113 06:00:23.839983   57009 cluster.go:86] Name: hollow-node-zwrbn, clusterIP: 10.64.7.60, externalIP: , isSchedulable: false
I1113 06:00:23.839991   57009 cluster.go:86] Name: hollow-node-zwspj, clusterIP: 10.64.1.23, externalIP: , isSchedulable: false
I1113 06:00:23.839998   57009 cluster.go:86] Name: hollow-node-zzfqk, clusterIP: 10.64.5.37, externalIP: , isSchedulable: false
I1113 06:00:23.840005   57009 cluster.go:86] Name: kubemark-100pods-kubemark-master, clusterIP: 10.40.0.14, externalIP: 34.23.233.10, isSchedulable: false
F1113 06:00:24.052290   57009 clusterloader.go:303] Cluster verification error: no schedulable nodes in the cluster
2022/11/13 06:00:24 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 2m50.717936445s
2022/11/13 06:00:24 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/1591667587077378048
2022/11/13 06:00:24 process.go:153: Running: /workspace/log-dump.sh /logs/artifacts gs://k8s-infra-scalability-tests-logs/ci-kubernetes-kubemark-high-density-100-gce/1591667587077378048
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-24
... 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-5tjt kubemark-100pods-minion-group-7mgm kubemark-100pods-minion-group-fmbp kubemark-100pods-minion-group-j1zr kubemark-100pods-minion-group-kwbt kubemark-100pods-minion-group-n315 kubemark-100pods-minion-group-p3bp kubemark-100pods-minion-group-q772 kubemark-100pods-minion-group-rl84
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/1591667587077378048' 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/1591667587077378048/logexported-nodes-registry) for successful nodes...
CommandException: One or more URLs matched no objects.
... skipping 126 lines ...
W1113 06:14:11.662832   61869 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-24_kubemark-100pods" unset.
Cleared config for k8s-infra-e2e-boskos-scale-24_kubemark-100pods from /home/prow/go/src/k8s.io/kubernetes/kubernetes/test/kubemark/resources/kubeconfig.kubemark
Done
2022/11/13 06:14:11 process.go:155: Step './hack/e2e-internal/e2e-down.sh' finished in 6m38.556132229s
2022/11/13 06:14:11 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2022/11/13 06:14:11 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 ...