This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2022-09-12 03:19
Elapsed20m43s
Revisionrelease-1.0

Test Failures


capi-e2e When testing MachineDeployment scale out/in Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count 7m26s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\stesting\sMachineDeployment\sscale\sout\/in\sShould\ssuccessfully\sscale\sa\sMachineDeployment\sup\sand\sdown\supon\schanges\sto\sthe\sMachineDeployment\sreplica\scount$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_scale.go:70
Timed out after 300.000s.
Error: Unexpected non-nil/non-zero extra argument at index 1:
	<*errors.fundamental>: Machine count does not match existing nodes count
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinedeployment_helpers.go:348
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 2 Passed Tests

Show 12 Skipped Tests

Error lines from build-log.txt

... skipping 849 lines ...
STEP: Waiting for the workload nodes to exist
INFO: Waiting for the machine pools to be provisioned
STEP: Scaling the MachineDeployment out to 3
INFO: Scaling machine deployment md-scale-ud60t0/md-scale-9xpgun-md-0 from 1 to 3 replicas
INFO: Waiting for correct number of replicas to exist
STEP: Dumping logs from the "md-scale-9xpgun" workload cluster
Failed to get logs for machine md-scale-9xpgun-control-plane-p52gz, cluster md-scale-ud60t0/md-scale-9xpgun: exit status 2
Failed to get logs for machine md-scale-9xpgun-md-0-79fb6fd868-hw9k2, cluster md-scale-ud60t0/md-scale-9xpgun: exit status 2
Failed to get logs for machine md-scale-9xpgun-md-0-79fb6fd868-mg2d9, cluster md-scale-ud60t0/md-scale-9xpgun: exit status 2
Failed to get logs for machine md-scale-9xpgun-md-0-79fb6fd868-ppwrp, cluster md-scale-ud60t0/md-scale-9xpgun: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-ud60t0" namespace
STEP: Deleting cluster md-scale-ud60t0/md-scale-9xpgun
STEP: Deleting cluster md-scale-9xpgun
INFO: Waiting for the Cluster md-scale-ud60t0/md-scale-9xpgun to be deleted
STEP: Waiting for cluster md-scale-9xpgun to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 4 lines ...
When testing MachineDeployment scale out/in
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_scale_test.go:25
  Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count [It]
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_scale.go:70

  Timed out after 300.000s.
  Error: Unexpected non-nil/non-zero extra argument at index 1:
  	<*errors.fundamental>: Machine count does not match existing nodes count

  /home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinedeployment_helpers.go:348

  Full Stack Trace
  sigs.k8s.io/cluster-api/test/framework.ScaleAndWaitMachineDeployment(0x22de868, 0xc000067040, 0x22fa080, 0xc0009eedc0, 0xc0003d5340, 0xc0007ba840, 0x3, 0xc001bf20c0, 0x2, 0x2)
... skipping 72 lines ...
STEP: Ensuring kube-proxy has the correct image
INFO: Waiting for CoreDNS to have the upgraded image tag
STEP: Ensuring CoreDNS has the correct image
INFO: Waiting for etcd to have the upgraded image tag
STEP: PASSED!
STEP: Dumping logs from the "kcp-upgrade-a0ryn2" workload cluster
Failed to get logs for machine kcp-upgrade-a0ryn2-control-plane-cz9nq, cluster kcp-upgrade-glhlnr/kcp-upgrade-a0ryn2: exit status 2
Failed to get logs for machine kcp-upgrade-a0ryn2-md-0-d98dd474f-td6wh, cluster kcp-upgrade-glhlnr/kcp-upgrade-a0ryn2: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-glhlnr" namespace
STEP: Deleting cluster kcp-upgrade-glhlnr/kcp-upgrade-a0ryn2
STEP: Deleting cluster kcp-upgrade-a0ryn2
INFO: Waiting for the Cluster kcp-upgrade-glhlnr/kcp-upgrade-a0ryn2 to be deleted
STEP: Waiting for cluster kcp-upgrade-a0ryn2 to be deleted
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
... skipping 49 lines ...
STEP: Ensuring kube-proxy has the correct image
INFO: Waiting for CoreDNS to have the upgraded image tag
STEP: Ensuring CoreDNS has the correct image
INFO: Waiting for etcd to have the upgraded image tag
STEP: PASSED!
STEP: Dumping logs from the "kcp-upgrade-ote7c8" workload cluster
Failed to get logs for machine kcp-upgrade-ote7c8-control-plane-f9gxz, cluster kcp-upgrade-u2hbax/kcp-upgrade-ote7c8: exit status 2
Failed to get logs for machine kcp-upgrade-ote7c8-control-plane-kldvj, cluster kcp-upgrade-u2hbax/kcp-upgrade-ote7c8: exit status 2
Failed to get logs for machine kcp-upgrade-ote7c8-control-plane-skrsc, cluster kcp-upgrade-u2hbax/kcp-upgrade-ote7c8: exit status 2
Failed to get logs for machine kcp-upgrade-ote7c8-md-0-777d8cb8d5-kvplk, cluster kcp-upgrade-u2hbax/kcp-upgrade-ote7c8: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-u2hbax" namespace
STEP: Deleting cluster kcp-upgrade-u2hbax/kcp-upgrade-ote7c8
STEP: Deleting cluster kcp-upgrade-ote7c8
INFO: Waiting for the Cluster kcp-upgrade-u2hbax/kcp-upgrade-ote7c8 to be deleted
STEP: Waiting for cluster kcp-upgrade-ote7c8 to be deleted
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
... skipping 4 lines ...
When testing KCP upgrade in a HA cluster using scale in rollout
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade_test.go:55
  Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade.go:75
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-si632u-control-plane: exit status 2
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] When testing MachineDeployment scale out/in [It] Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinedeployment_helpers.go:348

Ran 3 of 15 Specs in 963.565 seconds
FAIL! -- 2 Passed | 1 Failed | 0 Pending | 12 Skipped


Ginkgo ran 1 suite in 17m6.594873379s
Test Suite Failed
make: *** [Makefile:107: run] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ cleanup
++ pgrep -f 'docker events'
+ kill 13685
++ pgrep -f 'ctr -n moby events'
+ kill 13686
... skipping 21 lines ...