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 20:29
Elapsed52m21s
Revisionmain

Test Failures


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

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.002s.
Expected
    <*errors.fundamental | 0xc00095d6b0>: {
        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 1129 lines ...
INFO: Waiting for correct number of replicas to exist
STEP: Scaling the MachineDeployment down to 1
INFO: Scaling machine deployment md-scale-28aikn/md-scale-eow4ym-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-eow4ym" workload cluster
Failed to get logs for Machine md-scale-eow4ym-control-plane-zjbpp, Cluster md-scale-28aikn/md-scale-eow4ym: exit status 2
Failed to get logs for Machine md-scale-eow4ym-md-0-8484dd5fd5-pcfcb, Cluster md-scale-28aikn/md-scale-eow4ym: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-28aikn" namespace
STEP: Deleting cluster md-scale-28aikn/md-scale-eow4ym
STEP: Deleting cluster md-scale-eow4ym
INFO: Waiting for the Cluster md-scale-28aikn/md-scale-eow4ym to be deleted
STEP: Waiting for cluster md-scale-eow4ym to be deleted
STEP: Deleting namespace used for hosting the "md-scale" 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-xwsos1/machine-pool-rcdizk-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-rcdizk" workload cluster
Failed to get logs for Machine machine-pool-rcdizk-control-plane-kwwnl, Cluster machine-pool-xwsos1/machine-pool-rcdizk: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-xwsos1" namespace
STEP: Deleting cluster machine-pool-xwsos1/machine-pool-rcdizk
STEP: Deleting cluster machine-pool-rcdizk
INFO: Waiting for the Cluster machine-pool-xwsos1/machine-pool-rcdizk to be deleted
STEP: Waiting for cluster machine-pool-rcdizk 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-d86ifo" workload cluster
Failed to get logs for Machine mhc-remediation-d86ifo-control-plane-l7q99, Cluster mhc-remediation-3b429m/mhc-remediation-d86ifo: exit status 2
Failed to get logs for Machine mhc-remediation-d86ifo-md-0-66f8c785dc-29phh, Cluster mhc-remediation-3b429m/mhc-remediation-d86ifo: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-3b429m" namespace
STEP: Deleting cluster mhc-remediation-3b429m/mhc-remediation-d86ifo
STEP: Deleting cluster mhc-remediation-d86ifo
INFO: Waiting for the Cluster mhc-remediation-3b429m/mhc-remediation-d86ifo to be deleted
STEP: Waiting for cluster mhc-remediation-d86ifo 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-xsgdhc" workload cluster
Failed to get logs for Machine self-hosted-xsgdhc-control-plane-m6k7m, Cluster self-hosted-w5vyik/self-hosted-xsgdhc: exit status 2
Failed to get logs for Machine self-hosted-xsgdhc-md-0-7fbdd999d5-flz4k, Cluster self-hosted-w5vyik/self-hosted-xsgdhc: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-w5vyik" namespace
STEP: Deleting cluster self-hosted-w5vyik/self-hosted-xsgdhc
STEP: Deleting cluster self-hosted-xsgdhc
INFO: Waiting for the Cluster self-hosted-w5vyik/self-hosted-xsgdhc to be deleted
STEP: Waiting for cluster self-hosted-xsgdhc to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" 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-fqbexv" workload cluster
Failed to get logs for Machine kcp-adoption-fqbexv-control-plane-0, Cluster kcp-adoption-80jbql/kcp-adoption-fqbexv: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-80jbql" namespace
STEP: Deleting cluster kcp-adoption-80jbql/kcp-adoption-fqbexv
STEP: Deleting cluster kcp-adoption-fqbexv
INFO: Waiting for the Cluster kcp-adoption-80jbql/kcp-adoption-fqbexv to be deleted
STEP: Waiting for cluster kcp-adoption-fqbexv to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" 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-l1vpt5" workload cluster
Failed to get logs for Machine mhc-remediation-l1vpt5-control-plane-c5k6f, Cluster mhc-remediation-drs3q9/mhc-remediation-l1vpt5: exit status 2
Failed to get logs for Machine mhc-remediation-l1vpt5-control-plane-f54mn, Cluster mhc-remediation-drs3q9/mhc-remediation-l1vpt5: exit status 2
Failed to get logs for Machine mhc-remediation-l1vpt5-control-plane-xzjp6, Cluster mhc-remediation-drs3q9/mhc-remediation-l1vpt5: exit status 2
Failed to get logs for Machine mhc-remediation-l1vpt5-md-0-df5885bd-j6nv4, Cluster mhc-remediation-drs3q9/mhc-remediation-l1vpt5: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-drs3q9" namespace
STEP: Deleting cluster mhc-remediation-drs3q9/mhc-remediation-l1vpt5
STEP: Deleting cluster mhc-remediation-l1vpt5
INFO: Waiting for the Cluster mhc-remediation-drs3q9/mhc-remediation-l1vpt5 to be deleted
STEP: Waiting for cluster mhc-remediation-l1vpt5 to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-fwkwkv-unevictable-workload/unevictable-pod-0vc 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-fwkwkv/node-drain-v07cop-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-v07cop" workload cluster
Failed to get logs for Machine node-drain-v07cop-control-plane-xkrc6, Cluster node-drain-fwkwkv/node-drain-v07cop: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-fwkwkv" namespace
STEP: Deleting cluster node-drain-fwkwkv/node-drain-v07cop
STEP: Deleting cluster node-drain-v07cop
INFO: Waiting for the Cluster node-drain-fwkwkv/node-drain-v07cop to be deleted
STEP: Waiting for cluster node-drain-v07cop to be deleted
STEP: Deleting namespace used for hosting the "node-drain" 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-o76fcr/k8s-upgrade-and-conformance-v55ixm-md-0-vjs4v 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-v55ixm" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-v55ixm-md-0-vjs4v-76df966454-427pf, Cluster k8s-upgrade-and-conformance-o76fcr/k8s-upgrade-and-conformance-v55ixm: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-v55ixm-nqzqk-nqr9f, Cluster k8s-upgrade-and-conformance-o76fcr/k8s-upgrade-and-conformance-v55ixm: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-v55ixm-nqzqk-t8g7b, Cluster k8s-upgrade-and-conformance-o76fcr/k8s-upgrade-and-conformance-v55ixm: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-v55ixm-nqzqk-w2ckf, Cluster k8s-upgrade-and-conformance-o76fcr/k8s-upgrade-and-conformance-v55ixm: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-o76fcr" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-o76fcr/k8s-upgrade-and-conformance-v55ixm
STEP: Deleting cluster k8s-upgrade-and-conformance-v55ixm
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-o76fcr/k8s-upgrade-and-conformance-v55ixm to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-v55ixm to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-ms558p-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-ms558p" workload cluster
Failed to get logs for Machine quick-start-ms558p-control-plane-qqv6x, Cluster quick-start-p3rayk/quick-start-ms558p: exit status 2
Failed to get logs for Machine quick-start-ms558p-md-0-88644b668-tgcmn, Cluster quick-start-p3rayk/quick-start-ms558p: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-p3rayk" namespace
STEP: Deleting cluster quick-start-p3rayk/quick-start-ms558p
STEP: Deleting cluster quick-start-ms558p
INFO: Waiting for the Cluster quick-start-p3rayk/quick-start-ms558p to be deleted
STEP: Waiting for cluster quick-start-ms558p 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-sulo2z-md-0-45qlz are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-sulo2z" workload cluster
Failed to get logs for Machine quick-start-sulo2z-52z9k-qn62d, Cluster quick-start-qpegdi/quick-start-sulo2z: exit status 2
Failed to get logs for Machine quick-start-sulo2z-md-0-45qlz-777b4c7cf5-6jvfg, Cluster quick-start-qpegdi/quick-start-sulo2z: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-qpegdi" namespace
STEP: Deleting cluster quick-start-qpegdi/quick-start-sulo2z
STEP: Deleting cluster quick-start-sulo2z
INFO: Waiting for the Cluster quick-start-qpegdi/quick-start-sulo2z to be deleted
STEP: Waiting for cluster quick-start-sulo2z 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-en9on6/k8s-upgrade-and-conformance-f6xx6i-md-0-v29mj 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-f6xx6i" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-f6xx6i-9kkbv-tdzpd, Cluster k8s-upgrade-and-conformance-en9on6/k8s-upgrade-and-conformance-f6xx6i: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-f6xx6i-md-0-v29mj-855ff5b85b-4tp2p, Cluster k8s-upgrade-and-conformance-en9on6/k8s-upgrade-and-conformance-f6xx6i: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-f6xx6i-md-0-v29mj-855ff5b85b-xrdsz, Cluster k8s-upgrade-and-conformance-en9on6/k8s-upgrade-and-conformance-f6xx6i: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-en9on6" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-en9on6/k8s-upgrade-and-conformance-f6xx6i
STEP: Deleting cluster k8s-upgrade-and-conformance-f6xx6i
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-en9on6/k8s-upgrade-and-conformance-f6xx6i to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-f6xx6i 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-5h5qfr/k8s-upgrade-and-conformance-nw4b61-md-0-pg2bw 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-nw4b61" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-nw4b61-md-0-pg2bw-85f499cc94-dc7bb, Cluster k8s-upgrade-and-conformance-5h5qfr/k8s-upgrade-and-conformance-nw4b61: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-nw4b61-zrd79-kg6x5, Cluster k8s-upgrade-and-conformance-5h5qfr/k8s-upgrade-and-conformance-nw4b61: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-nw4b61-zrd79-m92sw, Cluster k8s-upgrade-and-conformance-5h5qfr/k8s-upgrade-and-conformance-nw4b61: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-nw4b61-zrd79-px96f, Cluster k8s-upgrade-and-conformance-5h5qfr/k8s-upgrade-and-conformance-nw4b61: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-5h5qfr" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-5h5qfr/k8s-upgrade-and-conformance-nw4b61
STEP: Deleting cluster k8s-upgrade-and-conformance-nw4b61
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-5h5qfr/k8s-upgrade-and-conformance-nw4b61 to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-nw4b61 to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-jnvgcm-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-jnvgcm" workload cluster
Failed to get logs for Machine quick-start-jnvgcm-control-plane-b7lgw, Cluster quick-start-pzzm7o/quick-start-jnvgcm: exit status 2
Failed to get logs for Machine quick-start-jnvgcm-md-0-7c847c957-v4nf6, Cluster quick-start-pzzm7o/quick-start-jnvgcm: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-pzzm7o" namespace
STEP: Deleting cluster quick-start-pzzm7o/quick-start-jnvgcm
STEP: Deleting cluster quick-start-jnvgcm
INFO: Waiting for the Cluster quick-start-pzzm7o/quick-start-jnvgcm to be deleted
STEP: Waiting for cluster quick-start-jnvgcm to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-d5a2zu" workload cluster
Failed to get logs for Machine md-rollout-d5a2zu-control-plane-cslf4, Cluster md-rollout-hwi84x/md-rollout-d5a2zu: exit status 2
Failed to get logs for Machine md-rollout-d5a2zu-md-0-6444dd7cb7-tn5dl, Cluster md-rollout-hwi84x/md-rollout-d5a2zu: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-hwi84x" namespace
STEP: Deleting cluster md-rollout-hwi84x/md-rollout-d5a2zu
STEP: Deleting cluster md-rollout-d5a2zu
INFO: Waiting for the Cluster md-rollout-hwi84x/md-rollout-d5a2zu to be deleted
STEP: Waiting for cluster md-rollout-d5a2zu to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" test spec
... skipping 42 lines ...
STEP: Checking all the machines controlled by clusterclass-changes-rktgeu-md-0-55btt 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-4m623m/quick-start
INFO: Waiting for ControlPlane rollout to complete.
STEP: Dumping logs from the "clusterclass-changes-rktgeu" workload cluster
Failed to get logs for Machine clusterclass-changes-rktgeu-md-0-55btt-7fcfcd5844-mrzq4, Cluster clusterclass-changes-4m623m/clusterclass-changes-rktgeu: exit status 2
Failed to get logs for Machine clusterclass-changes-rktgeu-qrprw-tgt44, Cluster clusterclass-changes-4m623m/clusterclass-changes-rktgeu: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-4m623m" namespace
STEP: Deleting cluster clusterclass-changes-4m623m/clusterclass-changes-rktgeu
STEP: Deleting cluster clusterclass-changes-rktgeu
INFO: Waiting for the Cluster clusterclass-changes-4m623m/clusterclass-changes-rktgeu to be deleted
STEP: Waiting for cluster clusterclass-changes-rktgeu to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 127 lines ...
INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-with-runtimesdk-eo6exg/k8s-upgrade-with-runtimesdk-dtnexa-mp-0
INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-with-runtimesdk-eo6exg/k8s-upgrade-with-runtimesdk-dtnexa-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-dtnexa-md-0-l7ln2-56dc6fc54c-9ckhx, Cluster k8s-upgrade-with-runtimesdk-eo6exg/k8s-upgrade-with-runtimesdk-dtnexa: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-dtnexa-md-0-l7ln2-56dc6fc54c-xqsxm, Cluster k8s-upgrade-with-runtimesdk-eo6exg/k8s-upgrade-with-runtimesdk-dtnexa: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-dtnexa-pwfck-q79m8, Cluster k8s-upgrade-with-runtimesdk-eo6exg/k8s-upgrade-with-runtimesdk-dtnexa: exit status 2
Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-dtnexa-mp-0, Cluster k8s-upgrade-with-runtimesdk-eo6exg/k8s-upgrade-with-runtimesdk-dtnexa: exit status 2
STEP: Deleting the workload cluster
STEP: Deleting cluster k8s-upgrade-with-runtimesdk-dtnexa
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 119 lines ...
STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-6b7c9b
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-6b7c9b" workload cluster
Failed to get logs for Machine clusterctl-upgrade-6b7c9b-control-plane-6k9vz, Cluster clusterctl-upgrade-zloayv/clusterctl-upgrade-6b7c9b: exit status 2
Failed to get logs for Machine clusterctl-upgrade-6b7c9b-md-0-789bc9599c-clq62, Cluster clusterctl-upgrade-zloayv/clusterctl-upgrade-6b7c9b: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-zloayv" namespace
STEP: Deleting cluster clusterctl-upgrade-zloayv/clusterctl-upgrade-6b7c9b
STEP: Deleting cluster clusterctl-upgrade-6b7c9b
INFO: Waiting for the Cluster clusterctl-upgrade-zloayv/clusterctl-upgrade-6b7c9b to be deleted
STEP: Waiting for cluster clusterctl-upgrade-6b7c9b to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
... skipping 4 lines ...
When testing clusterctl upgrades [clusterctl-Upgrade]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterctl_upgrade_test.go:26
  Should create a management cluster and then upgrade all the providers
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterctl_upgrade.go:152
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-d5duxi-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 2758.731 seconds
FAIL! -- 16 Passed | 1 Failed | 0 Pending | 4 Skipped


Ginkgo ran 1 suite in 47m1.342775069s
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 25963
++ pgrep -f 'ctr -n moby events'
+ kill 25964
... skipping 21 lines ...