This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 18 succeeded
Started2022-09-29 19:05
Elapsed36m9s
Revisionmain

Test Failures


capi-e2e [It] When testing clusterctl upgrades (v0.3=>current) Should create a management cluster and then upgrade all the providers 5m1s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\s\[It\]\sWhen\stesting\sclusterctl\supgrades\s\(v0\.3\=\>current\)\sShould\screate\sa\smanagement\scluster\sand\sthen\supgrade\sall\sthe\sproviders$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:144
sigs.k8s.io/cluster-api/test/framework.WaitForClusterToProvision({0x2603f88?, 0xc000472ac0}, {{0x7f766c27ac20?, 0xc00066aaf0?}, 0xc0010afba0?}, {0xc000c79cc0, 0x2, 0x2})
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:144 +0x25a
sigs.k8s.io/cluster-api/test/framework.DiscoveryAndWaitForCluster({0x2603f88?, 0xc000472ac0}, {{0x7f766c27ac20, 0xc00066aaf0}, {0xc00183d100, 0x19}, {0xc00183d280, 0x19}}, {0xc000c79cc0, 0x2, ...})
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:205 +0x490
sigs.k8s.io/cluster-api/test/framework/clusterctl.ApplyClusterTemplateAndWait({_, _}, {{0x2612408, 0xc000472f80}, {{0xc0006eeab0, 0x22}, {0xc00017c0f6, 0x31}, {0xc00017c128, 0x17}, ...}, ...}, ...)
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/clusterctl/clusterctl_helpers.go:292 +0xaed
sigs.k8s.io/cluster-api/test/e2e.ClusterctlUpgradeSpec.func2()
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterctl_upgrade.go:182 +0x5ba
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 18 Passed Tests

Show 11 Skipped Tests

Error lines from build-log.txt

... skipping 829 lines ...
Status: Downloaded newer image for quay.io/jetstack/cert-manager-controller:v1.9.1
quay.io/jetstack/cert-manager-controller:v1.9.1
+ export GINKGO_NODES=3
+ GINKGO_NODES=3
+ export GINKGO_NOCOLOR=true
+ GINKGO_NOCOLOR=true
+ export GINKGO_ARGS=--fail-fast
+ GINKGO_ARGS=--fail-fast
+ export E2E_CONF_FILE=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml
+ E2E_CONF_FILE=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml
+ export ARTIFACTS=/logs/artifacts
+ ARTIFACTS=/logs/artifacts
+ export SKIP_RESOURCE_CLEANUP=false
+ SKIP_RESOURCE_CLEANUP=false
... skipping 80 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-kcp-scale-in --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-kcp-scale-in.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-ipv6 --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-ipv6.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-topology --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-topology.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-ignition --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/main/cluster-template-ignition.yaml
mkdir -p /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/test-extension
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/extension/config/default > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/test-extension/deployment.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/ginkgo-v2.1.4 -v --trace --tags=e2e --focus="" -skip="\[Conformance\]" -skip="\[K8s-Upgrade\]|\[IPv6\]" --nodes=3 --timeout=2h --no-color=true --output-dir="/logs/artifacts" --junit-report="junit.e2e_suite.1.xml" --fail-fast . -- \
    -e2e.artifacts-folder="/logs/artifacts" \
    -e2e.config="/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml" \
    -e2e.skip-resource-cleanup=false -e2e.use-existing-cluster=false
