This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 16 succeeded
Started2022-09-28 08:39
Elapsed31m30s
Revisionmain

Test Failures


capi-e2e [It] When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields 10m21s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\s\[It\]\sWhen\stesting\sMachineDeployment\srolling\supgrades\sShould\ssuccessfully\supgrade\sMachines\supon\schanges\sin\srelevant\sMachineDeployment\sfields$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/controlplane_helpers.go:154
sigs.k8s.io/cluster-api/test/framework.WaitForOneKubeadmControlPlaneMachineToExist({0x2601288?, 0xc0006b2800}, {{0x7f63000fc4a8?, 0xc0000f5650?}, 0xc000e70340?, 0xc000e29000?}, {0xc0000aa5c0, 0x2, 0x2})
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/controlplane_helpers.go:154 +0x439
sigs.k8s.io/cluster-api/test/framework.DiscoveryAndWaitForControlPlaneInitialized({0x2601288?, 0xc0006b2800}, {{0x7f63000fc4a8?, 0xc0000f5650?}, 0xc000e70340?}, {0xc0000aa5c0, 0x2, 0x2})
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/controlplane_helpers.go:249 +0x54b
sigs.k8s.io/cluster-api/test/framework/clusterctl.setDefaults.func1({_, _}, {{0x260f708, 0xc0001bc300}, {{0xc000eac2a0, 0x22}, {0xc0000fe4b6, 0x31}, {0xc0000fe4e8, 0x17}, ...}, ...}, ...)
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/clusterctl/clusterctl_helpers.go:343 +0x9e
sigs.k8s.io/cluster-api/test/framework/clusterctl.ApplyClusterTemplateAndWait({_, _}, {{0x260f708, 0xc0001bc300}, {{0xc000eac2a0, 0x22}, {0xc0000fe4b6, 0x31}, {0xc0000fe4e8, 0x17}, ...}, ...}, ...)
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/clusterctl/clusterctl_helpers.go:304 +0xd10
sigs.k8s.io/cluster-api/test/e2e.MachineDeploymentRolloutSpec.func2()
	/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_rollout.go:73 +0x568
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 16 Passed Tests

Show 10 Skipped Tests

Error lines from build-log.txt

... skipping 831 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 github.com/onsi/gomega v1.20.0
go: downloading k8s.io/api v0.25.0
... skipping 211 lines ...

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

    Failed to get logs for Machine kcp-adoption-t2m4bg-control-plane-0, Cluster kcp-adoption-e3ha4o/kcp-adoption-t2m4bg: 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 08:47:53.887
    INFO: Creating namespace kcp-adoption-e3ha4o
    INFO: Creating event watcher for namespace "kcp-adoption-e3ha4o"
... skipping 36 lines ...
    machinedeployment.cluster.x-k8s.io/md-scale-l8hwz8-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/md-scale-l8hwz8-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/md-scale-l8hwz8 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-scale-l8hwz8-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-scale-l8hwz8-md-0 created

    Failed to get logs for Machine md-scale-l8hwz8-control-plane-jg8mw, Cluster md-scale-ic0d7l/md-scale-l8hwz8: exit status 2
    Failed to get logs for Machine md-scale-l8hwz8-md-0-6ff969cbd7-pbmgw, Cluster md-scale-ic0d7l/md-scale-l8hwz8: 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 08:47:53.878
    INFO: Creating namespace md-scale-ic0d7l
    INFO: Creating event watcher for namespace "md-scale-ic0d7l"
... skipping 52 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-6kwpdx-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/clusterclass-changes-6kwpdx-crs-0 created
    cluster.cluster.x-k8s.io/clusterclass-changes-6kwpdx created

    Failed to get logs for Machine clusterclass-changes-6kwpdx-8bw6b-wdfm8, Cluster clusterclass-changes-u0mw02/clusterclass-changes-6kwpdx: exit status 2
    Failed to get logs for Machine clusterclass-changes-6kwpdx-md-0-g8pjk-879b568f5-55995, Cluster clusterclass-changes-u0mw02/clusterclass-changes-6kwpdx: error creating container exec: Error response from daemon: No such container: clusterclass-changes-6kwpdx-md-0-g8pjk-879b568f5-55995
    Failed to get logs for Machine clusterclass-changes-6kwpdx-md-0-g8pjk-cd7498bb7-r6gkq, Cluster clusterclass-changes-u0mw02/clusterclass-changes-6kwpdx: error creating container exec: Error response from daemon: Container 646bcab7ef027ce6aeb161ca99225143852a4488d09e43bf602f5142343ae176 is not running
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "clusterclass-changes" test spec 09/28/22 08:50:16.14
    INFO: Creating namespace clusterclass-changes-u0mw02
    INFO: Creating event watcher for namespace "clusterclass-changes-u0mw02"
