This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 24 succeeded
Started2022-08-11 17:39
Elapsed1h59m
Revisione364c8309cca312ceb2cc75d7e8a6005b1860068

Test Failures


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

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.17.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 1911 lines ...
[10]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/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 1608.773 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-spot-instances" test spec
[14] INFO: Creating namespace functional-test-spot-instances-mbgllt
[14] INFO: Creating event watcher for namespace "functional-test-spot-instances-mbgllt"
[14] STEP: Creating a cluster
... skipping 36 lines ...
[9]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/mhc_remediations.go:114
[9] ------------------------------
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 1 of 1 Specs in 1721.491 seconds
[9] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[7] STEP: Node 7 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:4}
[7] STEP: Creating a namespace for hosting the "only-csi-external-upgrade" test spec
[18] STEP: Node 18 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:4}
[18] STEP: Creating a namespace for hosting the "csi-ccm-external-upgrade" test spec
[20] STEP: Node 20 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:4, volume-gp2:0}
... skipping 291 lines ...
[15] STEP: Deleting namespace used for hosting the "" test spec
[15] INFO: Deleting namespace functional-test-ignition-tk2vjy
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 2 of 3 Specs in 2351.885 seconds
[15] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[15] PASS
[1] STEP: Deleting namespace used for hosting the "" test spec
[1] INFO: Deleting namespace functional-test-ssm-parameter-store-vhltfd
[1] STEP: Node 1 released resources: {ec2-normal:4, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[1] 
[1] • [SLOW TEST:1084.939 seconds]
... skipping 42 lines ...
[12]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 2388.076 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[13] STEP: Node 13 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[13] STEP: Creating a namespace for hosting the "functional-test-md-misconfigurations" test spec
[13] INFO: Creating namespace functional-test-md-misconfigurations-9gd31i
[13] INFO: Creating event watcher for namespace "functional-test-md-misconfigurations-9gd31i"
[13] STEP: Creating a cluster
... skipping 29 lines ...
[6] STEP: Deleting namespace used for hosting the "" test spec
[6] INFO: Deleting namespace functional-efs-support-of326k
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 1 Specs in 2472.612 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[11] STEP: Upgrading the machinepool instances
[11] INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-and-conformance-gidfod/k8s-upgrade-and-conformance-t3e6e4-mp-0
[11] INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-and-conformance-gidfod/k8s-upgrade-and-conformance-t3e6e4-mp-0 to be upgraded from v1.23.6 to v1.24.0
[11] INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
[8] STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-5l89h6
... skipping 13 lines ...
[4]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 2581.494 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[18] INFO: Waiting for control plane to be initialized
[18] INFO: Waiting for the first control plane machine managed by csi-ccm-external-upgrade-mzx3hh/csi-ccm-external-upgrade-lv0elg-control-plane to be provisioned
[18] STEP: Waiting for one control plane node to exist
[8] STEP: Dumping logs from the "clusterctl-upgrade-5l89h6" workload cluster
[8] STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-tsu3s0" namespace
... skipping 22 lines ...
[16]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 1 of 1 Specs in 2627.794 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[2] STEP: Deleting namespace used for hosting the "" test spec
[2] INFO: Deleting namespace functional-test-multi-az-t10ums
[2] STEP: Node 2 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[2] 
[2] • [SLOW TEST:1216.162 seconds]
... skipping 5 lines ...
[2]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 2 of 2 Specs in 2702.480 seconds
[2] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[18] INFO: Waiting for control plane to be ready
[18] INFO: Waiting for control plane csi-ccm-external-upgrade-mzx3hh/csi-ccm-external-upgrade-lv0elg-control-plane to be ready (implies underlying nodes to be ready as well)
[18] STEP: Waiting for the control plane to be ready
[18] STEP: Checking all the the control plane machines are in the expected failure domains
[18] INFO: Waiting for the machine deployments to be provisioned
... skipping 182 lines ...
[8]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/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 3057.491 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[7] STEP: Retrieving IDs of dynamically provisioned volumes.
[7] STEP: Ensuring dynamically provisioned volumes exists
[7] INFO: Creating the workload cluster with name "only-csi-external-upgrade-lm4qes" using the "external-csi" template (Kubernetes v1.23.3, 1 control-plane machines, 1 worker machines)
[7] INFO: Getting the cluster template yaml
[7] INFO: clusterctl config cluster only-csi-external-upgrade-lm4qes --infrastructure (default) --kubernetes-version v1.23.3 --control-plane-machine-count 1 --worker-machine-count 1 --flavor external-csi
... skipping 65 lines ...
[3]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 1 of 2 Specs in 3239.224 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[3] PASS
[13] STEP: Deleting namespace used for hosting the "" test spec
[13] INFO: Deleting namespace functional-test-md-misconfigurations-9gd31i
[13] STEP: Node 13 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[13] 
[13] • [SLOW TEST:1917.007 seconds]
... skipping 5 lines ...
[13]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:500
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 2 of 2 Specs in 3247.670 seconds
[13] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[13] PASS
[19] INFO: Waiting for CoreDNS to have the upgraded image tag
[19] STEP: Ensuring CoreDNS has the correct image
[19] INFO: Waiting for etcd to have the upgraded image tag
[19] STEP: Waiting until nodes are ready
[19] STEP: PASSED!
... skipping 38 lines ...
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 2 of 4 Specs in 3390.536 seconds
[14] SUCCESS! -- 2 Passed | 0 Failed | 2 Pending | 0 Skipped
[14] PASS
[5] STEP: Deleting namespace used for hosting the "quick-start" test spec
[5] INFO: Deleting namespace quick-start-ownu9h
[5] [AfterEach] Running the quick-start spec with ClusterClass
[5]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_quick_clusterclass_test.go:67
[5] STEP: Node 5 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 14 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/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 3411.048 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[11] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[11] INFO: Deleting namespace k8s-upgrade-and-conformance-gidfod
[11] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[11]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:183
[11] STEP: Node 11 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[11]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[11] ------------------------------
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 1 Specs in 3477.245 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[11] PASS
[7] STEP: Creating the LB service
[7] STEP: Creating service of type Load Balancer with name: test-svc-b2y3yl under namespace: default
[7] STEP: Created Load Balancer service and ELB name is: a7163183ab2e74d6e977c33dc76c96ba
[7] STEP: Verifying ELB with name a7163183ab2e74d6e977c33dc76c96ba present
[7] STEP: ELB with name a7163183ab2e74d6e977c33dc76c96ba exists
... skipping 28 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 3622.701 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[20] STEP: Deleting namespace used for hosting the "" test spec
[20] INFO: Deleting namespace functional-gpu-cluster-8ic68v
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 1 of 1 Specs in 3688.454 seconds
[20] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[18] STEP: Deleting retained dynamically provisioned volumes
[18] STEP: Deleting dynamically provisioned volumes
[18] STEP: Deleted dynamically provisioned volume with ID: vol-02f082ec891f8bf17
[18] STEP: Deleted dynamically provisioned volume with ID: vol-04495a529b01f9c35
[18] STEP: PASSED!
... skipping 13 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 3837.437 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[7] STEP: Deleting retained dynamically provisioned volumes
[7] STEP: Deleting dynamically provisioned volumes
[7] STEP: Deleted dynamically provisioned volume with ID: vol-076f7bfe92c3f93e5
[7] STEP: Deleted dynamically provisioned volume with ID: vol-071f425df6826cea0
[7] STEP: PASSED!
... skipping 13 lines ...
[7]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 3987.202 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[17] [AfterEach] Machine Pool Spec
[17]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/machine_pool.go:128
[17] STEP: Dumping logs from the "machine-pool-fs8z6b" workload cluster
[17] STEP: Dumping all the Cluster API resources in the "machine-pool-cnb88l" namespace
[17] STEP: Deleting cluster machine-pool-cnb88l/machine-pool-fs8z6b
... skipping 61 lines ...
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] 
[17] Summarizing 1 Failure:
[17] 
[17] [Fail] [unmanaged] [Cluster API Framework] Machine Pool Spec [It] Should successfully create a cluster with machine pool machines 
[17] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/machinepool_helpers.go:90
[17] 
[17] Ran 1 of 1 Specs in 6351.557 seconds
[17] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[17] --- FAIL: TestE2E (6351.61s)
[17] 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 6895.074 seconds
[1] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h56m31.578952162s
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	116m31.588s
user	26m1.166s
sys	6m51.880s
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 ...