go: downloading k8s.io/apimachinery v0.25.0
go: downloading k8s.io/api v0.25.0
go: downloading github.com/onsi/gomega v1.20.0
... skipping 206 lines ...
    machinedeployment.cluster.x-k8s.io/md-rollout-vh0t15-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/md-rollout-vh0t15-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/md-rollout-vh0t15 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-rollout-vh0t15-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-rollout-vh0t15-md-0 created

    Failed to get logs for Machine md-rollout-vh0t15-control-plane-pqn9h, Cluster md-rollout-r5mc1h/md-rollout-vh0t15: exit status 2
    Failed to get logs for Machine md-rollout-vh0t15-md-0-554ddf9c85-m85mw, Cluster md-rollout-r5mc1h/md-rollout-vh0t15: error creating container exec: Error response from daemon: No such container: md-rollout-vh0t15-md-0-554ddf9c85-m85mw
    Failed to get logs for Machine md-rollout-vh0t15-md-0-666b6d58c7-ql4cz, Cluster md-rollout-r5mc1h/md-rollout-vh0t15: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "md-rollout" test spec 09/29/22 19:13:45.606
    INFO: Creating namespace md-rollout-r5mc1h
    INFO: Creating event watcher for namespace "md-rollout-r5mc1h"
... skipping 50 lines ...
    machinepool.cluster.x-k8s.io/machine-pool-b5zyd4-mp-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/machine-pool-b5zyd4-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/machine-pool-b5zyd4 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/machine-pool-b5zyd4-dmp-0 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/machine-pool-b5zyd4-control-plane created

    Failed to get logs for Machine machine-pool-b5zyd4-control-plane-4pftn, Cluster machine-pool-pum7zm/machine-pool-b5zyd4: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "machine-pool" test spec 09/29/22 19:17:05.374
    INFO: Creating namespace machine-pool-pum7zm
    INFO: Creating event watcher for namespace "machine-pool-pum7zm"
... skipping 62 lines ...
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
    kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
    configmap/cni-clusterctl-upgrade-6j7hmm-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/clusterctl-upgrade-6j7hmm-crs-0 created
    cluster.cluster.x-k8s.io/clusterctl-upgrade-6j7hmm created

    Failed to get logs for Machine clusterctl-upgrade-gvb8ds-control-plane-rxlnp, Cluster clusterctl-upgrade-bm2ri3/clusterctl-upgrade-gvb8ds: exit status 2
    Failed to get logs for Machine clusterctl-upgrade-gvb8ds-md-0-5f55d7cf78-8xb7w, Cluster clusterctl-upgrade-bm2ri3/clusterctl-upgrade-gvb8ds: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec 09/29/22 19:13:45.624
    INFO: Creating namespace clusterctl-upgrade-bm2ri3
    INFO: Creating event watcher for namespace "clusterctl-upgrade-bm2ri3"
... skipping 110 lines ...
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
    kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
    configmap/cni-self-hosted-ienn00-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/self-hosted-ienn00-crs-0 created
    cluster.cluster.x-k8s.io/self-hosted-ienn00 created

    Failed to get logs for Machine self-hosted-ienn00-4m66s-t4bw4, Cluster self-hosted-eb47bf/self-hosted-ienn00: exit status 2
    Failed to get logs for Machine self-hosted-ienn00-md-0-zckfb-cb8ff7f7b-gp9lf, Cluster self-hosted-eb47bf/self-hosted-ienn00: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "self-hosted" test spec 09/29/22 19:21:49.464
    INFO: Creating namespace self-hosted-eb47bf
    INFO: Creating event watcher for namespace "self-hosted-eb47bf"
... skipping 87 lines ...
    machinedeployment.cluster.x-k8s.io/quick-start-j03c8p-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/quick-start-j03c8p-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/quick-start-j03c8p created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-j03c8p-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-j03c8p-md-0 created

    Failed to get logs for Machine quick-start-j03c8p-control-plane-ln2z6, Cluster quick-start-ohznm7/quick-start-j03c8p: exit status 2
    Failed to get logs for Machine quick-start-j03c8p-md-0-7c5b57fc94-cpfl7, Cluster quick-start-ohznm7/quick-start-j03c8p: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "quick-start" test spec 09/29/22 19:29:01.61
    INFO: Creating namespace quick-start-ohznm7
    INFO: Creating event watcher for namespace "quick-start-ohznm7"
