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 07:27
Elapsed1h19m
Revision34944d63f7418d441006413b0a1e8f7601cf1dc5

Test Failures


capa-e2e [unmanaged] [functional] Multitenancy test should create cluster with nested assumed role 20s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[functional\]\sMultitenancy\stest\sshould\screate\scluster\swith\snested\sassumed\srole$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
Expected success, but got an error:
    <*errors.withStack | 0xc000caa858>: {
        error: <*exec.ExitError | 0xc000547160>{
            ProcessState: {
                pid: 30626,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 537569},
                    Stime: {Sec: 0, Usec: 290240},
                    Maxrss: 102220,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 12227,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 25568,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 5136,
                    Nivcsw: 1410,
                },
            },
            Stderr: nil,
        },
        stack: [0x1a888c0, 0x1a88e10, 0x1c0040c, 0x1fb4ed4, 0x2061958, 0x947ff1, 0x9479e5, 0x9470db, 0x94cdca, 0x94c7c7, 0x958c68, 0x958985, 0x958025, 0x95a3f2, 0x9667e9, 0x9665f6, 0x2063adb, 0x520982, 0x46d9e1],
    }
    exit status 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/framework/clusterctl/clusterctl_helpers.go:273
				
				Click to see stdout/stderrfrom junit.e2e_suite.19.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 579 lines ...
