This job view page is being replaced by Spyglass soon. Check out the new job view.
PRAnkitasw: Restructure e2e templates directory
ResultFAILURE
Tests 1 failed / 25 succeeded
Started2022-09-28 09:22
Elapsed1h43m
Revisiona0f0d668908cf06302b9f719d2c9c16aca0aa9c9
Refs 3754

Test Failures


capa-e2e [unmanaged] [functional] [ClusterClass] Multitenancy test [ClusterClass] should create cluster with nested assumed role 3m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[functional\]\s\[ClusterClass\]\sMultitenancy\stest\s\[ClusterClass\]\sshould\screate\scluster\swith\snested\sassumed\srole$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:54
Timed out after 10.000s.
Failed to apply the cluster template
Expected success, but got an error:
    <*errors.withStack | 0xc0011b6090>: {
        error: <*exec.ExitError | 0xc0004ae000>{
            ProcessState: {
                pid: 31434,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 766669},
                    Stime: {Sec: 0, Usec: 474672},
                    Maxrss: 107184,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 12091,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 280,
                    Oublock: 23864,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 3697,
                    Nivcsw: 957,
                },
            },
            Stderr: nil,
        },
        stack: [0x1b14680, 0x1b14bd0, 0x1c9050c, 0x2099cf3, 0x4d7625, 0x4d6b9f, 0x96b051, 0x96b3f9, 0x96b7e5, 0x96b16d, 0x20992ec, 0x215f598, 0x948d71, 0x948765, 0x947e5b, 0x94db4a, 0x94d547, 0x9599e8, 0x959705, 0x958da5, 0x95b172, 0x967569, 0x967376, 0x216e3bb, 0x520862, 0x46d9a1],
    }
    exit status 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/framework/clusterctl/clusterctl_helpers.go:278
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 25 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 764 lines ...
[4] configmap/cni-functional-multitenancy-nested-xiv5m9-crs-0 created
[4] clusterresourceset.addons.cluster.x-k8s.io/functional-multitenancy-nested-xiv5m9-crs-0 created
[4] awsclusterroleidentity.infrastructure.cluster.x-k8s.io/capamultitenancyjump created
[4] awsclusterroleidentity.infrastructure.cluster.x-k8s.io/capamultitenancynested created
[4] 
[4] INFO: Waiting for the cluster infrastructure to be provisioned
[1] Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancyjump" already exists
[1] 
[6] STEP: Waiting for cluster to enter the provisioned phase
[3] cluster.cluster.x-k8s.io/cluster-25ulus created
[3] awscluster.infrastructure.cluster.x-k8s.io/cluster-25ulus created
[3] kubeadmcontrolplane.controlplane.cluster.x-k8s.io/cluster-25ulus-control-plane created
[3] awsmachinetemplate.infrastructure.cluster.x-k8s.io/cluster-25ulus-control-plane created
... skipping 53 lines ...
[1]   Multitenancy test [ClusterClass]
[1]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:53
[1]     should create cluster with nested assumed role [It]
[1]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:54
[1] 
[1]     Timed out after 10.000s.
[1]     Failed to apply the cluster template
[1]     Expected success, but got an error:
[1]         <*errors.withStack | 0xc0011b6090>: {
[1]             error: <*exec.ExitError | 0xc0004ae000>{
[1]                 ProcessState: {
[1]                     pid: 31434,
[1]                     status: 256,
[1]                     rusage: {
[1]                         Utime: {Sec: 0, Usec: 766669},
[1]                         Stime: {Sec: 0, Usec: 474672},
... skipping 1770 lines ...
[3] STEP: Deleting namespace used for hosting the "" test spec
[3] INFO: Deleting namespace functional-test-ignition-lvs3se
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 4 of 5 Specs in 4179.089 seconds
[3] SUCCESS! -- 4 Passed | 0 Failed | 1 Pending | 0 Skipped
[3] PASS
[5] STEP: Waiting for the machine pool workload nodes
[5] STEP: PASSED!
[5] [AfterEach] Machine Pool Spec
[5]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/e2e/machine_pool.go:130
[5] STEP: Dumping logs from the "machine-pool-u19920" workload cluster
... skipping 81 lines ...
[2]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/e2e/clusterctl_upgrade.go:151
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 4 of 4 Specs in 4738.081 seconds
[2] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[7] STEP: Waiting until nodes are ready
[7] STEP: PASSED!
[7] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[7]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/e2e/cluster_upgrade.go:242
[7] STEP: Dumping logs from the "k8s-upgrade-and-conformance-7tnb6y" workload cluster
... skipping 14 lines ...
[6]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/e2e/cluster_upgrade.go:118
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 4 of 6 Specs in 4931.285 seconds
[6] SUCCESS! -- 4 Passed | 0 Failed | 2 Pending | 0 Skipped
[6] PASS
[5] STEP: Deleting namespace used for hosting the "" test spec
[5] INFO: Deleting namespace functional-gpu-cluster-nmiolq
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 3 of 3 Specs in 4969.591 seconds
[5] SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[4] INFO: Waiting for kube-proxy to have the upgraded kubernetes version
[4] STEP: Ensuring kube-proxy has the correct image
[4] INFO: Waiting for CoreDNS to have the upgraded image tag
[4] STEP: Ensuring CoreDNS has the correct image
[4] INFO: Waiting for etcd to have the upgraded image tag
... skipping 22 lines ...
[7]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/e2e/cluster_upgrade.go:118
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 4 of 4 Specs in 5414.635 seconds
[7] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[4] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[4] INFO: Deleting namespace k8s-upgrade-and-conformance-kkvp1q
[4] [AfterEach] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade]
[4]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:208
[4] STEP: Node 4 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[4]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/e2e/cluster_upgrade.go:118
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 4 of 4 Specs in 5517.258 seconds
[4] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] 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] 
[1] Summarizing 1 Failure:
[1] 
[1] [Fail] [unmanaged] [functional] [ClusterClass] Multitenancy test [ClusterClass] [It] should create cluster with nested assumed role 
[1] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/framework/clusterctl/clusterctl_helpers.go:278
[1] 
[1] Ran 3 of 4 Specs in 5952.084 seconds
[1] FAIL! -- 2 Passed | 1 Failed | 1 Pending | 0 Skipped
[1] --- FAIL: TestE2E (5952.13s)
[1] FAIL

Ginkgo ran 1 suite in 1h40m46.517607396s
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	100m46.527s
user	25m18.345s
sys	6m30.365s
make: *** [Makefile:405: 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 ...