This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnprokopic: Fix AKS cluster provisioning errors
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2021-03-02 17:54
Elapsed36m4s
Revision96812e741f85244df749c340fbf728744a863a43
Refs 1205

Test Failures


capz-e2e Workload cluster creation Creating a Windows enabled VMSS cluster with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node 25m53s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sWindows\senabled\sVMSS\scluster\swith\sa\ssingle\scontrol\splane\snode\sand\san\sLinux\sAzureMachinePool\swith\s1\snodes\sand\sWindows\sAzureMachinePool\swith\s1\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:468
Timed out after 900.000s.
Expected
    <int>: 0
to equal
    <int>: 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.11-0.20210209200458-51a6d64d171c/test/framework/machinepool_helpers.go:85
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Show 16 Skipped Tests

Error lines from build-log.txt

... skipping 545 lines ...
STEP: waiting for job default/curl-to-elb-job5p8k0 to be complete
STEP: connecting directly to the external LB service
2021/03/02 18:21:37 [DEBUG] GET http://40.74.181.108
STEP: deleting the test resources
STEP: Dumping logs from the "capz-e2e-dv774i" workload cluster
STEP: Dumping workload cluster create-workload-cluster-owwb8m/capz-e2e-dv774i logs
Failed to get logs for machine capz-e2e-dv774i-md-win-9f4f7ddc9-982f6, cluster create-workload-cluster-owwb8m/capz-e2e-dv774i: dialing from control plane to target node at capz-e2e-dv774i-md-win-zlgzp: ssh: rejected: connect failed (Temporary failure in name resolution)
STEP: Dumping workload cluster create-workload-cluster-owwb8m/capz-e2e-dv774i kube-system pod logs
STEP: Fetching kube-system pod logs took 373.87059ms
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-dv774i-control-plane-d7kpb, container etcd
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-dv774i-control-plane-xqztb, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-dv774i-control-plane-h5lx2, container kube-apiserver
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-dv774i-control-plane-xqztb, container etcd
... skipping 15 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-dv774i-control-plane-h5lx2, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-dv774i-control-plane-xqztb, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-dv774i-control-plane-d7kpb, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-dv774i-control-plane-h5lx2, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-dv774i-control-plane-xqztb, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-dv774i-control-plane-h5lx2, container etcd
STEP: Got error while iterating over activity logs for resource group capz-e2e-dv774i: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000374429s
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-owwb8m" namespace
STEP: Deleting all clusters in the create-workload-cluster-owwb8m namespace
STEP: Deleting cluster capz-e2e-dv774i
INFO: Waiting for the Cluster create-workload-cluster-owwb8m/capz-e2e-dv774i to be deleted
STEP: Waiting for cluster capz-e2e-dv774i to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-dv774i-control-plane-d7kpb, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-dv774i-control-plane-xqztb, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-h5v27, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-s67cv, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-dv774i-control-plane-xqztb, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-jhl7d, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-dv774i-control-plane-d7kpb, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-z4s8g, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-dv774i-control-plane-h5lx2, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-dv774i-control-plane-xqztb, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-dv774i-control-plane-h5lx2, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-pb68h, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-dv774i-control-plane-d7kpb, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-dv774i-control-plane-xqztb, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-dv774i-control-plane-h5lx2, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-dv774i-control-plane-h5lx2, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-9jbb4, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-dv774i-control-plane-d7kpb, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-ww4qr, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-s9pf4, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-8kgrd, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-xs9xm, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-szrgr, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-fs8lt, container kube-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-owwb8m
STEP: Redacting sensitive information from logs
INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" ran for 26m14s on Ginkgo node 1 of 3


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



Summarizing 1 Failure:

[Fail] Workload cluster creation Creating a Windows enabled VMSS cluster [It] with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.11-0.20210209200458-51a6d64d171c/test/framework/machinepool_helpers.go:85

Ran 2 of 18 Specs in 1703.185 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 16 Skipped


Ginkgo ran 1 suite in 29m41.383510603s
Test Suite Failed
make[1]: *** [Makefile:169: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:177: 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 ...