Recent runs || View in Spyglass
PR | nader-ziada: dont use hard-coded value for manager namespace |
Result | FAILURE |
Tests | 1 failed / 1 succeeded |
Started | |
Elapsed | 31m2s |
Revision | ec2cf91a342931e8853d6689d9bad9e0c672c873 |
Refs |
1209 |
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 180.039s. Service default/web-elb failed Service: { "metadata": { "name": "web-elb", "namespace": "default", "selfLink": "/api/v1/namespaces/default/services/web-elb", "uid": "d6728093-992d-4569-90fa-3e3c9863c772", "resourceVersion": "1352", "creationTimestamp": "2021-03-04T22:31:10Z", "finalizers": [ "service.kubernetes.io/load-balancer-cleanup" ], "managedFields": [ { "manager": "cluster-api-e2e", "operation": "Update", "apiVersion": "v1", "time": "2021-03-04T22:31:10Z", "fieldsType": "FieldsV1", "fieldsV1": { "f:spec": { "f:externalTrafficPolicy": {}, "f:ports": { ".": {}, "k:{\"port\":80,\"protocol\":\"TCP\"}": { ".": {}, "f:name": {}, "f:port": {}, "f:protocol": {}, "f:targetPort": {} }, "k:{\"port\":443,\"protocol\":\"TCP\"}": { ".": {}, "f:name": {}, "f:port": {}, "f:protocol": {}, "f:targetPort": {} } }, "f:selector": { ".": {}, "f:app": {} }, "f:sessionAffinity": {}, "f:type": {} } } }, { "manager": "kube-controller-manager", "operation": "Update", "apiVersion": "v1", "time": "2021-03-04T22:31:10Z", "fieldsType": "FieldsV1", "fieldsV1": { "f:metadata": { "f:finalizers": { ".": {}, "v:\"service.kubernetes.io/load-balancer-cleanup\"": {} } } } } ] }, "spec": { "ports": [ { "name": "http", "protocol": "TCP", "port": 80, "targetPort": 80, "nodePort": 30669 }, { "name": "https", "protocol": "TCP", "port": 443, "targetPort": 443, "nodePort": 32506 } ], "selector": { "app": "web" }, "clusterIP": "10.109.164.166", "type": "LoadBalancer", "sessionAffinity": "None", "externalTrafficPolicy": "Cluster" }, "status": { "loadBalancer": {} } } LAST SEEN TYPE REASON OBJECT MESSAGE 2021-03-04 22:31:10 +0000 UTC Normal EnsuringLoadBalancer service/web-elb Ensuring load balancer Expected <bool>: false to be true /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:195from junit.e2e_suite.2.xml
INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" started at Thu, 04 Mar 2021 22:23:38 UTC on Ginkgo node 2 of 3 �[1mSTEP�[0m: Creating a namespace for hosting the "create-workload-cluster" test spec INFO: Creating namespace create-workload-cluster-04esk4 INFO: Creating event watcher for namespace "create-workload-cluster-04esk4" INFO: Creating the workload cluster with name "capz-e2e-vr0uwx" using the "machine-pool-windows" template (Kubernetes v1.19.7, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-vr0uwx --infrastructure (default) --kubernetes-version v1.19.7 --control-plane-machine-count 1 --worker-machine-count 1 --flavor machine-pool-windows INFO: Applying the cluster template yaml to the cluster cluster.cluster.x-k8s.io/capz-e2e-vr0uwx created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-vr0uwx created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-vr0uwx-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-vr0uwx-control-plane created machinepool.exp.cluster.x-k8s.io/capz-e2e-vr0uwx-mp-0 created azuremachinepool.exp.infrastructure.cluster.x-k8s.io/capz-e2e-vr0uwx-mp-0 created kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-vr0uwx-mp-0 created machinepool.exp.cluster.x-k8s.io/capz-e2e-vr0uwx-mp-win created azuremachinepool.exp.infrastructure.cluster.x-k8s.io/capz-e2e-vr0uwx-mp-win created kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-vr0uwx-mp-win created configmap/cni-capz-e2e-vr0uwx-crs-0 created clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-vr0uwx-crs-0 created INFO: Waiting for the cluster infrastructure to be provisioned �[1mSTEP�[0m: Waiting for cluster to enter the provisioned phase INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by create-workload-cluster-04esk4/capz-e2e-vr0uwx-control-plane to be provisioned �[1mSTEP�[0m: Waiting for one control plane node to exist INFO: Waiting for control plane to be ready INFO: Waiting for control plane create-workload-cluster-04esk4/capz-e2e-vr0uwx-control-plane to be ready (implies underlying nodes to be ready as well) �[1mSTEP�[0m: Waiting for the control plane to be ready INFO: Waiting for the machine deployments to be provisioned INFO: Waiting for the machine pools to be provisioned �[1mSTEP�[0m: Waiting for the machine pool workload nodes to exist �[1mSTEP�[0m: Waiting for the machine pool workload nodes to exist �[1mSTEP�[0m: creating a Kubernetes client to the workload cluster �[1mSTEP�[0m: creating an HTTP deployment �[1mSTEP�[0m: waiting for deployment default/web to be available �[1mSTEP�[0m: creating an external Load Balancer service �[1mSTEP�[0m: waiting for service default/web-elb to be available �[1mSTEP�[0m: Dumping logs from the "capz-e2e-vr0uwx" workload cluster �[1mSTEP�[0m: Dumping workload cluster create-workload-cluster-04esk4/capz-e2e-vr0uwx logs �[1mSTEP�[0m: Dumping workload cluster create-workload-cluster-04esk4/capz-e2e-vr0uwx kube-system pod logs �[1mSTEP�[0m: Fetching kube-system pod logs took 280.265202ms �[1mSTEP�[0m: Dumping workload cluster create-workload-cluster-04esk4/capz-e2e-vr0uwx Azure activity log �[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-e2e-vr0uwx-control-plane-8rc5t, container etcd �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-dls6q, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-stn45, container kube-flannel �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-cvwps, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-sxm5k, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-6jbbf, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-vr0uwx-control-plane-8rc5t, container kube-scheduler �[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-f9fd979d6-q4khd, container coredns �[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-f9fd979d6-szd5r, container coredns �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-vr0uwx-control-plane-8rc5t, container kube-controller-manager �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-hscmx, container kube-flannel �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-vr0uwx-control-plane-8rc5t, container kube-apiserver �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-k5dcf, container kube-flannel �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-5zxhx, container kube-flannel �[1mSTEP�[0m: Fetching activity logs took 621.759547ms �[1mSTEP�[0m: Dumping all the Cluster API resources in the "create-workload-cluster-04esk4" namespace �[1mSTEP�[0m: Deleting all clusters in the create-workload-cluster-04esk4 namespace �[1mSTEP�[0m: Deleting cluster capz-e2e-vr0uwx INFO: Waiting for the Cluster create-workload-cluster-04esk4/capz-e2e-vr0uwx to be deleted �[1mSTEP�[0m: Waiting for cluster capz-e2e-vr0uwx to be deleted �[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-proxy-windows-sxm5k, container kube-proxy: Get "https://10.1.0.7:10250/containerLogs/kube-system/kube-proxy-windows-sxm5k/kube-proxy?follow=true": dial tcp 10.1.0.7:10250: i/o timeout �[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-flannel-ds-windows-amd64-5zxhx, container kube-flannel: Get "https://10.1.0.7:10250/containerLogs/kube-system/kube-flannel-ds-windows-amd64-5zxhx/kube-flannel?follow=true": dial tcp 10.1.0.7:10250: i/o timeout �[1mSTEP�[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace create-workload-cluster-04esk4 �[1mSTEP�[0m: 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 16m37s on Ginkgo node 2 of 3
Filter through log files | View test history on testgrid
capz-e2e Workload cluster creation Creating a Windows Enabled cluster With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node
capz-e2e Conformance Tests conformance-tests
capz-e2e Running the Cluster API E2E tests Running the KCP upgrade spec Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a HA cluster
capz-e2e Running the Cluster API E2E tests Running the KCP upgrade spec Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a single control plane cluster
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment upgrade spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Should adopt up-to-date control plane Machines without modification Should adopt up-to-date control plane Machines without modification
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Workload cluster creation Creating a GPU-enabled cluster with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster with a single control plane node and an AzureMachinePool with 2 nodes
capz-e2e Workload cluster creation Creating a cluster using a different SP identity with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster Creates a public management cluster in the same vnet
capz-e2e Workload cluster creation With 3 control-plane nodes and 2 worker nodes
... skipping 440 lines ... [1mSTEP[0m: Fetching activity logs took 621.759547ms [1mSTEP[0m: Dumping all the Cluster API resources in the "create-workload-cluster-04esk4" namespace [1mSTEP[0m: Deleting all clusters in the create-workload-cluster-04esk4 namespace [1mSTEP[0m: Deleting cluster capz-e2e-vr0uwx INFO: Waiting for the Cluster create-workload-cluster-04esk4/capz-e2e-vr0uwx to be deleted [1mSTEP[0m: Waiting for cluster capz-e2e-vr0uwx to be deleted [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-windows-sxm5k, container kube-proxy: Get "https://10.1.0.7:10250/containerLogs/kube-system/kube-proxy-windows-sxm5k/kube-proxy?follow=true": dial tcp 10.1.0.7:10250: i/o timeout [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-flannel-ds-windows-amd64-5zxhx, container kube-flannel: Get "https://10.1.0.7:10250/containerLogs/kube-system/kube-flannel-ds-windows-amd64-5zxhx/kube-flannel?follow=true": dial tcp 10.1.0.7:10250: i/o timeout [1mSTEP[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace create-workload-cluster-04esk4 [1mSTEP[0m: 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 16m37s on Ginkgo node 2 of 3 ... skipping 3 lines ... Creating a Windows enabled VMSS cluster [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:467[0m [91m[1mwith a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node [It][0m [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:468[0m [91mTimed out after 180.039s. Service default/web-elb failed Service: { "metadata": { "name": "web-elb", "namespace": "default", "selfLink": "/api/v1/namespaces/default/services/web-elb", ... skipping 201 lines ... [1mSTEP[0m: creating an external Load Balancer service [1mSTEP[0m: waiting for service default/web-windows-elb to be available [1mSTEP[0m: connecting to the external LB service from a curl pod [1mSTEP[0m: waiting for job default/curl-to-elb-jobs08cn to be complete [1mSTEP[0m: connecting directly to the external LB service 2021/03/04 22:38:10 [DEBUG] GET http://52.138.119.231 2021/03/04 22:38:40 [ERR] GET http://52.138.119.231 request failed: Get "http://52.138.119.231": dial tcp 52.138.119.231:80: i/o timeout 2021/03/04 22:38:40 [DEBUG] GET http://52.138.119.231: retrying in 1s (4 left) [1mSTEP[0m: deleting the test resources [1mSTEP[0m: Dumping logs from the "capz-e2e-cck3r7" workload cluster [1mSTEP[0m: Dumping workload cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 logs Failed to get logs for machine capz-e2e-cck3r7-md-win-5749f8dc99-cknq4, cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7: dialing from control plane to target node at capz-e2e-cck3r7-md-win-mz7j8: ssh: rejected: connect failed (Temporary failure in name resolution) [1mSTEP[0m: Dumping workload cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 kube-system pod logs [1mSTEP[0m: Fetching kube-system pod logs took 357.704082ms [1mSTEP[0m: Dumping workload cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 Azure activity log [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-f9fd979d6-g5t9c, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-q2hwv, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-pwfl7, container kube-proxy ... skipping 15 lines ... [1mSTEP[0m: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-k7tcv, container kube-flannel [1mSTEP[0m: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-2fb79, container kube-flannel [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-g9zdz, container kube-apiserver [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-f9fd979d6-p5v79, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-capz-e2e-cck3r7-control-plane-g9zdz, container etcd [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-cck3r7-control-plane-g9zdz, container kube-controller-manager [1mSTEP[0m: Got error while iterating over activity logs for resource group capz-e2e-cck3r7: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded [1mSTEP[0m: Fetching activity logs took 30.000530494s [1mSTEP[0m: Dumping all the Cluster API resources in the "create-workload-cluster-y40p8w" namespace [1mSTEP[0m: Deleting all clusters in the create-workload-cluster-y40p8w namespace [1mSTEP[0m: Deleting cluster capz-e2e-cck3r7 INFO: Waiting for the Cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 to be deleted [1mSTEP[0m: Waiting for cluster capz-e2e-cck3r7 to be deleted [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-bh9xk, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-g9zdz, container kube-apiserver: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-g5t9c, container coredns: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-mb6sl, container kube-apiserver: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-cck3r7-control-plane-g9zdz, container kube-controller-manager: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-ztk85, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-k7tcv, container kube-flannel: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-cck3r7-control-plane-g9zdz, container etcd: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-cck3r7-control-plane-mb6sl, container kube-scheduler: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-windows-pwfl7, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-cck3r7-control-plane-gjqmz, container kube-controller-manager: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-gjqmz, container kube-apiserver: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-sxhw2, container kube-flannel: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-cck3r7-control-plane-gjqmz, container kube-scheduler: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-vldsk, container kube-flannel: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-q2hwv, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-cck3r7-control-plane-g9zdz, container kube-scheduler: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-cck3r7-control-plane-gjqmz, container etcd: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-2fb79, container kube-flannel: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-p5v79, container coredns: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-bkbf6, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-cck3r7-control-plane-mb6sl, container kube-controller-manager: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-cck3r7-control-plane-mb6sl, container etcd: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-g7t72, container kube-flannel: http2: client connection lost [1mSTEP[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace create-workload-cluster-y40p8w [1mSTEP[0m: Redacting sensitive information from logs INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" ran for 24m26s on Ginkgo node 1 of 3 ... skipping 8 lines ... [1mSTEP[0m: Tearing down the management cluster [91m[1mSummarizing 1 Failure:[0m [91m[1m[Fail] [0m[90mWorkload cluster creation [0m[0mCreating a Windows enabled VMSS cluster [0m[91m[1m[It] with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node [0m [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:195[0m [1m[91mRan 2 of 18 Specs in 1602.647 seconds[0m [1m[91mFAIL![0m -- [32m[1m1 Passed[0m | [91m[1m1 Failed[0m | [33m[1m0 Pending[0m | [36m[1m16 Skipped[0m Ginkgo ran 1 suite in 27m41.375242903s 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 ...