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 18:22
Elapsed1h3m
Revisionmain

Test Failures


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

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.001s.
Expected
    <*errors.fundamental | 0xc000742bb8>: {
        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.2.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 1122 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-udrru2-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-udrru2" workload cluster
Failed to get logs for Machine quick-start-udrru2-control-plane-9p5t6, Cluster quick-start-tt2fkn/quick-start-udrru2: exit status 2
Failed to get logs for Machine quick-start-udrru2-md-0-66b575fb5b-9wktn, Cluster quick-start-tt2fkn/quick-start-udrru2: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-tt2fkn" namespace
STEP: Deleting cluster quick-start-tt2fkn/quick-start-udrru2
STEP: Deleting cluster quick-start-udrru2
INFO: Waiting for the Cluster quick-start-tt2fkn/quick-start-udrru2 to be deleted
STEP: Waiting for cluster quick-start-udrru2 to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-ag1m68-md-0-8jnsc are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-ag1m68" workload cluster
Failed to get logs for Machine quick-start-ag1m68-76vhc-gbpgg, Cluster quick-start-4gqocz/quick-start-ag1m68: exit status 2
Failed to get logs for Machine quick-start-ag1m68-md-0-8jnsc-779b7df699-784jt, Cluster quick-start-4gqocz/quick-start-ag1m68: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-4gqocz" namespace
STEP: Deleting cluster quick-start-4gqocz/quick-start-ag1m68
STEP: Deleting cluster quick-start-ag1m68
INFO: Waiting for the Cluster quick-start-4gqocz/quick-start-ag1m68 to be deleted
STEP: Waiting for cluster quick-start-ag1m68 to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-5t6pgw-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-5t6pgw" workload cluster
Failed to get logs for Machine quick-start-5t6pgw-control-plane-hrhxw, Cluster quick-start-8e0dnx/quick-start-5t6pgw: exit status 2
Failed to get logs for Machine quick-start-5t6pgw-md-0-d464fd655-md2r5, Cluster quick-start-8e0dnx/quick-start-5t6pgw: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-8e0dnx" namespace
STEP: Deleting cluster quick-start-8e0dnx/quick-start-5t6pgw
STEP: Deleting cluster quick-start-5t6pgw
INFO: Waiting for the Cluster quick-start-8e0dnx/quick-start-5t6pgw to be deleted
STEP: Waiting for cluster quick-start-5t6pgw to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-8udio8/machine-pool-qbikms-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-qbikms" workload cluster
Failed to get logs for Machine machine-pool-qbikms-control-plane-rhbrq, Cluster machine-pool-8udio8/machine-pool-qbikms: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-8udio8" namespace
STEP: Deleting cluster machine-pool-8udio8/machine-pool-qbikms
STEP: Deleting cluster machine-pool-qbikms
INFO: Waiting for the Cluster machine-pool-8udio8/machine-pool-qbikms to be deleted
STEP: Waiting for cluster machine-pool-qbikms to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" 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-kcge4x" workload cluster
Failed to get logs for Machine mhc-remediation-kcge4x-control-plane-988g8, Cluster mhc-remediation-wvmf5r/mhc-remediation-kcge4x: exit status 2
Failed to get logs for Machine mhc-remediation-kcge4x-md-0-cf44674cf-n4s97, Cluster mhc-remediation-wvmf5r/mhc-remediation-kcge4x: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-wvmf5r" namespace
STEP: Deleting cluster mhc-remediation-wvmf5r/mhc-remediation-kcge4x
STEP: Deleting cluster mhc-remediation-kcge4x
INFO: Waiting for the Cluster mhc-remediation-wvmf5r/mhc-remediation-kcge4x to be deleted
STEP: Waiting for cluster mhc-remediation-kcge4x to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" 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-kjqwfd" workload cluster
Failed to get logs for Machine mhc-remediation-kjqwfd-control-plane-c4n5n, Cluster mhc-remediation-bc9v3l/mhc-remediation-kjqwfd: exit status 2
Failed to get logs for Machine mhc-remediation-kjqwfd-control-plane-kgrk2, Cluster mhc-remediation-bc9v3l/mhc-remediation-kjqwfd: exit status 2
Failed to get logs for Machine mhc-remediation-kjqwfd-control-plane-q4299, Cluster mhc-remediation-bc9v3l/mhc-remediation-kjqwfd: exit status 2
Failed to get logs for Machine mhc-remediation-kjqwfd-md-0-5bfbb8cb45-9tr86, Cluster mhc-remediation-bc9v3l/mhc-remediation-kjqwfd: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-bc9v3l" namespace
STEP: Deleting cluster mhc-remediation-bc9v3l/mhc-remediation-kjqwfd
STEP: Deleting cluster mhc-remediation-kjqwfd
INFO: Waiting for the Cluster mhc-remediation-bc9v3l/mhc-remediation-kjqwfd to be deleted
STEP: Waiting for cluster mhc-remediation-kjqwfd to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 52 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-6b1i8f/k8s-upgrade-and-conformance-rhfqe8-md-0-z2l6f 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-rhfqe8" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-rhfqe8-fgqqm-bv4zx, Cluster k8s-upgrade-and-conformance-6b1i8f/k8s-upgrade-and-conformance-rhfqe8: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-rhfqe8-md-0-z2l6f-5bbd6c8cdb-9xl2h, Cluster k8s-upgrade-and-conformance-6b1i8f/k8s-upgrade-and-conformance-rhfqe8: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-rhfqe8-md-0-z2l6f-5bbd6c8cdb-dmpg7, Cluster k8s-upgrade-and-conformance-6b1i8f/k8s-upgrade-and-conformance-rhfqe8: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-6b1i8f" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-6b1i8f/k8s-upgrade-and-conformance-rhfqe8
STEP: Deleting cluster k8s-upgrade-and-conformance-rhfqe8
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-6b1i8f/k8s-upgrade-and-conformance-rhfqe8 to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-rhfqe8 to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-77lb0v" workload cluster
Failed to get logs for Machine md-rollout-77lb0v-control-plane-tj5s2, Cluster md-rollout-ejl9nb/md-rollout-77lb0v: exit status 2
Failed to get logs for Machine md-rollout-77lb0v-md-0-795b87875d-4csnf, Cluster md-rollout-ejl9nb/md-rollout-77lb0v: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-ejl9nb" namespace
STEP: Deleting cluster md-rollout-ejl9nb/md-rollout-77lb0v
STEP: Deleting cluster md-rollout-77lb0v
INFO: Waiting for the Cluster md-rollout-ejl9nb/md-rollout-77lb0v to be deleted
STEP: Waiting for cluster md-rollout-77lb0v to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" 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-bj1zfh" workload cluster
Failed to get logs for Machine kcp-adoption-bj1zfh-control-plane-0, Cluster kcp-adoption-n21zmn/kcp-adoption-bj1zfh: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-n21zmn" namespace
STEP: Deleting cluster kcp-adoption-n21zmn/kcp-adoption-bj1zfh
STEP: Deleting cluster kcp-adoption-bj1zfh
INFO: Waiting for the Cluster kcp-adoption-n21zmn/kcp-adoption-bj1zfh to be deleted
STEP: Waiting for cluster kcp-adoption-bj1zfh to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" test spec
... skipping 115 lines ...
STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-g3twu7
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-g3twu7" workload cluster
Failed to get logs for Machine clusterctl-upgrade-g3twu7-control-plane-nnv2r, Cluster clusterctl-upgrade-ymd90n/clusterctl-upgrade-g3twu7: exit status 2
Failed to get logs for Machine clusterctl-upgrade-g3twu7-md-0-5ddbb76bf5-rdjmf, Cluster clusterctl-upgrade-ymd90n/clusterctl-upgrade-g3twu7: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-ymd90n" namespace
STEP: Deleting cluster clusterctl-upgrade-ymd90n/clusterctl-upgrade-g3twu7
STEP: Deleting cluster clusterctl-upgrade-g3twu7
INFO: Waiting for the Cluster clusterctl-upgrade-ymd90n/clusterctl-upgrade-g3twu7 to be deleted
STEP: Waiting for cluster clusterctl-upgrade-g3twu7 to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" 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-khjzp5" workload cluster
Failed to get logs for Machine self-hosted-khjzp5-control-plane-bq8qz, Cluster self-hosted-gkbppr/self-hosted-khjzp5: exit status 2
Failed to get logs for Machine self-hosted-khjzp5-md-0-6b4dc97fb6-5dq8k, Cluster self-hosted-gkbppr/self-hosted-khjzp5: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-gkbppr" namespace
STEP: Deleting cluster self-hosted-gkbppr/self-hosted-khjzp5
STEP: Deleting cluster self-hosted-khjzp5
INFO: Waiting for the Cluster self-hosted-gkbppr/self-hosted-khjzp5 to be deleted
STEP: Waiting for cluster self-hosted-khjzp5 to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 81 lines ...
INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-with-runtimesdk-e0rcoi/k8s-upgrade-with-runtimesdk-0b6w63-mp-0
INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-with-runtimesdk-e0rcoi/k8s-upgrade-with-runtimesdk-0b6w63-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-0b6w63-f5ddn-24tsc, Cluster k8s-upgrade-with-runtimesdk-e0rcoi/k8s-upgrade-with-runtimesdk-0b6w63: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-0b6w63-md-0-8kczm-7757f6ccb-5bhrr, Cluster k8s-upgrade-with-runtimesdk-e0rcoi/k8s-upgrade-with-runtimesdk-0b6w63: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-0b6w63-md-0-8kczm-7757f6ccb-x2245, Cluster k8s-upgrade-with-runtimesdk-e0rcoi/k8s-upgrade-with-runtimesdk-0b6w63: exit status 2
Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-0b6w63-mp-0, Cluster k8s-upgrade-with-runtimesdk-e0rcoi/k8s-upgrade-with-runtimesdk-0b6w63: exit status 2
STEP: Deleting the workload cluster
STEP: Deleting cluster k8s-upgrade-with-runtimesdk-0b6w63
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 58 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j-md-0-vnln7 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-wyb30j" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-wyb30j-md-0-vnln7-5db56c49bc-tm94h, Cluster k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-wyb30j-s9mxz-2gwl6, Cluster k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-wyb30j-s9mxz-8nnnb, Cluster k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-wyb30j-s9mxz-qq8zp, Cluster k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-wupblp" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j
STEP: Deleting cluster k8s-upgrade-and-conformance-wyb30j
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-wupblp/k8s-upgrade-and-conformance-wyb30j to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-wyb30j to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-xazibd/k8s-upgrade-and-conformance-r396vv-md-0-89clq 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-r396vv" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-r396vv-dxp2h-jpkm8, Cluster k8s-upgrade-and-conformance-xazibd/k8s-upgrade-and-conformance-r396vv: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-r396vv-dxp2h-xfld7, Cluster k8s-upgrade-and-conformance-xazibd/k8s-upgrade-and-conformance-r396vv: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-r396vv-dxp2h-zw954, Cluster k8s-upgrade-and-conformance-xazibd/k8s-upgrade-and-conformance-r396vv: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-r396vv-md-0-89clq-c9d76b9b7-gjvh5, Cluster k8s-upgrade-and-conformance-xazibd/k8s-upgrade-and-conformance-r396vv: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-xazibd" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-xazibd/k8s-upgrade-and-conformance-r396vv
STEP: Deleting cluster k8s-upgrade-and-conformance-r396vv
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-xazibd/k8s-upgrade-and-conformance-r396vv to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-r396vv to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 54 lines ...
STEP: Waiting for deployment node-drain-js9n8v-unevictable-workload/unevictable-pod-sqy 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-js9n8v/node-drain-5iq86s-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-5iq86s" workload cluster
Failed to get logs for Machine node-drain-5iq86s-control-plane-l287s, Cluster node-drain-js9n8v/node-drain-5iq86s: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-js9n8v" namespace
STEP: Deleting cluster node-drain-js9n8v/node-drain-5iq86s
STEP: Deleting cluster node-drain-5iq86s
INFO: Waiting for the Cluster node-drain-js9n8v/node-drain-5iq86s to be deleted
STEP: Waiting for cluster node-drain-5iq86s to be deleted
STEP: Deleting namespace used for hosting the "node-drain" test spec
... skipping 46 lines ...
INFO: Waiting for correct number of replicas to exist
STEP: Scaling the MachineDeployment down to 1
INFO: Scaling machine deployment md-scale-2xd75m/md-scale-osgqra-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-osgqra" workload cluster
Failed to get logs for Machine md-scale-osgqra-control-plane-5xmpn, Cluster md-scale-2xd75m/md-scale-osgqra: exit status 2
Failed to get logs for Machine md-scale-osgqra-md-0-6987ff4955-d99bz, Cluster md-scale-2xd75m/md-scale-osgqra: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-2xd75m" namespace
STEP: Deleting cluster md-scale-2xd75m/md-scale-osgqra
STEP: Deleting cluster md-scale-osgqra
INFO: Waiting for the Cluster md-scale-2xd75m/md-scale-osgqra to be deleted
STEP: Waiting for cluster md-scale-osgqra to be deleted
STEP: Deleting namespace used for hosting the "md-scale" 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-80r7v7" workload cluster
Failed to get logs for Machine self-hosted-80r7v7-jtt9v-2s7z2, Cluster self-hosted-6hhkny/self-hosted-80r7v7: exit status 2
Failed to get logs for Machine self-hosted-80r7v7-md-0-jwpbh-79b69d85cc-ngcz9, Cluster self-hosted-6hhkny/self-hosted-80r7v7: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-6hhkny" namespace
STEP: Deleting cluster self-hosted-6hhkny/self-hosted-80r7v7
STEP: Deleting cluster self-hosted-80r7v7
INFO: Waiting for the Cluster self-hosted-6hhkny/self-hosted-80r7v7 to be deleted
STEP: Waiting for cluster self-hosted-80r7v7 to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 42 lines ...
STEP: Checking all the machines controlled by clusterclass-changes-oj81wi-md-0-mc9f9 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-57mylo/quick-start
INFO: Waiting for ControlPlane rollout to complete.
STEP: Dumping logs from the "clusterclass-changes-oj81wi" workload cluster
Failed to get logs for Machine clusterclass-changes-oj81wi-5kw9c-zs5sm, Cluster clusterclass-changes-57mylo/clusterclass-changes-oj81wi: exit status 2
Failed to get logs for Machine clusterclass-changes-oj81wi-md-0-mc9f9-5f97cc568c-kn5rl, Cluster clusterclass-changes-57mylo/clusterclass-changes-oj81wi: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-57mylo" namespace
STEP: Deleting cluster clusterclass-changes-57mylo/clusterclass-changes-oj81wi
STEP: Deleting cluster clusterclass-changes-oj81wi
INFO: Waiting for the Cluster clusterclass-changes-57mylo/clusterclass-changes-oj81wi to be deleted
STEP: Waiting for cluster clusterclass-changes-oj81wi to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 48 lines ...
  testing.tRunner(0xc000603a00, 0x22db160)
  	/usr/local/go/src/testing/testing.go:1439 +0x102
  created by testing.(*T).Run
  	/usr/local/go/src/testing/testing.go:1486 +0x35f
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-3chlu7-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 3373.765 seconds
FAIL! -- 17 Passed | 1 Failed | 0 Pending | 3 Skipped


Ginkgo ran 1 suite in 57m22.175730851s
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 26079
++ pgrep -f 'ctr -n moby events'
+ kill 26080
... skipping 21 lines ...