This job view page is being replaced by Spyglass soon. Check out the new job view.
PRCecileRobertMichon: re-enable ILB test for VMSS
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2021-02-26 21:40
Elapsed35m40s
Revisiond8643631ae39d6ea1cbe2216787582014f67b108
Refs 1177

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 17m38s

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:467
Timed out after 180.042s.
Service default/web-ilb failed
Service:
{
  "metadata": {
    "name": "web-ilb",
    "namespace": "default",
    "selfLink": "/api/v1/namespaces/default/services/web-ilb",
    "uid": "b812a357-dae4-4ce7-9267-ef5a39beda9f",
    "resourceVersion": "1260",
    "creationTimestamp": "2021-02-26T21:56:04Z",
    "annotations": {
      "service.beta.kubernetes.io/azure-load-balancer-internal": "true"
    },
    "finalizers": [
      "service.kubernetes.io/load-balancer-cleanup"
    ],
    "managedFields": [
      {
        "manager": "cluster-api-e2e",
        "operation": "Update",
        "apiVersion": "v1",
        "time": "2021-02-26T21:56:04Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:metadata": {
            "f:annotations": {
              ".": {},
              "f:service.beta.kubernetes.io/azure-load-balancer-internal": {}
            }
          },
          "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-02-26T21:56:04Z",
        "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": 32276
      },
      {
        "name": "https",
        "protocol": "TCP",
        "port": 443,
        "targetPort": 443,
        "nodePort": 32297
      }
    ],
    "selector": {
      "app": "web"
    },
    "clusterIP": "10.111.171.160",
    "type": "LoadBalancer",
    "sessionAffinity": "None",
    "externalTrafficPolicy": "Cluster"
  },
  "status": {
    "loadBalancer": {}
  }
}
LAST SEEN                      TYPE     REASON                  OBJECT             MESSAGE
2021-02-26 21:56:04 +0000 UTC  Normal   EnsuringLoadBalancer    service/web-ilb    Ensuring load balancer
2021-02-26 21:56:04 +0000 UTC  Warning  FailedToCreateEndpoint  endpoints/web-ilb  Failed to create endpoint for service default/web-ilb: endpoints "web-ilb" already exists

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 439 lines ...
STEP: Fetching activity logs took 842.749223ms
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-p8vldt" namespace
STEP: Deleting all clusters in the create-workload-cluster-p8vldt namespace
STEP: Deleting cluster capz-e2e-4ww3f6
INFO: Waiting for the Cluster create-workload-cluster-p8vldt/capz-e2e-4ww3f6 to be deleted
STEP: Waiting for cluster capz-e2e-4ww3f6 to be deleted
STEP: Error starting logs stream for pod kube-system/kube-flannel-ds-windows-amd64-462fv, container kube-flannel: Get "https://10.1.0.6:10250/containerLogs/kube-system/kube-flannel-ds-windows-amd64-462fv/kube-flannel?follow=true": dial tcp 10.1.0.6:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-ncd59, container kube-proxy: Get "https://10.1.0.6:10250/containerLogs/kube-system/kube-proxy-windows-ncd59/kube-proxy?follow=true": dial tcp 10.1.0.6:10250: i/o timeout
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-p8vldt
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 17m39s 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:466
    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:467

    Timed out after 180.042s.
    Service default/web-ilb failed
    Service:
    {
      "metadata": {
        "name": "web-ilb",
        "namespace": "default",
        "selfLink": "/api/v1/namespaces/default/services/web-ilb",
... skipping 93 lines ...
      "status": {
        "loadBalancer": {}
      }
    }
    LAST SEEN                      TYPE     REASON                  OBJECT             MESSAGE
    2021-02-26 21:56:04 +0000 UTC  Normal   EnsuringLoadBalancer    service/web-ilb    Ensuring load balancer
    2021-02-26 21:56:04 +0000 UTC  Warning  FailedToCreateEndpoint  endpoints/web-ilb  Failed to create endpoint for service default/web-ilb: endpoints "web-ilb" already exists
    
    Expected
        <bool>: false
    to be true

    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:195
... skipping 90 lines ...
STEP: creating an external Load Balancer service
STEP: waiting for service default/web-elb to be available
STEP: connecting to the external LB service from a curl pod
STEP: waiting for job default/curl-to-elb-jobnagjq to be complete
STEP: connecting directly to the external LB service
2021/02/26 22:03:15 [DEBUG] GET http://20.188.76.186
2021/02/26 22:03:45 [ERR] GET http://20.188.76.186 request failed: Get "http://20.188.76.186": dial tcp 20.188.76.186:80: i/o timeout
2021/02/26 22:03:45 [DEBUG] GET http://20.188.76.186: retrying in 1s (4 left)
STEP: deleting the test resources
STEP: creating a Kubernetes client to the workload cluster
STEP: creating an HTTP deployment
STEP: waiting for deployment default/web-windows to be available
STEP: creating an internal Load Balancer service
... skipping 4 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-jobspla5 to be complete
STEP: connecting directly to the external LB service
2021/02/26 22:06:19 [DEBUG] GET http://20.188.77.62
2021/02/26 22:06:49 [ERR] GET http://20.188.77.62 request failed: Get "http://20.188.77.62": dial tcp 20.188.77.62:80: i/o timeout
2021/02/26 22:06:49 [DEBUG] GET http://20.188.77.62: retrying in 1s (4 left)
STEP: deleting the test resources
STEP: Dumping logs from the "capz-e2e-r2bvlu" workload cluster
STEP: Dumping workload cluster create-workload-cluster-cs7r3f/capz-e2e-r2bvlu logs
Failed to get logs for machine capz-e2e-r2bvlu-md-win-6899d65ccf-z6vnh, cluster create-workload-cluster-cs7r3f/capz-e2e-r2bvlu: dialing from control plane to target node at capz-e2e-r2bvlu-md-win-6tq96: ssh: rejected: connect failed (Temporary failure in name resolution)
STEP: Dumping workload cluster create-workload-cluster-cs7r3f/capz-e2e-r2bvlu kube-system pod logs
STEP: Fetching kube-system pod logs took 357.959996ms
STEP: Creating log watcher for controller kube-system/coredns-f9fd979d6-tfrpp, container coredns
STEP: Creating log watcher for controller kube-system/kube-proxy-vd75k, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-r2bvlu-control-plane-gghwt, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-r2bvlu-control-plane-gghwt, container kube-scheduler
... skipping 15 lines ...
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-nj2sk, container kube-flannel
STEP: Creating log watcher for controller kube-system/kube-proxy-qtj9x, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-t7nxf, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-r2bvlu-control-plane-hstj4, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-r2bvlu-control-plane-ghr9f, container kube-apiserver
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-r2bvlu-control-plane-hstj4, container etcd
STEP: Got error while iterating over activity logs for resource group capz-e2e-r2bvlu: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000416027s
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-cs7r3f" namespace
STEP: Deleting all clusters in the create-workload-cluster-cs7r3f namespace
STEP: Deleting cluster capz-e2e-r2bvlu
INFO: Waiting for the Cluster create-workload-cluster-cs7r3f/capz-e2e-r2bvlu to be deleted
STEP: Waiting for cluster capz-e2e-r2bvlu to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-ddc2v, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-r2bvlu-control-plane-ghr9f, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-vd75k, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-tfrpp, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-r2bvlu-control-plane-hstj4, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-r2bvlu-control-plane-ghr9f, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-tzgvd, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-r2bvlu-control-plane-hstj4, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-7n74l, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-84w9h, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-r2bvlu-control-plane-ghr9f, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-r2bvlu-control-plane-gghwt, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-r2bvlu-control-plane-gghwt, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-t7nxf, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-qtj9x, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-64j4l, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-r2bvlu-control-plane-ghr9f, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-nj2sk, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-htcdc, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-r2bvlu-control-plane-hstj4, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-qv24s, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-r2bvlu-control-plane-gghwt, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-r2bvlu-control-plane-hstj4, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-r2bvlu-control-plane-gghwt, container kube-scheduler: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-cs7r3f
STEP: Redacting sensitive information from logs
INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" ran for 26m29s 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 1728.194 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 16 Skipped


Ginkgo ran 1 suite in 29m53.931424894s
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 ...