This job view page is being replaced by Spyglass soon. Check out the new job view.
PRinvidian: Add Flatcar Container Linux template
ResultFAILURE
Tests 1 failed / 26 succeeded
Started2023-01-23 18:08
Elapsed1h20m
Revision8dad8f074688f1790b08a185ed0a33a6bcf3fd4b
Refs 2890

Test Failures

capz-e2e [It] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node 1h7m

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\sdual\-stack\scluster\s\[OPTIONAL\]\sWith\sdual\-stack\sworker\snode$'
[FAILED] Timed out after 1800.000s.
Expected success, but got an error:
    <*errors.withStack | 0xc000984b70>: {
        error: <*errors.withMessage | 0xc000deaf80>{
            cause: <*url.Error | 0xc0018dd620>{
                Op: "Get",
                URL: "https://capz-e2e-mp1gwi-dual-stack-465edb8d.canadacentral.cloudapp.azure.com:6443/openapi/v2?timeout=32s",
                Err: <*http.httpError | 0xc001861800>{
                    err: "net/http: request canceled (Client.Timeout exceeded while awaiting headers)",
                    timeout: true,
                },
            },
            msg: "unable to build kubernetes objects from release manifest",
        },
        stack: [0x351553c, 0x3567b18, 0x1503085, 0x150257c, 0x192015a, 0x1921062, 0x191e80d, 0x356779b, 0x3557f05, 0x355aef7, 0x2fa4370, 0x356adc5, 0x18fb33b, 0x190f918, 0x1490741],
    }
    unable to build kubernetes objects from release manifest: Get "https://capz-e2e-mp1gwi-dual-stack-465edb8d.canadacentral.cloudapp.azure.com:6443/openapi/v2?timeout=32s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:988 @ 01/23/23 19:04:51.921

				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid

Show 26 Passed Tests
Show 20 Skipped Tests

Error lines from build-log.txt

... skipping 627 lines ...
------------------------------
• [898.368 seconds]
Workload cluster creation Creating a Flatcar cluster [OPTIONAL] With Flatcar control-plane and worker nodes
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:319

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-c7a58r):namespaces "capz-e2e-c7a58r" not found
  cluster.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-c7a58r-flatcar-md-0 created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created

  felixconfiguration.crd.projectcalico.org/default created

  Failed to get logs for Machine capz-e2e-c7a58r-flatcar-control-plane-jj69z, Cluster capz-e2e-c7a58r/capz-e2e-c7a58r-flatcar: [dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:56396->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:56410->20.175.140.85:22: read: connection reset by peer]
  Failed to get logs for Machine capz-e2e-c7a58r-flatcar-md-0-54554b9f79-ppfsr, Cluster capz-e2e-c7a58r/capz-e2e-c7a58r-flatcar: [dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49840->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49832->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49842->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49838->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49836->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49834->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49846->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49844->20.175.140.85:22: read: connection reset by peer, dialing public load balancer at capz-e2e-c7a58r-flatcar-c3d299d9.canadacentral.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.45.236:49848->20.175.140.85:22: read: connection reset by peer]
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 18:20:39 UTC on Ginkgo node 1 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-c7a58r" for hosting the cluster @ 01/23/23 18:20:39.547
  Jan 23 18:20:39.547: INFO: starting to create namespace for hosting the "capz-e2e-c7a58r" test spec
... skipping 153 lines ...
------------------------------
• [945.368 seconds]
Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:571

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-15p9op):namespaces "capz-e2e-15p9op" not found
  cluster.cluster.x-k8s.io/capz-e2e-15p9op-flex created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-15p9op-flex created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-15p9op-flex-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-15p9op-flex-control-plane created
  machinepool.cluster.x-k8s.io/capz-e2e-15p9op-flex-mp-0 created
  azuremachinepool.infrastructure.cluster.x-k8s.io/capz-e2e-15p9op-flex-mp-0 created
  kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-15p9op-flex-mp-0 created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created

  felixconfiguration.crd.projectcalico.org/default configured

  W0123 18:29:34.344974   37355 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
  2023/01/23 18:30:14 [DEBUG] GET http://20.175.154.161
  2023/01/23 18:30:44 [ERR] GET http://20.175.154.161 request failed: Get "http://20.175.154.161": dial tcp 20.175.154.161:80: i/o timeout
  2023/01/23 18:30:44 [DEBUG] GET http://20.175.154.161: retrying in 1s (4 left)
  W0123 18:31:47.154173   37355 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
  Failed to get logs for MachinePool capz-e2e-15p9op-flex-mp-0, Cluster capz-e2e-15p9op/capz-e2e-15p9op-flex: Unable to collect VMSS Boot Diagnostic logs: failed to parse resource id: parsing failed for /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-e2e-15p9op-flex/providers/Microsoft.Compute. Invalid resource Id format
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 18:20:39 UTC on Ginkgo node 7 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-15p9op" for hosting the cluster @ 01/23/23 18:20:39.553
  Jan 23 18:20:39.553: INFO: starting to create namespace for hosting the "capz-e2e-15p9op" test spec
