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

Test Failures

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

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[It\]\s\[unmanaged\]\s\[functional\]\sMultitenancy\stest\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 | 0xc000549728>: {
        error: <*exec.ExitError | 0xc000658ce0>{
            ProcessState: {
                pid: 32081,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 618109},
                    Stime: {Sec: 0, Usec: 245719},
                    Maxrss: 103076,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 17363,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 25136,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 2560,
                    Nivcsw: 1744,
                },
            },
            Stderr: nil,
        },
        stack: [0x1be46e0, 0x1be4c51, 0x1d5968c, 0x2190f13, 0x4db565, 0x4daa5c, 0xa35b9a, 0xa364c5, 0xa3440d, 0x21903ec, 0x22721d8, 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/20/23 04:42:55.584

				
				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 893 lines ...
  Jan 20 04:42:31.194: INFO: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
  Jan 20 04:42:31.194: INFO: Setting environment variable: key=AWS_REGION, value=us-west-2
  Jan 20 04:42:31.194: INFO: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
  Jan 20 04:42:31.194: INFO: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
  << Timeline
------------------------------
• [FAILED] [24.501 seconds]
[unmanaged] [functional] Multitenancy test [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_test.go:161

  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 14 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/20/23 04:42:31.085
  STEP: Node 14 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/20/23 04:42:32.087
... skipping 20 lines ...
  STEP: Deleting cluster functional-multitenancy-nested-n6s56w @ 01/20/23 04:42:44.535
  INFO: Waiting for the Cluster functional-multitenancy-nested-qsssq3/functional-multitenancy-nested-n6s56w to be deleted
  STEP: Waiting for cluster functional-multitenancy-nested-n6s56w to be deleted @ 01/20/23 04:42:44.549
  STEP: Deleting namespace used for hosting the "" test spec @ 01/20/23 04:42:54.565
  INFO: Deleting namespace functional-multitenancy-nested-qsssq3
  STEP: Node 14 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/20/23 04:42:55.583
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/20/23 04:42:55.584
  << Timeline

  [FAILED] Timed out after 10.001s.
  Failed to apply the cluster template
  Expected success, but got an error:
      <*errors.withStack | 0xc000549728>: {
          error: <*exec.ExitError | 0xc000658ce0>{
              ProcessState: {
                  pid: 32081,
                  status: 256,
                  rusage: {
                      Utime: {Sec: 0, Usec: 618109},
                      Stime: {Sec: 0, Usec: 245719},
... skipping 1052 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-h7jdmo created
  configmap/cni-self-hosted-h7jdmo-crs-0 created
  clusterresourceset.addons.cluster.x-k8s.io/self-hosted-h7jdmo-crs-0 created

  W0120 04:57:16.740291   27100 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/20/23 04:42:31.124
  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/20/23 04:42:32.126
  STEP: Creating a namespace for hosting the "self-hosted" test spec @ 01/20/23 04:42:32.126
... skipping 274 lines ...
  machinedeployment.cluster.x-k8s.io/self-hosted-26hwzh-md-0 created
  awsmachinetemplate.infrastructure.cluster.x-k8s.io/self-hosted-26hwzh-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/self-hosted-26hwzh-md-0 created
  configmap/cni-self-hosted-26hwzh-crs-0 created
  clusterresourceset.addons.cluster.x-k8s.io/self-hosted-26hwzh-crs-0 created

  W0120 05:07:21.263759   27099 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
  I0120 05:07:35.496698   27099 trace.go:205] Trace[1207920314]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.25.0/tools/cache/reflector.go:169 (20-Jan-2023 05:07:22.115) (total time: 13381ms):
  Trace[1207920314]: ---"Objects listed" error:<nil> 13381ms (05:07:35.496)
  Trace[1207920314]: [13.381269001s] [13.381269001s] END
  << Captured StdOut/StdErr Output

  Timeline >>
  STEP: Node 2 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/20/23 04:42:31.2
  STEP: Node 2 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/20/23 04:42:56.201
... skipping 577 lines ...
[ReportAfterSuite] PASSED [0.018 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] [unmanaged] [functional] Multitenancy test [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 3794.361 seconds
FAIL! -- 25 Passed | 1 Failed | 4 Pending | 0 Skipped


Ginkgo ran 1 suite in 1h4m53.065990313s

Test Suite Failed

real	64m53.140s
user	21m16.462s
sys	5m13.657s
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 ...