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

Test Failures


capa-e2e [It] [unmanaged] [functional] Workload cluster with AWS S3 and Ignition parameter It should be creatable and deletable 30m7s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[It\]\s\[unmanaged\]\s\[functional\]\sWorkload\scluster\swith\sAWS\sS3\sand\sIgnition\sparameter\sIt\sshould\sbe\screatable\sand\sdeletable$'
[FAILED] Timed out after 1800.000s.
Timed out waiting for Cluster functional-test-ignition-cgui9q/functional-test-ignition-dwm5en to provision
Expected
    <string>: Provisioning
to equal
    <string>: Provisioned
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144 @ 01/15/23 05:11:30.838

				
				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 1872 lines ...
  machinedeployment.cluster.x-k8s.io/self-hosted-3wibuu-md-0 created
  awsmachinetemplate.infrastructure.cluster.x-k8s.io/self-hosted-3wibuu-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/self-hosted-3wibuu-md-0 created
  configmap/cni-self-hosted-3wibuu-crs-0 created
  clusterresourceset.addons.cluster.x-k8s.io/self-hosted-3wibuu-crs-0 created

  W0115 04:57:39.510470   27172 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 15 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/15/23 04:41:23.247
  STEP: Node 15 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/15/23 04:41:24.249
  STEP: Creating a namespace for hosting the "self-hosted" test spec @ 01/15/23 04:41:24.249
... skipping 148 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-k6c18z created
  configmap/cni-self-hosted-k6c18z-crs-0 created
  clusterresourceset.addons.cluster.x-k8s.io/self-hosted-k6c18z-crs-0 created

  W0115 04:59:30.339267   27070 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 1 acquiring resources: {ec2-normal:4, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/15/23 04:41:23.127
  STEP: Node 1 acquired resources: {ec2-normal:4, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} @ 01/15/23 04:41:24.128
  STEP: Creating a namespace for hosting the "self-hosted" test spec @ 01/15/23 04:41:24.128
... skipping 114 lines ...
  << Timeline
------------------------------
[SynchronizedAfterSuite] PASSED [0.000 seconds]
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_suite_test.go:54
------------------------------
• [FAILED] [1807.632 seconds]
[unmanaged] [functional] Workload cluster with AWS S3 and Ignition parameter [It] It should be creatable and deletable
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:949

  Captured StdOut/StdErr Output >>
  cluster.cluster.x-k8s.io/functional-test-ignition-dwm5en created
  awscluster.infrastructure.cluster.x-k8s.io/functional-test-ignition-dwm5en created
... skipping 15 lines ...
  INFO: Creating the workload cluster with name "functional-test-ignition-dwm5en" using the "ignition" template (Kubernetes v1.25.3, 1 control-plane machines, 1 worker machines)
  INFO: Getting the cluster template yaml
  INFO: clusterctl config cluster functional-test-ignition-dwm5en --infrastructure (default) --kubernetes-version v1.25.3 --control-plane-machine-count 1 --worker-machine-count 1 --flavor ignition
  INFO: Applying the cluster template yaml to the cluster
  INFO: Waiting for the cluster infrastructure to be provisioned
  STEP: Waiting for cluster to enter the provisioned phase @ 01/15/23 04:41:30.837
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144 @ 01/15/23 05:11:30.838
  << Timeline

  [FAILED] Timed out after 1800.000s.
  Timed out waiting for Cluster functional-test-ignition-cgui9q/functional-test-ignition-dwm5en to provision
  Expected
      <string>: Provisioning
  to equal
      <string>: Provisioned
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144 @ 01/15/23 05:11:30.838
... skipping 668 lines ...
[ReportAfterSuite] PASSED [0.019 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] [unmanaged] [functional] Workload cluster with AWS S3 and Ignition parameter [It] It should be creatable and deletable
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144

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


Ginkgo ran 1 suite in 1h3m26.794334578s

Test Suite Failed

real	63m26.871s
user	22m38.301s
sys	5m56.904s
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 ...