This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 7 succeeded
Started2020-10-05 12:35
Elapsed43m34s
Revisionmaster

Test Failures


capi-e2e When testing KCP upgrade Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a HA cluster 26m59s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\stesting\sKCP\supgrade\sShould\ssuccessfully\supgrade\sKubernetes\,\sDNS\,\skube\-proxy\,\sand\setcd\sin\sa\sHA\scluster$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade.go:109
Timed out after 1200.000s.
Error: Unexpected non-nil/non-zero extra argument at index 1:
	<*errors.fundamental>: old nodes remain
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machine_helpers.go:143
				
				Click to see stdout/stderrfrom junit.e2e_suite.2.xml

Filter through log files


Show 7 Passed Tests

Error lines from build-log.txt

... skipping 1723 lines ...
INFO: Waiting for rolling upgrade to start.
INFO: Waiting for MachineDeployment rolling upgrade to start
INFO: Waiting for rolling upgrade to complete.
INFO: Waiting for MachineDeployment rolling upgrade to complete
STEP: PASSED!
STEP: Dumping logs from the "md-upgrades-w510wf" workload cluster
Failed to get logs for machine md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf, cluster md-upgrades-6ol080/md-upgrades-w510wf: [command "docker exec --privileged md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf journalctl --no-pager --output=short-precise -u containerd.service" failed with error: exit status 1, command "docker exec --privileged md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf journalctl --no-pager --output=short-precise -u kubelet.service" failed with error: exit status 1, command "docker exec --privileged md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf kubelet --version" failed with error: exit status 1, command "docker exec --privileged md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf journalctl --no-pager --output=short-precise" failed with error: exit status 1, command "docker exec --privileged md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf journalctl --no-pager --output=short-precise -k" failed with error: exit status 1, command "docker exec --privileged md-upgrades-w510wf-md-0-7b4db9dddf-pf5zf crictl info" failed with error: exit status 1]
STEP: Dumping all the Cluster API resources in the "md-upgrades-6ol080" namespace
STEP: Deleting cluster md-upgrades-6ol080/md-upgrades-w510wf
STEP: Deleting cluster md-upgrades-w510wf
INFO: Waiting for the Cluster md-upgrades-6ol080/md-upgrades-w510wf to be deleted
STEP: Waiting for cluster md-upgrades-w510wf to be deleted
STEP: Deleting namespace used for hosting the "md-upgrades" test spec
... skipping 200 lines ...
STEP: Ensure API servers are stable before doing move
STEP: Moving the cluster back to bootstrap
STEP: Moving workload clusters
INFO: Waiting for the cluster to be reconciled after moving back to booststrap
STEP: Waiting for cluster to enter the provisioned phase
STEP: Dumping logs from the "self-hosted-2mdzhi" workload cluster
Failed to get logs for machine self-hosted-2mdzhi-md-0-5d5868f988-krh2h, cluster self-hosted-fiuyy3/self-hosted-2mdzhi: [command "docker exec --privileged self-hosted-2mdzhi-md-0-5d5868f988-krh2h journalctl --no-pager --output=short-precise -u kubelet.service" failed with error: exit status 1, command "docker exec --privileged self-hosted-2mdzhi-md-0-5d5868f988-krh2h crictl info" failed with error: exit status 1, command "docker exec --privileged self-hosted-2mdzhi-md-0-5d5868f988-krh2h journalctl --no-pager --output=short-precise" failed with error: exit status 1, command "docker exec --privileged self-hosted-2mdzhi-md-0-5d5868f988-krh2h journalctl --no-pager --output=short-precise -k" failed with error: exit status 1, command "docker exec --privileged self-hosted-2mdzhi-md-0-5d5868f988-krh2h journalctl --no-pager --output=short-precise -u containerd.service" failed with error: exit status 1, command "docker exec --privileged self-hosted-2mdzhi-md-0-5d5868f988-krh2h kubelet --version" failed with error: exit status 1]
STEP: Dumping all the Cluster API resources in the "self-hosted-fiuyy3" namespace
STEP: Deleting cluster self-hosted-fiuyy3/self-hosted-2mdzhi
STEP: Deleting cluster self-hosted-2mdzhi
INFO: Waiting for the Cluster self-hosted-fiuyy3/self-hosted-2mdzhi to be deleted
STEP: Waiting for cluster self-hosted-2mdzhi to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 119 lines ...
When testing KCP upgrade
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade_test.go:27
  Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a HA cluster [It]
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade.go:109

  Timed out after 1200.000s.
  Error: Unexpected non-nil/non-zero extra argument at index 1:
  	<*errors.fundamental>: old nodes remain

  /home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machine_helpers.go:143

  Full Stack Trace
  sigs.k8s.io/cluster-api/test/framework.WaitForControlPlaneMachinesToBeUpgraded(0x1e316c0, 0xc0000d8018, 0x7fd3cd966588, 0xc0007aec60, 0xc0000e3520, 0xc0005e37a0, 0x7, 0x3, 0xc0004c1600, 0x2, ...)
... skipping 34 lines ...
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] When testing KCP upgrade [It] Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a HA cluster 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machine_helpers.go:143

Ran 8 of 8 Specs in 2089.659 seconds
FAIL! -- 7 Passed | 1 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 36m6.56839031s
Test Suite Failed
make: *** [Makefile:78: run] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
... skipping 4 lines ...