This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 0 succeeded
Started2021-11-26 18:37
Elapsed40m6s
Revisionmain

Test Failures


capz-e2e Conformance Tests conformance-tests 31m28s

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:102
Timed out after 1200.000s.
Expected
    <int>: 1
to equal
    <int>: 2
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.1/framework/machinedeployment_helpers.go:121
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 19 Skipped Tests

Error lines from build-log.txt

... skipping 388 lines ...
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102
[BeforeEach] Conformance Tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:58
INFO: Cluster name is capz-conf-yvzy9y
STEP: Creating namespace "capz-conf-yvzy9y" for hosting the cluster
Nov 26 18:46:07.394: INFO: starting to create namespace for hosting the "capz-conf-yvzy9y" test spec
2021/11/26 18:46:07 failed trying to get namespace (capz-conf-yvzy9y):namespaces "capz-conf-yvzy9y" not found
INFO: Creating namespace capz-conf-yvzy9y
INFO: Creating event watcher for namespace "capz-conf-yvzy9y"
[Measure] conformance-tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102
INFO: Creating the workload cluster with name "capz-conf-yvzy9y" using the "(default)" template (Kubernetes v1.22.4, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
... skipping 29 lines ...
STEP: Dumping logs from the "capz-conf-yvzy9y" workload cluster
STEP: Dumping workload cluster capz-conf-yvzy9y/capz-conf-yvzy9y logs
Nov 26 19:10:08.993: INFO: INFO: Collecting logs for node capz-conf-yvzy9y-control-plane-8b4gj in cluster capz-conf-yvzy9y in namespace capz-conf-yvzy9y

Nov 26 19:10:24.889: INFO: INFO: Collecting boot logs for AzureMachine capz-conf-yvzy9y-control-plane-8b4gj

Failed to get logs for machine capz-conf-yvzy9y-md-0-7bf8c64ff6-4tgtm, cluster capz-conf-yvzy9y/capz-conf-yvzy9y: azuremachines.infrastructure.cluster.x-k8s.io "capz-conf-yvzy9y-md-0-fmdgp" not found
Nov 26 19:10:26.277: INFO: INFO: Collecting logs for node capz-conf-yvzy9y-md-0-pczln in cluster capz-conf-yvzy9y in namespace capz-conf-yvzy9y

Nov 26 19:10:36.127: INFO: INFO: Collecting boot logs for AzureMachine capz-conf-yvzy9y-md-0-pczln

STEP: Dumping workload cluster capz-conf-yvzy9y/capz-conf-yvzy9y kube-system pod logs
STEP: Fetching kube-system pod logs took 1.079445371s
... skipping 12 lines ...
STEP: Fetching activity logs took 1.225282435s
STEP: Dumping all the Cluster API resources in the "capz-conf-yvzy9y" namespace
STEP: Deleting all clusters in the capz-conf-yvzy9y namespace
STEP: Deleting cluster capz-conf-yvzy9y
INFO: Waiting for the Cluster capz-conf-yvzy9y/capz-conf-yvzy9y to be deleted
STEP: Waiting for cluster capz-conf-yvzy9y to be deleted
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-b9z8c, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-llplz, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-44qp4, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-hmnnx, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-conf-yvzy9y-control-plane-8b4gj, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-conf-yvzy9y-control-plane-8b4gj, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-conf-yvzy9y-control-plane-8b4gj, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-6vlb2, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-conf-yvzy9y-control-plane-8b4gj, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "conformance-tests" test spec
INFO: Deleting namespace capz-conf-yvzy9y
STEP: Checking if any resources are left over in Azure for spec "conformance-tests"
STEP: Redacting sensitive information from logs

• Failure [1888.727 seconds]
... skipping 62 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.0.1/framework/machinedeployment_helpers.go:121

Ran 1 of 20 Specs in 2131.121 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 19 Skipped
--- FAIL: TestE2E (2131.13s)
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 10 lines ...

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


Ginkgo ran 1 suite in 36m55.38665889s
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[2]: *** [Makefile:176: test-e2e-run] Error 1
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[1]: *** [Makefile:192: test-e2e-local] Error 2
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:201: 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 ...