This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 22 succeeded
Started2022-09-28 21:51
Elapsed55m45s
Revisionmain

Test Failures


capi-e2e [It] When testing Cluster API working on self-hosted clusters using ClusterClass [ClusterClass] Should pivot the bootstrap cluster to a self-hosted cluster 12m38s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\s\[It\]\sWhen\stesting\sCluster\sAPI\sworking\son\sself\-hosted\sclusters\susing\sClusterClass\s\[ClusterClass\]\sShould\spivot\sthe\sbootstrap\scluster\sto\sa\sself\-hosted\scluster$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:176
sigs.k8s.io/cluster-api/test/framework.WaitForClusterDeleted({0x26000c8?, 0xc00057e1c0}, {{0x7f6e3c6e0360?, 0xc000362d20?}, 0xc00099a700?}, {0xc0001cb5c0, 0x2, 0x2})
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:176 +0x176
sigs.k8s.io/cluster-api/test/framework.DeleteAllClustersAndWait({0x26000c8?, 0xc00057e1c0}, {{0x260c810?, 0xc000362d20?}, {0xc001bc8f90?, 0x12?}}, {0xc0001cb5c0, 0x2, 0x2})
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:272 +0x439
sigs.k8s.io/cluster-api/test/e2e.dumpSpecResourcesAndCleanup({0x26000c8, 0xc00057e1c0}, {0x227a8aa, 0xb}, {0x260e548, 0xc0022a48c0}, {0xc000a99cc0, 0xf}, 0xc00049fe40, 0xc0008ca380, ...)
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/common.go:86 +0x48a
sigs.k8s.io/cluster-api/test/e2e.SelfHostedSpec.func3()
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/self_hosted.go:265 +0xa3e
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 22 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 835 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 78 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/cluster-template-kcp-scale-in --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/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/cluster-template-ipv6 --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/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/cluster-template-topology --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/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/cluster-template-ignition --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/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 github.com/blang/semver v3.5.1+incompatible
go: downloading k8s.io/apimachinery v0.25.0
go: downloading github.com/onsi/gomega v1.20.0
... skipping 206 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-8o5tbr-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/quick-start-8o5tbr-crs-0 created
    cluster.cluster.x-k8s.io/quick-start-8o5tbr created

    Failed to get logs for Machine quick-start-8o5tbr-h7m7z-tbtrf, Cluster quick-start-ikry3x/quick-start-8o5tbr: exit status 2
    Failed to get logs for Machine quick-start-8o5tbr-md-0-qt5r8-6dbd7fdcdd-8bhct, Cluster quick-start-ikry3x/quick-start-8o5tbr: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "quick-start" test spec 09/28/22 22:03:30.262
    INFO: Creating namespace quick-start-ikry3x
    INFO: Creating event watcher for namespace "quick-start-ikry3x"
... skipping 46 lines ...
    machinedeployment.cluster.x-k8s.io/md-scale-4e1nei-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/md-scale-4e1nei-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/md-scale-4e1nei created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-scale-4e1nei-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-scale-4e1nei-md-0 created

    Failed to get logs for Machine md-scale-4e1nei-control-plane-mjs8m, Cluster md-scale-brjzr6/md-scale-4e1nei: exit status 2
    Failed to get logs for Machine md-scale-4e1nei-md-0-85c5856f5d-xmwsx, Cluster md-scale-brjzr6/md-scale-4e1nei: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "md-scale" test spec 09/28/22 22:03:30.221
    INFO: Creating namespace md-scale-brjzr6
    INFO: Creating event watcher for namespace "md-scale-brjzr6"
... skipping 51 lines ...
    machinehealthcheck.cluster.x-k8s.io/mhc-remediation-iyicaw-mhc-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/mhc-remediation-iyicaw-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/mhc-remediation-iyicaw created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-iyicaw-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-iyicaw-md-0 created

    Failed to get logs for Machine mhc-remediation-iyicaw-control-plane-sdsgw, Cluster mhc-remediation-oc5pbo/mhc-remediation-iyicaw: exit status 2
    Failed to get logs for Machine mhc-remediation-iyicaw-md-0-756cf5885f-vpd5c, Cluster mhc-remediation-oc5pbo/mhc-remediation-iyicaw: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "mhc-remediation" test spec 09/28/22 22:06:17.402
    INFO: Creating namespace mhc-remediation-oc5pbo
    INFO: Creating event watcher for namespace "mhc-remediation-oc5pbo"
