This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 16 succeeded
Started2022-08-17 14:19
Elapsed53m39s
Revisionmain

Test Failures


capi-e2e When testing ClusterClass changes [ClusterClass] Should successfully rollout the managed topology upon changes to the ClusterClass 11m54s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\stesting\sClusterClass\schanges\s\[ClusterClass\]\sShould\ssuccessfully\srollout\sthe\smanaged\stopology\supon\schanges\sto\sthe\sClusterClass$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterclass_changes.go:119
Timed out after 600.003s.
Expected
    <*errors.fundamental | 0xc0026de270>: {
        msg: "field \"spec.machineTemplate.nodeDrainTimeout\" should be equal to \"10s\", but is \"30s\"",
        stack: [0x1be4da5, 0x4d7245, 0x4d67bf, 0x7df971, 0x7dfcd9, 0x7e0507, 0x7dfa6b, 0x1be4ad2, 0x1be35a6, 0x7a9cd1, 0x7a96c5, 0x7a8dbb, 0x7aeaaa, 0x7ae4a7, 0x7ceea8, 0x7cebc5, 0x7ce265, 0x7d0632, 0x7dc529, 0x7dc336, 0x1bffb8d, 0x5204a2, 0x46d941],
    }
to be nil
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterclass_changes.go:240
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 16 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 1131 lines ...
STEP: Waiting for the machine pool workload nodes
STEP: Scaling the machine pool to zero
INFO: Patching the replica count in Machine Pool machine-pool-pqfnbq/machine-pool-v4qttv-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-v4qttv" workload cluster
Failed to get logs for Machine machine-pool-v4qttv-control-plane-nfvvh, Cluster machine-pool-pqfnbq/machine-pool-v4qttv: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-pqfnbq" namespace
STEP: Deleting cluster machine-pool-pqfnbq/machine-pool-v4qttv
STEP: Deleting cluster machine-pool-v4qttv
INFO: Waiting for the Cluster machine-pool-pqfnbq/machine-pool-v4qttv to be deleted
STEP: Waiting for cluster machine-pool-v4qttv to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" test spec
... skipping 81 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 bootstrap
STEP: Waiting for cluster to enter the provisioned phase
STEP: Dumping logs from the "self-hosted-q4wcbz" workload cluster
Failed to get logs for Machine self-hosted-q4wcbz-control-plane-j9ss5, Cluster self-hosted-kbcdvn/self-hosted-q4wcbz: exit status 2
Failed to get logs for Machine self-hosted-q4wcbz-md-0-6467767b65-7qln7, Cluster self-hosted-kbcdvn/self-hosted-q4wcbz: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-kbcdvn" namespace
STEP: Deleting cluster self-hosted-kbcdvn/self-hosted-q4wcbz
STEP: Deleting cluster self-hosted-q4wcbz
INFO: Waiting for the Cluster self-hosted-kbcdvn/self-hosted-q4wcbz to be deleted
STEP: Waiting for cluster self-hosted-q4wcbz to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 40 lines ...
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
STEP: Checking all the machines controlled by quick-start-fwho1p-md-0 are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-fwho1p" workload cluster
Failed to get logs for Machine quick-start-fwho1p-control-plane-9cktg, Cluster quick-start-i44wer/quick-start-fwho1p: exit status 2
Failed to get logs for Machine quick-start-fwho1p-md-0-67f76864b5-n8l8v, Cluster quick-start-i44wer/quick-start-fwho1p: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-i44wer" namespace
STEP: Deleting cluster quick-start-i44wer/quick-start-fwho1p
STEP: Deleting cluster quick-start-fwho1p
INFO: Waiting for the Cluster quick-start-i44wer/quick-start-fwho1p to be deleted
STEP: Waiting for cluster quick-start-fwho1p to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-annxiw-unevictable-workload/unevictable-pod-9ft to be available
STEP: Scale down the controlplane of the workload cluster and make sure that nodes running workload can be deleted even the draining process is blocked.
INFO: Scaling controlplane node-drain-annxiw/node-drain-di5jz7-control-plane from 3 to 1 replicas
INFO: Waiting for correct number of replicas to exist
STEP: PASSED!
STEP: Dumping logs from the "node-drain-di5jz7" workload cluster
Failed to get logs for Machine node-drain-di5jz7-control-plane-w98mg, Cluster node-drain-annxiw/node-drain-di5jz7: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-annxiw" namespace
STEP: Deleting cluster node-drain-annxiw/node-drain-di5jz7
STEP: Deleting cluster node-drain-di5jz7
INFO: Waiting for the Cluster node-drain-annxiw/node-drain-di5jz7 to be deleted
STEP: Waiting for cluster node-drain-di5jz7 to be deleted
STEP: Deleting namespace used for hosting the "node-drain" test spec
... skipping 40 lines ...
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
STEP: Checking all the machines controlled by quick-start-13p3yp-md-0-bb7sk are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-13p3yp" workload cluster
Failed to get logs for Machine quick-start-13p3yp-md-0-bb7sk-b44bc7568-j76h2, Cluster quick-start-5hq6ju/quick-start-13p3yp: exit status 2
Failed to get logs for Machine quick-start-13p3yp-v92j4-7njxp, Cluster quick-start-5hq6ju/quick-start-13p3yp: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-5hq6ju" namespace
STEP: Deleting cluster quick-start-5hq6ju/quick-start-13p3yp
STEP: Deleting cluster quick-start-13p3yp
INFO: Waiting for the Cluster quick-start-5hq6ju/quick-start-13p3yp to be deleted
STEP: Waiting for cluster quick-start-13p3yp to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 35 lines ...

