This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2023-01-31 15:50
Elapsed1h21m
Revisionrelease-1.7

Test Failures

capz-e2e [It] Conformance Tests conformance-tests 1h10m

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'
[FAILED] Timed out after 1500.000s.
Timed out waiting for 2 nodes to be created for MachineDeployment capz-conf-ttqvdh/capz-conf-ttqvdh-md-win
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/31/23 16:31:40.085

There were additional failures detected after the initial failure. These are visible in the timeline

				
				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 486 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-ttqvdh
  STEP: Creating namespace "capz-conf-ttqvdh" for hosting the cluster @ 01/31/23 15:59:53.39
  Jan 31 15:59:53.390: INFO: starting to create namespace for hosting the "capz-conf-ttqvdh" test spec
2023/01/31 15:59:53 failed trying to get namespace (capz-conf-ttqvdh):namespaces "capz-conf-ttqvdh" not found
  INFO: Creating namespace capz-conf-ttqvdh
  INFO: Creating event watcher for namespace "capz-conf-ttqvdh"
  conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/31/23 15:59:53.429
    conformance-tests
    Name | N | Min | Median | Mean | StdDev | Max
  INFO: Creating the workload cluster with name "capz-conf-ttqvdh" using the "conformance-ci-artifacts-windows-containerd" template (Kubernetes v1.25.7-rc.0.14+f6fb2e8bdbec52, 1 control-plane machines, 0 worker machines)
... skipping 107 lines ...
  STEP: Waiting for the control plane to be ready @ 01/31/23 16:06:40.029
  STEP: Checking all the control plane machines are in the expected failure domains @ 01/31/23 16:06:40.037
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/31/23 16:06:40.063
  STEP: Checking all the machines controlled by capz-conf-ttqvdh-md-0 are in the "<None>" failure domain @ 01/31/23 16:06:40.074
  STEP: Waiting for the workload nodes to exist @ 01/31/23 16:06:40.084
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:131 @ 01/31/23 16:31:40.085
  Jan 31 16:31:40.085: INFO: FAILED!
  Jan 31 16:31:40.085: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
  STEP: Dumping logs from the "capz-conf-ttqvdh" workload cluster @ 01/31/23 16:31:40.085
  Jan 31 16:31:40.085: INFO: Dumping workload cluster capz-conf-ttqvdh/capz-conf-ttqvdh logs
  Jan 31 16:31:40.128: INFO: Collecting logs for Linux node capz-conf-ttqvdh-control-plane-hqqpr in cluster capz-conf-ttqvdh in namespace capz-conf-ttqvdh

  Jan 31 16:32:00.737: INFO: Collecting boot logs for AzureMachine capz-conf-ttqvdh-control-plane-hqqpr

  Jan 31 16:32:01.688: INFO: Unable to collect logs as node doesn't have addresses
  Jan 31 16:32:01.688: INFO: Collecting logs for Windows node capz-conf-ttqvdh-md-win-f68px in cluster capz-conf-ttqvdh in namespace capz-conf-ttqvdh

  Jan 31 16:36:17.645: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-ttqvdh-md-win-f68px to /logs/artifacts/clusters/capz-conf-ttqvdh/machines/capz-conf-ttqvdh-md-win-8bd8475b5-6sxlt/crashdumps.tar
  Jan 31 16:36:18.170: INFO: Collecting boot logs for AzureMachine capz-conf-ttqvdh-md-win-f68px

Failed to get logs for Machine capz-conf-ttqvdh-md-win-8bd8475b5-6sxlt, Cluster capz-conf-ttqvdh/capz-conf-ttqvdh: [dialing from control plane to target node at capz-conf-ttqvdh-md-win-f68px: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 31 16:36:18.201: INFO: Unable to collect logs as node doesn't have addresses
  Jan 31 16:36:18.201: INFO: Collecting logs for Windows node capz-conf-ttqvdh-md-win-rg8qc in cluster capz-conf-ttqvdh in namespace capz-conf-ttqvdh

  Jan 31 16:40:28.369: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-ttqvdh-md-win-rg8qc to /logs/artifacts/clusters/capz-conf-ttqvdh/machines/capz-conf-ttqvdh-md-win-8bd8475b5-jbfws/crashdumps.tar
  Jan 31 16:40:28.897: INFO: Collecting boot logs for AzureMachine capz-conf-ttqvdh-md-win-rg8qc

Failed to get logs for Machine capz-conf-ttqvdh-md-win-8bd8475b5-jbfws, Cluster capz-conf-ttqvdh/capz-conf-ttqvdh: [dialing from control plane to target node at capz-conf-ttqvdh-md-win-rg8qc: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 31 16:40:28.914: INFO: Dumping workload cluster capz-conf-ttqvdh/capz-conf-ttqvdh kube-system pod logs
  Jan 31 16:40:29.380: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-546454464f-nhl98, container calico-apiserver
  Jan 31 16:40:29.380: INFO: Describing Pod calico-apiserver/calico-apiserver-546454464f-nhl98
  Jan 31 16:40:29.454: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-546454464f-z2gbf, container calico-apiserver
  Jan 31 16:40:29.454: INFO: Describing Pod calico-apiserver/calico-apiserver-546454464f-z2gbf
  Jan 31 16:40:29.537: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-5f9dc85578-9tzhw, container calico-kube-controllers
... skipping 40 lines ...
  Jan 31 16:40:38.506: INFO: Dumping all the Cluster API resources in the "capz-conf-ttqvdh" namespace
  Jan 31 16:40:38.850: INFO: Deleting all clusters in the capz-conf-ttqvdh namespace
  STEP: Deleting cluster capz-conf-ttqvdh @ 01/31/23 16:40:38.867
  INFO: Waiting for the Cluster capz-conf-ttqvdh/capz-conf-ttqvdh to be deleted
  STEP: Waiting for cluster capz-conf-ttqvdh to be deleted @ 01/31/23 16:40:38.882
  STEP: Redacting sensitive information from logs @ 01/31/23 17:10:38.883
  [FAILED] in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:176 @ 01/31/23 17:10:51.612
• [FAILED] [4258.223 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.000s.
  Timed out waiting for 2 nodes to be created for MachineDeployment capz-conf-ttqvdh/capz-conf-ttqvdh-md-win
  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/31/23 16:31:40.085
... skipping 20 lines ...
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.003 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 4421.561 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 22 Skipped
--- FAIL: TestE2E (4421.57s)
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 1h16m32.852432374s

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