This job view page is being replaced by Spyglass soon. Check out the new job view.
PRk8s-infra-cherrypick-robot: [release-1.0] v1alpha4 -> v1beta1 clusterctl upgrade test
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2021-11-18 23:58
Elapsed41m57s
Revision1c0dcc8c548f577cdb65c915251e8c56f8f18eda
Refs 1878

Test Failures


capz-e2e Workload cluster creation Creating a Windows Enabled cluster with dockershim With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node 34m26s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sWindows\sEnabled\scluster\swith\sdockershim\sWith\s3\scontrol\-plane\snodes\sand\s1\sLinux\sworker\snode\sand\s1\sWindows\sworker\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:532
Timed out after 300.060s.
Service default/webgqa7o3-ilb failed
Service:
{
  "metadata": {
    "name": "webgqa7o3-ilb",
    "namespace": "default",
    "uid": "9bf482de-f38c-4248-813f-10329e9f4b34",
    "resourceVersion": "1434",
    "creationTimestamp": "2021-11-19T00:13:40Z",
    "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-11-19T00:13:40Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:metadata": {
            "f:annotations": {
              ".": {},
              "f:service.beta.kubernetes.io/azure-load-balancer-internal": {}
            }
          },
          "f:spec": {
            "f:allocateLoadBalancerNodePorts": {},
            "f:externalTrafficPolicy": {},
            "f:internalTrafficPolicy": {},
            "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:sessionAffinity": {},
            "f:type": {}
          }
        }
      },
      {
        "manager": "kube-controller-manager",
        "operation": "Update",
        "apiVersion": "v1",
        "time": "2021-11-19T00:13:40Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:metadata": {
            "f:finalizers": {
              ".": {},
              "v:\"service.kubernetes.io/load-balancer-cleanup\"": {}
            }
          }
        },
        "subresource": "status"
      }
    ]
  },
  "spec": {
    "ports": [
      {
        "name": "http",
        "protocol": "TCP",
        "port": 80,
        "targetPort": 80,
        "nodePort": 30570
      },
      {
        "name": "https",
        "protocol": "TCP",
        "port": 443,
        "targetPort": 443,
        "nodePort": 30790
      }
    ],
    "selector": {
      "app": "webgqa7o3"
    },
    "clusterIP": "10.105.141.128",
    "clusterIPs": [
      "10.105.141.128"
    ],
    "type": "LoadBalancer",
    "sessionAffinity": "None",
    "externalTrafficPolicy": "Cluster",
    "ipFamilies": [
      "IPv4"
    ],
    "ipFamilyPolicy": "SingleStack",
    "allocateLoadBalancerNodePorts": true,
    "internalTrafficPolicy": "Cluster"
  },
  "status": {
    "loadBalancer": {}
  }
}
LAST SEEN                      TYPE    REASON                OBJECT                 MESSAGE
2021-11-19 00:13:40 +0000 UTC  Normal  EnsuringLoadBalancer  service/webgqa7o3-ilb  Ensuring load balancer

Expected
    <bool>: false
to be true
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:214
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Show 22 Skipped Tests

Error lines from build-log.txt

... skipping 426 lines ...
  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/azure_test.go:579

INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" started at Fri, 19 Nov 2021 00:05:28 UTC on Ginkgo node 3 of 3
STEP: Creating namespace "capz-e2e-f0rt62" for hosting the cluster
Nov 19 00:05:28.078: INFO: starting to create namespace for hosting the "capz-e2e-f0rt62" test spec
2021/11/19 00:05:28 failed trying to get namespace (capz-e2e-f0rt62):namespaces "capz-e2e-f0rt62" not found
INFO: Creating namespace capz-e2e-f0rt62
INFO: Creating event watcher for namespace "capz-e2e-f0rt62"
Nov 19 00:05:28.142: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-f0rt62-win-vmss
INFO: Creating the workload cluster with name "capz-e2e-f0rt62-win-vmss" using the "machine-pool-windows" template (Kubernetes v1.22.1, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 129 lines ...
STEP: Fetching activity logs took 981.715311ms
STEP: Dumping all the Cluster API resources in the "capz-e2e-f0rt62" namespace
STEP: Deleting all clusters in the capz-e2e-f0rt62 namespace
STEP: Deleting cluster capz-e2e-f0rt62-win-vmss
INFO: Waiting for the Cluster capz-e2e-f0rt62/capz-e2e-f0rt62-win-vmss to be deleted
STEP: Waiting for cluster capz-e2e-f0rt62-win-vmss to be deleted
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-x6xfl, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-f0rt62-win-vmss-control-plane-lqszh, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-d2htb, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-28l47, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-kt76m, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-lnvxx, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-qj2sh, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-f0rt62-win-vmss-control-plane-lqszh, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-2zg9d, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-f0rt62-win-vmss-control-plane-lqszh, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-xmrrh, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-f0rt62-win-vmss-control-plane-lqszh, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-f0rt62
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
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 33m8s on Ginkgo node 3 of 3

... skipping 10 lines ...
  With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:532

INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" started at Fri, 19 Nov 2021 00:05:28 UTC on Ginkgo node 1 of 3
STEP: Creating namespace "capz-e2e-tpiodr" for hosting the cluster
Nov 19 00:05:28.062: INFO: starting to create namespace for hosting the "capz-e2e-tpiodr" test spec
2021/11/19 00:05:28 failed trying to get namespace (capz-e2e-tpiodr):namespaces "capz-e2e-tpiodr" not found
INFO: Creating namespace capz-e2e-tpiodr
INFO: Creating event watcher for namespace "capz-e2e-tpiodr"
Nov 19 00:05:28.107: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-tpiodr-win-ha
INFO: Creating the workload cluster with name "capz-e2e-tpiodr-win-ha" using the "windows" template (Kubernetes v1.22.1, 3 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 94 lines ...
STEP: Fetching activity logs took 1.4316216s
STEP: Dumping all the Cluster API resources in the "capz-e2e-tpiodr" namespace
STEP: Deleting all clusters in the capz-e2e-tpiodr namespace
STEP: Deleting cluster capz-e2e-tpiodr-win-ha
INFO: Waiting for the Cluster capz-e2e-tpiodr/capz-e2e-tpiodr-win-ha to be deleted
STEP: Waiting for cluster capz-e2e-tpiodr-win-ha to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-tpiodr-win-ha-control-plane-8t4z2, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-tpiodr-win-ha-control-plane-8t4z2, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-b4z6f, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-6z2fh, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-tpiodr-win-ha-control-plane-dbnl6, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-tpiodr-win-ha-control-plane-8t4z2, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-tpiodr-win-ha-control-plane-sbzmv, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-tpiodr-win-ha-control-plane-sbzmv, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-tpiodr-win-ha-control-plane-dbnl6, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-tpiodr-win-ha-control-plane-dbnl6, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-nx5hm, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-zmdzb, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-tpiodr-win-ha-control-plane-8t4z2, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-458cr, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-hzgwj, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-mltbl, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-pnfr2, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-tpiodr-win-ha-control-plane-sbzmv, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-99nzw, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5txbs, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-tpiodr-win-ha-control-plane-dbnl6, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-9mblk, container kube-flannel: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-48xtx, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-gm2l4, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-tpiodr-win-ha-control-plane-sbzmv, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-f9jwj, container kube-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-tpiodr
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
INFO: "With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node" ran for 34m27s on Ginkgo node 1 of 3

... skipping 4 lines ...
  Creating a Windows Enabled cluster with dockershim
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:530
    With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node [It]
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:532

    Timed out after 300.060s.
    Service default/webgqa7o3-ilb failed
    Service:
    {
      "metadata": {
        "name": "webgqa7o3-ilb",
        "namespace": "default",
        "uid": "9bf482de-f38c-4248-813f-10329e9f4b34",
... skipping 156 lines ...
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] Workload cluster creation Creating a Windows Enabled cluster with dockershim [It] With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:214

Ran 2 of 24 Specs in 2194.242 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 22 Skipped


Ginkgo ran 1 suite in 37m58.219571929s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc
make[1]: *** [Makefile:173: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:181: 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 ...