... skipping 51 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-pxyivv-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-and-conformance-pxyivv-crs-0 created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-pxyivv created

    Failed to get logs for Machine k8s-upgrade-and-conformance-pxyivv-jxjxv-jk558, Cluster k8s-upgrade-and-conformance-1x8pta/k8s-upgrade-and-conformance-pxyivv: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-pxyivv-jxjxv-p4p4v, Cluster k8s-upgrade-and-conformance-1x8pta/k8s-upgrade-and-conformance-pxyivv: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-pxyivv-jxjxv-s7qxs, Cluster k8s-upgrade-and-conformance-1x8pta/k8s-upgrade-and-conformance-pxyivv: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-pxyivv-md-0-45g72-5dcd9d467c-6bjfx, Cluster k8s-upgrade-and-conformance-1x8pta/k8s-upgrade-and-conformance-pxyivv: 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/28/22 22:03:30.262
    INFO: Creating namespace k8s-upgrade-and-conformance-1x8pta
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-1x8pta"
... skipping 59 lines ...
    machinehealthcheck.cluster.x-k8s.io/mhc-remediation-9cxena-mhc-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/mhc-remediation-9cxena-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/mhc-remediation-9cxena created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-9cxena-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-9cxena-md-0 created

    Failed to get logs for Machine mhc-remediation-9cxena-control-plane-j8vqf, Cluster mhc-remediation-lcbmgb/mhc-remediation-9cxena: exit status 2
    Failed to get logs for Machine mhc-remediation-9cxena-control-plane-n56bk, Cluster mhc-remediation-lcbmgb/mhc-remediation-9cxena: exit status 2
    Failed to get logs for Machine mhc-remediation-9cxena-control-plane-zn5xx, Cluster mhc-remediation-lcbmgb/mhc-remediation-9cxena: exit status 2
    Failed to get logs for Machine mhc-remediation-9cxena-md-0-b9b7cbf6-p95gl, Cluster mhc-remediation-lcbmgb/mhc-remediation-9cxena: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "mhc-remediation" test spec 09/28/22 22:10:37.926
    INFO: Creating namespace mhc-remediation-lcbmgb
    INFO: Creating event watcher for namespace "mhc-remediation-lcbmgb"
... skipping 63 lines ...
    machinedeployment.cluster.x-k8s.io/clusterctl-upgrade-u87j82-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/clusterctl-upgrade-u87j82-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-u87j82 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-u87j82-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-u87j82-md-0 created

    Failed to get logs for Machine clusterctl-upgrade-hjxnzz-control-plane-g92q5, Cluster clusterctl-upgrade-9cczw1/clusterctl-upgrade-hjxnzz: exit status 2
    Failed to get logs for Machine clusterctl-upgrade-hjxnzz-md-0-5785b55884-4blc8, Cluster clusterctl-upgrade-9cczw1/clusterctl-upgrade-hjxnzz: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec 09/28/22 22:05:58.243
    INFO: Creating namespace clusterctl-upgrade-9cczw1
    INFO: Creating event watcher for namespace "clusterctl-upgrade-9cczw1"
... skipping 109 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-qyk6ea-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/clusterclass-changes-qyk6ea-crs-0 created
    cluster.cluster.x-k8s.io/clusterclass-changes-qyk6ea created

    Failed to get logs for Machine clusterclass-changes-qyk6ea-md-0-gbswg-6cdf79fc94-jx6mp, Cluster clusterclass-changes-ifcs3d/clusterclass-changes-qyk6ea: exit status 2
    Failed to get logs for Machine clusterclass-changes-qyk6ea-md-0-gbswg-8665f84c66-dhs95, Cluster clusterclass-changes-ifcs3d/clusterclass-changes-qyk6ea: exit status 2
    Failed to get logs for Machine clusterclass-changes-qyk6ea-v66bx-zcmch, Cluster clusterclass-changes-ifcs3d/clusterclass-changes-qyk6ea: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "clusterclass-changes" test spec 09/28/22 22:16:33.744
    INFO: Creating namespace clusterclass-changes-ifcs3d
    INFO: Creating event watcher for namespace "clusterclass-changes-ifcs3d"
