This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 21 succeeded
Started2022-09-13 04:57
Elapsed1h26m
Revisionmain

Test Failures


capa-e2e [unmanaged] [functional] Multitenancy test should create cluster with nested assumed role 32m20s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[functional\]\sMultitenancy\stest\sshould\screate\scluster\swith\snested\sassumed\srole$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
Timed out after 1800.000s.
Expected
    <string>: Provisioning
to equal
    <string>: Provisioned
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/cluster_helpers.go:143
				
				Click to see stdout/stderrfrom junit.e2e_suite.9.xml

Filter through log files | View test history on testgrid


Show 21 Passed Tests

Show 8 Skipped Tests

Error lines from build-log.txt

... skipping 1768 lines ...
[18]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:77
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 1 of 1 Specs in 1316.059 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[20] INFO: Applying the cluster template yaml to the cluster
[11] STEP: Dumping all EC2 instances in the "functional-gpu-cluster-1qs5vk" namespace
[20] cluster.cluster.x-k8s.io/clusterctl-upgrade-iz32wl created
[20] awscluster.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-iz32wl created
[20] kubeadmcontrolplane.controlplane.cluster.x-k8s.io/clusterctl-upgrade-iz32wl-control-plane created
... skipping 21 lines ...
[7]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 3 Specs in 1330.977 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 2 Pending | 0 Skipped
[7] PASS
[16] STEP: Node 16 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[16] [BeforeEach] Clusterctl Upgrade Spec [from v1alpha4]
[16]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:122
[16] STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec
[16] INFO: Creating namespace clusterctl-upgrade-dh3oc9
... skipping 94 lines ...
[5]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/self_hosted.go:80
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 1 Specs in 1524.770 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[4] INFO: Waiting for control plane to be initialized
[4] INFO: Waiting for the first control plane machine managed by mhc-remediation-1zz7q8/mhc-remediation-m32t3a-control-plane to be provisioned
[4] STEP: Waiting for one control plane node to exist
[2] INFO: Waiting for control plane to be initialized
[2] INFO: Waiting for the first control plane machine managed by quick-start-paqzt0/quick-start-ajsh9n-hqjp9 to be provisioned
... skipping 16 lines ...
[19]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/mhc_remediations.go:82
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 1 Specs in 1604.261 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[19] PASS
[10] STEP: Node 10 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[10] [BeforeEach] Cluster Upgrade Spec - HA control plane with scale in rollout [K8s-Upgrade]
[10]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:83
[10] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[10] INFO: Creating namespace k8s-upgrade-and-conformance-q2avfi
... skipping 61 lines ...
[17]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[17] ------------------------------
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 1613.832 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[15] STEP: Checking all the the control plane machines are in the expected failure domains
[15] INFO: Waiting for the machine deployments to be provisioned
[15] STEP: Waiting for the workload nodes to exist
[2] INFO: Waiting for control plane to be ready
[2] INFO: Waiting for control plane quick-start-paqzt0/quick-start-ajsh9n-hqjp9 to be ready (implies underlying nodes to be ready as well)
... skipping 47 lines ...
[13]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 2 Specs in 1779.071 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[13] PASS
[3] STEP: Node 3 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[3] [BeforeEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[3]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:83
[3] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[3] INFO: Creating namespace k8s-upgrade-and-conformance-fkrprt
... skipping 41 lines ...
[6]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 1 of 1 Specs in 1805.881 seconds
[6] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS
[10] INFO: Waiting for control plane to be initialized
[10] INFO: Waiting for the first control plane machine managed by k8s-upgrade-and-conformance-q2avfi/k8s-upgrade-and-conformance-yylhyj-control-plane to be provisioned
[10] STEP: Waiting for one control plane node to exist
[1] INFO: Waiting for control plane to be initialized
[1] INFO: Waiting for the first control plane machine managed by functional-efs-support-bv448e/cluster-imtcmb-control-plane to be provisioned
... skipping 14 lines ...
[11] STEP: Deleting namespace used for hosting the "" test spec
[11] INFO: Deleting namespace functional-gpu-cluster-1qs5vk
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 3 Specs in 1898.721 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 2 Skipped
[11] PASS
[1] INFO: Waiting for control plane to be ready
[1] INFO: Waiting for control plane functional-efs-support-bv448e/cluster-imtcmb-control-plane to be ready (implies underlying nodes to be ready as well)
[1] STEP: Waiting for the control plane to be ready
[20] STEP: Checking all the machines controlled by clusterctl-upgrade-iz32wl-md-0 are in the "<None>" failure domain
[20] INFO: Waiting for the machine pools to be provisioned
... skipping 42 lines ...
[14]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 1 Specs in 1935.356 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[14] PASS
[1] STEP: Checking all the machines controlled by cluster-imtcmb-md-0 are in the "<None>" failure domain
[1] INFO: Waiting for the machine pools to be provisioned
[1] STEP: Setting up EFS in AWS
[2] STEP: Deleting namespace used for hosting the "quick-start" test spec
[2] INFO: Deleting namespace quick-start-paqzt0
... skipping 17 lines ...
[2]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:77
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 3 Specs in 1984.320 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 2 Skipped
[2] PASS
[20] INFO: Waiting for provider controllers to be running
[20] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
[20] INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-7b68686c58-vzfnj, container manager
[20] STEP: Waiting for deployment capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager to be available
[20] INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-655cfbc4b-cfx4q, container manager
... skipping 72 lines ...
[15]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:466
[15] ------------------------------
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 1 of 1 Specs in 2138.948 seconds
[15] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[15] PASS
[9] STEP: Dumping all the Cluster API resources in the "functional-multitenancy-nested-69j0o4" namespace
[9] STEP: Dumping all EC2 instances in the "functional-multitenancy-nested-69j0o4" namespace
[9] STEP: Deleting all clusters in the "functional-multitenancy-nested-69j0o4" namespace with intervals ["20m" "10s"]
[9] STEP: Deleting cluster functional-multitenancy-nested-hhnl2v
[9] INFO: Waiting for the Cluster functional-multitenancy-nested-69j0o4/functional-multitenancy-nested-hhnl2v to be deleted
... skipping 82 lines ...
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] 
[9] Summarizing 1 Failure:
[9] 
[9] [Fail] [unmanaged] [functional] Multitenancy test [It] should create cluster with nested assumed role 
[9] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/cluster_helpers.go:143
[9] 
[9] Ran 1 of 1 Specs in 2272.590 seconds
[9] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[9] --- FAIL: TestE2E (2272.69s)
[9] FAIL
[16] STEP: Checking all the the control plane machines are in the expected failure domains
[16] INFO: Waiting for the machine deployments to be provisioned
[16] STEP: Waiting for the workload nodes to exist
[16] STEP: Checking all the machines controlled by clusterctl-upgrade-13mvip-md-0 are in the "<None>" failure domain
[16] INFO: Waiting for the machine pools to be provisioned
[16] STEP: Turning the workload cluster into a management cluster with older versions of providers
... skipping 87 lines ...
[4]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/mhc_remediations.go:114
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 2669.928 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[3] STEP: Upgrading the Kubernetes control-plane
[3] INFO: Patching the new kubernetes version to KCP
[3] INFO: Waiting for control-plane machines to have the upgraded kubernetes version
[3] STEP: Ensuring all control-plane machines have upgraded kubernetes version v1.24.0
[12] STEP: Waiting for the machine pool workload nodes
... skipping 124 lines ...
[20]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[20] ------------------------------
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 1 of 1 Specs in 3481.297 seconds
[20] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[20] PASS
[12] STEP: Deleting namespace used for hosting the "machine-pool" test spec
[12] INFO: Deleting namespace machine-pool-73hq3f
[12] [AfterEach] Machine Pool Spec
[12]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:85
[12] STEP: Node 12 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[12]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/machine_pool.go:76
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 3555.181 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[8] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[8] INFO: Deleting namespace k8s-upgrade-and-conformance-arpwar
[8] [AfterEach] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade]
[8]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:233
[8] STEP: Node 8 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[8]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 2 of 2 Specs in 3610.605 seconds
[8] SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[10] STEP: Deleting namespace used for hosting the "" test spec
[10] INFO: Deleting namespace functional-test-ignition-eaq35k
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 2 of 3 Specs in 3613.764 seconds
[10] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[10] PASS
[3] STEP: Upgrading the machinepool instances
[3] INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-and-conformance-fkrprt/k8s-upgrade-and-conformance-iunhoq-mp-0
[3] INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-and-conformance-fkrprt/k8s-upgrade-and-conformance-iunhoq-mp-0 to be upgraded from v1.23.6 to v1.24.0
[3] INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
[16] STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-13mvip
... skipping 32 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 4064.738 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[3] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[3] INFO: Deleting namespace k8s-upgrade-and-conformance-fkrprt
[3] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[3]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:183
[3] STEP: Node 3 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 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 4450.355 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[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 1 of 1 Specs in 4915.249 seconds
[1] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h23m30.298125911s
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	83m30.306s
user	25m13.602s
sys	6m36.418s
make: *** [Makefile:418: 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 ...