This job view page is being replaced by Spyglass soon. Check out the new job view.
PRffromani: node: create podresources endpoint also on windows
ResultFAILURE
Tests 1 failed / 2 succeeded
Started2023-02-02 15:53
Elapsed1h24m
Revision98b02907c75474107b508e7d2110713304598cec
Refs 115133

Test Failures


capz-e2e [It] Conformance Tests conformance-tests 46m40s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'
[FAILED] Timed out after 1500.001s.
Timed out waiting for 2 nodes to be created for MachineDeployment capz-conf-8a1pbc/capz-conf-8a1pbc-md-win
Expected
    <int>: 0
to equal
    <int>: 2
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 02/02/23 17:05:08.115

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

Filter through log files | View test history on testgrid


Show 2 Passed Tests

Show 23 Skipped Tests

Error lines from build-log.txt

... skipping 137 lines ...
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   138  100   138    0     0   4600      0 --:--:-- --:--:-- --:--:--  4600

100    34  100    34    0     0    361      0 --:--:-- --:--:-- --:--:--   361
using CI_VERSION=v1.27.0-alpha.1.201+fc7b25cf720b60
using KUBERNETES_VERSION=v1.27.0-alpha.1.201+fc7b25cf720b60
using IMAGE_TAG=v1.27.0-alpha.1.207_626fcee09f1f4e
Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.1.207_626fcee09f1f4e not found: manifest unknown: manifest tagged by "v1.27.0-alpha.1.207_626fcee09f1f4e" is not found
Building Kubernetes
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [0202 15:54:56] Verifying Prerequisites....
+++ [0202 15:54:57] Building Docker image kube-build:build-6af54e2a18-5-v1.26.0-go1.19.5-bullseye.0
+++ [0202 15:57:52] Creating data container kube-build-data-6af54e2a18-5-v1.26.0-go1.19.5-bullseye.0
+++ [0202 15:58:12] Syncing sources to container
... skipping 766 lines ...
------------------------------
Conformance Tests conformance-tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100
  INFO: Cluster name is capz-conf-8a1pbc
  STEP: Creating namespace "capz-conf-8a1pbc" for hosting the cluster @ 02/02/23 16:31:16.391
  Feb  2 16:31:16.391: INFO: starting to create namespace for hosting the "capz-conf-8a1pbc" test spec
2023/02/02 16:31:16 failed trying to get namespace (capz-conf-8a1pbc):namespaces "capz-conf-8a1pbc" not found
  INFO: Creating namespace capz-conf-8a1pbc
  INFO: Creating event watcher for namespace "capz-conf-8a1pbc"
  conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 02/02/23 16:31:16.443
    conformance-tests
    Name | N | Min | Median | Mean | StdDev | Max
  INFO: Creating the workload cluster with name "capz-conf-8a1pbc" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.1.201+fc7b25cf720b60, 1 control-plane machines, 0 worker machines)
... skipping 104 lines ...
  STEP: Waiting for the control plane to be ready @ 02/02/23 16:40:07.994
  STEP: Checking all the control plane machines are in the expected failure domains @ 02/02/23 16:40:08.009
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 02/02/23 16:40:08.065
  STEP: Checking all the machines controlled by capz-conf-8a1pbc-md-0 are in the "<None>" failure domain @ 02/02/23 16:40:08.089
  STEP: Waiting for the workload nodes to exist @ 02/02/23 16:40:08.113
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 02/02/23 17:05:08.115
  Feb  2 17:05:08.115: INFO: FAILED!
  Feb  2 17:05:08.115: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
  STEP: Dumping logs from the "capz-conf-8a1pbc" workload cluster @ 02/02/23 17:05:08.115
  Feb  2 17:05:08.116: INFO: Dumping workload cluster capz-conf-8a1pbc/capz-conf-8a1pbc logs
  Feb  2 17:05:08.198: INFO: Collecting logs for Linux node capz-conf-8a1pbc-control-plane-8vzk5 in cluster capz-conf-8a1pbc in namespace capz-conf-8a1pbc

  Feb  2 17:05:27.657: INFO: Collecting boot logs for AzureMachine capz-conf-8a1pbc-control-plane-8vzk5

  Feb  2 17:05:29.687: INFO: Collecting logs for Windows node capz-conf-cjgzb in cluster capz-conf-8a1pbc in namespace capz-conf-8a1pbc

  Feb  2 17:07:57.977: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-cjgzb to /logs/artifacts/clusters/capz-conf-8a1pbc/machines/capz-conf-8a1pbc-md-win-f8965994f-bw52g/crashdumps.tar
  Feb  2 17:08:01.398: INFO: Collecting boot logs for AzureMachine capz-conf-8a1pbc-md-win-cjgzb

