This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandrewsykim: Add cluster-role storage-version-migration-migrator instead of using cluster-admin
ResultFAILURE
Tests 1 failed / 17 succeeded
Started2023-03-01 19:07
Elapsed22m16s
Revision956b97f2c4cd71ec5b24c450ce45e309aa868276
Refs 112
job-versionv1.27.0-alpha.2.380+44bedc2a46f740
kubetest-versionv20230207-192d5afee3
revisionv1.27.0-alpha.2.380+44bedc2a46f740

Test Failures


kubetest 2m28s

error during ../test/e2e/test-fully-automated.sh --skip=\[Disruptive\]: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 17 Passed Tests

Error lines from build-log.txt

... skipping 355 lines ...
Trying to find master named 'bootstrap-e2e-master'
Looking for address 'bootstrap-e2e-master-ip'
Using master: bootstrap-e2e-master (external IP: 35.192.34.60; 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 "kube-gce-upg-lat-master_bootstrap-e2e" set.
User "kube-gce-upg-lat-master_bootstrap-e2e" set.
Context "kube-gce-upg-lat-master_bootstrap-e2e" created.
Switched to context "kube-gce-upg-lat-master_bootstrap-e2e".
... skipping 20 lines ...
NAME                              STATUS                     ROLES    AGE   VERSION
bootstrap-e2e-master              Ready,SchedulingDisabled   <none>   11s   v1.27.0-alpha.2.380+44bedc2a46f740
bootstrap-e2e-minion-group-zjgv   Ready                      <none>   9s    v1.27.0-alpha.2.380+44bedc2a46f740
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 207 lines ...
    	If set, ginkgo will emit node output to files when running in parallel.
  -ginkgo.dryRun
    	If set, ginkgo will walk the test hierarchy without actually running anything.  Best paired with -v.
  -ginkgo.failFast
    	If set, ginkgo will stop running a test suite after a failure occurs.
  -ginkgo.failOnPending
    	If set, ginkgo will mark the test suite as failed if any specs are pending.
  -ginkgo.flakeAttempts int
    	Make up to this many attempts to run each spec. Please note that if any of the attempts succeed, the suite will not be failed. But any failures will still be recorded. (default 1)
  -ginkgo.focus string
    	If set, ginkgo will only run specs that match this regular expression.
  -ginkgo.noColor
    	If set, suppress color output in default reporter.
  -ginkgo.noisyPendings
    	If set, default reporter will shout about pending tests. (default true)
... skipping 95 lines ...
    	write an execution trace to file
  -test.v
    	verbose: print additional output

Ginkgo ran 1 suite in 21.555211ms

Test Suite Failed
===== migrator logs
Error from server (NotFound): deployments.apps "migrator" not found
===== trigger logs
Error from server (NotFound): deployments.apps "trigger" not found
===== storageversionmigrations
error: the server doesn't have a resource type "storageversionmigrations"
2023/03/01 19:16:43 process.go:155: Step '../test/e2e/test-fully-automated.sh --skip=\[Disruptive\]' finished in 2m28.370909226s
2023/03/01 19:16:43 e2e.go:572: Dumping logs locally to: /logs/artifacts
2023/03/01 19:16:43 process.go:153: Running: ./cluster/log-dump/log-dump.sh /logs/artifacts
Checking for custom logdump instances, if any
----------------------------------------------------------------------------------------------------
k/k version of the log-dump.sh script is deprecated!
... skipping 15 lines ...
Specify --start=70825 in the next get-serial-port-output invocation to get only the new output starting from here.
scp: /var/log/cloud-controller-manager.log*: No such file or directory
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
Changing logfiles to be world-readable for download
Copying 'kube-proxy.log containers/konnectivity-agent-*.log fluentd.log node-problem-detector.log kubelet.cov startupscript.log' from bootstrap-e2e-minion-group-zjgv

Specify --start=115880 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=bootstrap-e2e-minion-group
NODE_NAMES=bootstrap-e2e-minion-group-zjgv
Failures for bootstrap-e2e-minion-group (if any):
2023/03/01 19:19:24 process.go:155: Step './cluster/log-dump/log-dump.sh /logs/artifacts' finished in 2m41.172252292s
2023/03/01 19:19:24 e2e.go:476: Listing resources...
2023/03/01 19:19:24 process.go:153: Running: ./cluster/gce/list-resources.sh
... skipping 75 lines ...
Listed 0 items.
Listed 0 items.
2023/03/01 19:28:58 process.go:155: Step './cluster/gce/list-resources.sh' finished in 33.203604202s
2023/03/01 19:28:58 process.go:153: Running: diff -sw -U0 -F^\[.*\]$ /logs/artifacts/gcp-resources-before.txt /logs/artifacts/gcp-resources-after.txt
2023/03/01 19:28:58 process.go:155: Step 'diff -sw -U0 -F^\[.*\]$ /logs/artifacts/gcp-resources-before.txt /logs/artifacts/gcp-resources-after.txt' finished in 4.047701ms
2023/03/01 19:28:58 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2023/03/01 19:28:58 main.go:328: Something went wrong: encountered 1 errors: [error during ../test/e2e/test-fully-automated.sh --skip=\[Disruptive\]: 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 ...