This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 8 succeeded
Started2022-09-19 18:15
Elapsed1h10m
Revisionmaster
job-versionv1.24.6-rc.0.5+2e1922da25d997
kubetest-versionv20220916-c3af09ab20
revisionv1.24.6-rc.0.5+2e1922da25d997

Test Failures


kubetest Up 58m36s

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

Filter through log files


Show 8 Passed Tests

Error lines from build-log.txt

... skipping 501 lines ...
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
ERROR: (gcloud.compute.instance-groups.managed.wait-until) Timeout while waiting for group to become stable.
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
Waiting for group to become stable, current operations: creating: 3
... skipping 49 lines ...
Trying to find master named 'e2e-d6f7ae9eae-03678-master'
Looking for address 'e2e-d6f7ae9eae-03678-master-ip'
Using master: e2e-d6f7ae9eae-03678-master (external IP: 34.82.23.154; 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 "e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678" set.
User "e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678" set.
Context "e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678" created.
Switched to context "e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678".
... skipping 134 lines ...

Specify --start=53876 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/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.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found


Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].

Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found


Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].

Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found


Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found


Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].

Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
Changing logfiles to be world-readable for download
ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

Copying 'kube-proxy.log containers/konnectivity-agent-*.log fluentd.log node-problem-detector.log kubelet.cov startupscript.log' from e2e-d6f7ae9eae-03678-minion-group-2475

Specify --start=106475 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].

Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].

Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.ssh) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

Changing logfiles to be world-readable for download

Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found


Recommendation: To check for possible causes of SSH connectivity issues and get
recommendations, rerun the ssh command with the --troubleshoot option.

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot

Or, to investigate an IAP tunneling issue:

gcloud compute ssh e2e-d6f7ae9eae-03678-minion-group-5d6n --project=e2e-gce-gci-ci-serial --zone=us-west1-b --troubleshoot --tunnel-through-iap

ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
Copying 'kube-proxy.log containers/konnectivity-agent-*.log fluentd.log node-problem-detector.log kubelet.cov startupscript.log' from e2e-d6f7ae9eae-03678-minion-group-5d6n

Specify --start=106046 in the next get-serial-port-output invocation to get only the new output starting from here.
scp: /var/log/containers/konnectivity-agent-jchrr_kube-system_konnectivity-agent-34c3413f3294771136d2f12640426841d9686c59ff01f1b9cc8266288b000bd5.log: Permission denied
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].
ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found

ERROR: (gcloud.compute.scp) Could not fetch resource:
 - The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found

ERROR: (gcloud.compute.instances.get-serial-port-output) Could not fetch serial port output: The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-sgz4' was not found
ERROR: (gcloud.compute.instances.get-serial-port-output) Could not fetch serial port output: The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-64qc' was not found
ERROR: (gcloud.compute.instances.get-serial-port-output) Could not fetch serial port output: The resource 'projects/e2e-gce-gci-ci-serial/zones/us-west1-b/instances/e2e-d6f7ae9eae-03678-windows-node-group-8t2g' was not found
Detecting nodes in the cluster
INSTANCE_GROUPS=e2e-d6f7ae9eae-03678-minion-group
NODE_NAMES=e2e-d6f7ae9eae-03678-minion-group-2475 e2e-d6f7ae9eae-03678-minion-group-5d6n
WINDOWS_INSTANCE_GROUPS=e2e-d6f7ae9eae-03678-windows-node-group
WINDOWS_NODE_NAMES=e2e-d6f7ae9eae-03678-windows-node-group-64qc e2e-d6f7ae9eae-03678-windows-node-group-8t2g e2e-d6f7ae9eae-03678-windows-node-group-sgz4
Detecting nodes in the cluster
... skipping 56 lines ...
Property "users.e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678-basic-auth" unset.
Property "contexts.e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678" unset.
Cleared config for e2e-gce-gci-ci-serial_e2e-d6f7ae9eae-03678 from /workspace/.kube/config
Done
2022/09/19 19:25:42 process.go:155: Step './hack/e2e-internal/e2e-down.sh' finished in 6m12.303769418s
2022/09/19 19:25:42 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2022/09/19 19:25:42 main.go:331: Something went wrong: starting e2e cluster: error during ./hack/e2e-internal/e2e-up.sh: 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 9 lines ...