... skipping 55 lines ...
    machinehealthcheck.cluster.x-k8s.io/mhc-remediation-pu8f4j-mhc-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/mhc-remediation-pu8f4j-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/mhc-remediation-pu8f4j created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-pu8f4j-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-pu8f4j-md-0 created

    Failed to get logs for Machine mhc-remediation-pu8f4j-control-plane-xcd4w, Cluster mhc-remediation-jsncsh/mhc-remediation-pu8f4j: exit status 2
    Failed to get logs for Machine mhc-remediation-pu8f4j-md-0-6d595c94b-pb2c2, Cluster mhc-remediation-jsncsh/mhc-remediation-pu8f4j: 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 08:51:36.983
    INFO: Creating namespace mhc-remediation-jsncsh
    INFO: Creating event watcher for namespace "mhc-remediation-jsncsh"
... skipping 51 lines ...
    machinedeployment.cluster.x-k8s.io/node-drain-q4wdpe-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/node-drain-q4wdpe-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/node-drain-q4wdpe created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/node-drain-q4wdpe-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/node-drain-q4wdpe-md-0 created

    Failed to get logs for Machine node-drain-q4wdpe-control-plane-9br7p, Cluster node-drain-shopjq/node-drain-q4wdpe: 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 08:47:53.886
    INFO: Creating namespace node-drain-shopjq
    INFO: Creating event watcher for namespace "node-drain-shopjq"
... skipping 57 lines ...
    machinehealthcheck.cluster.x-k8s.io/mhc-remediation-m1z0m4-mhc-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/mhc-remediation-m1z0m4-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/mhc-remediation-m1z0m4 created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-m1z0m4-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/mhc-remediation-m1z0m4-md-0 created

    Failed to get logs for Machine mhc-remediation-m1z0m4-control-plane-brkrf, Cluster mhc-remediation-3zxtfj/mhc-remediation-m1z0m4: exit status 2
    Failed to get logs for Machine mhc-remediation-m1z0m4-control-plane-s5gvm, Cluster mhc-remediation-3zxtfj/mhc-remediation-m1z0m4: exit status 2
    Failed to get logs for Machine mhc-remediation-m1z0m4-control-plane-zjffp, Cluster mhc-remediation-3zxtfj/mhc-remediation-m1z0m4: exit status 2
    Failed to get logs for Machine mhc-remediation-m1z0m4-md-0-7998b7c579-pqsj9, Cluster mhc-remediation-3zxtfj/mhc-remediation-m1z0m4: 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 08:53:25.557
    INFO: Creating namespace mhc-remediation-3zxtfj
    INFO: Creating event watcher for namespace "mhc-remediation-3zxtfj"
... skipping 53 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-doqubb-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/self-hosted-doqubb-crs-0 created
    cluster.cluster.x-k8s.io/self-hosted-doqubb created

    Failed to get logs for Machine self-hosted-doqubb-kzwvn-8l7b9, Cluster self-hosted-hnnk1i/self-hosted-doqubb: exit status 2
    Failed to get logs for Machine self-hosted-doqubb-md-0-cr4sn-78cf6fbd45-kw7lk, Cluster self-hosted-hnnk1i/self-hosted-doqubb: 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 08:54:42.823
    INFO: Creating namespace self-hosted-hnnk1i
    INFO: Creating event watcher for namespace "self-hosted-hnnk1i"
... skipping 87 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-moernn-crs-0 created
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-and-conformance-moernn-crs-0 created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-moernn created

    Failed to get logs for Machine k8s-upgrade-and-conformance-moernn-md-0-pr2zk-66fcb5d74-dnwxk, Cluster k8s-upgrade-and-conformance-c3zx9j/k8s-upgrade-and-conformance-moernn: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-moernn-mkbsd-q67lk, Cluster k8s-upgrade-and-conformance-c3zx9j/k8s-upgrade-and-conformance-moernn: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-moernn-mkbsd-t44g4, Cluster k8s-upgrade-and-conformance-c3zx9j/k8s-upgrade-and-conformance-moernn: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-moernn-mkbsd-t92wk, Cluster k8s-upgrade-and-conformance-c3zx9j/k8s-upgrade-and-conformance-moernn: 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 08:57:34.811
    INFO: Creating namespace k8s-upgrade-and-conformance-c3zx9j
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-c3zx9j"
... skipping 41 lines ...
  << End Captured GinkgoWriter Output
------------------------------
When testing MachineDeployment rolling upgrades
  Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_rollout.go:71
