This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 24 succeeded
Started2022-07-25 15:14
Elapsed1h13m
Revision3a0e8a221dcbcdc09573c7dc7763277c60d2bff3

Test Failures


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

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 | 0xc000bda8d0>: {
        error: <*exec.ExitError | 0xc000218840>{
            ProcessState: {
                pid: 30337,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 803147},
                    Stime: {Sec: 0, Usec: 360083},
                    Maxrss: 118604,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 14666,
                    Majflt: 1,
                    Nswap: 0,
                    Inblock: 8,
                    Oublock: 28000,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 2036,
                    Nivcsw: 451,
                },
            },
            Stderr: nil,
        },
        stack: [0x1a89ce0, 0x1a8a230, 0x1c07e2c, 0x1f89ef4, 0x2031578, 0x94c871, 0x94c265, 0x94b95b, 0x95164a, 0x951047, 0x95d4e8, 0x95d205, 0x95c8a5, 0x95ec72, 0x96b089, 0x96ae96, 0x20336fb, 0x520602, 0x46d9a1],
    }
    exit status 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/framework/clusterctl/clusterctl_helpers.go:273
				
				Click to see stdout/stderrfrom junit.e2e_suite.14.xml

Filter through log files | View test history on testgrid


Show 24 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 21 lines ...
Collecting charset-normalizer<3,>=2
  Downloading charset_normalizer-2.1.0-py3-none-any.whl (39 kB)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from requests) (1.26.10)
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 566 lines ...
[1]  ✓ Installing CNI 🔌
[1]  • Installing StorageClass 💾  ...
[1]  ✓ Installing StorageClass 💾
[1] INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind3684508795
[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-0btr9y": error saving image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" to "/tmp/image-tar2359706722/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-0btr9y": error saving image "quay.io/jetstack/cert-manager-webhook:v1.7.2" to "/tmp/image-tar1040023811/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-0btr9y": error saving image "quay.io/jetstack/cert-manager-controller:v1.7.2" to "/tmp/image-tar837324641/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.2"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.2" into the kind cluster "test-0btr9y": error saving image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.2" to "/tmp/image-tar152242342/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.2"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.2" into the kind cluster "test-0btr9y": error saving image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.2" to "/tmp/image-tar3701081937/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.2"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.2" into the kind cluster "test-0btr9y": error saving image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.2" to "/tmp/image-tar4152517864/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 1045 lines ...
[10] configmap/cni-cluster-0nufjm-crs-0 created
[10] clusterresourceset.addons.cluster.x-k8s.io/cluster-0nufjm-crs-0 created
[10] awsclusterroleidentity.infrastructure.cluster.x-k8s.io/capamultitenancyjump created
[10] awsclusterroleidentity.infrastructure.cluster.x-k8s.io/capamultitenancynested created
[10] 
[10] INFO: Waiting for the cluster infrastructure to be provisioned
[14] Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancyjump" already exists
[14] Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancynested" already exists
[14] 
[14] STEP: Dumping all the Cluster API resources in the "functional-multitenancy-nested-jivyxg" namespace
[10] STEP: Waiting for cluster to enter the provisioned phase
[14] STEP: Dumping all EC2 instances in the "functional-multitenancy-nested-jivyxg" namespace
[14] STEP: Deleting all clusters in the "functional-multitenancy-nested-jivyxg" namespace with intervals ["20m" "10s"]
[14] STEP: Deleting cluster functional-multitenancy-nested-75fzar
... skipping 45 lines ...
[14] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:50
[14]   Multitenancy test
[14]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:162
[14]     should create cluster with nested assumed role [It]
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
[14] 
[14]     Expected success, but got an error:
[14]         <*errors.withStack | 0xc000bda8d0>: {
[14]             error: <*exec.ExitError | 0xc000218840>{
[14]                 ProcessState: {
[14]                     pid: 30337,
[14]                     status: 256,
[14]                     rusage: {
[14]                         Utime: {Sec: 0, Usec: 803147},
[14]                         Stime: {Sec: 0, Usec: 360083},
... skipping 520 lines ...
[8]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/e2e/clusterctl_upgrade.go:147
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 1 of 1 Specs in 2311.389 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[18] STEP: Node 18 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[18] STEP: Creating a namespace for hosting the "functional-test-ssm-parameter-store" test spec
[18] INFO: Creating namespace functional-test-ssm-parameter-store-3ac9rv
[18] INFO: Creating event watcher for namespace "functional-test-ssm-parameter-store-3ac9rv"
[18] STEP: Creating a cluster
... skipping 46 lines ...
[12]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/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 2342.016 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[10] STEP: Deleting namespace used for hosting the "" test spec
[10] INFO: Deleting namespace functional-multitenancy-nested-clusterclass-mi9jdw
[10] STEP: Node 10 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[10] 
[10] • [SLOW TEST:2021.819 seconds]
... skipping 5 lines ...
[10]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:54
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 2361.902 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[14] STEP: Node 14 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[14] STEP: Creating a namespace for hosting the "functional-test-multi-az" test spec
[14] INFO: Creating namespace functional-test-multi-az-z57vmz
[14] INFO: Creating event watcher for namespace "functional-test-multi-az-z57vmz"
[14] STEP: Creating a cluster
... skipping 62 lines ...
[19]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/e2e/machine_pool.go:76
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 1 Specs in 2482.101 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[9] STEP: Node 9 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[9] STEP: Creating a namespace for hosting the "functional-test-spot-instances" test spec
[9] INFO: Creating namespace functional-test-spot-instances-45blvs
[9] INFO: Creating event watcher for namespace "functional-test-spot-instances-45blvs"
[9] STEP: Creating a cluster
... skipping 32 lines ...
[2]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:96
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 2504.036 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[4] INFO: Waiting for control plane to be initialized
[4] INFO: Waiting for the first control plane machine managed by functional-gpu-cluster-hfc3it/functional-gpu-cluster-7c3m24-control-plane to be provisioned
[4] STEP: Waiting for one control plane node to exist
[16] INFO: Waiting for control plane to be ready
[16] INFO: Waiting for control plane quick-start-3cbjk1/quick-start-u8qtqp-vgsth to be ready (implies underlying nodes to be ready as well)
... skipping 27 lines ...
[7]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/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 2620.370 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[16] INFO: Waiting for the machine deployments to be provisioned
[20] STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
[16] STEP: Waiting for the workload nodes to exist
[20] INFO: Deleting namespace clusterctl-upgrade-1ma9kn
[20] [AfterEach] Clusterctl Upgrade Spec [from v1alpha4]
... skipping 16 lines ...
[20]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/e2e/clusterctl_upgrade.go:147
[20] ------------------------------
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 1 of 1 Specs in 2631.780 seconds
[20] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[16] STEP: Deleting cluster quick-start-u8qtqp
[16] INFO: Waiting for the Cluster quick-start-3cbjk1/quick-start-u8qtqp to be deleted
[16] STEP: Waiting for cluster quick-start-u8qtqp to be deleted
[1] INFO: Waiting for control plane to be ready
[1] INFO: Waiting for control plane functional-test-md-misconfigurations-tr2ggm/functional-test-md-misconfigurations-87jcyv-control-plane to be ready (implies underlying nodes to be ready as well)
... skipping 66 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/e2e/quick_start.go:77
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 1 Specs in 2683.260 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[6] STEP: Retrieving IDs of dynamically provisioned volumes.
[6] STEP: Ensuring dynamically provisioned volumes exists
[6] STEP: Deleting LB service
[6] STEP: Deleting the Clusters
[6] STEP: Deleting cluster csimigration-off-upgrade-9gil2o
... skipping 13 lines ...
[11]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/e2e/cluster_upgrade.go:115
[11] ------------------------------
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 1 Specs in 2689.538 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[11] PASS
[1] STEP: Deleting all clusters in the "functional-test-md-misconfigurations-tr2ggm" namespace with intervals ["20m" "10s"]
[1] STEP: Deleting cluster functional-test-md-misconfigurations-87jcyv
[1] INFO: Waiting for the Cluster functional-test-md-misconfigurations-tr2ggm/functional-test-md-misconfigurations-87jcyv to be deleted
[1] STEP: Waiting for cluster functional-test-md-misconfigurations-87jcyv to be deleted
[15] STEP: Deleting all clusters in the "functional-test-ignition-vowy7l" namespace with intervals ["20m" "10s"]
... skipping 35 lines ...
[17] STEP: Deleting namespace used for hosting the "" test spec
[17] INFO: Deleting namespace functional-efs-support-r7eek1
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 2750.486 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[3] STEP: Retrieving IDs of dynamically provisioned volumes.
[3] STEP: Ensuring dynamically provisioned volumes exists
[3] INFO: Creating the workload cluster with name "csi-ccm-external-upgrade-c29z5k" using the "external-cloud-provider" template (Kubernetes v1.23.3, 1 control-plane machines, 1 worker machines)
[3] INFO: Getting the cluster template yaml
[3] INFO: clusterctl config cluster csi-ccm-external-upgrade-c29z5k --infrastructure (default) --kubernetes-version v1.23.3 --control-plane-machine-count 1 --worker-machine-count 1 --flavor external-cloud-provider
... skipping 145 lines ...
[16]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/e2e/quick_start.go:77
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 1 of 1 Specs in 3083.888 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[6] STEP: Deleting retained dynamically provisioned volumes
[6] STEP: Deleting dynamically provisioned volumes
[6] STEP: Deleted dynamically provisioned volume with ID: vol-06f522e80cb7e13cc
[6] STEP: Deleted dynamically provisioned volume with ID: vol-0d5203820ce9163c9
[6] STEP: PASSED!
... skipping 13 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 3159.863 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[6] PASS
[15] STEP: Deleting namespace used for hosting the "" test spec
[15] INFO: Deleting namespace functional-test-ignition-vowy7l
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 2 of 3 Specs in 3171.792 seconds
[15] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[15] PASS
[18] STEP: Deleting namespace used for hosting the "" test spec
[18] INFO: Deleting namespace functional-test-ssm-parameter-store-3ac9rv
[18] STEP: Node 18 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[18] 
[18] • [SLOW TEST:1692.593 seconds]
... skipping 5 lines ...
[18]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:466
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 2 of 2 Specs in 3185.062 seconds
[18] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[3] STEP: Creating the LB service
[3] STEP: Creating service of type Load Balancer with name: test-svc-4u2v91 under namespace: default
[3] STEP: Created Load Balancer service and ELB name is: a7bfc55dd56b34c8bb9799ebe3fb6314
[3] STEP: Verifying ELB with name a7bfc55dd56b34c8bb9799ebe3fb6314 present
[3] STEP: ELB with name a7bfc55dd56b34c8bb9799ebe3fb6314 exists
... skipping 33 lines ...
[13]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 1 Specs in 3343.782 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[13] PASS
[9] STEP: Deleting namespace used for hosting the "" test spec
[9] INFO: Deleting namespace functional-test-spot-instances-45blvs
[9] STEP: Node 9 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[9] 
[9] • [SLOW TEST:1537.604 seconds]
... skipping 5 lines ...
[9]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[9] ------------------------------
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 2 of 4 Specs in 3384.474 seconds
[9] SUCCESS! -- 2 Passed | 0 Failed | 2 Pending | 0 Skipped
[9] PASS
[4] STEP: Deleting namespace used for hosting the "" test spec
[4] INFO: Deleting namespace functional-gpu-cluster-hfc3it
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 3506.895 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[14] STEP: Deleting namespace used for hosting the "" test spec
[14] INFO: Deleting namespace functional-test-multi-az-z57vmz
[14] STEP: Node 14 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[14] 
[14] • [SLOW TEST:1785.888 seconds]
... skipping 7 lines ...
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] 
[14] Summarizing 1 Failure:
[14] 
[14] [Fail] [unmanaged] [functional] Multitenancy test [It] should create cluster with nested assumed role 
[14] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.2/framework/clusterctl/clusterctl_helpers.go:273
[14] 
[14] Ran 2 of 2 Specs in 3529.571 seconds
[14] FAIL! -- 1 Passed | 1 Failed | 0 Pending | 0 Skipped
[14] --- FAIL: TestE2E (3529.61s)
[14] FAIL
[3] STEP: Deleting retained dynamically provisioned volumes
[3] STEP: Deleting dynamically provisioned volumes
[3] STEP: Deleted dynamically provisioned volume with ID: vol-0c0d995b12f6dc436
[3] STEP: Deleted dynamically provisioned volume with ID: vol-0aac86ba7aff9eec6
[3] STEP: PASSED!
[3] STEP: Dumping all the Cluster API resources in the "csi-ccm-external-upgrade-3hnowh" namespace
... skipping 12 lines ...
[3]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 1 of 1 Specs in 3659.281 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] 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 2 of 2 Specs in 4100.196 seconds
[1] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h10m9.982364014s
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	70m9.993s
user	26m47.667s
sys	7m1.059s
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 ...