This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2023-01-29 05:58
Elapsed49m33s
Revisionrelease-1.7

Test Failures

capz-e2e [It] Conformance Tests conformance-tests 38m17s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'
[FAILED] Timed out after 1500.001s.
Timed out waiting for 2 nodes to be created for MachineDeployment capz-conf-und25k/capz-conf-und25k-md-0
Expected
    <int>: 0
to equal
    <int>: 2
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:131 @ 01/29/23 06:41:48.569

				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid

Show 2 Passed Tests
Show 22 Skipped Tests

Error lines from build-log.txt

... skipping 485 lines ...
------------------------------
Conformance Tests conformance-tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100
  INFO: Cluster name is capz-conf-und25k
  STEP: Creating namespace "capz-conf-und25k" for hosting the cluster @ 01/29/23 06:09:13.555
  Jan 29 06:09:13.555: INFO: starting to create namespace for hosting the "capz-conf-und25k" test spec
2023/01/29 06:09:13 failed trying to get namespace (capz-conf-und25k):namespaces "capz-conf-und25k" not found
  INFO: Creating namespace capz-conf-und25k
  INFO: Creating event watcher for namespace "capz-conf-und25k"
  conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/29/23 06:09:13.612
    conformance-tests
    Name | N | Min | Median | Mean | StdDev | Max
  INFO: Creating the workload cluster with name "capz-conf-und25k" using the "conformance-ci-artifacts" template (Kubernetes v1.27.0-alpha.1.73+8e642d3d0deab2, 1 control-plane machines, 2 worker machines)
... skipping 105 lines ...
  INFO: Waiting for control plane to be ready
  INFO: Waiting for control plane capz-conf-und25k/capz-conf-und25k-control-plane to be ready (implies underlying nodes to be ready as well)
  STEP: Waiting for the control plane to be ready @ 01/29/23 06:16:48.541
  STEP: Checking all the control plane machines are in the expected failure domains @ 01/29/23 06:16:48.547
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/29/23 06:16:48.567
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:131 @ 01/29/23 06:41:48.569
  Jan 29 06:41:48.570: INFO: FAILED!
  Jan 29 06:41:48.570: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
  STEP: Dumping logs from the "capz-conf-und25k" workload cluster @ 01/29/23 06:41:48.57
  Jan 29 06:41:48.570: INFO: Dumping workload cluster capz-conf-und25k/capz-conf-und25k logs
  Jan 29 06:41:48.727: INFO: Collecting logs for Linux node capz-conf-und25k-control-plane-ktkpt in cluster capz-conf-und25k in namespace capz-conf-und25k

  Jan 29 06:42:04.589: INFO: Collecting boot logs for AzureMachine capz-conf-und25k-control-plane-ktkpt
... skipping 58 lines ...
  INFO: Waiting for the Cluster capz-conf-und25k/capz-conf-und25k to be deleted
  STEP: Waiting for cluster capz-conf-und25k to be deleted @ 01/29/23 06:42:38.34
  Jan 29 06:47:18.566: INFO: Deleting namespace used for hosting the "conformance-tests" test spec
  INFO: Deleting namespace capz-conf-und25k
  Jan 29 06:47:18.583: INFO: Checking if any resources are left over in Azure for spec "conformance-tests"
  STEP: Redacting sensitive information from logs @ 01/29/23 06:47:19.209
• [FAILED] [2297.288 seconds]
Conformance Tests [It] conformance-tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100

  [FAILED] Timed out after 1500.001s.
  Timed out waiting for 2 nodes to be created for MachineDeployment capz-conf-und25k/capz-conf-und25k-md-0
  Expected
      <int>: 0
  to equal
      <int>: 2
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:131 @ 01/29/23 06:41:48.569
... skipping 18 lines ...
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.005 seconds]
------------------------------

Summarizing 1 Failure:
  [FAIL] Conformance Tests [It] conformance-tests
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:131

Ran 1 of 23 Specs in 2518.061 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 22 Skipped
--- FAIL: TestE2E (2518.07s)
FAIL
You're using deprecated Ginkgo functionality:
=============================================
  CurrentGinkgoTestDescription() is deprecated in Ginkgo V2.  Use CurrentSpecReport() instead.
  Learn more at: https://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:278
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:281

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.6.0


Ginkgo ran 1 suite in 45m1.603047224s

Test Suite Failed
make[2]: *** [Makefile:655: test-e2e-run] Error 1
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[1]: *** [Makefile:670: test-e2e-skip-push] Error 2
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:686: test-conformance] Error 2
================ REDACTING LOGS ================
All sensitive variables are redacted
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 5 lines ...