This job view page is being replaced by Spyglass soon. Check out the new job view.
PRCecileRobertMichon: Switch flavor and test templates to external cloud-provider
ResultFAILURE
Tests 1 failed / 20 succeeded
Started2023-01-27 00:30
Elapsed45m50s
Revision65957cf999e471834699d80bd2d98beb33399003
Refs 3105

Test Failures

capz-e2e [It] Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers 33m29s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sRunning\sthe\sCluster\sAPI\sE2E\stests\sAPI\sVersion\sUpgrade\supgrade\sfrom\sv1alpha4\sto\sv1beta1\,\sand\sscale\sworkload\sclusters\screated\sin\sv1alpha4\sShould\screate\sa\smanagement\scluster\sand\sthen\supgrade\sall\sthe\sproviders$'
[FAILED] Timed out after 1200.000s.
No Control Plane machines came into existence. 
Expected
    <bool>: false
to be true
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:07:27.585

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

Filter through log files | View test history on testgrid

Show 20 Passed Tests
Show 23 Skipped Tests

Error lines from build-log.txt

... skipping 642 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/e2e_suite_test.go:116
------------------------------
[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] [2009.082 seconds]
Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 [It] Should create a management cluster and then upgrade all the providers
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/e2e/clusterctl_upgrade.go:209

  Captured StdOut/StdErr Output >>
  cluster.cluster.x-k8s.io/clusterctl-upgrade-3mtzz4 created
  azurecluster.infrastructure.cluster.x-k8s.io/clusterctl-upgrade-3mtzz4 created
