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 12:18
Elapsed1h43m
Revisiond409991431b51a9b475fdb322c2ec9137498e12f

Test Failures


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

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.5.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 1885 lines ...
[12]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/mhc_remediations.go:114
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 1745.020 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[16] STEP: Node 16 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[16] STEP: Creating a namespace for hosting the "functional-test-md-misconfigurations" test spec
[16] INFO: Creating namespace functional-test-md-misconfigurations-t42q0a
[16] INFO: Creating event watcher for namespace "functional-test-md-misconfigurations-t42q0a"
[16] STEP: Creating a cluster
... skipping 299 lines ...
[8]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 1 of 1 Specs in 2091.652 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[4] STEP: Node 4 acquired resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[4] [BeforeEach] Running the quick-start spec
[4]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:62
[4] STEP: Creating a namespace for hosting the "quick-start" test spec
[4] INFO: Creating namespace quick-start-ka5srm
... skipping 58 lines ...
[20] INFO: Waiting for the cluster infrastructure to be provisioned
[20] 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 2095.208 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[11] PASS
[5] STEP: Waiting for the machine pool workload nodes
[5] STEP: Scaling the machine pool to zero
[5] INFO: Patching the replica count in Machine Pool machine-pool-1iboz9/machine-pool-3yxlb2-mp-0
[5] INFO: Patching the replica count in Machine Pool machine-pool-1iboz9/machine-pool-3yxlb2-mp-1
[5] STEP: Waiting for the machine pool workload nodes
... skipping 35 lines ...
[7] STEP: Deleting namespace used for hosting the "" test spec
[7] INFO: Deleting namespace functional-test-ignition-6fg2kx
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 2 of 3 Specs in 2204.637 seconds
[7] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[7] PASS
[3] INFO: Waiting for kube-proxy to have the upgraded kubernetes version
[3] STEP: Ensuring kube-proxy has the correct image
[3] INFO: Waiting for CoreDNS to have the upgraded image tag
[3] STEP: Ensuring CoreDNS has the correct image
[3] INFO: Waiting for etcd to have the upgraded image tag
... skipping 37 lines ...
[6]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 1 Specs in 2440.062 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[17] STEP: Node 17 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:4, volume-gp2:0}
[17] STEP: Creating cluster with a single worker
[17] INFO: Creating the workload cluster with name "functional-gpu-cluster-upjz4y" using the "gpu" template (Kubernetes v1.24.0, 1 control-plane machines, 1 worker machines)
[17] INFO: Getting the cluster template yaml
[17] INFO: clusterctl config cluster functional-gpu-cluster-upjz4y --infrastructure (default) --kubernetes-version v1.24.0 --control-plane-machine-count 1 --worker-machine-count 1 --flavor gpu
... skipping 92 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 2517.551 seconds
[2] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[20] STEP: Checking all the machines controlled by quick-start-20tk41-md-0-swc7p are in the "<None>" failure domain
[20] INFO: Waiting for the machine pools to be provisioned
[20] STEP: PASSED!
[20] [AfterEach] Running the quick-start spec with ClusterClass
[20]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:107
... skipping 23 lines ...
[19]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 1 Specs in 2531.546 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[18] STEP: Retrieving IDs of dynamically provisioned volumes.
[18] STEP: Ensuring dynamically provisioned volumes exists
[18] STEP: Deleting LB service
[18] STEP: Deleting the Clusters
[18] STEP: Deleting cluster csimigration-off-upgrade-c6u160
... skipping 24 lines ...
[3]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 1 of 1 Specs in 2557.983 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[13] STEP: Created Load Balancer service and ELB name is: a96dd18f703364bed831cefdebf2ed5e
[13] STEP: Verifying ELB with name a96dd18f703364bed831cefdebf2ed5e present
[13] STEP: ELB with name a96dd18f703364bed831cefdebf2ed5e exists
[13] STEP: Checking v1.22 StatefulSet still healthy after the upgrade
[13] STEP: Ensuring Statefulset(intree-nginx-statefulset) is running
... skipping 23 lines ...
[16]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:500
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 2 of 2 Specs in 2602.706 seconds
[16] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[15] STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
[15] INFO: Deleting namespace clusterctl-upgrade-esh9w8
[15] [AfterEach] Clusterctl Upgrade Spec [from latest v1beta1 release to main]
[15]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:133
[15] STEP: Node 15 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[15]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[15] ------------------------------
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 1 of 1 Specs in 2610.043 seconds
[15] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[15] PASS
[9] STEP: Upgrading the machinepool instances
[9] INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-and-conformance-kn3cln/k8s-upgrade-and-conformance-16prf2-mp-0
[9] INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-and-conformance-kn3cln/k8s-upgrade-and-conformance-16prf2-mp-0 to be upgraded from v1.23.6 to v1.24.0
[9] INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
[17] INFO: Waiting for control plane to be initialized
... skipping 28 lines ...
[4]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:77
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 2815.868 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[17] STEP: Checking all the machines controlled by functional-gpu-cluster-upjz4y-md are in the "<None>" failure domain
[17] INFO: Waiting for the machine pools to be provisioned
[17] STEP: creating a Kubernetes client to the workload cluster
[17] STEP: running a CUDA vector calculation job
[20] STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 18 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 2837.595 seconds
[20] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[10] STEP: Deleting retained dynamically provisioned volumes
[10] STEP: Deleting dynamically provisioned volumes
[10] STEP: Deleted dynamically provisioned volume with ID: vol-0834b517c13fcfec5
[10] STEP: Deleted dynamically provisioned volume with ID: vol-091f681155267976a
[10] STEP: PASSED!
... skipping 13 lines ...
[10]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 2929.847 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[14] STEP: Deleting namespace used for hosting the "" test spec
[14] INFO: Deleting namespace functional-test-ssm-parameter-store-p1unf0
[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:2622.719 seconds]
... skipping 5 lines ...
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:466
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 1 Specs in 2950.576 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[14] PASS
[9] STEP: Waiting until nodes are ready
[9] STEP: PASSED!
[9] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[9]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:240
[9] STEP: Dumping logs from the "k8s-upgrade-and-conformance-16prf2" workload cluster
... skipping 35 lines ...
[18]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 1 of 1 Specs in 3009.840 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[13] STEP: Deleting retained dynamically provisioned volumes
[13] STEP: Deleting dynamically provisioned volumes
[13] STEP: Deleted dynamically provisioned volume with ID: vol-08a5ff1bf89afe806
[13] STEP: Deleted dynamically provisioned volume with ID: vol-070749df6b0adfe72
[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:397
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 2 Specs in 3032.664 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[13] PASS
[17] STEP: PASSED!
[17] STEP: Node 17 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:4, volume-gp2:0}
[17] 
[17] • [SLOW TEST:2887.313 seconds]
[17] [unmanaged] [functional]
... skipping 24 lines ...
[9]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[9] ------------------------------
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 1 of 1 Specs in 3446.007 seconds
[9] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[17] STEP: Deleting namespace used for hosting the "" test spec
[17] INFO: Deleting namespace functional-gpu-cluster-ptp7io
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 3731.629 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[5] [AfterEach] Machine Pool Spec
[5]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/machine_pool.go:128
[5] STEP: Dumping logs from the "machine-pool-3yxlb2" workload cluster
[5] STEP: Dumping all the Cluster API resources in the "machine-pool-1iboz9" namespace
[5] STEP: Deleting cluster machine-pool-1iboz9/machine-pool-3yxlb2
... skipping 61 lines ...
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] 
[5] Summarizing 1 Failure:
[5] 
[5] [Fail] [unmanaged] [Cluster API Framework] Machine Pool Spec [It] Should successfully create a cluster with machine pool machines 
[5] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/machinepool_helpers.go:90
[5] 
[5] Ran 1 of 1 Specs in 5518.504 seconds
[5] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[5] --- FAIL: TestE2E (5518.58s)
[5] 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 4 Specs in 5952.901 seconds
[1] SUCCESS! -- 2 Passed | 0 Failed | 2 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h40m43.862268064s
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	100m43.872s
user	22m49.848s
sys	5m47.028s
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 ...