... skipping 229 lines ...
------------------------------
• [1285.600 seconds]
Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:635

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-m8gazm):namespaces "capz-e2e-m8gazm" not found
  cluster.cluster.x-k8s.io/capz-e2e-m8gazm-oot created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-m8gazm-oot created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-m8gazm-oot-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-m8gazm-oot-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-m8gazm-oot-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-m8gazm-oot-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-m8gazm-oot-md-0 created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created

  felixconfiguration.crd.projectcalico.org/default configured

  W0123 18:31:04.520857   37363 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
  2023/01/23 18:32:25 [DEBUG] GET http://20.175.157.154
  2023/01/23 18:32:55 [ERR] GET http://20.175.157.154 request failed: Get "http://20.175.157.154": dial tcp 20.175.157.154:80: i/o timeout
  2023/01/23 18:32:55 [DEBUG] GET http://20.175.157.154: retrying in 1s (4 left)
  W0123 18:34:27.583537   37363 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 18:20:39 UTC on Ginkgo node 9 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
... skipping 273 lines ...
------------------------------
• [1408.528 seconds]
Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:884

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-wf6dr1):namespaces "capz-e2e-wf6dr1" not found
  clusterclass.cluster.x-k8s.io/ci-default created
  kubeadmcontrolplanetemplate.controlplane.cluster.x-k8s.io/ci-default-kubeadm-control-plane created
  azureclustertemplate.infrastructure.cluster.x-k8s.io/ci-default-azure-cluster created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-control-plane created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/ci-default-worker created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-worker created
... skipping 5 lines ...
  clusterresourceset.addons.cluster.x-k8s.io/csi-proxy created
  configmap/cni-capz-e2e-wf6dr1-cc-calico-windows created
  configmap/csi-proxy-addon created

  felixconfiguration.crd.projectcalico.org/default configured

  Failed to get logs for Machine capz-e2e-wf6dr1-cc-7prvk-mx2xd, Cluster capz-e2e-wf6dr1/capz-e2e-wf6dr1-cc: dialing public load balancer at capz-e2e-wf6dr1-cc-d93c95bd.canadacentral.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  Failed to get logs for Machine capz-e2e-wf6dr1-cc-md-0-wvv5g-778f8b7647-fhqkz, Cluster capz-e2e-wf6dr1/capz-e2e-wf6dr1-cc: dialing public load balancer at capz-e2e-wf6dr1-cc-d93c95bd.canadacentral.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  Failed to get logs for Machine capz-e2e-wf6dr1-cc-md-win-t6xmm-79d545999-cglkf, Cluster capz-e2e-wf6dr1/capz-e2e-wf6dr1-cc: dialing public load balancer at capz-e2e-wf6dr1-cc-d93c95bd.canadacentral.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 18:20:39 UTC on Ginkgo node 8 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-wf6dr1" for hosting the cluster @ 01/23/23 18:20:39.555
  Jan 23 18:20:39.555: INFO: starting to create namespace for hosting the "capz-e2e-wf6dr1" test spec
... skipping 186 lines ...
  Jan 23 18:37:51.609: INFO: Collecting events for Pod kube-system/kube-apiserver-capz-e2e-wf6dr1-cc-control-plane-csps9-ccvst
  Jan 23 18:37:51.609: INFO: Collecting events for Pod kube-system/kube-proxy-r9kz8
  Jan 23 18:37:51.666: INFO: Fetching kube-system pod logs took 582.405268ms
  Jan 23 18:37:51.666: INFO: Dumping workload cluster capz-e2e-wf6dr1/capz-e2e-wf6dr1-cc Azure activity log
  Jan 23 18:37:51.666: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-xxdks, container tigera-operator
  Jan 23 18:37:51.667: INFO: Collecting events for Pod tigera-operator/tigera-operator-65d6bf4d4f-xxdks
  Jan 23 18:37:51.691: INFO: Error fetching activity logs for cluster capz-e2e-wf6dr1-cc in namespace capz-e2e-wf6dr1.  Not able to find the AzureManagedControlPlane on the management cluster: azuremanagedcontrolplanes.infrastructure.cluster.x-k8s.io "capz-e2e-wf6dr1-cc" not found
  Jan 23 18:37:51.692: INFO: Fetching activity logs took 25.93236ms
  Jan 23 18:37:51.692: INFO: Dumping all the Cluster API resources in the "capz-e2e-wf6dr1" namespace
  Jan 23 18:37:52.188: INFO: Deleting all clusters in the capz-e2e-wf6dr1 namespace
  STEP: Deleting cluster capz-e2e-wf6dr1-cc @ 01/23/23 18:37:52.206
  INFO: Waiting for the Cluster capz-e2e-wf6dr1/capz-e2e-wf6dr1-cc to be deleted
  STEP: Waiting for cluster capz-e2e-wf6dr1-cc to be deleted @ 01/23/23 18:37:52.225