------------------------------
• [FAILED] [621.747 seconds]
When testing MachineDeployment rolling upgrades
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_rollout_test.go:26
  [It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_rollout.go:71

  Begin Captured StdOut/StdErr Output >>
... skipping 4 lines ...
    machinedeployment.cluster.x-k8s.io/md-rollout-7fkqgv-md-0 created
    kubeadmcontrolplane.controlplane.cluster.x-k8s.io/md-rollout-7fkqgv-control-plane created
    dockercluster.infrastructure.cluster.x-k8s.io/md-rollout-7fkqgv created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-rollout-7fkqgv-control-plane created
    dockermachinetemplate.infrastructure.cluster.x-k8s.io/md-rollout-7fkqgv-md-0 created

    Failed to get logs for Machine md-rollout-7fkqgv-control-plane-s55f2, Cluster md-rollout-1ysfav/md-rollout-7fkqgv: error creating container exec: Error response from daemon: Container 4f893deb23511becd8dbe4be26ccea73f75951db5e7a571f64db00f37a798192 is not running
    Failed to get logs for Machine md-rollout-7fkqgv-md-0-6bbd554fc-n7x2j, Cluster md-rollout-1ysfav/md-rollout-7fkqgv: error creating container exec: Error response from daemon: No such container: md-rollout-7fkqgv-md-0-6bbd554fc-n7x2j
  << End Captured StdOut/StdErr Output

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

    Failed to get logs for Machine self-hosted-jynf2q-control-plane-p4c5z, Cluster self-hosted-w4y5hy/self-hosted-jynf2q: exit status 2
    Failed to get logs for Machine self-hosted-jynf2q-md-0-6f54d55b5d-ljxds, Cluster self-hosted-w4y5hy/self-hosted-jynf2q: 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 09:08:41.085
    INFO: Creating namespace self-hosted-w4y5hy
    INFO: Creating event watcher for namespace "self-hosted-w4y5hy"
... skipping 35 lines ...
    INFO: Waiting for the Cluster self-hosted-w4y5hy/self-hosted-jynf2q to be deleted
    STEP: Waiting for cluster self-hosted-jynf2q to be deleted 09/28/22 09:10:29.224
    INFO: Loading image: "quay.io/jetstack/cert-manager-webhook:v1.9.1"
    INFO: Image quay.io/jetstack/cert-manager-webhook:v1.9.1 is present in local container image cache
    INFO: Loading image: "quay.io/jetstack/cert-manager-controller:v1.9.1"
    INFO: Image quay.io/jetstack/cert-manager-controller:v1.9.1 is present in local container image cache
    INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-controller:v1.9.1" into the kind cluster "self-hosted-jynf2q": failed to load image: command "docker exec --privileged -i self-hosted-jynf2q-control-plane-p4c5z ctr --namespace=k8s.io images import --digests --snapshotter=overlayfs -" failed with error: exit status 126
    STEP: Creating a namespace for hosting the self-hosted test spec 09/28/22 09:10:35.424
    STEP: Deleting namespace used for hosting the "self-hosted" test spec 09/28/22 09:10:39.232
    INFO: Deleting namespace self-hosted-w4y5hy
  << End Captured GinkgoWriter Output

  Interrupted by Other Ginkgo Process
... skipping 38 lines ...
    clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-d8bvjo-crs-0 created
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-d8bvjo-mp-0-config created
    cluster.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-d8bvjo created
    machinepool.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-d8bvjo-mp-0 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-d8bvjo-dmp-0 created

    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-d8bvjo-bjznf-6fgn5, Cluster k8s-upgrade-with-runtimesdk-gbgycr/k8s-upgrade-with-runtimesdk-d8bvjo: exit status 2
    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-d8bvjo-bjznf-vxcwf, Cluster k8s-upgrade-with-runtimesdk-gbgycr/k8s-upgrade-with-runtimesdk-d8bvjo: exit status 2
    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-d8bvjo-md-0-gd865-6c9f795989-8z8rp, Cluster k8s-upgrade-with-runtimesdk-gbgycr/k8s-upgrade-with-runtimesdk-d8bvjo: exit status 2
    Failed to get logs for Machine k8s-upgrade-with-runtimesdk-d8bvjo-md-0-gd865-6c9f795989-tb47x, Cluster k8s-upgrade-with-runtimesdk-gbgycr/k8s-upgrade-with-runtimesdk-d8bvjo: exit status 2
    Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-d8bvjo-mp-0, Cluster k8s-upgrade-with-runtimesdk-gbgycr/k8s-upgrade-with-runtimesdk-d8bvjo: 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 09:02:15.438
    INFO: Creating namespace k8s-upgrade-with-runtimesdk-gbgycr
    INFO: Creating event watcher for namespace "k8s-upgrade-with-runtimesdk-gbgycr"
... skipping 47 lines ...
  Interrupted by Other Ginkgo Process

  In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk.go:131

  Full Stack Trace
------------------------------
Failed to get logs for the bootstrap cluster node test-kj33ce-control-plane: exit status 2
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:169
------------------------------
[SynchronizedAfterSuite] PASSED [2.015 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-kj33ce-control-plane: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Dumping logs from the bootstrap cluster 09/28/22 09:10:52.421
    STEP: Tearing down the management cluster 09/28/22 09:10:53.063
  << End Captured GinkgoWriter Output
... skipping 5 lines ...
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------


Summarizing 3 Failures:
  [FAIL] When testing MachineDeployment rolling upgrades [It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/controlplane_helpers.go:154
  [INTERRUPTED] When testing Cluster API working on self-hosted clusters [It] 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
  [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

Ran 11 of 21 Specs in 1484.928 seconds
FAIL! - Interrupted by Other Ginkgo Process -- 8 Passed | 3 Failed | 0 Pending | 10 Skipped


Ginkgo ran 1 suite in 25m54.451401467s

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 26130
++ pgrep -f 'ctr -n moby events'
+ kill 26131
... skipping 21 lines ...