STEP: Waiting for the control plane to be ready
STEP: Taking stable ownership of the Machines
STEP: Taking ownership of the cluster's PKI material
STEP: PASSED!
STEP: Dumping logs from the "kcp-adoption-m5gq4d" workload cluster
Failed to get logs for Machine kcp-adoption-m5gq4d-control-plane-0, Cluster kcp-adoption-8x3qh2/kcp-adoption-m5gq4d: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-8x3qh2" namespace
STEP: Deleting cluster kcp-adoption-8x3qh2/kcp-adoption-m5gq4d
STEP: Deleting cluster kcp-adoption-m5gq4d
INFO: Waiting for the Cluster kcp-adoption-8x3qh2/kcp-adoption-m5gq4d to be deleted
STEP: Waiting for cluster kcp-adoption-m5gq4d to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" test spec
... skipping 54 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk-md-0-4wkkk to be upgraded to v1.24.0
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: PASSED!
STEP: Dumping logs from the "k8s-upgrade-and-conformance-t4k1nk" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-t4k1nk-md-0-4wkkk-6db58db899-zmm46, Cluster k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-t4k1nk-sbwt4-fbr89, Cluster k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-t4k1nk-sbwt4-nf8g6, Cluster k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-t4k1nk-sbwt4-rpj5b, Cluster k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-rrj1l8" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk
STEP: Deleting cluster k8s-upgrade-and-conformance-t4k1nk
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-rrj1l8/k8s-upgrade-and-conformance-t4k1nk to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-t4k1nk to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 48 lines ...
Patching MachineHealthCheck unhealthy condition to one of the nodes
INFO: Patching the node condition to the node
Waiting for remediation
Waiting until the node with unhealthy node condition is remediated
STEP: PASSED!
STEP: Dumping logs from the "mhc-remediation-4jx275" workload cluster
Failed to get logs for Machine mhc-remediation-4jx275-control-plane-bb8ts, Cluster mhc-remediation-0gsfq6/mhc-remediation-4jx275: exit status 2
Failed to get logs for Machine mhc-remediation-4jx275-md-0-77bfcb48f7-pz5tf, Cluster mhc-remediation-0gsfq6/mhc-remediation-4jx275: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-0gsfq6" namespace
STEP: Deleting cluster mhc-remediation-0gsfq6/mhc-remediation-4jx275
STEP: Deleting cluster mhc-remediation-4jx275
INFO: Waiting for the Cluster mhc-remediation-0gsfq6/mhc-remediation-4jx275 to be deleted
STEP: Waiting for cluster mhc-remediation-4jx275 to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 81 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 bootstrap
STEP: Waiting for cluster to enter the provisioned phase
STEP: Dumping logs from the "self-hosted-fmmzsk" workload cluster
Failed to get logs for Machine self-hosted-fmmzsk-9fqk6-vkc6s, Cluster self-hosted-87f36c/self-hosted-fmmzsk: exit status 2
Failed to get logs for Machine self-hosted-fmmzsk-md-0-22pmr-84fbfbb44b-gvkt6, Cluster self-hosted-87f36c/self-hosted-fmmzsk: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-87f36c" namespace
STEP: Deleting cluster self-hosted-87f36c/self-hosted-fmmzsk
STEP: Deleting cluster self-hosted-fmmzsk
INFO: Waiting for the Cluster self-hosted-87f36c/self-hosted-fmmzsk to be deleted
STEP: Waiting for cluster self-hosted-fmmzsk to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 54 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8-md-0-94bc6 to be upgraded to v1.24.0
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: PASSED!
STEP: Dumping logs from the "k8s-upgrade-and-conformance-86w5s8" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-86w5s8-bnqsx-25rhd, Cluster k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-86w5s8-bnqsx-n4p7c, Cluster k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-86w5s8-bnqsx-qkr74, Cluster k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-86w5s8-md-0-94bc6-76855b4765-vt26z, Cluster k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-hgjf7q" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8
STEP: Deleting cluster k8s-upgrade-and-conformance-86w5s8
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-hgjf7q/k8s-upgrade-and-conformance-86w5s8 to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-86w5s8 to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 48 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-rollout-iajc3i" workload cluster
Failed to get logs for Machine md-rollout-iajc3i-control-plane-2hwx4, Cluster md-rollout-w0mwep/md-rollout-iajc3i: exit status 2
Failed to get logs for Machine md-rollout-iajc3i-md-0-5cb5cf859-4zxz6, Cluster md-rollout-w0mwep/md-rollout-iajc3i: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-w0mwep" namespace
STEP: Deleting cluster md-rollout-w0mwep/md-rollout-iajc3i
STEP: Deleting cluster md-rollout-iajc3i
INFO: Waiting for the Cluster md-rollout-w0mwep/md-rollout-iajc3i to be deleted
STEP: Waiting for cluster md-rollout-iajc3i to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" test spec
... skipping 50 lines ...
Patching MachineHealthCheck unhealthy condition to one of the nodes
INFO: Patching the node condition to the node
Waiting for remediation
Waiting until the node with unhealthy node condition is remediated
STEP: PASSED!
STEP: Dumping logs from the "mhc-remediation-1e54hi" workload cluster
Failed to get logs for Machine mhc-remediation-1e54hi-control-plane-9vf8q, Cluster mhc-remediation-7sean3/mhc-remediation-1e54hi: exit status 2
Failed to get logs for Machine mhc-remediation-1e54hi-control-plane-dzfv4, Cluster mhc-remediation-7sean3/mhc-remediation-1e54hi: exit status 2
Failed to get logs for Machine mhc-remediation-1e54hi-control-plane-m5tfk, Cluster mhc-remediation-7sean3/mhc-remediation-1e54hi: exit status 2
Failed to get logs for Machine mhc-remediation-1e54hi-md-0-86dbdb7d46-chph2, Cluster mhc-remediation-7sean3/mhc-remediation-1e54hi: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-7sean3" namespace
STEP: Deleting cluster mhc-remediation-7sean3/mhc-remediation-1e54hi
STEP: Deleting cluster mhc-remediation-1e54hi
INFO: Waiting for the Cluster mhc-remediation-7sean3/mhc-remediation-1e54hi to be deleted
STEP: Waiting for cluster mhc-remediation-1e54hi to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 40 lines ...
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
STEP: Checking all the machines controlled by quick-start-1i5972-md-0 are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-1i5972" workload cluster
Failed to get logs for Machine quick-start-1i5972-control-plane-jqbrj, Cluster quick-start-oluer7/quick-start-1i5972: exit status 2
Failed to get logs for Machine quick-start-1i5972-md-0-77d7cbd4d7-v22tf, Cluster quick-start-oluer7/quick-start-1i5972: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-oluer7" namespace
STEP: Deleting cluster quick-start-oluer7/quick-start-1i5972
STEP: Deleting cluster quick-start-1i5972
INFO: Waiting for the Cluster quick-start-oluer7/quick-start-1i5972 to be deleted
STEP: Waiting for cluster quick-start-1i5972 to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 48 lines ...
INFO: Waiting for correct number of replicas to exist
STEP: Scaling the MachineDeployment down to 1
INFO: Scaling machine deployment md-scale-mnhcmz/md-scale-uu6tm7-md-0 from 3 to 1 replicas
INFO: Waiting for correct number of replicas to exist
STEP: PASSED!
STEP: Dumping logs from the "md-scale-uu6tm7" workload cluster
Failed to get logs for Machine md-scale-uu6tm7-control-plane-94nb5, Cluster md-scale-mnhcmz/md-scale-uu6tm7: exit status 2
Failed to get logs for Machine md-scale-uu6tm7-md-0-69cfc95f8d-prkl2, Cluster md-scale-mnhcmz/md-scale-uu6tm7: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-mnhcmz" namespace
STEP: Deleting cluster md-scale-mnhcmz/md-scale-uu6tm7
STEP: Deleting cluster md-scale-uu6tm7
INFO: Waiting for the Cluster md-scale-mnhcmz/md-scale-uu6tm7 to be deleted
STEP: Waiting for cluster md-scale-uu6tm7 to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 42 lines ...
STEP: Checking all the machines controlled by clusterclass-changes-c517o7-md-0-844bf are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: Modifying the control plane configuration in ClusterClass and wait for changes to be applied to the control plane object
INFO: Modifying the ControlPlaneTemplate of ClusterClass clusterclass-changes-du5nmr/quick-start
INFO: Waiting for ControlPlane rollout to complete.
STEP: Dumping logs from the "clusterclass-changes-c517o7" workload cluster
Failed to get logs for Machine clusterclass-changes-c517o7-6tv5x-fjd7v, Cluster clusterclass-changes-du5nmr/clusterclass-changes-c517o7: exit status 2
Failed to get logs for Machine clusterclass-changes-c517o7-md-0-844bf-dffcf86f4-tgvvv, Cluster clusterclass-changes-du5nmr/clusterclass-changes-c517o7: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-du5nmr" namespace
STEP: Deleting cluster clusterclass-changes-du5nmr/clusterclass-changes-c517o7
STEP: Deleting cluster clusterclass-changes-c517o7
INFO: Waiting for the Cluster clusterclass-changes-du5nmr/clusterclass-changes-c517o7 to be deleted
STEP: Waiting for cluster clusterclass-changes-c517o7 to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 161 lines ...
STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-2k6wb2
STEP: Deleting namespace clusterctl-upgrade used for hosting the "clusterctl-upgrade" test
INFO: Deleting namespace clusterctl-upgrade
STEP: Deleting providers
INFO: clusterctl delete --all
STEP: Dumping logs from the "clusterctl-upgrade-2k6wb2" workload cluster
Failed to get logs for Machine clusterctl-upgrade-2k6wb2-control-plane-lt5kw, Cluster clusterctl-upgrade-3y5lmi/clusterctl-upgrade-2k6wb2: exit status 2
Failed to get logs for Machine clusterctl-upgrade-2k6wb2-md-0-5dbf4cff9b-ck52h, Cluster clusterctl-upgrade-3y5lmi/clusterctl-upgrade-2k6wb2: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-3y5lmi" namespace
STEP: Deleting cluster clusterctl-upgrade-3y5lmi/clusterctl-upgrade-2k6wb2
STEP: Deleting cluster clusterctl-upgrade-2k6wb2
INFO: Waiting for the Cluster clusterctl-upgrade-3y5lmi/clusterctl-upgrade-2k6wb2 to be deleted
STEP: Waiting for cluster clusterctl-upgrade-2k6wb2 to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
... skipping 81 lines ...
INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-with-runtimesdk-eh2nre/k8s-upgrade-with-runtimesdk-gjqlj7-mp-0
INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-with-runtimesdk-eh2nre/k8s-upgrade-with-runtimesdk-gjqlj7-mp-0 to be upgraded from v1.23.6 to v1.24.0
INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: Dumping resources and deleting the workload cluster
STEP: Deleting the workload cluster
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-gjqlj7-c6fm2-zqpql, Cluster k8s-upgrade-with-runtimesdk-eh2nre/k8s-upgrade-with-runtimesdk-gjqlj7: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-gjqlj7-md-0-9jzq6-5d97986844-bdsb8, Cluster k8s-upgrade-with-runtimesdk-eh2nre/k8s-upgrade-with-runtimesdk-gjqlj7: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-gjqlj7-md-0-9jzq6-5d97986844-ndbxf, Cluster k8s-upgrade-with-runtimesdk-eh2nre/k8s-upgrade-with-runtimesdk-gjqlj7: exit status 2
Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-gjqlj7-mp-0, Cluster k8s-upgrade-with-runtimesdk-eh2nre/k8s-upgrade-with-runtimesdk-gjqlj7: exit status 2
STEP: Deleting the workload cluster
STEP: Deleting cluster k8s-upgrade-with-runtimesdk-gjqlj7
INFO: Blocking with BeforeClusterDelete hook
STEP: Setting BeforeClusterDelete response to Status:Success to unblock the reconciliation
STEP: Checking all lifecycle hooks have been called
STEP: PASSED!
... skipping 8 lines ...
When upgrading a workload cluster using ClusterClass with RuntimeSDK [PR-Informing] [ClusterClass]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk_test.go:29
  Should create, upgrade and delete a workload cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk.go:130
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-gzrl4p-control-plane: exit status 2
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] When testing ClusterClass changes [ClusterClass] [It] Should successfully rollout the managed topology upon changes to the ClusterClass 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterclass_changes.go:240

Ran 17 of 21 Specs in 2801.711 seconds
FAIL! -- 16 Passed | 1 Failed | 0 Pending | 4 Skipped


Ginkgo ran 1 suite in 47m53.313734651s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc
make: *** [Makefile:129: run] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ cleanup
++ pgrep -f 'docker events'
+ kill 26029
++ pgrep -f 'ctr -n moby events'
+ kill 26030
... skipping 21 lines ...