This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2022-09-27 10:44
Elapsed1h20m
Revision2c8580ad04ac8416f655af4d21c1a591fe45277e

Test Failures


capa-eks-e2e [managed] [general] [ipv6] EKS cluster tests should create a cluster and add nodes 30m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-eks\-e2e\s\[managed\]\s\[general\]\s\[ipv6\]\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.003s.
Expected
    <string>: Provisioning
to equal
    <string>: Provisioned
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/framework/cluster_helpers.go:143
				
				Click to see stdout/stderrfrom junit.e2e_suite.8.xml

Filter through log files | View test history on testgrid


Show 2 Passed Tests

Error lines from build-log.txt

... skipping 560 lines ...
[2] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[2] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 0 of 0 Specs in 365.724 seconds
[2] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] 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 365.741 seconds
[10] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[6] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[6] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[6] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[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=*******
[1] INFO: Creating event watcher for namespace "eks-upgrade-lrmh2a"
[1] STEP: default iam role should exist
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 0 of 0 Specs in 365.748 seconds
[6] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[8] INFO: Creating namespace eks-nodes-cspcs8
[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=*******
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 0 of 0 Specs in 365.740 seconds
[7] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] 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
[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 365.767 seconds
[3] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[5] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[5] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[5] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[5] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[5] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
... skipping 3 lines ...
[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=*******
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 0 of 0 Specs in 365.775 seconds
[5] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 0 of 0 Specs in 365.778 seconds
[4] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[8] INFO: Creating event watcher for namespace "eks-nodes-cspcs8"
[8] STEP: default iam role should exist
[9] INFO: Creating namespace cluster-kk39lc
[9] INFO: Creating event watcher for namespace "cluster-kk39lc"
[9] STEP: default iam role should exist
... skipping 198 lines ...
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] 
[8] Summarizing 1 Failure:
[8] 
[8] [Fail] [managed] [general] [ipv6] EKS cluster tests [It] should create a cluster and add nodes 
[8] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/framework/cluster_helpers.go:143
[8] 
[8] Ran 1 of 1 Specs in 2319.894 seconds
[8] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[8] --- FAIL: TestE2E (2319.90s)
[8] FAIL
[9] STEP: should create a machine pool and scale
[9] STEP: getting cluster with name cluster-9xbmzh
[9] STEP: creating an applying the eks-machinepool-only template
[9] STEP: Getting the cluster template yaml
[9] INFO: clusterctl config cluster cluster-9xbmzh --infrastructure aws --kubernetes-version v1.22.9 --control-plane-machine-count 1 --worker-machine-count 1 --flavor eks-machinepool-only
[9] STEP: apiVersion: cluster.x-k8s.io/v1beta1
... skipping 130 lines ...
[9] STEP: Deleting namespace used for hosting the "" test spec
[9] INFO: Deleting namespace cluster-kk39lc
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 1 of 1 Specs in 4358.130 seconds
[9] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[1] folder created for eks clusters: /logs/artifacts/clusters/bootstrap/aws-resources
[1] STEP: Deleting AWS static credentials
[1] STEP: Deleting AWSClusterStaticIdentity e2e-account
[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 1 of 1 Specs in 4565.483 seconds
[1] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h17m40.186668028s
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	77m40.197s
user	13m58.358s
sys	3m19.773s
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 ...