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-25 22:31
Elapsed32m10s
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 21m8s

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.040s.
Service default/web-elb failed
Service:
{
  "metadata": {
    "name": "web-elb",
    "namespace": "default",
    "selfLink": "/api/v1/namespaces/default/services/web-elb",
    "uid": "3f673783-1f9e-48d6-8c9d-3cb6fd319007",
    "resourceVersion": "2016",
    "creationTimestamp": "2021-02-25T22:48:04Z",
    "finalizers": [
      "service.kubernetes.io/load-balancer-cleanup"
    ],
    "managedFields": [
      {
        "manager": "cluster-api-e2e",
        "operation": "Update",
        "apiVersion": "v1",
        "time": "2021-02-25T22:48:04Z",
        "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-02-25T22:50:06Z",
        "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": 30923
      },
      {
        "name": "https",
        "protocol": "TCP",
        "port": 443,
        "targetPort": 443,
        "nodePort": 30365
      }
    ],
    "selector": {
      "app": "web"
    },
    "clusterIP": "10.104.167.129",
    "type": "LoadBalancer",
    "sessionAffinity": "None",
    "externalTrafficPolicy": "Cluster"
  },
  "status": {
    "loadBalancer": {}
  }
}
LAST SEEN                      TYPE    REASON                OBJECT           MESSAGE
2021-02-25 22:50:06 +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 16 Skipped Tests

Error lines from build-log.txt

... skipping 441 lines ...
STEP: Fetching activity logs took 713.024771ms
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-ee49la" namespace
STEP: Deleting all clusters in the create-workload-cluster-ee49la namespace
STEP: Deleting cluster capz-e2e-f7vzf5
INFO: Waiting for the Cluster create-workload-cluster-ee49la/capz-e2e-f7vzf5 to be deleted
STEP: Waiting for cluster capz-e2e-f7vzf5 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-r8545, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-x4g2z, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-zbwj9, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-f7vzf5-control-plane-sn8w6, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-lzj2k, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-f7vzf5-control-plane-sn8w6, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-9fws8, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-f7vzf5-control-plane-sn8w6, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-kwzfn, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-sxt88, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-fg5vg, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-f7vzf5-control-plane-sn8w6, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-ee49la
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 21m9s on Ginkgo node 3 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.040s.
    Service default/web-elb failed
    Service:
    {
      "metadata": {
        "name": "web-elb",
        "namespace": "default",
        "selfLink": "/api/v1/namespaces/default/services/web-elb",
... skipping 204 lines ...
STEP: waiting for job default/curl-to-elb-job7e97o to be complete
STEP: connecting directly to the external LB service
2021/02/25 22:54:11 [DEBUG] GET http://40.119.1.150
STEP: deleting the test resources
STEP: Dumping logs from the "capz-e2e-og62cg" workload cluster
STEP: Dumping workload cluster create-workload-cluster-d02qba/capz-e2e-og62cg logs
Failed to get logs for machine capz-e2e-og62cg-md-win-84567ffdb8-qmgmf, cluster create-workload-cluster-d02qba/capz-e2e-og62cg: dialing from control plane to target node at capz-e2e-og62cg-md-win-5ggsf: ssh: rejected: connect failed (Temporary failure in name resolution)
STEP: Dumping workload cluster create-workload-cluster-d02qba/capz-e2e-og62cg kube-system pod logs
STEP: Fetching kube-system pod logs took 401.927939ms
STEP: Dumping workload cluster create-workload-cluster-d02qba/capz-e2e-og62cg Azure activity log
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-2przw, container kube-flannel
STEP: Creating log watcher for controller kube-system/kube-proxy-q4drx, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-p8kkf, container kube-flannel
... skipping 15 lines ...
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-og62cg-control-plane-rh45l, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-og62cg-control-plane-qj75j, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-og62cg-control-plane-rh45l, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-og62cg-control-plane-qj75j, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-og62cg-control-plane-qj75j, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-og62cg-control-plane-rh45l, container kube-scheduler
STEP: Got error while iterating over activity logs for resource group capz-e2e-og62cg: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000390733s
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-d02qba" namespace
STEP: Deleting all clusters in the create-workload-cluster-d02qba namespace
STEP: Deleting cluster capz-e2e-og62cg
INFO: Waiting for the Cluster create-workload-cluster-d02qba/capz-e2e-og62cg to be deleted
STEP: Waiting for cluster capz-e2e-og62cg to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-2przw, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-zqbjl, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-og62cg-control-plane-qj75j, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-qrwsr, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-v4gjw, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-og62cg-control-plane-rh45l, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-og62cg-control-plane-qj75j, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-og62cg-control-plane-qj75j, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-og62cg-control-plane-mphsl, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-og62cg-control-plane-mphsl, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-rbdlw, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-n445d, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-p8kkf, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-og62cg-control-plane-mphsl, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-og62cg-control-plane-rh45l, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-lsz9m, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-g2gnm, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-og62cg-control-plane-mphsl, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-og62cg-control-plane-qj75j, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-zqb7s, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-og62cg-control-plane-rh45l, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-j9rhg, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-q4drx, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-og62cg-control-plane-rh45l, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-d02qba
STEP: Redacting sensitive information from logs
INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" ran for 25m29s on Ginkgo node 2 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 1668.707 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 16 Skipped


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