This job view page is being replaced by Spyglass soon. Check out the new job view.
PRCecileRobertMichon: Update kubectl hack/tools version to v1.22.4
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2021-11-24 19:58
Elapsed32m31s
Revisionb344e7c502dd9a43974ee7c01f586fb9fe915641
Refs 1884

Test Failures


capz-e2e Workload cluster creation Creating a Windows Enabled cluster with dockershim With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node 23m24s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sWindows\sEnabled\scluster\swith\sdockershim\sWith\s3\scontrol\-plane\snodes\sand\s1\sLinux\sworker\snode\sand\s1\sWindows\sworker\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:532
Timed out after 1200.002s.
Expected
    <int>: 1
to equal
    <int>: 3
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.1/framework/controlplane_helpers.go:108
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Show 22 Skipped Tests

Error lines from build-log.txt

... skipping 434 lines ...
  With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:532

INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" started at Wed, 24 Nov 2021 20:06:17 UTC on Ginkgo node 1 of 3
STEP: Creating namespace "capz-e2e-nz79td" for hosting the cluster
Nov 24 20:06:17.372: INFO: starting to create namespace for hosting the "capz-e2e-nz79td" test spec
2021/11/24 20:06:17 failed trying to get namespace (capz-e2e-nz79td):namespaces "capz-e2e-nz79td" not found
INFO: Creating namespace capz-e2e-nz79td
INFO: Creating event watcher for namespace "capz-e2e-nz79td"
Nov 24 20:06:17.405: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-nz79td-win-ha
INFO: Creating the workload cluster with name "capz-e2e-nz79td-win-ha" using the "windows" template (Kubernetes v1.22.4, 3 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 90 lines ...
  with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:579

INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" started at Wed, 24 Nov 2021 20:06:17 UTC on Ginkgo node 2 of 3
STEP: Creating namespace "capz-e2e-qt7xpx" for hosting the cluster
Nov 24 20:06:17.786: INFO: starting to create namespace for hosting the "capz-e2e-qt7xpx" test spec
2021/11/24 20:06:17 failed trying to get namespace (capz-e2e-qt7xpx):namespaces "capz-e2e-qt7xpx" not found
INFO: Creating namespace capz-e2e-qt7xpx
INFO: Creating event watcher for namespace "capz-e2e-qt7xpx"
Nov 24 20:06:17.826: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-qt7xpx-win-vmss
INFO: Creating the workload cluster with name "capz-e2e-qt7xpx-win-vmss" using the "machine-pool-windows" template (Kubernetes v1.22.4, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 53 lines ...
STEP: waiting for job default/curl-to-elb-jobzv751dgv777 to be complete
Nov 24 20:17:04.118: INFO: waiting for job default/curl-to-elb-jobzv751dgv777 to be complete
Nov 24 20:17:14.231: INFO: job default/curl-to-elb-jobzv751dgv777 is complete, took 10.113374223s
STEP: connecting directly to the external LB service
Nov 24 20:17:14.231: INFO: starting attempts to connect directly to the external LB service
2021/11/24 20:17:14 [DEBUG] GET http://20.99.131.120
2021/11/24 20:17:44 [ERR] GET http://20.99.131.120 request failed: Get "http://20.99.131.120": dial tcp 20.99.131.120:80: i/o timeout
2021/11/24 20:17:44 [DEBUG] GET http://20.99.131.120: retrying in 1s (4 left)
Nov 24 20:18:00.592: INFO: successfully connected to the external LB service
STEP: deleting the test resources
Nov 24 20:18:00.592: INFO: starting to delete external LB service weblbxjlj-elb
Nov 24 20:18:00.674: INFO: starting to delete deployment weblbxjlj
Nov 24 20:18:00.732: INFO: starting to delete job curl-to-elb-jobzv751dgv777
... skipping 65 lines ...
STEP: Fetching activity logs took 968.306811ms
STEP: Dumping all the Cluster API resources in the "capz-e2e-qt7xpx" namespace
STEP: Deleting all clusters in the capz-e2e-qt7xpx namespace
STEP: Deleting cluster capz-e2e-qt7xpx-win-vmss
INFO: Waiting for the Cluster capz-e2e-qt7xpx/capz-e2e-qt7xpx-win-vmss to be deleted
STEP: Waiting for cluster capz-e2e-qt7xpx-win-vmss to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-qt7xpx-win-vmss-control-plane-mqffv, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-5dcdz, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-5mw89, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-6rkr2, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-hbxp5, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-qt7xpx-win-vmss-control-plane-mqffv, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-qqvbm, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-qt7xpx-win-vmss-control-plane-mqffv, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-rq9ps, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-lxlj5, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-qt7xpx-win-vmss-control-plane-mqffv, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-g2fl4, container kube-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-qt7xpx
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" ran for 24m27s on Ginkgo node 2 of 3

... skipping 9 lines ...
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] Workload cluster creation Creating a Windows Enabled cluster with dockershim [It] With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.1/framework/controlplane_helpers.go:108

Ran 2 of 24 Specs in 1639.318 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 22 Skipped


Ginkgo ran 1 suite in 28m42.998068999s
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[1]: *** [Makefile:176: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:184: test-e2e] Error 2
================ REDACTING LOGS ================
All sensitive variables are redacted
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 5 lines ...