This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 15 succeeded
Started2020-06-29 18:01
Elapsed29m15s
Revisionmaster
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/238500da-8572-4080-a0ee-78a8cc1a1df1/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/238500da-8572-4080-a0ee-78a8cc1a1df1/targets/test
job-versionv1.19.0-beta.2.517+ec36ff40016e1e
revisionv1.19.0-beta.2.517+ec36ff40016e1e

Test Failures


ClusterLoaderV2 7m59s

error during /home/prow/go/src/k8s.io/windows-testing/gce/load-test.sh cluster-loader2 --nodes=1 --provider=gce --report-dir=/logs/artifacts --enable-prometheus-server=true --testconfig=testing/windows-tests/config.yaml --testoverrides=./testing/windows-tests/windows_override.yaml: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 15 Passed Tests

Error lines from build-log.txt

... skipping 362 lines ...
Trying to find master named 'e2e-7c89e4b617-42aea-master'
Looking for address 'e2e-7c89e4b617-42aea-master-ip'
Using master: e2e-7c89e4b617-42aea-master (external IP: 34.83.245.14; internal IP: (not set))
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-jnks-gci-autoscaling-migs_e2e-7c89e4b617-42aea" set.
User "k8s-jnks-gci-autoscaling-migs_e2e-7c89e4b617-42aea" set.
Context "k8s-jnks-gci-autoscaling-migs_e2e-7c89e4b617-42aea" created.
Switched to context "k8s-jnks-gci-autoscaling-migs_e2e-7c89e4b617-42aea".
... skipping 29 lines ...
Found 3 node(s).
NAME                                           STATUS                     ROLES    AGE     VERSION
e2e-7c89e4b617-42aea-master                    Ready,SchedulingDisabled   <none>   3m43s   v1.19.0-beta.2.517+ec36ff40016e1e
e2e-7c89e4b617-42aea-minion-group-4d2r         Ready                      <none>   3m32s   v1.19.0-beta.2.517+ec36ff40016e1e
e2e-7c89e4b617-42aea-windows-node-group-4n91   Ready                      <none>   26s     v1.19.0-beta.2.517+ec36ff40016e1e
Validate output:
NAME                 STATUS    MESSAGE             ERROR
controller-manager   Healthy   ok                  
scheduler            Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}   
Cluster validation succeeded
Done, listing cluster services:
... skipping 246 lines ...
I0629 18:20:42.530742   15614 cluster.go:70] Name: e2e-7c89e4b617-42aea-master, clusterIP: 10.40.0.2, externalIP: 34.83.245.14, isSchedulable: false
I0629 18:20:42.530751   15614 cluster.go:70] Name: e2e-7c89e4b617-42aea-minion-group-4d2r, clusterIP: 10.40.0.4, externalIP: 34.83.52.136, isSchedulable: true
I0629 18:20:42.530755   15614 cluster.go:70] Name: e2e-7c89e4b617-42aea-windows-node-group-4n91, clusterIP: 10.40.0.3, externalIP: 34.82.22.53, isSchedulable: false
I0629 18:20:42.585513   15614 prometheus.go:381] Using internal master ips ([10.40.0.2]) to monitor master's components
I0629 18:20:42.585556   15614 prometheus.go:156] Setting up prometheus stack
I0629 18:20:42.744171   15614 gce_windows_util.go:81] Installing wmi exporter onto projectId: k8s-jnks-gci-autoscaling-migs, zone: us-west1-b, nodeName: e2e-7c89e4b617-42aea-windows-node-group-4n91 with cmd: Start-Job -Name InstallWmiExporter -ScriptBlock {invoke-webrequest -uri https://github.com/martinlindhe/wmi_exporter/releases/download/v0.11.0/wmi_exporter-0.11.0-amd64.exe -outfile C:\wmi_exporter.exe; New-Service -Name wmi_exporter -BinaryPathName 'C:\wmi_exporter.exe --collectors.enabled="process,cs" --telemetry.addr=":5000"'; Start-Service wmi_exporter}; Wait-Job -Timeout 300 -Name InstallWmiExporter
F0629 18:20:45.156743   15614 clusterloader.go:282] Error while setting up prometheus stack: exit status 255
2020/06/29 18:20:45 process.go:155: Step '/home/prow/go/src/k8s.io/windows-testing/gce/load-test.sh cluster-loader2 --nodes=1 --provider=gce --report-dir=/logs/artifacts --enable-prometheus-server=true --testconfig=testing/windows-tests/config.yaml --testoverrides=./testing/windows-tests/windows_override.yaml' finished in 7m59.803586555s
2020/06/29 18:20:45 e2e.go:534: Dumping logs locally to: /logs/artifacts
2020/06/29 18:20:45 process.go:153: Running: ./cluster/log-dump/log-dump.sh /logs/artifacts
Checking for custom logdump instances, if any
Sourcing kube-util.sh
Detecting project
... skipping 10 lines ...
Specify --start=45195 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 locally to '/logs/artifacts'
Detecting nodes in the cluster
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
Changing logfiles to be world-readable for download

Specify --start=181530 in the next get-serial-port-output invocation to get only the new output starting from here.
Copying 'kube-proxy.log fluentd.log node-problem-detector.log kubelet.cov  startupscript.log' from e2e-7c89e4b617-42aea-minion-group-4d2r

Specify --start=47137 in the next get-serial-port-output invocation to get only the new output starting from here.
scp: /var/log/fluentd.log*: No such file or directory
scp: /var/log/node-problem-detector.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].
INSTANCE_GROUPS=e2e-7c89e4b617-42aea-minion-group
NODE_NAMES=e2e-7c89e4b617-42aea-minion-group-4d2r
Failures for e2e-7c89e4b617-42aea-minion-group (if any):
Failures for e2e-7c89e4b617-42aea-windows-node-group (if any):
2020/06/29 18:23:23 process.go:155: Step './cluster/log-dump/log-dump.sh /logs/artifacts' finished in 2m38.208223693s
2020/06/29 18:23:23 e2e.go:456: Listing resources...
... skipping 73 lines ...
Listed 0 items.
Listed 0 items.
2020/06/29 18:30:54 process.go:155: Step './cluster/gce/list-resources.sh' finished in 15.677708153s
2020/06/29 18:30:54 process.go:153: Running: diff -sw -U0 -F^\[.*\]$ /logs/artifacts/gcp-resources-before.txt /logs/artifacts/gcp-resources-after.txt
2020/06/29 18:30:54 process.go:155: Step 'diff -sw -U0 -F^\[.*\]$ /logs/artifacts/gcp-resources-before.txt /logs/artifacts/gcp-resources-after.txt' finished in 2.521486ms
2020/06/29 18:30:54 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/06/29 18:30:54 main.go:312: Something went wrong: encountered 1 errors: [error during /home/prow/go/src/k8s.io/windows-testing/gce/load-test.sh cluster-loader2 --nodes=1 --provider=gce --report-dir=/logs/artifacts --enable-prometheus-server=true --testconfig=testing/windows-tests/config.yaml --testoverrides=./testing/windows-tests/windows_override.yaml: exit status 1]
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 720, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 570, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...