Recent runs || View in Spyglass
PR | andrewsykim: Add cluster-role storage-version-migration-migrator instead of using cluster-admin |
Result | FAILURE |
Tests | 1 failed / 17 succeeded |
Started | |
Elapsed | 18m42s |
Revision | 956b97f2c4cd71ec5b24c450ce45e309aa868276 |
Refs |
112 |
job-version | v1.27.0-alpha.3.394+3ed9c61864864e |
kubetest-version | v20230222-b5208facd4 |
revision | v1.27.0-alpha.3.394+3ed9c61864864e |
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
kubetest Check APIReachability
kubetest Deferred TearDown
kubetest DumpClusterLogs
kubetest Extract
kubetest GetDeployer
kubetest Prepare
kubetest TearDown
kubetest TearDown Previous
kubetest Timeout
kubetest Up
kubetest diffResources
kubetest list nodes
kubetest listResources After
kubetest listResources Before
kubetest listResources Down
kubetest listResources Up
kubetest test setup
... skipping 356 lines ... Trying to find master named 'bootstrap-e2e-master' Looking for address 'bootstrap-e2e-master-ip' Using master: bootstrap-e2e-master (external IP: 34.30.234.8; 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-boskos-gce-project-07_bootstrap-e2e" set. User "k8s-boskos-gce-project-07_bootstrap-e2e" set. Context "k8s-boskos-gce-project-07_bootstrap-e2e" created. Switched to context "k8s-boskos-gce-project-07_bootstrap-e2e". ... skipping 20 lines ... NAME STATUS ROLES AGE VERSION bootstrap-e2e-master Ready,SchedulingDisabled <none> 7s v1.27.0-alpha.3.394+3ed9c61864864e bootstrap-e2e-minion-group-4j9q Ready <none> 9s v1.27.0-alpha.3.394+3ed9c61864864e 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 [0;32mCluster validation succeeded[0m Done, listing cluster services: ... skipping 208 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 15.714769ms 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/11 03:17:28 process.go:155: Step '../test/e2e/test-fully-automated.sh --skip=\[Disruptive\]' finished in 2m0.75687986s 2023/03/11 03:17:28 e2e.go:572: Dumping logs locally to: /logs/artifacts 2023/03/11 03:17:28 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=70112 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-4j9q Specify --start=115292 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-4j9q Failures for bootstrap-e2e-minion-group (if any): 2023/03/11 03:19:25 process.go:155: Step './cluster/log-dump/log-dump.sh /logs/artifacts' finished in 1m57.690393526s 2023/03/11 03:19:25 e2e.go:476: Listing resources... 2023/03/11 03:19:25 process.go:153: Running: ./cluster/gce/list-resources.sh ... skipping 75 lines ... Listed 0 items. Listed 0 items. 2023/03/11 03:27:44 process.go:155: Step './cluster/gce/list-resources.sh' finished in 16.082054283s 2023/03/11 03:27:44 process.go:153: Running: diff -sw -U0 -F^\[.*\]$ /logs/artifacts/gcp-resources-before.txt /logs/artifacts/gcp-resources-after.txt 2023/03/11 03:27:44 process.go:155: Step 'diff -sw -U0 -F^\[.*\]$ /logs/artifacts/gcp-resources-before.txt /logs/artifacts/gcp-resources-after.txt' finished in 4.842997ms 2023/03/11 03:27:44 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml. 2023/03/11 03:27:44 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 ...