This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2022-09-21 16:17
Elapsed1h3m
Revision852f846c8a92203685ad1dc31aacbab057aeb6f7

Test Failures


capa-eks-e2e [managed] [general] EKS cluster tests should create a cluster and add nodes 47m38s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-eks\-e2e\s\[managed\]\s\[general\]\sEKS\scluster\stests\sshould\screate\sa\scluster\sand\sadd\snodes$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:223
Timed out after 1800.001s.
Expected
    <int>: 0
to equal
    <int>: 1
/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.1.xml

Filter through log files | View test history on testgrid


Show 2 Passed Tests

Error lines from build-log.txt

... skipping 570 lines ...
[6] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[6] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 0 of 0 Specs in 343.331 seconds
[6] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[10] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[10] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[10] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[10] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[10] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 0 of 0 Specs in 343.385 seconds
[10] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[3] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[3] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[3] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[8] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[8] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
... skipping 3 lines ...
[3] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[3] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 0 of 0 Specs in 343.387 seconds
[3] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 0 of 0 Specs in 343.340 seconds
[8] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[4] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[4] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[4] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[4] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[4] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 0 of 0 Specs in 343.397 seconds
[4] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[9] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[9] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[9] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[9] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[9] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 0 of 0 Specs in 343.371 seconds
[9] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[7] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[7] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[7] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[7] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[7] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[2] INFO: Creating namespace eks-upgrade-uphukj
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 0 of 0 Specs in 343.349 seconds
[7] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[5] INFO: Creating namespace eks-nodes-2rnth2
[2] INFO: Creating event watcher for namespace "eks-upgrade-uphukj"
[2] STEP: default iam role should exist
[5] INFO: Creating event watcher for namespace "eks-nodes-2rnth2"
[5] STEP: default iam role should exist
... skipping 224 lines ...
[5] STEP: Deleting namespace used for hosting the "" test spec
[5] INFO: Deleting namespace eks-nodes-2rnth2
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 1 Specs in 1795.727 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[2] 
[2] • [SLOW TEST:1749.876 seconds]
[2] EKS Cluster upgrade test
[2] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/managed/upgrade_test.go:37
[2]   [managed] [upgrade] should create a cluster and upgrade the kubernetes version
... skipping 5 lines ...
[2] STEP: Deleting namespace used for hosting the "" test spec
[2] INFO: Deleting namespace eks-upgrade-uphukj
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 2093.807 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[1] 
[1] • Failure [2858.435 seconds]
[1] [managed] [general] EKS cluster tests
[1] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/managed/eks_test.go:37
[1]   should create a cluster and add nodes [It]
... skipping 61 lines ...
[1] 
[1] JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml
[1] 
[1] 
[1] Summarizing 1 Failure:
[1] 
[1] [Fail] [managed] [general] EKS cluster tests [It] should create a cluster and add nodes 
[1] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/machinepool_helpers.go:90
[1] 
[1] Ran 1 of 1 Specs in 3533.209 seconds
[1] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[1] --- FAIL: TestE2E (3533.22s)
[1] FAIL

Ginkgo ran 1 suite in 1h0m29.446267235s
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	60m29.455s
user	13m7.219s
sys	2m50.751s
make: *** [Makefile:405: test-e2e-eks] 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 ...