... skipping 10 lines ...
------------------------------
• [1629.239 seconds]
Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:504

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-qx4bh3):namespaces "capz-e2e-qx4bh3" not found
  cluster.cluster.x-k8s.io/capz-e2e-qx4bh3-gpu serverside-applied
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-qx4bh3-gpu serverside-applied
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-qx4bh3-gpu-control-plane serverside-applied
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-qx4bh3-gpu-control-plane serverside-applied
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp serverside-applied
  machinedeployment.cluster.x-k8s.io/capz-e2e-qx4bh3-gpu-md-0 serverside-applied
... skipping 243 lines ...
------------------------------
• [2974.798 seconds]
Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:154

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-aevbx6):namespaces "capz-e2e-aevbx6" not found
  cluster.cluster.x-k8s.io/capz-e2e-aevbx6-public-custom-vnet created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-aevbx6-public-custom-vnet created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-aevbx6-public-custom-vnet-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-aevbx6-public-custom-vnet-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-aevbx6-public-custom-vnet-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-aevbx6-public-custom-vnet-md-0 created
... skipping 250 lines ...
  Jan 23 19:04:53.357: INFO: Collecting events for Pod kube-system/etcd-capz-e2e-aevbx6-public-custom-vnet-control-plane-t7d6s
  Jan 23 19:04:53.357: INFO: Creating log watcher for controller kube-system/kube-proxy-z724d, container kube-proxy
  Jan 23 19:04:53.385: INFO: Fetching kube-system pod logs took 533.185247ms
  Jan 23 19:04:53.385: INFO: Dumping workload cluster capz-e2e-aevbx6/capz-e2e-aevbx6-public-custom-vnet Azure activity log
  Jan 23 19:04:53.385: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-p5kjb, container tigera-operator
  Jan 23 19:04:53.385: INFO: Collecting events for Pod tigera-operator/tigera-operator-65d6bf4d4f-p5kjb
  Jan 23 19:05:00.197: INFO: Got error while iterating over activity logs for resource group capz-e2e-aevbx6-public-custom-vnet: insights.ActivityLogsClient#listNextResults: Failure responding to next results request: StatusCode=404 -- Original Error: autorest/azure: error response cannot be parsed: {"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\r\n<html xmlns=\"http://www.w3.org/1999/xhtml\">\r\n<head>\r\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=iso-8859-1\"/>\r\n<title>404 - File or directory not found.</title>\r\n<style type=\"text/css\">\r\n<!--\r\nbody{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}\r\nfieldset{padding:0 15px 10px 15px;} \r\nh1{font-size:2.4em;margin:0;color:#FFF;}\r\nh2{font-si" '\x00' '\x00'} error: invalid character '<' looking for beginning of value
  Jan 23 19:05:00.197: INFO: Fetching activity logs took 6.811731513s
  Jan 23 19:05:00.197: INFO: Dumping all the Cluster API resources in the "capz-e2e-aevbx6" namespace
  Jan 23 19:05:00.562: INFO: Deleting all clusters in the capz-e2e-aevbx6 namespace
  STEP: Deleting cluster capz-e2e-aevbx6-public-custom-vnet @ 01/23/23 19:05:00.582
  INFO: Waiting for the Cluster capz-e2e-aevbx6/capz-e2e-aevbx6-public-custom-vnet to be deleted
  STEP: Waiting for cluster capz-e2e-aevbx6-public-custom-vnet to be deleted @ 01/23/23 19:05:00.595
  INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-768b7b88f9-cxk2t, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-8588769979-zqjxh, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-8ddf45bf4-dt4d9, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-66576dfdb7-bhjcb, container manager: http2: client connection lost
  Jan 23 19:07:50.712: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec
  INFO: Deleting namespace capz-e2e-aevbx6
  Jan 23 19:07:50.737: INFO: Running additional cleanup for the "create-workload-cluster" test spec
  Jan 23 19:07:50.737: INFO: deleting an existing virtual network "custom-vnet"
  Jan 23 19:08:01.305: INFO: deleting an existing route table "node-routetable"
  Jan 23 19:08:03.808: INFO: deleting an existing network security group "node-nsg"