... skipping 44 lines ...
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
    kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
    configmap/cni-k8s-upgrade-and-conformance-jvrhcq-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-and-conformance-jvrhcq-crs-0 created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-jvrhcq created

    Failed to get logs for Machine k8s-upgrade-and-conformance-jvrhcq-md-0-9ft76-86b6bcc785-ftjdk, Cluster k8s-upgrade-and-conformance-51a6wj/k8s-upgrade-and-conformance-jvrhcq: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-jvrhcq-mgl67-7prd4, Cluster k8s-upgrade-and-conformance-51a6wj/k8s-upgrade-and-conformance-jvrhcq: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-jvrhcq-mgl67-9x9dz, Cluster k8s-upgrade-and-conformance-51a6wj/k8s-upgrade-and-conformance-jvrhcq: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-jvrhcq-mgl67-k46nr, Cluster k8s-upgrade-and-conformance-51a6wj/k8s-upgrade-and-conformance-jvrhcq: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec 09/29/22 19:13:45.587
    INFO: Creating namespace k8s-upgrade-and-conformance-51a6wj
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-51a6wj"
... skipping 58 lines ...
    machinedeployment.cluster.x-k8s.io/node-drain-qzs79n-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/node-drain-qzs79n-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/node-drain-qzs79n created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/node-drain-qzs79n-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/node-drain-qzs79n-md-0 created

    Failed to get logs for Machine node-drain-qzs79n-control-plane-k5kq7, Cluster node-drain-kies59/node-drain-qzs79n: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "node-drain" test spec 09/29/22 19:24:12.849
    INFO: Creating namespace node-drain-kies59
    INFO: Creating event watcher for namespace "node-drain-kies59"
... skipping 56 lines ...
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
    kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
    configmap/cni-quick-start-dx9pki-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/quick-start-dx9pki-crs-0 created
    cluster.cluster.x-k8s.io/quick-start-dx9pki created

    Failed to get logs for Machine quick-start-dx9pki-l5f5p-gj52r, Cluster quick-start-salju2/quick-start-dx9pki: exit status 2
    Failed to get logs for Machine quick-start-dx9pki-md-0-rvv2x-d4d5bfff8-q5777, Cluster quick-start-salju2/quick-start-dx9pki: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "quick-start" test spec 09/29/22 19:31:50.182
    INFO: Creating namespace quick-start-salju2
    INFO: Creating event watcher for namespace "quick-start-salju2"
... skipping 44 lines ...
    machinedeployment.cluster.x-k8s.io/quick-start-909pds-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/quick-start-909pds-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/quick-start-909pds created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-909pds-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-909pds-md-0 created

    Failed to get logs for Machine quick-start-909pds-control-plane-tnqrd, Cluster quick-start-ggrb83/quick-start-909pds: exit status 2
    Failed to get logs for Machine quick-start-909pds-md-0-79d56d6dc-l9t6n, Cluster quick-start-ggrb83/quick-start-909pds: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "quick-start" test spec 09/29/22 19:33:44.771
    INFO: Creating namespace quick-start-ggrb83
    INFO: Creating event watcher for namespace "quick-start-ggrb83"
... skipping 44 lines ...
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
    kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
    configmap/cni-k8s-upgrade-and-conformance-b2xfb1-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-and-conformance-b2xfb1-crs-0 created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-b2xfb1 created

    Failed to get logs for Machine k8s-upgrade-and-conformance-b2xfb1-md-0-pn7lk-5b547cd7bd-lpz6r, Cluster k8s-upgrade-and-conformance-0bzeyv/k8s-upgrade-and-conformance-b2xfb1: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-b2xfb1-md-0-pn7lk-5b547cd7bd-rs7k2, Cluster k8s-upgrade-and-conformance-0bzeyv/k8s-upgrade-and-conformance-b2xfb1: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-b2xfb1-rrzqp-nk2gw, Cluster k8s-upgrade-and-conformance-0bzeyv/k8s-upgrade-and-conformance-b2xfb1: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec 09/29/22 19:31:40.805
    INFO: Creating namespace k8s-upgrade-and-conformance-0bzeyv
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-0bzeyv"
... skipping 39 lines ...
  << End Captured GinkgoWriter Output