[1]  ✓ Installing CNI 🔌
[1]  • Installing StorageClass 💾  ...
[1]  ✓ Installing StorageClass 💾
[1] INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind3818247369
[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-yivg01": error saving image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" to "/tmp/image-tar2306527657/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-yivg01": error saving image "quay.io/jetstack/cert-manager-webhook:v1.7.2" to "/tmp/image-tar2537909078/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-yivg01": error saving image "quay.io/jetstack/cert-manager-controller:v1.7.2" to "/tmp/image-tar848146485/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-yivg01": error saving image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5" to "/tmp/image-tar4183917272/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-yivg01": error saving image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5" to "/tmp/image-tar1733752724/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-yivg01": error saving image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5" to "/tmp/image-tar3829603429/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 709 lines ...
[8] configmap/cni-cluster-uberd1-crs-0 created
[8] clusterresourceset.addons.cluster.x-k8s.io/cluster-uberd1-crs-0 created
[8] awsclusterroleidentity.infrastructure.cluster.x-k8s.io/capamultitenancyjump created
[8] awsclusterroleidentity.infrastructure.cluster.x-k8s.io/capamultitenancynested created
[8] 
[8] INFO: Waiting for the cluster infrastructure to be provisioned
[19] Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancynested" already exists
[19] 
[19] STEP: Dumping all the Cluster API resources in the "functional-multitenancy-nested-t5du6w" namespace
[8] STEP: Waiting for cluster to enter the provisioned phase
[10] STEP: Waiting for cluster to enter the provisioned phase
[2] cluster.cluster.x-k8s.io/mhc-remediation-pcpqw8 created
[2] awscluster.infrastructure.cluster.x-k8s.io/mhc-remediation-pcpqw8 created
... skipping 22 lines ...
[19] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:50
[19]   Multitenancy test
[19]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:162
[19]     should create cluster with nested assumed role [It]
[19]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
[19] 
[19]     Expected success, but got an error:
[19]         <*errors.withStack | 0xc000caa858>: {
[19]             error: <*exec.ExitError | 0xc000547160>{
[19]                 ProcessState: {
[19]                     pid: 30626,
[19]                     status: 256,
[19]                     rusage: {
[19]                         Utime: {Sec: 0, Usec: 537569},
[19]                         Stime: {Sec: 0, Usec: 290240},
... skipping 586 lines ...
[12]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:500
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 1568.352 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[5] STEP: Node 5 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[5] [BeforeEach] Running the quick-start spec
[5]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:62
[5] STEP: Creating a namespace for hosting the "quick-start" test spec
[5] INFO: Creating namespace quick-start-z940dj
... skipping 49 lines ...
[6]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/self_hosted.go:80
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 1 Specs in 1617.959 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[14] STEP: Creating the LB service
[14] STEP: Creating service of type Load Balancer with name: test-svc-j4z107 under namespace: default
[14] STEP: Created Load Balancer service and ELB name is: ac604ef4699ef4bc3ad5906ddb82fa78
[14] STEP: Verifying ELB with name ac604ef4699ef4bc3ad5906ddb82fa78 present
[14] STEP: ELB with name ac604ef4699ef4bc3ad5906ddb82fa78 exists
... skipping 25 lines ...
[11]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[11] ------------------------------
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 3 Specs in 1642.063 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 2 Pending | 0 Skipped
[11] 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-ojpkww
... skipping 30 lines ...
[13]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:96
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 1 Specs in 1655.031 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[13] PASS
[14] STEP: Retrieving IDs of dynamically provisioned volumes.
[14] STEP: Ensuring dynamically provisioned volumes exists
[14] STEP: Deleting LB service
[14] STEP: Deleting the Clusters
[14] STEP: Deleting cluster csimigration-off-upgrade-2r5squ
... skipping 13 lines ...
[10]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/mhc_remediations.go:82
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 1754.824 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] 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 - Single control plane with workers [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-y24hxj
... skipping 96 lines ...
[2]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/mhc_remediations.go:114
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 1930.805 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[3] STEP: Node 3 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[3] [BeforeEach] Clusterctl Upgrade Spec [from v1alpha4]
[3]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:122
[3] STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec
[3] INFO: Creating namespace clusterctl-upgrade-ixwdjk
... skipping 36 lines ...
[17]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[17] ------------------------------
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 1943.443 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[5] INFO: Waiting for the machine deployments to be provisioned
[5] STEP: Waiting for the workload nodes to exist
[19] INFO: Waiting for control plane to be initialized
[19] INFO: Waiting for the first control plane machine managed by k8s-upgrade-and-conformance-y24hxj/k8s-upgrade-and-conformance-obzii9-control-plane to be provisioned
[19] STEP: Waiting for one control plane node to exist
... skipping 34 lines ...
[16]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 1 of 1 Specs in 1998.525 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[4] INFO: Waiting for control plane to be initialized
[4] INFO: Waiting for the first control plane machine managed by clusterctl-upgrade-u2lp0w/clusterctl-upgrade-ge6mei-control-plane to be provisioned
[4] STEP: Waiting for one control plane node to exist
[7] INFO: Waiting for the machine pools to be provisioned
[7] STEP: PASSED!
... skipping 26 lines ...
[18]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 1 of 1 Specs in 2048.199 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[5] INFO: Waiting for the machine pools to be provisioned
[5] STEP: PASSED!
[5] [AfterEach] Running the quick-start spec
[5]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:107
[5] STEP: Dumping logs from the "quick-start-c0q815" workload cluster
... skipping 31 lines ...
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 2 Specs in 2128.377 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[14] PASS
[19] INFO: Waiting for the machine pools to be provisioned
[19] STEP: Waiting for the machine pool workload nodes
[9] INFO: Waiting for control plane k8s-upgrade-and-conformance-ectdua/k8s-upgrade-and-conformance-4xwxyw-control-plane to be ready (implies underlying nodes to be ready as well)
[9] STEP: Waiting for the control plane to be ready
[9] INFO: Waiting for the machine deployments to be provisioned
... skipping 40 lines ...
[8]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:54
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 1 of 1 Specs in 2279.264 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[4] INFO: Waiting for the machine pools to be provisioned
[4] STEP: Turning the workload cluster into a management cluster with older versions of providers
[4] INFO: Downloading clusterctl binary from https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.1.5/clusterctl-linux-amd64
[4] STEP: Initializing the workload cluster with older versions of providers
[4] INFO: clusterctl init --core cluster-api:v1.1.5 --bootstrap kubeadm:v1.1.5 --control-plane kubeadm:v1.1.5 --infrastructure aws:v1.4.99
... skipping 88 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:77
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 2 of 2 Specs in 2512.992 seconds
[5] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[7] STEP: Deleting namespace used for hosting the "quick-start" test spec
[7] INFO: Deleting namespace quick-start-42299x
[7] [AfterEach] Running the quick-start spec with ClusterClass
[7]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_quick_clusterclass_test.go:67
[7] STEP: Node 7 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 14 lines ...
[7]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/quick_start.go:77
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 2542.003 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[15] STEP: PASSED!
[15] [AfterEach] Machine Pool Spec
[15]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:128
[15] STEP: Dumping logs from the "machine-pool-0w6mrt" workload cluster
[15] STEP: Dumping all the Cluster API resources in the "machine-pool-hfuuzm" namespace
... skipping 51 lines ...
[15]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:76
[15] ------------------------------
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 1 of 1 Specs in 2928.030 seconds
[15] SUCCESS! -- 1 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-g9vql, 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-4wgqk, container manager
... skipping 130 lines ...
[4]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:147
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 3751.172 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[9] STEP: Deleting namespace used for hosting the "" test spec
[9] INFO: Deleting namespace functional-test-ignition-zr258e
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 2 of 3 Specs in 3780.010 seconds
[9] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[9] PASS
[3] STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
[3] INFO: Deleting namespace clusterctl-upgrade-ixwdjk
[3] [AfterEach] Clusterctl Upgrade Spec [from v1alpha4]
[3]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:158
[3] STEP: Node 3 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 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 3857.220 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[19] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[19] INFO: Deleting namespace k8s-upgrade-and-conformance-y24hxj
[19] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[19]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:183
[19] STEP: Node 19 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 9 lines ...
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] 
[19] Summarizing 1 Failure:
[19] 
[19] [Fail] [unmanaged] [functional] Multitenancy test [It] should create cluster with nested assumed role 
[19] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/framework/clusterctl/clusterctl_helpers.go:273
[19] 
[19] Ran 2 of 2 Specs in 4006.774 seconds
[19] FAIL! -- 1 Passed | 1 Failed | 0 Pending | 0 Skipped
[19] --- FAIL: TestE2E (4006.82s)
[19] FAIL
[20] STEP: Deleting namespace used for hosting the "" test spec
[20] INFO: Deleting namespace functional-gpu-cluster-3fnmxf
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 2 of 2 Specs in 4075.642 seconds
[20] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] 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 4520.762 seconds
[1] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h16m50.288127031s
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	76m50.297s
user	27m6.057s
sys	6m40.826s
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 ...