... skipping 6 lines ...
  << Timeline
------------------------------
[SynchronizedAfterSuite] PASSED [0.000 seconds]
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/e2e_suite_test.go:116
------------------------------
• [FAILED] [4023.250 seconds]
Workload cluster creation Creating a dual-stack cluster [OPTIONAL] [It] With dual-stack worker node
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:808

  Captured StdOut/StdErr Output >>
  2023/01/23 18:20:39 failed trying to get namespace (capz-e2e-mp1gwi):namespaces "capz-e2e-mp1gwi" not found
  cluster.cluster.x-k8s.io/capz-e2e-mp1gwi-dual-stack created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-mp1gwi-dual-stack created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-mp1gwi-dual-stack-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-mp1gwi-dual-stack-control-plane created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created
  machinedeployment.cluster.x-k8s.io/capz-e2e-mp1gwi-dual-stack-md-0 created
... skipping 1383 lines ...
  Jan 23 19:04:35.401: INFO: creating 1 resource(s)
  Jan 23 19:04:36.373: INFO: CRD imagesets.operator.tigera.io is already present. Skipping.
  Jan 23 19:04:36.474: INFO: creating 1 resource(s)
  Jan 23 19:04:45.069: INFO: CRD installations.operator.tigera.io is already present. Skipping.
  Jan 23 19:04:45.076: INFO: creating 1 resource(s)
  Jan 23 19:04:45.719: INFO: CRD tigerastatuses.operator.tigera.io is already present. Skipping.
  [FAILED] in [It] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:988 @ 01/23/23 19:04:51.921
  Jan 23 19:04:51.921: INFO: FAILED!
  Jan 23 19:04:51.921: INFO: Cleaning up after "Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node" spec
  STEP: Dumping logs from the "capz-e2e-mp1gwi-dual-stack" workload cluster @ 01/23/23 19:04:51.921
  Jan 23 19:04:51.921: INFO: Dumping workload cluster capz-e2e-mp1gwi/capz-e2e-mp1gwi-dual-stack logs
  Jan 23 19:04:52.014: INFO: Collecting logs for Linux node capz-e2e-mp1gwi-dual-stack-control-plane-7qdsv in cluster capz-e2e-mp1gwi-dual-stack in namespace capz-e2e-mp1gwi

  Jan 23 19:11:06.861: INFO: Collecting boot logs for AzureMachine capz-e2e-mp1gwi-dual-stack-control-plane-7qdsv
... skipping 33 lines ...
  INFO: Deleting namespace capz-e2e-mp1gwi
  Jan 23 19:26:06.475: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster"
  STEP: Redacting sensitive information from logs @ 01/23/23 19:26:07.061
  INFO: "With dual-stack worker node" started at Mon, 23 Jan 2023 19:27:42 UTC on Ginkgo node 6 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  << Timeline

  [FAILED] Timed out after 1800.000s.
  Expected success, but got an error:
      <*errors.withStack | 0xc000984b70>: {
          error: <*errors.withMessage | 0xc000deaf80>{
              cause: <*url.Error | 0xc0018dd620>{
                  Op: "Get",
                  URL: "https://capz-e2e-mp1gwi-dual-stack-465edb8d.canadacentral.cloudapp.azure.com:6443/openapi/v2?timeout=32s",
                  Err: <*http.httpError | 0xc001861800>{
                      err: "net/http: request canceled (Client.Timeout exceeded while awaiting headers)",
                      timeout: true,
                  },
... skipping 32 lines ...
[ReportAfterSuite] PASSED [0.019 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] [It] With dual-stack worker node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:988

Ran 7 of 27 Specs in 4195.487 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 20 Skipped

You're using deprecated Ginkgo functionality:
=============================================
  CurrentGinkgoTestDescription() is deprecated in Ginkgo V2.  Use CurrentSpecReport() instead.
  Learn more at: https://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:429
... skipping 43 lines ...
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:284
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:429

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.7.0

--- FAIL: TestE2E (4193.94s)
FAIL

You're using deprecated Ginkgo functionality:
=============================================
  CurrentGinkgoTestDescription() is deprecated in Ginkgo V2.  Use CurrentSpecReport() instead.
  Learn more at: https://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:429
... skipping 34 lines ...

PASS


Ginkgo ran 1 suite in 1h13m33.351544945s

Test Suite Failed
make[1]: *** [Makefile:654: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:663: 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 ...