This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 23 succeeded
Started2022-08-11 08:47
Elapsed1h24m
Revision2ff82f3deb71ad2a26e3afa719f4909371ab1346

Test Failures


capa-e2e [unmanaged] [functional] GPU-enabled cluster test should create cluster with single worker 19m29s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[functional\]\sGPU\-enabled\scluster\stest\sshould\screate\scluster\swith\ssingle\sworker$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:116
Timed out after 600.069s.
Job default/cuda-vector-add failed
Job:
{
  "metadata": {
    "name": "cuda-vector-add",
    "namespace": "default",
    "uid": "0f5898a0-7b4b-443c-ad48-f9b4fda55972",
    "resourceVersion": "785",
    "generation": 1,
    "creationTimestamp": "2022-08-11T09:05:29Z",
    "labels": {
      "controller-uid": "0f5898a0-7b4b-443c-ad48-f9b4fda55972",
      "job-name": "cuda-vector-add"
    },
    "managedFields": [
      {
        "manager": "cluster-api-e2e",
        "operation": "Update",
        "apiVersion": "batch/v1",
        "time": "2022-08-11T09:05:29Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:spec": {
            "f:backoffLimit": {},
            "f:completionMode": {},
            "f:completions": {},
            "f:parallelism": {},
            "f:suspend": {},
            "f:template": {
              "f:spec": {
                "f:containers": {
                  "k:{\"name\":\"cuda-vector-add\"}": {
                    ".": {},
                    "f:image": {},
                    "f:imagePullPolicy": {},
                    "f:name": {},
                    "f:resources": {
                      ".": {},
                      "f:limits": {
                        ".": {},
                        "f:nvidia.com/gpu": {}
                      }
                    },
                    "f:terminationMessagePath": {},
                    "f:terminationMessagePolicy": {}
                  }
                },
                "f:dnsPolicy": {},
                "f:restartPolicy": {},
                "f:schedulerName": {},
                "f:securityContext": {},
                "f:terminationGracePeriodSeconds": {}
              }
            }
          }
        }
      },
      {
        "manager": "kube-controller-manager",
        "operation": "Update",
        "apiVersion": "batch/v1",
        "time": "2022-08-11T09:05:29Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:status": {
            "f:active": {},
            "f:ready": {},
            "f:startTime": {}
          }
        },
        "subresource": "status"
      }
    ]
  },
  "spec": {
    "parallelism": 1,
    "completions": 1,
    "backoffLimit": 6,
    "selector": {
      "matchLabels": {
        "controller-uid": "0f5898a0-7b4b-443c-ad48-f9b4fda55972"
      }
    },
    "template": {
      "metadata": {
        "creationTimestamp": null,
        "labels": {
          "controller-uid": "0f5898a0-7b4b-443c-ad48-f9b4fda55972",
          "job-name": "cuda-vector-add"
        }
      },
      "spec": {
        "containers": [
          {
            "name": "cuda-vector-add",
            "image": "nvcr.io/nvidia/k8s/cuda-sample:vectoradd-cuda11.1-ubuntu18.04",
            "resources": {
              "limits": {
                "nvidia.com/gpu": "1"
              }
            },
            "terminationMessagePath": "/dev/termination-log",
            "terminationMessagePolicy": "File",
            "imagePullPolicy": "IfNotPresent"
          }
        ],
        "restartPolicy": "OnFailure",
        "terminationGracePeriodSeconds": 30,
        "dnsPolicy": "ClusterFirst",
        "securityContext": {},
        "schedulerName": "default-scheduler"
      }
    },
    "completionMode": "NonIndexed",
    "suspend": false
  },
  "status": {
    "startTime": "2022-08-11T09:05:29Z",
    "active": 1,
    "ready": 0
  }
}
LAST SEEN                      TYPE    REASON            OBJECT               MESSAGE
2022-08-11 09:05:29 +0000 UTC  Normal  SuccessfulCreate  job/cuda-vector-add  Created pod: cuda-vector-add-htbww

Expected
    <bool>: false
to be true
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/gpu.go:134
				
				Click to see stdout/stderrfrom junit.e2e_suite.4.xml

Filter through log files | View test history on testgrid