Failed to get logs for Machine capz-conf-8a1pbc-md-win-f8965994f-bw52g, Cluster capz-conf-8a1pbc/capz-conf-8a1pbc: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1]
  Feb  2 17:08:03.089: INFO: Collecting logs for Windows node capz-conf-7zftj in cluster capz-conf-8a1pbc in namespace capz-conf-8a1pbc

  Feb  2 17:10:35.956: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-7zftj to /logs/artifacts/clusters/capz-conf-8a1pbc/machines/capz-conf-8a1pbc-md-win-f8965994f-zttcg/crashdumps.tar
  Feb  2 17:10:39.344: INFO: Collecting boot logs for AzureMachine capz-conf-8a1pbc-md-win-7zftj

Failed to get logs for Machine capz-conf-8a1pbc-md-win-f8965994f-zttcg, Cluster capz-conf-8a1pbc/capz-conf-8a1pbc: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1]
  Feb  2 17:10:40.744: INFO: Dumping workload cluster capz-conf-8a1pbc/capz-conf-8a1pbc kube-system pod logs
  Feb  2 17:10:42.000: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-5b8dd6dbd9-sb59d, container calico-apiserver
  Feb  2 17:10:42.000: INFO: Describing Pod calico-apiserver/calico-apiserver-5b8dd6dbd9-sb59d
  Feb  2 17:10:42.213: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-5b8dd6dbd9-xsqgs, container calico-apiserver
  Feb  2 17:10:42.213: INFO: Describing Pod calico-apiserver/calico-apiserver-5b8dd6dbd9-xsqgs
  Feb  2 17:10:42.431: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-6b7b9c649d-xfrlw, container calico-kube-controllers
... skipping 43 lines ...
  INFO: Waiting for the Cluster capz-conf-8a1pbc/capz-conf-8a1pbc to be deleted
  STEP: Waiting for cluster capz-conf-8a1pbc to be deleted @ 02/02/23 17:10:52.114
  Feb  2 17:17:42.360: INFO: Deleting namespace used for hosting the "conformance-tests" test spec
  INFO: Deleting namespace capz-conf-8a1pbc
  Feb  2 17:17:42.378: INFO: Checking if any resources are left over in Azure for spec "conformance-tests"
  STEP: Redacting sensitive information from logs @ 02/02/23 17:17:42.98
• [FAILED] [2800.750 seconds]
Conformance Tests [It] conformance-tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100

  [FAILED] Timed out after 1500.001s.
  Timed out waiting for 2 nodes to be created for MachineDeployment capz-conf-8a1pbc/capz-conf-8a1pbc-md-win
  Expected
      <int>: 0
  to equal
      <int>: 2
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 02/02/23 17:05:08.115
... skipping 18 lines ...
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.003 seconds]
------------------------------

Summarizing 1 Failure:
  [FAIL] Conformance Tests [It] conformance-tests
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131

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

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


Ginkgo ran 1 suite in 53m22.338446697s

Test Suite Failed
make[3]: *** [Makefile:654: test-e2e-run] Error 1
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: *** [Makefile:669: test-e2e-skip-push] Error 2
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[1]: *** [Makefile:685: test-conformance] Error 2
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:695: test-windows-upstream] Error 2
================ REDACTING LOGS ================
All sensitive variables are redacted
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 7 lines ...