This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultsuccess
Tests 0 failed / 3 succeeded
Started2022-09-02 19:22
Elapsed1h19m
Revision
uploadercrier
uploadercrier

No Test Failures!


Show 3 Passed Tests

Error lines from build-log.txt

... skipping 573 lines ...
[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 324.582 seconds
[10] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[4] INFO: Creating namespace eks-nodes-l8khsk
[2] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[2] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[2] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[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 324.568 seconds
[2] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[4] INFO: Creating event watcher for namespace "eks-nodes-l8khsk"
[4] STEP: default iam role should exist
[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 324.581 seconds
[3] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[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
[8] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[8] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[8] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 0 of 0 Specs in 324.591 seconds
[8] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] 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=*******
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 0 of 0 Specs in 324.587 seconds
[5] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] 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=*******
... skipping 3 lines ...
[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=*******
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 0 of 0 Specs in 324.618 seconds
[6] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] Ran 0 of 0 Specs in 324.617 seconds
[9] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[9] PASS
[7] INFO: Creating namespace eks-upgrade-26i4tj
[7] INFO: Creating event watcher for namespace "eks-upgrade-26i4tj"
[7] STEP: default iam role should exist
[1] STEP: should create an EKS control plane
[1] STEP: creating an applying the eks-control-plane-only-withaddon template
... skipping 224 lines ...
[4] STEP: Deleting namespace used for hosting the "" test spec
[4] INFO: Deleting namespace eks-nodes-l8khsk
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 1671.644 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[7] STEP: Deleting cluster eks-upgrade-7o3o8i
[7] STEP: Waiting for cluster eks-upgrade-7o3o8i to be deleted
[1] STEP: Scaling the machine pool down
[1] INFO: Patching the replica count in Machine Pool cluster-nuogp4/cluster-kcacrw-pool-0
[1] STEP: Waiting for the machine pool workload nodes
... skipping 10 lines ...
[7] STEP: Deleting namespace used for hosting the "" test spec
[7] INFO: Deleting namespace eks-upgrade-26i4tj
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 1923.429 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[1] STEP: Deleting machine pool cluster-kcacrw-pool-0
[1] STEP: Waiting for machine pool cluster-kcacrw-pool-0 to be deleted
[1] STEP: should create a machine pool and scale
[1] STEP: getting cluster with name cluster-kcacrw
[1] STEP: creating an applying the eks-machinepool-only template
... skipping 138 lines ...
[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 4492.444 seconds
[1] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h16m26.390660456s
Test Suite Passed

real	76m26.398s
... skipping 12 lines ...