... skipping 54 lines ...
    machinedeployment.cluster.x-k8s.io/quick-start-64qxl5-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/quick-start-64qxl5-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/quick-start-64qxl5 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-64qxl5-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-64qxl5-md-0 created

    Failed to get logs for Machine quick-start-64qxl5-control-plane-8gjtm, Cluster quick-start-pvcab0/quick-start-64qxl5: exit status 2
    Failed to get logs for Machine quick-start-64qxl5-md-0-5f9bf74b58-682gt, Cluster quick-start-pvcab0/quick-start-64qxl5: exit status 2
  << End Captured StdOut/StdErr Output

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

    Failed to get logs for Machine quick-start-xjuppf-control-plane-6hxtl, Cluster quick-start-cdaaw3/quick-start-xjuppf: exit status 2
    Failed to get logs for Machine quick-start-xjuppf-md-0-547c98ddf9-5kdwr, Cluster quick-start-cdaaw3/quick-start-xjuppf: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "quick-start" test spec 09/28/22 22:21:17.261
    INFO: Creating namespace quick-start-cdaaw3
    INFO: Creating event watcher for namespace "quick-start-cdaaw3"
... skipping 46 lines ...
    machinedeployment.cluster.x-k8s.io/md-rollout-7l9uba-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/md-rollout-7l9uba-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/md-rollout-7l9uba created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-rollout-7l9uba-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-rollout-7l9uba-md-0 created

    Failed to get logs for Machine md-rollout-7l9uba-control-plane-jlkcw, Cluster md-rollout-s8k5xn/md-rollout-7l9uba: exit status 2
    Failed to get logs for Machine md-rollout-7l9uba-md-0-55bc5d8dfc-dnz8x, Cluster md-rollout-s8k5xn/md-rollout-7l9uba: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "md-rollout" test spec 09/28/22 22:24:21.239
    INFO: Creating namespace md-rollout-s8k5xn
    INFO: Creating event watcher for namespace "md-rollout-s8k5xn"
... skipping 50 lines ...
    machinedeployment.cluster.x-k8s.io/self-hosted-xysn9h-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/self-hosted-xysn9h-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/self-hosted-xysn9h created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/self-hosted-xysn9h-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/self-hosted-xysn9h-md-0 created

    Failed to get logs for Machine self-hosted-xysn9h-control-plane-xc59d, Cluster self-hosted-j56hal/self-hosted-xysn9h: exit status 2
    Failed to get logs for Machine self-hosted-xysn9h-md-0-84db95c6c7-hdtbz, Cluster self-hosted-j56hal/self-hosted-xysn9h: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "self-hosted" test spec 09/28/22 22:19:10.624
    INFO: Creating namespace self-hosted-j56hal
    INFO: Creating event watcher for namespace "self-hosted-j56hal"
... skipping 87 lines ...
    machinedeployment.cluster.x-k8s.io/node-drain-aar5z7-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/node-drain-aar5z7-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/node-drain-aar5z7 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/node-drain-aar5z7-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/node-drain-aar5z7-md-0 created

    Failed to get logs for Machine node-drain-aar5z7-control-plane-29tp6, Cluster node-drain-w04ei5/node-drain-aar5z7: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "node-drain" test spec 09/28/22 22:17:29.439
    INFO: Creating namespace node-drain-w04ei5
    INFO: Creating event watcher for namespace "node-drain-w04ei5"
... skipping 59 lines ...

    cluster.cluster.x-k8s.io/kcp-adoption-hg7fbh configured
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/kcp-adoption-hg7fbh-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/kcp-adoption-hg7fbh configured
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/kcp-adoption-hg7fbh-control-plane created

    Failed to get logs for Machine kcp-adoption-hg7fbh-control-plane-0, Cluster kcp-adoption-w81fav/kcp-adoption-hg7fbh: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "kcp-adoption" test spec 09/28/22 22:27:57.133
    INFO: Creating namespace kcp-adoption-w81fav
    INFO: Creating event watcher for namespace "kcp-adoption-w81fav"
... skipping 36 lines ...
    machinepool.cluster.x-k8s.io/machine-pool-y0yhbm-mp-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/machine-pool-y0yhbm-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/machine-pool-y0yhbm created
    dockermachinepool.infrastructure.cluster.x-k8s.io/machine-pool-y0yhbm-dmp-0 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/machine-pool-y0yhbm-control-plane created

    Failed to get logs for Machine machine-pool-y0yhbm-control-plane-fkk65, Cluster machine-pool-d54jcr/machine-pool-y0yhbm: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "machine-pool" test spec 09/28/22 22:29:11.702
    INFO: Creating namespace machine-pool-d54jcr
    INFO: Creating event watcher for namespace "machine-pool-d54jcr"
... skipping 35 lines ...
  << End Captured GinkgoWriter Output
------------------------------
When testing Cluster API working on self-hosted clusters using ClusterClass [ClusterClass]
  Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/self_hosted.go:83
