This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 0 succeeded
Started2022-11-02 00:48
Elapsed58m3s
Revisionmain

Test Failures


capz-e2e Conformance Tests conformance-tests 47m42s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sConformance\sTests\sconformance\-tests$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
Timed out after 1500.001s.
Expected
    <int>: 0
to equal
    <int>: 2
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.4/framework/machinedeployment_helpers.go:129
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 22 Skipped Tests

Error lines from build-log.txt

... skipping 489 lines ...
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
[BeforeEach] Conformance Tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:55
INFO: Cluster name is capz-conf-yh2dw8
STEP: Creating namespace "capz-conf-yh2dw8" for hosting the cluster
Nov  2 00:58:07.194: INFO: starting to create namespace for hosting the "capz-conf-yh2dw8" test spec
2022/11/02 00:58:07 failed trying to get namespace (capz-conf-yh2dw8):namespaces "capz-conf-yh2dw8" not found
INFO: Creating namespace capz-conf-yh2dw8
INFO: Creating event watcher for namespace "capz-conf-yh2dw8"
[Measure] conformance-tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
INFO: Creating the workload cluster with name "capz-conf-yh2dw8" using the "conformance-ci-artifacts-windows-containerd" template (Kubernetes v1.26.0-alpha.2.535+2452a95bd4ee1a, 1 control-plane machines, 0 worker machines)
INFO: Getting the cluster template yaml
... skipping 32 lines ...
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
STEP: Checking all the machines controlled by capz-conf-yh2dw8-md-0 are in the "<None>" failure domain
STEP: Waiting for the workload nodes to exist
[AfterEach] Conformance Tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:237
Nov  2 01:30:11.642: INFO: FAILED!
Nov  2 01:30:11.642: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
STEP: Dumping logs from the "capz-conf-yh2dw8" workload cluster
STEP: Dumping workload cluster capz-conf-yh2dw8/capz-conf-yh2dw8 logs
Nov  2 01:30:11.689: INFO: Collecting logs for Linux node capz-conf-yh2dw8-control-plane-zl5gv in cluster capz-conf-yh2dw8 in namespace capz-conf-yh2dw8

Nov  2 01:30:26.835: INFO: Collecting boot logs for AzureMachine capz-conf-yh2dw8-control-plane-zl5gv

Nov  2 01:30:27.861: INFO: Unable to collect logs as node doesn't have addresses
Nov  2 01:30:27.861: INFO: Collecting logs for Windows node capz-conf-yh2dw8-md-win-p7p8w in cluster capz-conf-yh2dw8 in namespace capz-conf-yh2dw8

Nov  2 01:34:40.288: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-yh2dw8-md-win-p7p8w to /logs/artifacts/clusters/capz-conf-yh2dw8/machines/capz-conf-yh2dw8-md-win-5ff5458c86-5gx7f/crashdumps.tar
Nov  2 01:34:40.777: INFO: Collecting boot logs for AzureMachine capz-conf-yh2dw8-md-win-p7p8w

Failed to get logs for machine capz-conf-yh2dw8-md-win-5ff5458c86-5gx7f, cluster capz-conf-yh2dw8/capz-conf-yh2dw8: [dialing from control plane to target node at capz-conf-yh2dw8-md-win-p7p8w: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
Nov  2 01:34:40.810: INFO: Unable to collect logs as node doesn't have addresses
Nov  2 01:34:40.810: INFO: Collecting logs for Windows node capz-conf-yh2dw8-md-win-9sngz in cluster capz-conf-yh2dw8 in namespace capz-conf-yh2dw8

Nov  2 01:38:53.068: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-yh2dw8-md-win-9sngz to /logs/artifacts/clusters/capz-conf-yh2dw8/machines/capz-conf-yh2dw8-md-win-5ff5458c86-krld4/crashdumps.tar
Nov  2 01:38:54.240: INFO: Collecting boot logs for AzureMachine capz-conf-yh2dw8-md-win-9sngz

Failed to get logs for machine capz-conf-yh2dw8-md-win-5ff5458c86-krld4, cluster capz-conf-yh2dw8/capz-conf-yh2dw8: [dialing from control plane to target node at capz-conf-yh2dw8-md-win-9sngz: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
STEP: Dumping workload cluster capz-conf-yh2dw8/capz-conf-yh2dw8 kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-kube-controllers-755ff8d7b5-gjk52
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-mzb92, container coredns
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-conf-yh2dw8-control-plane-zl5gv
STEP: Collecting events for Pod kube-system/kube-proxy-kvlfs
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-tckch
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-755ff8d7b5-gjk52, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/etcd-capz-conf-yh2dw8-control-plane-zl5gv
STEP: Creating log watcher for controller kube-system/etcd-capz-conf-yh2dw8-control-plane-zl5gv, container etcd
STEP: Fetching kube-system pod logs took 389.499564ms
STEP: Dumping workload cluster capz-conf-yh2dw8/capz-conf-yh2dw8 Azure activity log
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-conf-yh2dw8-control-plane-zl5gv
STEP: failed to find events of Pod "kube-scheduler-capz-conf-yh2dw8-control-plane-zl5gv"
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-yh2dw8-control-plane-zl5gv, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-yh2dw8-control-plane-zl5gv, container kube-controller-manager
STEP: Collecting events for Pod kube-system/metrics-server-76f7667fbf-bt8w8
STEP: Creating log watcher for controller kube-system/calico-node-jkkkz, container calico-node
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-yh2dw8-control-plane-zl5gv
STEP: failed to find events of Pod "kube-controller-manager-capz-conf-yh2dw8-control-plane-zl5gv"
STEP: Creating log watcher for controller kube-system/kube-proxy-kvlfs, container kube-proxy
STEP: Creating log watcher for controller kube-system/metrics-server-76f7667fbf-bt8w8, container metrics-server
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-mzb92
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-yh2dw8-control-plane-zl5gv, container kube-apiserver
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-tckch, container coredns
STEP: Collecting events for Pod kube-system/calico-node-jkkkz
STEP: failed to find events of Pod "etcd-capz-conf-yh2dw8-control-plane-zl5gv"
STEP: failed to find events of Pod "kube-apiserver-capz-conf-yh2dw8-control-plane-zl5gv"
STEP: Fetching activity logs took 2.762275179s
Nov  2 01:38:57.413: INFO: Dumping all the Cluster API resources in the "capz-conf-yh2dw8" namespace
Nov  2 01:38:57.814: INFO: Deleting all clusters in the capz-conf-yh2dw8 namespace
STEP: Deleting cluster capz-conf-yh2dw8
INFO: Waiting for the Cluster capz-conf-yh2dw8/capz-conf-yh2dw8 to be deleted
STEP: Waiting for cluster capz-conf-yh2dw8 to be deleted
... skipping 68 lines ...

JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml


Summarizing 1 Failure:

[Fail] Conformance Tests [Measurement] conformance-tests 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.4/framework/machinedeployment_helpers.go:129

Ran 1 of 23 Specs in 3010.621 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 22 Skipped
--- FAIL: TestE2E (3010.64s)
FAIL

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 13 lines ...

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


Ginkgo ran 1 suite in 52m25.415512767s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc
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:672: test-e2e-local] Error 2
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[1]: *** [Makefile:682: test-conformance] Error 2
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:692: 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 ...