... skipping 13 lines ...
  configmap/cni-clusterctl-upgrade-3mtzz4-calico-windows created
  configmap/csi-proxy-addon created
  configmap/containerd-logger-clusterctl-upgrade-3mtzz4 created

  felixconfiguration.crd.projectcalico.org/default configured

  Failed to get logs for Machine clusterctl-upgrade-3mtzz4-md-0-54768d5f75-mkjkz, Cluster clusterctl-upgrade-jiigwq/clusterctl-upgrade-3mtzz4: [dialing from control plane to target node at clusterctl-upgrade-3mtzz4-md-0-n6q8r: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: failed to get boot diagnostics data: compute.VirtualMachinesClient#RetrieveBootDiagnosticsData: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Compute/virtualMachines/clusterctl-upgrade-3mtzz4-md-0-n6q8r' under resource group 'clusterctl-upgrade-3mtzz4' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"]
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Fri, 27 Jan 2023 00:41:51 UTC on Ginkgo node 1 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec @ 01/27/23 00:41:51.579
  INFO: Creating namespace clusterctl-upgrade-jiigwq
... skipping 61 lines ...
  STEP: Waiting for Ready cloud-controller-manager deployment pods @ 01/27/23 00:47:26.99
  STEP: waiting for deployment kube-system/cloud-controller-manager to be available @ 01/27/23 00:47:27.508
  Jan 27 00:47:27.508: INFO: starting to wait for deployment to become available
  Jan 27 00:47:27.567: INFO: Deployment kube-system/cloud-controller-manager is now available, took 59.36365ms
  INFO: Waiting for the first control plane machine managed by clusterctl-upgrade-jiigwq/clusterctl-upgrade-3mtzz4-control-plane to be provisioned
  STEP: Waiting for one control plane node to exist @ 01/27/23 00:47:27.585
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:07:27.585
  STEP: Dumping logs from the "clusterctl-upgrade-3mtzz4" workload cluster @ 01/27/23 01:07:27.585
  Jan 27 01:07:27.585: INFO: Dumping workload cluster clusterctl-upgrade-jiigwq/clusterctl-upgrade-3mtzz4 logs
  Jan 27 01:07:27.629: INFO: Collecting logs for Linux node clusterctl-upgrade-3mtzz4-control-plane-bbpl9 in cluster clusterctl-upgrade-3mtzz4 in namespace clusterctl-upgrade-jiigwq

  Jan 27 01:07:41.174: INFO: Collecting boot logs for AzureMachine clusterctl-upgrade-3mtzz4-control-plane-bbpl9

... skipping 7 lines ...
  Jan 27 01:08:47.896: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-6c99cd59c7-dc6w2, container calico-apiserver
  Jan 27 01:08:47.896: INFO: Describing Pod calico-apiserver/calico-apiserver-6c99cd59c7-dc6w2
  Jan 27 01:08:48.014: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-8fdfc695-cqccp, container calico-kube-controllers
  Jan 27 01:08:48.014: INFO: Describing Pod calico-system/calico-kube-controllers-8fdfc695-cqccp
  Jan 27 01:08:48.149: INFO: Creating log watcher for controller calico-system/calico-node-5krs6, container calico-node
  Jan 27 01:08:48.150: INFO: Describing Pod calico-system/calico-node-5krs6
  Jan 27 01:08:48.211: INFO: Error starting logs stream for pod calico-system/calico-node-5krs6, container calico-node: pods "clusterctl-upgrade-3mtzz4-md-0-n6q8r" not found
  Jan 27 01:08:48.275: INFO: Creating log watcher for controller calico-system/calico-node-sbv5r, container calico-node
  Jan 27 01:08:48.275: INFO: Describing Pod calico-system/calico-node-sbv5r
  Jan 27 01:08:48.409: INFO: Creating log watcher for controller calico-system/calico-typha-777988cb5b-stdx2, container calico-typha
  Jan 27 01:08:48.409: INFO: Describing Pod calico-system/calico-typha-777988cb5b-stdx2
  Jan 27 01:08:48.525: INFO: Describing Pod calico-system/csi-node-driver-gtl52
  Jan 27 01:08:48.525: INFO: Creating log watcher for controller calico-system/csi-node-driver-gtl52, container calico-csi
  Jan 27 01:08:48.526: INFO: Creating log watcher for controller calico-system/csi-node-driver-gtl52, container csi-node-driver-registrar
  Jan 27 01:08:48.921: INFO: Describing Pod calico-system/csi-node-driver-srlfc
  Jan 27 01:08:48.921: INFO: Creating log watcher for controller calico-system/csi-node-driver-srlfc, container calico-csi
  Jan 27 01:08:48.921: INFO: Creating log watcher for controller calico-system/csi-node-driver-srlfc, container csi-node-driver-registrar
  Jan 27 01:08:48.980: INFO: Error starting logs stream for pod calico-system/csi-node-driver-srlfc, container csi-node-driver-registrar: pods "clusterctl-upgrade-3mtzz4-md-0-n6q8r" not found
  Jan 27 01:08:48.980: INFO: Error starting logs stream for pod calico-system/csi-node-driver-srlfc, container calico-csi: pods "clusterctl-upgrade-3mtzz4-md-0-n6q8r" not found
  Jan 27 01:08:49.319: INFO: Creating log watcher for controller kube-system/cloud-controller-manager-6dcd4c6dd6-fhtvj, container cloud-controller-manager
  Jan 27 01:08:49.319: INFO: Describing Pod kube-system/cloud-controller-manager-6dcd4c6dd6-fhtvj
  Jan 27 01:08:49.719: INFO: Creating log watcher for controller kube-system/cloud-node-manager-4tpkh, container cloud-node-manager
  Jan 27 01:08:49.719: INFO: Describing Pod kube-system/cloud-node-manager-4tpkh
  Jan 27 01:08:50.119: INFO: Creating log watcher for controller kube-system/cloud-node-manager-md6np, container cloud-node-manager
  Jan 27 01:08:50.119: INFO: Describing Pod kube-system/cloud-node-manager-md6np
  Jan 27 01:08:50.177: INFO: Error starting logs stream for pod kube-system/cloud-node-manager-md6np, container cloud-node-manager: pods "clusterctl-upgrade-3mtzz4-md-0-n6q8r" not found
  Jan 27 01:08:50.520: INFO: Creating log watcher for controller kube-system/coredns-78fcd69978-5cnd6, container coredns
  Jan 27 01:08:50.520: INFO: Describing Pod kube-system/coredns-78fcd69978-5cnd6
  Jan 27 01:08:50.919: INFO: Creating log watcher for controller kube-system/coredns-78fcd69978-fh95q, container coredns
  Jan 27 01:08:50.919: INFO: Describing Pod kube-system/coredns-78fcd69978-fh95q
  Jan 27 01:08:51.319: INFO: Describing Pod kube-system/etcd-clusterctl-upgrade-3mtzz4-control-plane-bbpl9
  Jan 27 01:08:51.319: INFO: Creating log watcher for controller kube-system/etcd-clusterctl-upgrade-3mtzz4-control-plane-bbpl9, container etcd
  Jan 27 01:08:51.719: INFO: Creating log watcher for controller kube-system/kube-apiserver-clusterctl-upgrade-3mtzz4-control-plane-bbpl9, container kube-apiserver
  Jan 27 01:08:51.719: INFO: Describing Pod kube-system/kube-apiserver-clusterctl-upgrade-3mtzz4-control-plane-bbpl9
  Jan 27 01:08:52.117: INFO: Creating log watcher for controller kube-system/kube-controller-manager-clusterctl-upgrade-3mtzz4-control-plane-bbpl9, container kube-controller-manager
  Jan 27 01:08:52.117: INFO: Describing Pod kube-system/kube-controller-manager-clusterctl-upgrade-3mtzz4-control-plane-bbpl9
  Jan 27 01:08:52.519: INFO: Describing Pod kube-system/kube-proxy-jf7kr
  Jan 27 01:08:52.519: INFO: Creating log watcher for controller kube-system/kube-proxy-jf7kr, container kube-proxy
  Jan 27 01:08:52.581: INFO: Error starting logs stream for pod kube-system/kube-proxy-jf7kr, container kube-proxy: pods "clusterctl-upgrade-3mtzz4-md-0-n6q8r" not found
  Jan 27 01:08:52.923: INFO: Creating log watcher for controller kube-system/kube-proxy-xv6qn, container kube-proxy
  Jan 27 01:08:52.923: INFO: Describing Pod kube-system/kube-proxy-xv6qn
  Jan 27 01:08:53.318: INFO: Creating log watcher for controller kube-system/kube-scheduler-clusterctl-upgrade-3mtzz4-control-plane-bbpl9, container kube-scheduler
  Jan 27 01:08:53.318: INFO: Describing Pod kube-system/kube-scheduler-clusterctl-upgrade-3mtzz4-control-plane-bbpl9
  Jan 27 01:08:53.718: INFO: Fetching kube-system pod logs took 6.654387142s
  Jan 27 01:08:53.718: INFO: Dumping workload cluster clusterctl-upgrade-jiigwq/clusterctl-upgrade-3mtzz4 Azure activity log
... skipping 4 lines ...
  STEP: Deleting cluster clusterctl-upgrade-jiigwq/clusterctl-upgrade-3mtzz4 @ 01/27/23 01:09:22.622
  STEP: Deleting cluster clusterctl-upgrade-3mtzz4 @ 01/27/23 01:09:22.646
  INFO: Waiting for the Cluster clusterctl-upgrade-jiigwq/clusterctl-upgrade-3mtzz4 to be deleted
  STEP: Waiting for cluster clusterctl-upgrade-3mtzz4 to be deleted @ 01/27/23 01:09:22.663
  STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec @ 01/27/23 01:15:12.843
  INFO: Deleting namespace clusterctl-upgrade-jiigwq
  Jan 27 01:15:12.861: INFO: FAILED!
  Jan 27 01:15:12.861: INFO: Cleaning up after "Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers" spec
  STEP: Redacting sensitive information from logs @ 01/27/23 01:15:12.861
  INFO: "Should create a management cluster and then upgrade all the providers" started at Fri, 27 Jan 2023 01:15:20 UTC on Ginkgo node 1 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  << Timeline

  [FAILED] Timed out after 1200.000s.
  No Control Plane machines came into existence. 
  Expected
      <bool>: false
  to be true
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:07:27.585

... skipping 22 lines ...
[ReportAfterSuite] PASSED [0.013 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 [It] Should create a management cluster and then upgrade all the providers
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154

Ran 1 of 24 Specs in 2158.829 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 23 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:426
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:282
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:285
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:426

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

--- FAIL: TestE2E (2158.83s)
FAIL


Ginkgo ran 1 suite in 39m47.79172493s

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 ...