------------------------------
• [FAILED] [758.533 seconds]
When testing Cluster API working on self-hosted clusters using ClusterClass [ClusterClass] [AfterEach]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/self_hosted.go:221
  Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/self_hosted.go:83

  Begin Captured StdOut/StdErr Output >>
... skipping 4 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-hnw18b-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/self-hosted-hnw18b-crs-0 created
    cluster.cluster.x-k8s.io/self-hosted-hnw18b created

    Failed to get logs for Machine self-hosted-hnw18b-5ctgs-7b7b8, Cluster self-hosted-spioxf/self-hosted-hnw18b: exit status 2
    Failed to get logs for Machine self-hosted-hnw18b-md-0-6zp6t-dc55bfc8f-qpg22, Cluster self-hosted-spioxf/self-hosted-hnw18b: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "self-hosted" test spec 09/28/22 22:34:04.648
    INFO: Creating namespace self-hosted-spioxf
    INFO: Creating event watcher for namespace "self-hosted-spioxf"
... skipping 103 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-ae00vz-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-and-conformance-ae00vz-crs-0 created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-ae00vz created

    Failed to get logs for Machine k8s-upgrade-and-conformance-ae00vz-md-0-qn8r2-77f7f5f44d-kfrm4, Cluster k8s-upgrade-and-conformance-lu2198/k8s-upgrade-and-conformance-ae00vz: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-ae00vz-md-0-qn8r2-77f7f5f44d-zg47s, Cluster k8s-upgrade-and-conformance-lu2198/k8s-upgrade-and-conformance-ae00vz: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-ae00vz-vfrzv-9dz25, Cluster k8s-upgrade-and-conformance-lu2198/k8s-upgrade-and-conformance-ae00vz: 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/28/22 22:28:21.393
    INFO: Creating namespace k8s-upgrade-and-conformance-lu2198
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-lu2198"
... skipping 69 lines ...
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-t26w2l-crs-0 created
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-t26w2l-mp-0-config created
    cluster.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-t26w2l created
    machinepool.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-t26w2l-mp-0 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-t26w2l-dmp-0 created

    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-t26w2l-md-0-6m8dl-5c7d6d564b-mgxtg, Cluster k8s-upgrade-with-runtimesdk-xwft7u/k8s-upgrade-with-runtimesdk-t26w2l: exit status 2
    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-t26w2l-md-0-6m8dl-5c7d6d564b-vtb99, Cluster k8s-upgrade-with-runtimesdk-xwft7u/k8s-upgrade-with-runtimesdk-t26w2l: exit status 2
    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-t26w2l-md-0-6m8dl-5d78ccbb67-zwkdt, Cluster k8s-upgrade-with-runtimesdk-xwft7u/k8s-upgrade-with-runtimesdk-t26w2l: error creating container exec: Error response from daemon: No such container: k8s-upgrade-with-runtimesdk-t26w2l-md-0-6m8dl-5d78ccbb67-zwkdt
    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-t26w2l-tpxfx-l2rx4, Cluster k8s-upgrade-with-runtimesdk-xwft7u/k8s-upgrade-with-runtimesdk-t26w2l: exit status 2
    Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-t26w2l-mp-0, Cluster k8s-upgrade-with-runtimesdk-xwft7u/k8s-upgrade-with-runtimesdk-t26w2l: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "k8s-upgrade-with-runtimesdk" test spec 09/28/22 22:29:30.754
    INFO: Creating namespace k8s-upgrade-with-runtimesdk-xwft7u
    INFO: Creating event watcher for namespace "k8s-upgrade-with-runtimesdk-xwft7u"
... skipping 84 lines ...

Summarizing 4 Failures:
  [INTERRUPTED] When upgrading a workload cluster using ClusterClass [ClusterClass] [It] 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
  [INTERRUPTED] When upgrading a workload cluster using ClusterClass with RuntimeSDK [PR-Informing] [ClusterClass] [It] Should create, upgrade and delete a workload cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk.go:131
  [FAIL] When testing Cluster API working on self-hosted clusters using ClusterClass [ClusterClass] [AfterEach] Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/cluster_helpers.go:176
  [INTERRUPTED] [SynchronizedAfterSuite] 
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:169

Ran 17 of 21 Specs in 2737.573 seconds
FAIL! - Interrupted by Other Ginkgo Process -- 14 Passed | 3 Failed | 0 Pending | 4 Skipped


Ginkgo ran 1 suite in 46m59.844969652s

Test Suite Failed
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 26688
++ pgrep -f 'ctr -n moby events'
+ kill 26689
... skipping 29 lines ...