Show 23 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 589 lines ...
[1]  ✓ Installing CNI 🔌
[1]  • Installing StorageClass 💾  ...
[1]  ✓ Installing StorageClass 💾
[1] INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind999773897
[1] INFO: Loading image: "gcr.io/k8s-staging-cluster-api/capa-manager:e2e"
[1] INFO: Loading image: "quay.io/jetstack/cert-manager-cainjector:v1.7.2"
[1] INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" into the kind cluster "test-lf0f1l": error saving image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" to "/tmp/image-tar3003389368/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "quay.io/jetstack/cert-manager-webhook:v1.7.2"
[1] INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-webhook:v1.7.2" into the kind cluster "test-lf0f1l": error saving image "quay.io/jetstack/cert-manager-webhook:v1.7.2" to "/tmp/image-tar3670364464/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "quay.io/jetstack/cert-manager-controller:v1.7.2"
[1] INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-controller:v1.7.2" into the kind cluster "test-lf0f1l": error saving image "quay.io/jetstack/cert-manager-controller:v1.7.2" to "/tmp/image-tar3102657043/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5" into the kind cluster "test-lf0f1l": error saving image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5" to "/tmp/image-tar2413893411/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5" into the kind cluster "test-lf0f1l": error saving image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5" to "/tmp/image-tar941169327/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5" into the kind cluster "test-lf0f1l": error saving image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5" to "/tmp/image-tar1674336364/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[1] STEP: Writing AWS service quotas to a file for parallel tests
[1] STEP: Initializing the bootstrap cluster
[1] INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure aws
[1] STEP: Waiting for provider controllers to be running
[1] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
... skipping 1161 lines ...
[4]   GPU-enabled cluster test
[4]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:115
[4]     should create cluster with single worker [It]
[4]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:116
[4] 
[4]     Timed out after 600.069s.
[4]     Job default/cuda-vector-add failed
[4]     Job:
[4]     {
[4]       "metadata": {
[4]         "name": "cuda-vector-add",
[4]         "namespace": "default",
[4]         "uid": "0f5898a0-7b4b-443c-ad48-f9b4fda55972",
... skipping 207 lines ...
[12]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:96
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 1502.018 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[10] INFO: Waiting for control plane to be ready
[10] INFO: Waiting for control plane self-hosted-13lb5d/self-hosted-70owrv-control-plane to be ready (implies underlying nodes to be ready as well)
[10] STEP: Waiting for the control plane to be ready
[1] STEP: Node 1 released resources: {ec2-normal:4, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[1] 
... skipping 56 lines ...
[19]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 1 Specs in 1567.077 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[10] INFO: Waiting for the machine pools to be provisioned
[10] STEP: Turning the workload cluster into a management cluster
[10] STEP: Creating a namespace for hosting the self-hosted test spec
[10] INFO: Creating namespace self-hosted-13lb5d
[10] INFO: Creating event watcher for namespace "self-hosted-13lb5d"
... skipping 95 lines ...
[6]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 2 Specs in 1806.964 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[6] PASS
[15] INFO: Waiting for control plane to be ready
[15] INFO: Waiting for control plane quick-start-mvoikd/quick-start-fua68c-pw5xv to be ready (implies underlying nodes to be ready as well)
[15] STEP: Waiting for the control plane to be ready
[14] STEP: Node 14 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[14] [BeforeEach] Clusterctl Upgrade Spec [from v1alpha4]
... skipping 50 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/mhc_remediations.go:114
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 1 Specs in 1852.195 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[16] STEP: Node 16 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[16] [BeforeEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[16]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:81
[16] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[2] STEP: Deleting all clusters in the "functional-multitenancy-nested-clusterclass-wqyxmc" namespace with intervals ["20m" "10s"]
... skipping 55 lines ...
[7]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 1896.976 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[20] STEP: Node 20 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[20] [BeforeEach] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade]
[20]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:81
[20] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[20] INFO: Creating namespace k8s-upgrade-and-conformance-7fh9w1
... skipping 31 lines ...
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] 
[4] Summarizing 1 Failure:
[4] 
[4] [Fail] [unmanaged] [functional] GPU-enabled cluster test [It] should create cluster with single worker 
[4] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/gpu.go:134
[4] 
[4] Ran 1 of 1 Specs in 1951.655 seconds
[4] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[4] --- FAIL: TestE2E (1951.71s)
[4] FAIL
[3] INFO: Waiting for control plane to be initialized
[3] INFO: Waiting for the first control plane machine managed by clusterctl-upgrade-qu4bpf/clusterctl-upgrade-o02m1r-control-plane to be provisioned
[3] STEP: Waiting for one control plane node to exist
[17] STEP: Scaling the machine pool up
[17] INFO: Patching the replica count in Machine Pool machine-pool-hk3b1m/machine-pool-97m9jj-mp-0
[17] STEP: Waiting for the machine pool workload nodes
... skipping 13 lines ...
[9]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:500
[9] ------------------------------
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 1 of 1 Specs in 2053.964 seconds
[9] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[14] INFO: Waiting for control plane to be initialized
[14] INFO: Waiting for the first control plane machine managed by clusterctl-upgrade-nz3qug/clusterctl-upgrade-0s7hwq-control-plane to be provisioned
[14] STEP: Waiting for one control plane node to exist
[3] INFO: Waiting for control plane to be ready
[3] INFO: Waiting for control plane clusterctl-upgrade-qu4bpf/clusterctl-upgrade-o02m1r-control-plane to be ready (implies underlying nodes to be ready as well)
... skipping 14 lines ...
[2]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:54
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 2143.920 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[8] INFO: Waiting for control plane to be ready
[8] INFO: Waiting for control plane only-csi-external-upgrade-8as9cg/only-csi-external-upgrade-sz6sx8-control-plane to be ready (implies underlying nodes to be ready as well)
[8] STEP: Waiting for the control plane to be ready
[3] INFO: Waiting for the machine deployments to be provisioned
[3] STEP: Waiting for the workload nodes to exist
... skipping 43 lines ...
[10]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/self_hosted.go:80
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 2267.398 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[18] STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
[18] INFO: Deleting namespace mhc-remediation-1guln0
[18] [AfterEach] Machine Remediation Spec
[18]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:63
[18] STEP: Node 18 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:3, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[18]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/mhc_remediations.go:82
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 1 of 1 Specs in 2273.836 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[15] STEP: Deleting namespace used for hosting the "quick-start" test spec
[15] INFO: Deleting namespace quick-start-mvoikd
[15] [AfterEach] Running the quick-start spec with ClusterClass
[15]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_quick_clusterclass_test.go:67
[15] STEP: Node 15 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 14 lines ...
[15]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:77
[15] ------------------------------
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 2 of 2 Specs in 2279.911 seconds
[15] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[15] PASS
[3] INFO: Waiting for provider controllers to be running
[3] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
[3] INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-7b68686c58-5gmdb, container manager
[3] STEP: Waiting for deployment capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager to be available
[3] INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-6746fb9fcc-l424n, container manager
... skipping 209 lines ...
[13]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:77
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 2 of 3 Specs in 2779.105 seconds
[13] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[13] PASS
[14] INFO: Waiting for provider controllers to be running
[14] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
[14] INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-7b68686c58-q5czt, container manager
[14] STEP: Waiting for deployment capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager to be available
[14] INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-6746fb9fcc-5qnz8, container manager
... skipping 50 lines ...
[8]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 1 of 1 Specs in 3206.852 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[3] STEP: Dumping logs from the "clusterctl-upgrade-o02m1r" workload cluster
[3] STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-qu4bpf" namespace
[3] STEP: Deleting cluster clusterctl-upgrade-qu4bpf/clusterctl-upgrade-o02m1r
[3] STEP: Deleting cluster clusterctl-upgrade-o02m1r
[3] INFO: Waiting for the Cluster clusterctl-upgrade-qu4bpf/clusterctl-upgrade-o02m1r to be deleted
... skipping 28 lines ...
[3]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:147
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 1 of 1 Specs in 3582.111 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[11] INFO: Waiting for kube-proxy to have the upgraded kubernetes version
[11] STEP: Ensuring kube-proxy has the correct image
[11] INFO: Waiting for CoreDNS to have the upgraded image tag
[11] STEP: Ensuring CoreDNS has the correct image
[11] INFO: Waiting for etcd to have the upgraded image tag
... skipping 37 lines ...
[14]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:147
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 1 Specs in 3679.664 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[14] PASS
[17] STEP: PASSED!
[17] [AfterEach] Machine Pool Spec
[17]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:128
[17] STEP: Dumping logs from the "machine-pool-97m9jj" workload cluster
[17] STEP: Dumping all the Cluster API resources in the "machine-pool-hk3b1m" namespace
... skipping 43 lines ...
[20]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:115
[20] ------------------------------
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 2 of 2 Specs in 3993.183 seconds
[20] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[17] STEP: Deleting namespace used for hosting the "machine-pool" test spec
[17] INFO: Deleting namespace machine-pool-hk3b1m
[17] [AfterEach] Machine Pool Spec
[17]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:85
[17] STEP: Node 17 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[17]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:76
[17] ------------------------------
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 4046.515 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[11] STEP: Deleting namespace used for hosting the "" test spec
[11] INFO: Deleting namespace functional-test-ignition-y86zy7
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 2 of 4 Specs in 4173.770 seconds
[11] SUCCESS! -- 2 Passed | 0 Failed | 2 Pending | 0 Skipped
[11] PASS
[16] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[16] INFO: Deleting namespace k8s-upgrade-and-conformance-d4srsl
[16] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[16]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:183
[16] STEP: Node 16 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[16]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:115
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 1 of 1 Specs in 4331.777 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[1] folder created for eks clusters: /logs/artifacts/clusters/bootstrap/aws-resources
[1] STEP: Tearing down the management cluster
[1] STEP: Deleting cluster-api-provider-aws-sigs-k8s-io CloudFormation stack
[1] 
[1] JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml
[1] 
[1] Ran 1 of 1 Specs in 4820.718 seconds
[1] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h21m49.10385584s
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
... skipping 3 lines ...
To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc

real	81m49.111s
user	24m33.881s
sys	6m9.200s
make: *** [Makefile:409: test-e2e] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...