This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 25 succeeded
Started2022-08-11 21:31
Elapsed1h42m
Revision61d146ba145f292f71585232ea20dd1620a6ce8a

Test Failures


capa-e2e [unmanaged] [Cluster API Framework] Machine Pool Spec Should successfully create a cluster with machine pool machines 1h25m

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[Cluster\sAPI\sFramework\]\sMachine\sPool\sSpec\sShould\ssuccessfully\screate\sa\scluster\swith\smachine\spool\smachines$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/machine_pool.go:76
Timed out after 2400.001s.
Expected
    <int>: 1
to equal
    <int>: 0
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/machinepool_helpers.go:90
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 25 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 2244 lines ...
[10]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 2261.668 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[20] STEP: Node 20 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[20] [BeforeEach] Running the quick-start spec
[20]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:62
[20] STEP: Creating a namespace for hosting the "quick-start" test spec
[20] INFO: Creating namespace quick-start-cupj2k
... skipping 71 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 1 Specs in 2272.830 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[12] STEP: Node 12 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:4, volume-gp2:0}
[12] STEP: Creating cluster with a single worker
[12] INFO: Creating the workload cluster with name "functional-gpu-cluster-fl3s4s" using the "gpu" template (Kubernetes v1.24.0, 1 control-plane machines, 1 worker machines)
[12] INFO: Getting the cluster template yaml
[12] INFO: clusterctl config cluster functional-gpu-cluster-fl3s4s --infrastructure (default) --kubernetes-version v1.24.0 --control-plane-machine-count 1 --worker-machine-count 1 --flavor gpu
... skipping 79 lines ...
[1] INFO: Waiting for the cluster infrastructure to be provisioned
[1] STEP: Waiting for cluster to enter the provisioned phase
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 1 Specs in 2367.626 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[11] PASS
[18] INFO: Waiting for kube-proxy to have the upgraded kubernetes version
[18] STEP: Ensuring kube-proxy has the correct image
[18] INFO: Waiting for CoreDNS to have the upgraded image tag
[18] STEP: Ensuring CoreDNS has the correct image
[18] INFO: Waiting for etcd to have the upgraded image tag
... skipping 20 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 2437.324 seconds
[9] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[19] STEP: Upgrading the machinepool instances
[19] INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-and-conformance-fbzqj6/k8s-upgrade-and-conformance-1zi9ye-mp-0
[19] INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-and-conformance-fbzqj6/k8s-upgrade-and-conformance-1zi9ye-mp-0 to be upgraded from v1.23.6 to v1.24.0
[19] INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
[20] INFO: Waiting for control plane to be initialized
... skipping 18 lines ...
[8]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 2 of 4 Specs in 2525.739 seconds
[8] SUCCESS! -- 2 Passed | 0 Failed | 2 Pending | 0 Skipped
[8] 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 - HA control plane with workers [K8s-Upgrade] [ClusterClass]
[16]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:83
[16] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[16] INFO: Creating namespace k8s-upgrade-and-conformance-ca351c
... skipping 36 lines ...
[2]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 2563.476 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[20] INFO: Waiting for control plane to be ready
[20] INFO: Waiting for control plane quick-start-cupj2k/quick-start-awjhax-control-plane to be ready (implies underlying nodes to be ready as well)
[20] STEP: Waiting for the control plane to be ready
[13] STEP: Creating the LB service
[13] STEP: Creating service of type Load Balancer with name: test-svc-vi3de1 under namespace: default
... skipping 33 lines ...
[6]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 1 Specs in 2676.020 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[20] STEP: Checking all the the control plane machines are in the expected failure domains
[20] INFO: Waiting for the machine deployments to be provisioned
[20] STEP: Waiting for the workload nodes to exist
[15] STEP: Checking all the the control plane machines are in the expected failure domains
[15] INFO: Waiting for the machine deployments to be provisioned
... skipping 39 lines ...
[7]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:466
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 2704.650 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[4] STEP: Created Load Balancer service and ELB name is: a08ab9a9b911d41429cecd88ca681013
[4] STEP: Verifying ELB with name a08ab9a9b911d41429cecd88ca681013 present
[4] STEP: ELB with name a08ab9a9b911d41429cecd88ca681013 exists
[4] STEP: Checking v1.22 StatefulSet still healthy after the upgrade
[4] STEP: Ensuring Statefulset(intree-nginx-statefulset) is running
... skipping 27 lines ...
[18]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 1 of 1 Specs in 2731.497 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[12] STEP: Checking all the machines controlled by functional-gpu-cluster-fl3s4s-md are in the "<None>" failure domain
[12] INFO: Waiting for the machine pools to be provisioned
[12] STEP: creating a Kubernetes client to the workload cluster
[12] STEP: running a CUDA vector calculation job
[14] STEP: Retrieving IDs of dynamically provisioned volumes.
... skipping 43 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 2 of 2 Specs in 2787.655 seconds
[17] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[1] INFO: Waiting for provider controllers to be running
[1] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
[16] INFO: Waiting for control plane to be ready
[16] INFO: Waiting for the remaining control plane machines managed by k8s-upgrade-and-conformance-ca351c/k8s-upgrade-and-conformance-gxiles-7284v to be provisioned
[16] STEP: Waiting for all control plane nodes to exist
... skipping 83 lines ...
[20]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:77
[20] ------------------------------
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 1 of 1 Specs in 3106.378 seconds
[20] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[13] STEP: Deleting retained dynamically provisioned volumes
[13] STEP: Deleting dynamically provisioned volumes
[13] STEP: Deleted dynamically provisioned volume with ID: vol-0eb71e2d1efab0e77
[13] STEP: Deleted dynamically provisioned volume with ID: vol-05702bc8e271f94d8
[13] STEP: PASSED!
... skipping 13 lines ...
[13]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 2 Specs in 3113.119 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[13] PASS
[12] STEP: PASSED!
[12] STEP: Node 12 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:4, volume-gp2:0}
[12] 
[12] • [SLOW TEST:2787.680 seconds]
[12] [unmanaged] [functional]
... skipping 36 lines ...
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 1 Specs in 3137.908 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[14] PASS
[12] STEP: Deleting all clusters in the "functional-gpu-cluster-3gvntu" namespace with intervals ["20m" "10s"]
[12] STEP: Deleting cluster functional-gpu-cluster-fl3s4s
[12] INFO: Waiting for the Cluster functional-gpu-cluster-3gvntu/functional-gpu-cluster-fl3s4s to be deleted
[12] STEP: Waiting for cluster functional-gpu-cluster-fl3s4s to be deleted
[4] STEP: Deleting retained dynamically provisioned volumes
... skipping 17 lines ...
[4]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 3228.129 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[1] STEP: Deleting namespace used for hosting the "self-hosted" test spec
[1] INFO: Deleting namespace self-hosted-qaklh9
[1] [AfterEach] Self Hosted Spec [ClusterClass]
[1]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_clusterclass_test.go:64
[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}
... skipping 9 lines ...
[15] STEP: Deleting namespace used for hosting the "" test spec
[15] INFO: Deleting namespace functional-test-ignition-1vu71d
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 3 of 4 Specs in 3370.850 seconds
[15] SUCCESS! -- 3 Passed | 0 Failed | 1 Pending | 0 Skipped
[15] PASS
[19] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[19] INFO: Deleting namespace k8s-upgrade-and-conformance-fbzqj6
[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 7 lines ...
[19]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 1 Specs in 3598.735 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[12] STEP: Deleting namespace used for hosting the "" test spec
[12] INFO: Deleting namespace functional-gpu-cluster-3gvntu
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 3608.989 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[16] INFO: Waiting for kube-proxy to have the upgraded Kubernetes version
[16] STEP: Ensuring kube-proxy has the correct image
[16] INFO: Waiting for CoreDNS to have the upgraded image tag
[16] STEP: Ensuring CoreDNS has the correct image
[16] INFO: Waiting for etcd to have the upgraded image tag
... skipping 24 lines ...
[16]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 2 of 2 Specs in 4822.829 seconds
[16] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[3] [AfterEach] Machine Pool Spec
[3]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/machine_pool.go:128
[3] STEP: Dumping logs from the "machine-pool-0amndp" workload cluster
[3] STEP: Dumping all the Cluster API resources in the "machine-pool-boy9tw" namespace
[3] STEP: Deleting cluster machine-pool-boy9tw/machine-pool-0amndp
... skipping 61 lines ...
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] 
[3] Summarizing 1 Failure:
[3] 
[3] [Fail] [unmanaged] [Cluster API Framework] Machine Pool Spec [It] Should successfully create a cluster with machine pool machines 
[3] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/machinepool_helpers.go:90
[3] 
[3] Ran 1 of 1 Specs in 5431.095 seconds
[3] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[3] --- FAIL: TestE2E (5431.15s)
[3] FAIL
[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 5897.591 seconds
[1] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h39m55.06631467s
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	99m55.078s
user	25m38.625s
sys	6m58.344s
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 ...