This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 21 succeeded
Started2022-08-10 12:51
Elapsed1h17m
Revisionrelease-1.5

Test Failures


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

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.066s.
Job default/cuda-vector-add failed
Job:
{
  "metadata": {
    "name": "cuda-vector-add",
    "namespace": "default",
    "uid": "c94fdbbf-2fb8-4077-825c-5ef488654ba1",
    "resourceVersion": "852",
    "generation": 1,
    "creationTimestamp": "2022-08-10T13:11:05Z",
    "labels": {
      "controller-uid": "c94fdbbf-2fb8-4077-825c-5ef488654ba1",
      "job-name": "cuda-vector-add"
    },
    "managedFields": [
      {
        "manager": "cluster-api-e2e",
        "operation": "Update",
        "apiVersion": "batch/v1",
        "time": "2022-08-10T13:11:05Z",
        "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-10T13:11:05Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:status": {
            "f:active": {},
            "f:ready": {},
            "f:startTime": {}
          }
        },
        "subresource": "status"
      }
    ]
  },
  "spec": {
    "parallelism": 1,
    "completions": 1,
    "backoffLimit": 6,
    "selector": {
      "matchLabels": {
        "controller-uid": "c94fdbbf-2fb8-4077-825c-5ef488654ba1"
      }
    },
    "template": {
      "metadata": {
        "creationTimestamp": null,
        "labels": {
          "controller-uid": "c94fdbbf-2fb8-4077-825c-5ef488654ba1",
          "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-10T13:11:05Z",
    "active": 1,
    "ready": 0
  }
}
LAST SEEN  TYPE  REASON  OBJECT  MESSAGE

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.1.xml

Filter through log files | View test history on testgrid


Show 21 Passed Tests

Show 6 Skipped Tests

Error lines from build-log.txt

... skipping 21 lines ...
Collecting idna<4,>=2.5
  Downloading idna-3.3-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.2/61.2 kB 8.9 MB/s eta 0:00:00
Installing collected packages: idna, charset-normalizer, certifi, requests
Successfully installed certifi-2022.6.15 charset-normalizer-2.1.0 idna-3.3 requests-2.28.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
--- Logging error ---
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/pip/_internal/utils/logging.py", line 177, in emit
    self.console.print(renderable, overflow="ignore", crop=False, style=style)
  File "/usr/local/lib/python3.7/dist-packages/pip/_vendor/rich/console.py", line 1752, in print
    extend(render(renderable, render_options))
  File "/usr/local/lib/python3.7/dist-packages/pip/_vendor/rich/console.py", line 1390, in render
... skipping 577 lines ...
[1]  ✓ Installing CNI 🔌
[1]  • Installing StorageClass 💾  ...
[1]  ✓ Installing StorageClass 💾
[1] INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind3113107173
[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-qwxxrw": error saving image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" to "/tmp/image-tar2350608788/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-qwxxrw": error saving image "quay.io/jetstack/cert-manager-webhook:v1.7.2" to "/tmp/image-tar2354313542/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-qwxxrw": error saving image "quay.io/jetstack/cert-manager-controller:v1.7.2" to "/tmp/image-tar3097468989/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-qwxxrw": error saving image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5" to "/tmp/image-tar3714676122/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-qwxxrw": error saving image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5" to "/tmp/image-tar4106670181/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-qwxxrw": error saving image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5" to "/tmp/image-tar2078899006/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 1192 lines ...
[11]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[11] ------------------------------
[11] SS
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 5 Specs in 1461.913 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 2 Pending | 2 Skipped
[11] PASS
[15] STEP: Creating the LB service
[15] STEP: Creating service of type Load Balancer with name: test-svc-ofe6zo under namespace: default
[15] STEP: Created Load Balancer service and ELB name is: aa61f4ad339ed465eabcbcd228689a61
[15] STEP: Verifying ELB with name aa61f4ad339ed465eabcbcd228689a61 present
[15] STEP: ELB with name aa61f4ad339ed465eabcbcd228689a61 exists
... skipping 24 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/self_hosted.go:80
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 1 Specs in 1509.865 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[18] STEP: Node 18 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[18] [BeforeEach] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade]
[18]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:81
[18] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[18] INFO: Creating namespace k8s-upgrade-and-conformance-ry0gjm
... skipping 37 lines ...
[1]   GPU-enabled cluster test
[1]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:115
[1]     should create cluster with single worker [It]
[1]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:116
[1] 
[1]     Timed out after 600.066s.
[1]     Job default/cuda-vector-add failed
[1]     Job:
[1]     {
[1]       "metadata": {
[1]         "name": "cuda-vector-add",
[1]         "namespace": "default",
[1]         "uid": "c94fdbbf-2fb8-4077-825c-5ef488654ba1",
... skipping 180 lines ...
[6]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/mhc_remediations.go:82
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 1 Specs in 1563.143 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[7] STEP: Node 7 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[7] [BeforeEach] Clusterctl Upgrade Spec [from v1alpha4]
[7]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:122
[7] STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec
[12] STEP: Node 12 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 105 lines ...
[8] STEP: Deleting namespace used for hosting the "" test spec
[8] INFO: Deleting namespace functional-efs-support-rgbc72
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 1 of 1 Specs in 1751.771 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[13] INFO: Waiting for the machine pools to be provisioned
[13] STEP: Dumping all the Cluster API resources in the "functional-test-ssm-parameter-store-y25fdw" namespace
[13] STEP: Dumping all EC2 instances in the "functional-test-ssm-parameter-store-y25fdw" namespace
[13] STEP: Deleting all clusters in the "functional-test-ssm-parameter-store-y25fdw" namespace with intervals ["20m" "10s"]
[13] STEP: Deleting cluster functional-test-ssm-parameter-store-h22uha
... skipping 12 lines ...
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 1 Specs in 1773.149 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[14] PASS
[19] STEP: Node 19 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[19] [BeforeEach] Cluster Upgrade Spec - HA control plane with scale in rollout [K8s-Upgrade]
[19]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:81
[19] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[19] INFO: Creating namespace k8s-upgrade-and-conformance-ilzxqm
... skipping 59 lines ...
[3]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 1 of 1 Specs in 1886.813 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[10] STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
[10] INFO: Deleting namespace mhc-remediation-pj2mwv
[10] [AfterEach] Machine Remediation Spec
[10]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:63
[10] STEP: Node 10 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:3, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[10]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/mhc_remediations.go:114
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 1895.551 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[16] STEP: Retrieving IDs of dynamically provisioned volumes.
[16] STEP: Ensuring dynamically provisioned volumes exists
[16] INFO: Creating the workload cluster with name "csi-ccm-external-upgrade-ullmat" using the "external-cloud-provider" template (Kubernetes v1.23.3, 1 control-plane machines, 1 worker machines)
[16] INFO: Getting the cluster template yaml
[16] INFO: clusterctl config cluster csi-ccm-external-upgrade-ullmat --infrastructure (default) --kubernetes-version v1.23.3 --control-plane-machine-count 1 --worker-machine-count 1 --flavor external-cloud-provider
... skipping 62 lines ...
[15]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[15] ------------------------------
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 1 of 2 Specs in 1976.456 seconds
[15] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[15] PASS
[4] STEP: Deleting namespace used for hosting the "" test spec
[4] INFO: Deleting namespace functional-test-ignition-wa4mzm
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 2 Specs in 1988.667 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[4] PASS
[2] STEP: Scaling the machine pool to zero
[2] INFO: Patching the replica count in Machine Pool machine-pool-u83ulf/machine-pool-flbf1a-mp-0
[2] STEP: Waiting for the machine pool workload nodes
[12] INFO: Waiting for control plane to be ready
[12] INFO: Waiting for control plane k8s-upgrade-and-conformance-z12hs7/k8s-upgrade-and-conformance-qnxrcg-control-plane to be ready (implies underlying nodes to be ready as well)
... skipping 48 lines ...
[13]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:466
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 1 Specs in 2171.960 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[13] PASS
[2] STEP: PASSED!
[2] [AfterEach] Machine Pool Spec
[2]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:128
[2] STEP: Dumping logs from the "machine-pool-flbf1a" workload cluster
[2] STEP: Dumping all the Cluster API resources in the "machine-pool-u83ulf" namespace
... skipping 40 lines ...
[9]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:77
[9] ------------------------------
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 1 of 1 Specs in 2228.434 seconds
[9] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[7] INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-58bf4fb8cf-59smd, container manager
[7] INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-58bf4fb8cf-59smd, container kube-rbac-proxy
[7] STEP: Waiting for deployment capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager to be available
[7] INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-7fd79947fd-2trgk, container manager
[7] STEP: Waiting for deployment capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager to be available
... skipping 69 lines ...
[20]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:77
[20] ------------------------------
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 2 of 2 Specs in 2380.641 seconds
[20] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[16] STEP: Retrieving IDs of dynamically provisioned volumes.
[16] STEP: Ensuring dynamically provisioned volumes exists
[16] STEP: Deleting LB service
[16] STEP: Deleting the Clusters
[16] STEP: Deleting cluster csi-ccm-external-upgrade-ullmat
... skipping 27 lines ...
[2]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:76
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 2526.037 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[12] STEP: Upgrading the machine deployment
[12] INFO: Patching the new kubernetes version to Machine Deployment k8s-upgrade-and-conformance-z12hs7/k8s-upgrade-and-conformance-qnxrcg-md-0
[12] INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-z12hs7/k8s-upgrade-and-conformance-qnxrcg-md-0 to be upgraded from v1.23.6 to v1.24.0
[12] INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.24.0
[7] STEP: THE MANAGEMENT CLUSTER WITH OLDER VERSION OF PROVIDERS WORKS!
... skipping 51 lines ...
[16]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 1 of 1 Specs in 2886.660 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[17] STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
[17] INFO: Deleting namespace clusterctl-upgrade-1vuxpg
[17] [AfterEach] Clusterctl Upgrade Spec [from latest v1beta1 release to main]
[17]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:133
[17] STEP: Node 17 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, 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/clusterctl_upgrade.go:147
[17] ------------------------------
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 2966.960 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[12] STEP: Upgrading the machinepool instances
[12] INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-and-conformance-z12hs7/k8s-upgrade-and-conformance-qnxrcg-mp-0
[12] INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-and-conformance-z12hs7/k8s-upgrade-and-conformance-qnxrcg-mp-0 to be upgraded from v1.23.6 to v1.24.0
[12] INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
[7] STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-uad2pz
... skipping 59 lines ...
[19]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:115
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 1 Specs in 3557.590 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[7] STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
[7] INFO: Deleting namespace clusterctl-upgrade-an9hah
[7] [AfterEach] Clusterctl Upgrade Spec [from v1alpha4]
[7]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:158
[7] STEP: Node 7 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[7]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:147
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 3659.013 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[18] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[18] INFO: Deleting namespace k8s-upgrade-and-conformance-ry0gjm
[18] [AfterEach] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade]
[18]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:233
[18] STEP: Node 18 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, 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/cluster_upgrade.go:115
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 2 of 2 Specs in 3705.776 seconds
[18] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[12] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[12] INFO: Deleting namespace k8s-upgrade-and-conformance-z12hs7
[12] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[12]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:183
[12] STEP: Node 12 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[12]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:115
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 3904.137 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] 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] 
[1] Summarizing 1 Failure:
[1] 
[1] [Fail] [unmanaged] [functional] GPU-enabled cluster test [It] should create cluster with single worker 
[1] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/gpu.go:134
[1] 
[1] Ran 1 of 1 Specs in 4394.959 seconds
[1] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[1] --- FAIL: TestE2E (4395.00s)
[1] FAIL

Ginkgo ran 1 suite in 1h14m46.139467495s
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	74m46.148s
user	22m2.947s
sys	5m30.903s
make: *** [Makefile:404: 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 ...