This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 65 succeeded
Started2023-01-25 16:36
Elapsed1h7m
Revisionmain

Test Failures


capa-e2e [It] [unmanaged] [functional] [ClusterClass] Multitenancy test [ClusterClass] should create cluster with nested assumed role 25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[It\]\s\[unmanaged\]\s\[functional\]\s\[ClusterClass\]\sMultitenancy\stest\s\[ClusterClass\]\sshould\screate\scluster\swith\snested\sassumed\srole$'
[FAILED] Timed out after 10.001s.
Failed to apply the cluster template
Expected success, but got an error:
    <*errors.withStack | 0xc000707878>: {
        error: <*exec.ExitError | 0xc0005fe300>{
            ProcessState: {
                pid: 32617,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 773819},
                    Stime: {Sec: 0, Usec: 361999},
                    Maxrss: 104032,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 13083,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 25696,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 3240,
                    Nivcsw: 1929,
                },
            },
            Stderr: nil,
        },
        stack: [0x1be5460, 0x1be59d1, 0x1d5a40c, 0x2191c93, 0x4db565, 0x4daa5c, 0xa35e9a, 0xa36b0e, 0xa344cd, 0x219116c, 0x2265878, 0xa11f5b, 0xa26058, 0x4704e1],
    }
    exit status 1
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/25/23 16:49:05.077

				
				Click to see stdout/stderrfrom junit.e2e_suite.xml

Filter through log files | View test history on testgrid


Show 65 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 878 lines ...
  Jan 25 16:48:39.573: INFO: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
  Jan 25 16:48:39.573: INFO: Setting environment variable: key=AWS_REGION, value=us-west-2
  Jan 25 16:48:39.573: INFO: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
  Jan 25 16:48:39.573: INFO: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
  << Timeline
------------------------------
• [FAILED] [25.523 seconds]
[unmanaged] [functional] [ClusterClass] Multitenancy test [ClusterClass] [It] should create cluster with nested assumed role
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:53

  Captured StdOut/StdErr Output >>
  Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancyjump" already exists
  Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancynested" already exists

  << Captured StdOut/StdErr Output

  Timeline >>
  STEP: Node 19 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 16:48:39.575
  STEP: Node 19 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 16:48:40.576
... skipping 20 lines ...
  STEP: Deleting cluster cluster-5d0zkd @ 01/25/23 16:48:54.004
  INFO: Waiting for the Cluster functional-multitenancy-nested-clusterclass-brffsg/cluster-5d0zkd to be deleted
  STEP: Waiting for cluster cluster-5d0zkd to be deleted @ 01/25/23 16:48:54.04
  STEP: Deleting namespace used for hosting the "" test spec @ 01/25/23 16:49:04.055
  INFO: Deleting namespace functional-multitenancy-nested-clusterclass-brffsg
  STEP: Node 19 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 16:49:05.077
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/25/23 16:49:05.077
  << Timeline

  [FAILED] Timed out after 10.001s.
  Failed to apply the cluster template
  Expected success, but got an error:
      <*errors.withStack | 0xc000707878>: {
          error: <*exec.ExitError | 0xc0005fe300>{
              ProcessState: {
                  pid: 32617,
                  status: 256,
                  rusage: {
                      Utime: {Sec: 0, Usec: 773819},
                      Stime: {Sec: 0, Usec: 361999},
... skipping 1323 lines ...
  machinedeployment.cluster.x-k8s.io/self-hosted-tu6cj0-md-0 created
  awsmachinetemplate.infrastructure.cluster.x-k8s.io/self-hosted-tu6cj0-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/self-hosted-tu6cj0-md-0 created
  configmap/cni-self-hosted-tu6cj0-crs-0 created
  clusterresourceset.addons.cluster.x-k8s.io/self-hosted-tu6cj0-crs-0 created

  W0125 17:14:56.730605   27572 reflector.go:347] pkg/mod/k8s.io/client-go@v0.25.0/tools/cache/reflector.go:169: watch of *v1.Event ended with: Internal error occurred: etcdserver: no leader
  << Captured StdOut/StdErr Output

  Timeline >>
  STEP: Node 3 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 16:48:39.601
  STEP: Node 3 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 16:49:05.602
  STEP: Creating a namespace for hosting the "self-hosted" test spec @ 01/25/23 16:49:05.602
... skipping 79 lines ...
  awsmachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-worker-machinetemplate created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/ci-default-worker-bootstraptemplate created
  cluster.cluster.x-k8s.io/self-hosted-7hq32n created
  configmap/cni-self-hosted-7hq32n-crs-0 created
  clusterresourceset.addons.cluster.x-k8s.io/self-hosted-7hq32n-crs-0 created

  W0125 17:17:40.383840   27680 reflector.go:347] pkg/mod/k8s.io/client-go@v0.25.0/tools/cache/reflector.go:169: watch of *v1.Event ended with: Internal error occurred: etcdserver: no leader
  << Captured StdOut/StdErr Output

  Timeline >>
  STEP: Node 16 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 17:02:01.374
  STEP: Node 16 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/25/23 17:04:57.375
  STEP: Creating a namespace for hosting the "self-hosted" test spec @ 01/25/23 17:04:57.375
... skipping 499 lines ...
[ReportAfterSuite] PASSED [0.020 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] [unmanaged] [functional] [ClusterClass] Multitenancy test [ClusterClass] [It] should create cluster with nested assumed role
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308

Ran 26 of 30 Specs in 3667.189 seconds
FAIL! -- 25 Passed | 1 Failed | 4 Pending | 0 Skipped


Ginkgo ran 1 suite in 1h4m10.765789889s

Test Suite Failed

real	64m10.859s
user	30m8.200s
sys	9m47.647s
make: *** [Makefile:406: 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 ...