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

Test Failures


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

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 | 0xc0018881f8>: {
        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.1.xml

Filter through log files | View test history on testgrid


Show 17 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 1136 lines ...
INFO: Waiting for correct number of replicas to exist
STEP: Scaling the MachineDeployment down to 1
INFO: Scaling machine deployment md-scale-mk5jwv/md-scale-fprhru-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-fprhru" workload cluster
Failed to get logs for Machine md-scale-fprhru-control-plane-jwx4l, Cluster md-scale-mk5jwv/md-scale-fprhru: exit status 2
Failed to get logs for Machine md-scale-fprhru-md-0-869fc8849-95vst, Cluster md-scale-mk5jwv/md-scale-fprhru: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-mk5jwv" namespace
STEP: Deleting cluster md-scale-mk5jwv/md-scale-fprhru
STEP: Deleting cluster md-scale-fprhru
INFO: Waiting for the Cluster md-scale-mk5jwv/md-scale-fprhru to be deleted
STEP: Waiting for cluster md-scale-fprhru to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 46 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-659u9h" workload cluster
Failed to get logs for Machine md-rollout-659u9h-control-plane-dq8f4, Cluster md-rollout-9uql4s/md-rollout-659u9h: exit status 2
Failed to get logs for Machine md-rollout-659u9h-md-0-674cf6f9dc-vhfpx, Cluster md-rollout-9uql4s/md-rollout-659u9h: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-9uql4s" namespace
STEP: Deleting cluster md-rollout-9uql4s/md-rollout-659u9h
STEP: Deleting cluster md-rollout-659u9h
INFO: Waiting for the Cluster md-rollout-9uql4s/md-rollout-659u9h to be deleted
STEP: Waiting for cluster md-rollout-659u9h to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" test spec
... skipping 42 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-7xwqf7-md-0-c46v5 are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-7xwqf7" workload cluster
Failed to get logs for Machine quick-start-7xwqf7-89bpr-lrlwr, Cluster quick-start-x601gm/quick-start-7xwqf7: exit status 2
Failed to get logs for Machine quick-start-7xwqf7-md-0-c46v5-69bb5cc74f-rsrbf, Cluster quick-start-x601gm/quick-start-7xwqf7: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-x601gm" namespace
STEP: Deleting cluster quick-start-x601gm/quick-start-7xwqf7
STEP: Deleting cluster quick-start-7xwqf7
INFO: Waiting for the Cluster quick-start-x601gm/quick-start-7xwqf7 to be deleted
STEP: Waiting for cluster quick-start-7xwqf7 to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-3nohtz-unevictable-workload/unevictable-pod-3ac 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-3nohtz/node-drain-o3z3de-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-o3z3de" workload cluster
Failed to get logs for Machine node-drain-o3z3de-control-plane-qndcm, Cluster node-drain-3nohtz/node-drain-o3z3de: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-3nohtz" namespace
STEP: Deleting cluster node-drain-3nohtz/node-drain-o3z3de
STEP: Deleting cluster node-drain-o3z3de
INFO: Waiting for the Cluster node-drain-3nohtz/node-drain-o3z3de to be deleted
STEP: Waiting for cluster node-drain-o3z3de to be deleted
STEP: Deleting namespace used for hosting the "node-drain" test spec
... skipping 115 lines ...
STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-yjk82h
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-yjk82h" workload cluster
Failed to get logs for Machine clusterctl-upgrade-yjk82h-control-plane-fpm6k, Cluster clusterctl-upgrade-lfmfdr/clusterctl-upgrade-yjk82h: exit status 2
Failed to get logs for Machine clusterctl-upgrade-yjk82h-md-0-7c8666549d-gtgfn, Cluster clusterctl-upgrade-lfmfdr/clusterctl-upgrade-yjk82h: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-lfmfdr" namespace
STEP: Deleting cluster clusterctl-upgrade-lfmfdr/clusterctl-upgrade-yjk82h
STEP: Deleting cluster clusterctl-upgrade-yjk82h
INFO: Waiting for the Cluster clusterctl-upgrade-lfmfdr/clusterctl-upgrade-yjk82h to be deleted
STEP: Waiting for cluster clusterctl-upgrade-yjk82h to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" 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-523r6v" workload cluster
Failed to get logs for Machine mhc-remediation-523r6v-control-plane-87nth, Cluster mhc-remediation-mjchot/mhc-remediation-523r6v: exit status 2
Failed to get logs for Machine mhc-remediation-523r6v-md-0-7d9df6fc6c-sczmr, Cluster mhc-remediation-mjchot/mhc-remediation-523r6v: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-mjchot" namespace
STEP: Deleting cluster mhc-remediation-mjchot/mhc-remediation-523r6v
STEP: Deleting cluster mhc-remediation-523r6v
INFO: Waiting for the Cluster mhc-remediation-mjchot/mhc-remediation-523r6v to be deleted
STEP: Waiting for cluster mhc-remediation-523r6v to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 48 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-5ktenz/machine-pool-ggvsvo-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-ggvsvo" workload cluster
Failed to get logs for Machine machine-pool-ggvsvo-control-plane-szsdj, Cluster machine-pool-5ktenz/machine-pool-ggvsvo: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-5ktenz" namespace
STEP: Deleting cluster machine-pool-5ktenz/machine-pool-ggvsvo
STEP: Deleting cluster machine-pool-ggvsvo
INFO: Waiting for the Cluster machine-pool-5ktenz/machine-pool-ggvsvo to be deleted
STEP: Waiting for cluster machine-pool-ggvsvo to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" 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-55crpx-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-55crpx" workload cluster
Failed to get logs for Machine quick-start-55crpx-control-plane-s9lb4, Cluster quick-start-mkz73e/quick-start-55crpx: exit status 2
Failed to get logs for Machine quick-start-55crpx-md-0-7b5fbdbc4f-jm69d, Cluster quick-start-mkz73e/quick-start-55crpx: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-mkz73e" namespace
STEP: Deleting cluster quick-start-mkz73e/quick-start-55crpx
STEP: Deleting cluster quick-start-55crpx
INFO: Waiting for the Cluster quick-start-mkz73e/quick-start-55crpx to be deleted
STEP: Waiting for cluster quick-start-55crpx to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-m7yz18" workload cluster
Failed to get logs for Machine self-hosted-m7yz18-874sc-rn5fs, Cluster self-hosted-ee6rf8/self-hosted-m7yz18: exit status 2
Failed to get logs for Machine self-hosted-m7yz18-md-0-7jk8x-6ddd4766f8-f9fpb, Cluster self-hosted-ee6rf8/self-hosted-m7yz18: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-ee6rf8" namespace
STEP: Deleting cluster self-hosted-ee6rf8/self-hosted-m7yz18
STEP: Deleting cluster self-hosted-m7yz18
INFO: Waiting for the Cluster self-hosted-ee6rf8/self-hosted-m7yz18 to be deleted
STEP: Waiting for cluster self-hosted-m7yz18 to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" 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-4scoaw" workload cluster
Failed to get logs for Machine mhc-remediation-4scoaw-control-plane-8pd4r, Cluster mhc-remediation-hxfuut/mhc-remediation-4scoaw: exit status 2
Failed to get logs for Machine mhc-remediation-4scoaw-control-plane-xhdrn, Cluster mhc-remediation-hxfuut/mhc-remediation-4scoaw: exit status 2
Failed to get logs for Machine mhc-remediation-4scoaw-control-plane-z9qgt, Cluster mhc-remediation-hxfuut/mhc-remediation-4scoaw: exit status 2
Failed to get logs for Machine mhc-remediation-4scoaw-md-0-77dcc6dfc-nxfqp, Cluster mhc-remediation-hxfuut/mhc-remediation-4scoaw: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-hxfuut" namespace
STEP: Deleting cluster mhc-remediation-hxfuut/mhc-remediation-4scoaw
STEP: Deleting cluster mhc-remediation-4scoaw
INFO: Waiting for the Cluster mhc-remediation-hxfuut/mhc-remediation-4scoaw to be deleted
STEP: Waiting for cluster mhc-remediation-4scoaw 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-r9xhdt" workload cluster
Failed to get logs for Machine self-hosted-r9xhdt-control-plane-6ndhh, Cluster self-hosted-x3d1mk/self-hosted-r9xhdt: exit status 2
Failed to get logs for Machine self-hosted-r9xhdt-md-0-7d5648845f-zc45d, Cluster self-hosted-x3d1mk/self-hosted-r9xhdt: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-x3d1mk" namespace
STEP: Deleting cluster self-hosted-x3d1mk/self-hosted-r9xhdt
STEP: Deleting cluster self-hosted-r9xhdt
INFO: Waiting for the Cluster self-hosted-x3d1mk/self-hosted-r9xhdt to be deleted
STEP: Waiting for cluster self-hosted-r9xhdt 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-pxcf7f-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-pxcf7f" workload cluster
Failed to get logs for Machine quick-start-pxcf7f-control-plane-6kf2v, Cluster quick-start-h5x1wq/quick-start-pxcf7f: exit status 2
Failed to get logs for Machine quick-start-pxcf7f-md-0-9d7b48c5d-pr9p2, Cluster quick-start-h5x1wq/quick-start-pxcf7f: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-h5x1wq" namespace
STEP: Deleting cluster quick-start-h5x1wq/quick-start-pxcf7f
STEP: Deleting cluster quick-start-pxcf7f
INFO: Waiting for the Cluster quick-start-h5x1wq/quick-start-pxcf7f to be deleted
STEP: Waiting for cluster quick-start-pxcf7f to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-mad8vv/k8s-upgrade-and-conformance-il0bn5-md-0-sp75f 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-il0bn5" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-il0bn5-6pcj5-7hwbv, Cluster k8s-upgrade-and-conformance-mad8vv/k8s-upgrade-and-conformance-il0bn5: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-il0bn5-6pcj5-fm96k, Cluster k8s-upgrade-and-conformance-mad8vv/k8s-upgrade-and-conformance-il0bn5: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-il0bn5-6pcj5-sw2v4, Cluster k8s-upgrade-and-conformance-mad8vv/k8s-upgrade-and-conformance-il0bn5: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-il0bn5-md-0-sp75f-5c5896bc99-hrpd7, Cluster k8s-upgrade-and-conformance-mad8vv/k8s-upgrade-and-conformance-il0bn5: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-mad8vv" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-mad8vv/k8s-upgrade-and-conformance-il0bn5
STEP: Deleting cluster k8s-upgrade-and-conformance-il0bn5
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-mad8vv/k8s-upgrade-and-conformance-il0bn5 to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-il0bn5 to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-p5lebu" workload cluster
Failed to get logs for Machine kcp-adoption-p5lebu-control-plane-0, Cluster kcp-adoption-6y4atk/kcp-adoption-p5lebu: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-6y4atk" namespace
STEP: Deleting cluster kcp-adoption-6y4atk/kcp-adoption-p5lebu
STEP: Deleting cluster kcp-adoption-p5lebu
INFO: Waiting for the Cluster kcp-adoption-6y4atk/kcp-adoption-p5lebu to be deleted
STEP: Waiting for cluster kcp-adoption-p5lebu 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-kzsip0/k8s-upgrade-and-conformance-ll6104-md-0-6h5lb 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-ll6104" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-ll6104-hhpz2-z5n48, Cluster k8s-upgrade-and-conformance-kzsip0/k8s-upgrade-and-conformance-ll6104: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-ll6104-md-0-6h5lb-5f9df7485c-dmg6c, Cluster k8s-upgrade-and-conformance-kzsip0/k8s-upgrade-and-conformance-ll6104: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-ll6104-md-0-6h5lb-5f9df7485c-zx65b, Cluster k8s-upgrade-and-conformance-kzsip0/k8s-upgrade-and-conformance-ll6104: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-kzsip0" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-kzsip0/k8s-upgrade-and-conformance-ll6104
STEP: Deleting cluster k8s-upgrade-and-conformance-ll6104
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-kzsip0/k8s-upgrade-and-conformance-ll6104 to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-ll6104 to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 81 lines ...
INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-with-runtimesdk-rwalkf/k8s-upgrade-with-runtimesdk-gf9umq-mp-0
INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-with-runtimesdk-rwalkf/k8s-upgrade-with-runtimesdk-gf9umq-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-gf9umq-md-0-jrrqw-6f9d9d9886-rqd6w, Cluster k8s-upgrade-with-runtimesdk-rwalkf/k8s-upgrade-with-runtimesdk-gf9umq: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-gf9umq-md-0-jrrqw-6f9d9d9886-vl7kt, Cluster k8s-upgrade-with-runtimesdk-rwalkf/k8s-upgrade-with-runtimesdk-gf9umq: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-gf9umq-r7tct-ktnrc, Cluster k8s-upgrade-with-runtimesdk-rwalkf/k8s-upgrade-with-runtimesdk-gf9umq: exit status 2
Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-gf9umq-mp-0, Cluster k8s-upgrade-with-runtimesdk-rwalkf/k8s-upgrade-with-runtimesdk-gf9umq: exit status 2
STEP: Deleting the workload cluster
STEP: Deleting cluster k8s-upgrade-with-runtimesdk-gf9umq
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 46 lines ...
STEP: Checking all the machines controlled by clusterclass-changes-4u71zg-md-0-g2zbf 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-7c0kqr/quick-start
INFO: Waiting for ControlPlane rollout to complete.
STEP: Dumping logs from the "clusterclass-changes-4u71zg" workload cluster
Failed to get logs for Machine clusterclass-changes-4u71zg-gtb87-f9bjf, Cluster clusterclass-changes-7c0kqr/clusterclass-changes-4u71zg: exit status 2
Failed to get logs for Machine clusterclass-changes-4u71zg-md-0-g2zbf-7445d6b4c4-8mv66, Cluster clusterclass-changes-7c0kqr/clusterclass-changes-4u71zg: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-7c0kqr" namespace
STEP: Deleting cluster clusterclass-changes-7c0kqr/clusterclass-changes-4u71zg
STEP: Deleting cluster clusterclass-changes-4u71zg
INFO: Waiting for the Cluster clusterclass-changes-7c0kqr/clusterclass-changes-4u71zg to be deleted
STEP: Waiting for cluster clusterclass-changes-4u71zg to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 98 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y-md-0-57zwx 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-yynl8y" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-yynl8y-md-0-57zwx-7d94d596f7-29c6v, Cluster k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-yynl8y-zdrk7-flv67, Cluster k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-yynl8y-zdrk7-qvhk2, Cluster k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-yynl8y-zdrk7-zk5mm, Cluster k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-26ne28" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y
STEP: Deleting cluster k8s-upgrade-and-conformance-yynl8y
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-26ne28/k8s-upgrade-and-conformance-yynl8y to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-yynl8y to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 4 lines ...
When upgrading a workload cluster using ClusterClass with a HA control plane using scale-in rollout [ClusterClass]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_test.go:101
  Should create and upgrade a workload cluster and eventually run kubetest
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade.go:118
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-9c4nmu-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 18 of 21 Specs in 2992.876 seconds
FAIL! -- 17 Passed | 1 Failed | 0 Pending | 3 Skipped


Ginkgo ran 1 suite in 50m57.14515298s
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 25946
++ pgrep -f 'ctr -n moby events'
+ kill 25947
... skipping 21 lines ...