------------------------------
When testing clusterctl upgrades (v0.3=>current)
  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:177
------------------------------
• [FAILED] [301.114 seconds]
When testing clusterctl upgrades (v0.3=>current)
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterctl_upgrade_test.go:26
  [It] 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:177

  Begin Captured StdOut/StdErr Output >>
... skipping 77 lines ...
    machinedeployment.cluster.x-k8s.io/clusterctl-upgrade-4qfk6f-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/clusterctl-upgrade-4qfk6f-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-4qfk6f created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-4qfk6f-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-4qfk6f-md-0 created

    Failed to get logs for Machine clusterctl-upgrade-w68qxb-control-plane-tqfmd, Cluster clusterctl-upgrade-tbx9cl/clusterctl-upgrade-w68qxb: exit status 2
    Failed to get logs for Machine clusterctl-upgrade-w68qxb-md-0-7d8db4858d-lc7tz, Cluster clusterctl-upgrade-tbx9cl/clusterctl-upgrade-w68qxb: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec 09/29/22 19:31:49.4
    INFO: Creating namespace clusterctl-upgrade-tbx9cl
    INFO: Creating event watcher for namespace "clusterctl-upgrade-tbx9cl"
... skipping 114 lines ...
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
    kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
    configmap/cni-clusterclass-changes-i5mkii-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/clusterclass-changes-i5mkii-crs-0 created
    cluster.cluster.x-k8s.io/clusterclass-changes-i5mkii created

    Failed to get logs for Machine clusterclass-changes-i5mkii-6wbhq-6bjnw, Cluster clusterclass-changes-yy8wrc/clusterclass-changes-i5mkii: exit status 2
    Failed to get logs for Machine clusterclass-changes-i5mkii-md-0-znk2f-74694649-gmm9m, Cluster clusterclass-changes-yy8wrc/clusterclass-changes-i5mkii: error creating container exec: Error response from daemon: No such container: clusterclass-changes-i5mkii-md-0-znk2f-74694649-gmm9m
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "clusterclass-changes" test spec 09/29/22 19:40:28.15
    INFO: Creating namespace clusterclass-changes-yy8wrc
    INFO: Creating event watcher for namespace "clusterclass-changes-yy8wrc"
... skipping 27 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:169
------------------------------
[SynchronizedAfterSuite] PASSED [0.000 seconds]
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:169
------------------------------
Failed to get logs for the bootstrap cluster node test-liulce-control-plane: exit status 2
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:169
------------------------------
[SynchronizedAfterSuite] PASSED [23.458 seconds]
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:169

  Begin Captured StdOut/StdErr Output >>
    Failed to get logs for the bootstrap cluster node test-liulce-control-plane: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec 09/29/22 19:41:10.127
    INFO: Deleting namespace clusterctl-upgrade-tbx9cl
    STEP: Dumping logs from the bootstrap cluster 09/29/22 19:41:21.205
... skipping 7 lines ...
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------


Summarizing 3 Failures:
  [FAIL] When testing clusterctl upgrades (v0.3=>current) [It] Should create a management cluster and then upgrade all the providers
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:144
  [INTERRUPTED] 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:132
  [INTERRUPTED] When testing clusterctl upgrades (v1.2=>current) [AfterEach] 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:393

Ran 13 of 24 Specs in 1758.962 seconds
FAIL! - Interrupted by Other Ginkgo Process -- 10 Passed | 3 Failed | 0 Pending | 11 Skipped


Ginkgo ran 1 suite in 30m29.591380797s

Test Suite Failed
make: *** [Makefile:133: run] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ cleanup
++ pgrep -f 'docker events'
+ kill 26123
++ pgrep -f 'ctr -n moby events'
+ kill 26124
... skipping 22 lines ...