This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnader-ziada: dont use hard-coded value for manager namespace
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2021-03-04 22:17
Elapsed31m2s
Revisionec2cf91a342931e8853d6689d9bad9e0c672c873
Refs 1209

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 16m37s

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:195
				
				Click to see stdout/stderrfrom junit.e2e_suite.2.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 440 lines ...
STEP: Fetching activity logs took 621.759547ms
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-04esk4" namespace
STEP: Deleting all clusters in the create-workload-cluster-04esk4 namespace
STEP: Deleting cluster capz-e2e-vr0uwx
INFO: Waiting for the Cluster create-workload-cluster-04esk4/capz-e2e-vr0uwx to be deleted
STEP: Waiting for cluster capz-e2e-vr0uwx to be deleted
STEP: 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
STEP: 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
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-04esk4
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 16m37s on Ginkgo node 2 of 3


... skipping 3 lines ...
  Creating a Windows enabled VMSS cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:467
    with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node [It]
    /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",
... skipping 201 lines ...
STEP: creating an external Load Balancer service
STEP: waiting for service default/web-windows-elb to be available
STEP: connecting to the external LB service from a curl pod
STEP: waiting for job default/curl-to-elb-jobs08cn to be complete
STEP: 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)
STEP: deleting the test resources
STEP: Dumping logs from the "capz-e2e-cck3r7" workload cluster
STEP: 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)
STEP: Dumping workload cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 kube-system pod logs
STEP: Fetching kube-system pod logs took 357.704082ms
STEP: Dumping workload cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 Azure activity log
STEP: Creating log watcher for controller kube-system/coredns-f9fd979d6-g5t9c, container coredns
STEP: Creating log watcher for controller kube-system/kube-proxy-q2hwv, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-pwfl7, container kube-proxy
... skipping 15 lines ...
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-k7tcv, container kube-flannel
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-2fb79, container kube-flannel
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-g9zdz, container kube-apiserver
STEP: Creating log watcher for controller kube-system/coredns-f9fd979d6-p5v79, container coredns
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-cck3r7-control-plane-g9zdz, container etcd
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-cck3r7-control-plane-g9zdz, container kube-controller-manager
STEP: 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
STEP: Fetching activity logs took 30.000530494s
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-y40p8w" namespace
STEP: Deleting all clusters in the create-workload-cluster-y40p8w namespace
STEP: Deleting cluster capz-e2e-cck3r7
INFO: Waiting for the Cluster create-workload-cluster-y40p8w/capz-e2e-cck3r7 to be deleted
STEP: Waiting for cluster capz-e2e-cck3r7 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bh9xk, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-g9zdz, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-g5t9c, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-mb6sl, container kube-apiserver: http2: client connection lost
STEP: 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
STEP: Got error while streaming logs for pod kube-system/kube-proxy-ztk85, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-k7tcv, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-cck3r7-control-plane-g9zdz, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-cck3r7-control-plane-mb6sl, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-pwfl7, container kube-proxy: http2: client connection lost
STEP: 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
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-cck3r7-control-plane-gjqmz, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-sxhw2, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-cck3r7-control-plane-gjqmz, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-vldsk, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-q2hwv, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-cck3r7-control-plane-g9zdz, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-cck3r7-control-plane-gjqmz, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-2fb79, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-p5v79, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bkbf6, container kube-proxy: http2: client connection lost
STEP: 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
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-cck3r7-control-plane-mb6sl, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-g7t72, container kube-flannel: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-y40p8w
STEP: 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 ...
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/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:195

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


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 ...