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-03-16 13:24
Elapsed35m11s
Revisionb99972892a98d054bb001c9e0a6f53d2ff9ad106
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 19m3s

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:507
Timed out after 180.037s.
Service default/web-elb failed
Service:
{
  "metadata": {
    "name": "web-elb",
    "namespace": "default",
    "selfLink": "/api/v1/namespaces/default/services/web-elb",
    "uid": "50f246cc-6d75-4dc5-b126-bf3c9516ab19",
    "resourceVersion": "2001",
    "creationTimestamp": "2021-03-16T13:44:51Z",
    "finalizers": [
      "service.kubernetes.io/load-balancer-cleanup"
    ],
    "managedFields": [
      {
        "manager": "cluster-api-e2e",
        "operation": "Update",
        "apiVersion": "v1",
        "time": "2021-03-16T13:44:51Z",
        "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-16T13:47:31Z",
        "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": 31305
      },
      {
        "name": "https",
        "protocol": "TCP",
        "port": 443,
        "targetPort": 443,
        "nodePort": 32204
      }
    ],
    "selector": {
      "app": "web"
    },
    "clusterIP": "10.101.177.61",
    "type": "LoadBalancer",
    "sessionAffinity": "None",
    "externalTrafficPolicy": "Cluster"
  },
  "status": {
    "loadBalancer": {}
  }
}
LAST SEEN                      TYPE    REASON                OBJECT           MESSAGE
2021-03-16 13:47:31 +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.3.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Show 17 Skipped Tests

Error lines from build-log.txt

... skipping 459 lines ...
  Creating a Windows enabled VMSS cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:506
    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:507

    Timed out after 180.037s.
    Service default/web-elb failed
    Service:
    {
      "metadata": {
        "name": "web-elb",
        "namespace": "default",
        "selfLink": "/api/v1/namespaces/default/services/web-elb",
... skipping 186 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-job6n5g5 to be complete
STEP: connecting directly to the external LB service
2021/03/16 13:49:12 [DEBUG] GET http://20.72.134.148
2021/03/16 13:49:42 [ERR] GET http://20.72.134.148 request failed: Get "http://20.72.134.148": dial tcp 20.72.134.148:80: i/o timeout
2021/03/16 13:49:42 [DEBUG] GET http://20.72.134.148: 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 7 lines ...
STEP: waiting for job default/curl-to-elb-job0nas1 to be complete
STEP: connecting directly to the external LB service
2021/03/16 13:52:08 [DEBUG] GET http://20.81.96.41
STEP: deleting the test resources
STEP: Dumping logs from the "capz-e2e-oo58lq" workload cluster
STEP: Dumping workload cluster create-workload-cluster-xmze6b/capz-e2e-oo58lq logs
Failed to get logs for machine capz-e2e-oo58lq-md-win-7c98897b6d-nk5nj, cluster create-workload-cluster-xmze6b/capz-e2e-oo58lq: dialing from control plane to target node at capz-e2e-oo58lq-md-win-g7759: ssh: rejected: connect failed (Temporary failure in name resolution)
STEP: Dumping workload cluster create-workload-cluster-xmze6b/capz-e2e-oo58lq kube-system pod logs
STEP: Fetching kube-system pod logs took 232.239185ms
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-oo58lq-control-plane-x7mw6, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-oo58lq-control-plane-d4c6w, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-proxy-sjddm, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-6knh4, container kube-proxy
... skipping 21 lines ...
STEP: Fetching activity logs took 1.066600889s
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-xmze6b" namespace
STEP: Deleting all clusters in the create-workload-cluster-xmze6b namespace
STEP: Deleting cluster capz-e2e-oo58lq
INFO: Waiting for the Cluster create-workload-cluster-xmze6b/capz-e2e-oo58lq to be deleted
STEP: Waiting for cluster capz-e2e-oo58lq to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-455mr, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-9h6p6, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-oo58lq-control-plane-d4c6w, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-6knh4, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-5pww6, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-oo58lq-control-plane-x7mw6, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-oo58lq-control-plane-d4c6w, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-oo58lq-control-plane-d52b9, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-4nzdc, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-oo58lq-control-plane-x7mw6, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-oo58lq-control-plane-d4c6w, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-oo58lq-control-plane-x7mw6, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-oo58lq-control-plane-d52b9, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-oo58lq-control-plane-d52b9, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-xk5nf, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-oo58lq-control-plane-d52b9, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-859nr, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-2j755, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-mk5qh, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-sjddm, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-2rc9n, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-oo58lq-control-plane-d4c6w, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-oo58lq-control-plane-x7mw6, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-5q4pv, 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-xmze6b
STEP: Redacting sensitive information from logs
INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" ran for 23m21s 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 19 Specs in 1588.538 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 17 Skipped


Ginkgo ran 1 suite in 28m3.485067525s
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 ...