ci-kubernetes-e2e-azuredisk-capz-windows-2019 #1615025993980841984
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 41m4s |
| Revision | main |
... skipping 793 lines ... certificate.cert-manager.io "selfsigned-cert" deleted # Create secret for AzureClusterIdentity ./hack/create-identity-secret.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' Error from server (NotFound): secrets "cluster-identity-secret" not found secret/cluster-identity-secret created secret/cluster-identity-secret labeled # Create customized cloud provider configs ./hack/create-custom-cloud-provider-config.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. ... skipping 180 lines ... pod/kube-apiserver-capz-vxy33w-control-plane-mlk98 condition met pod/kube-controller-manager-capz-vxy33w-control-plane-mlk98 condition met pod/kube-proxy-k6trq condition met pod/kube-proxy-windows-nh5h8 condition met pod/kube-scheduler-capz-vxy33w-control-plane-mlk98 condition met pod/metrics-server-c9574f845-97btp condition met error: timed out waiting for the condition on pods/kube-proxy-windows-n59q7 NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME capz-vxy3-fcwbg Ready <none> 13m v1.27.0-alpha.0.999+ed8cad1e80d096 10.1.0.4 <none> Windows Server 2019 Datacenter 10.0.17763.3770 containerd://1.6.2 capz-vxy3-nnrmj Ready <none> 11m v1.27.0-alpha.0.999+ed8cad1e80d096 10.1.0.5 <none> Windows Server 2019 Datacenter 10.0.17763.3770 containerd://1.6.2 capz-vxy33w-control-plane-mlk98 Ready control-plane 16m v1.27.0-alpha.0.999+ed8cad1e80d096 10.0.0.4 <none> Ubuntu 18.04.6 LTS 5.4.0-1098-azure containerd://1.6.2 NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES calico-apiserver calico-apiserver-6bdc9fccf6-c6qrr 1/1 Running 0 15m 192.168.75.134 capz-vxy33w-control-plane-mlk98 <none> <none> ... skipping 31 lines ... Jan 16 17:11:12.531: INFO: Collecting logs for Windows node capz-vxy3-fcwbg in cluster capz-vxy33w in namespace default Jan 16 17:13:30.403: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-vxy3-fcwbg to /logs/artifacts/clusters/capz-vxy33w/machines/capz-vxy33w-md-win-5fbf99d7f7-f25s9/crashdumps.tar Jan 16 17:13:31.845: INFO: Collecting boot logs for AzureMachine capz-vxy33w-md-win-fcwbg Failed to get logs for Machine capz-vxy33w-md-win-5fbf99d7f7-f25s9, Cluster default/capz-vxy33w: [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] Jan 16 17:13:32.725: INFO: Collecting logs for Windows node capz-vxy3-nnrmj in cluster capz-vxy33w in namespace default Jan 16 17:15:57.049: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-vxy3-nnrmj to /logs/artifacts/clusters/capz-vxy33w/machines/capz-vxy33w-md-win-5fbf99d7f7-sqmds/crashdumps.tar Jan 16 17:15:58.768: INFO: Collecting boot logs for AzureMachine capz-vxy33w-md-win-nnrmj Failed to get logs for Machine capz-vxy33w-md-win-5fbf99d7f7-sqmds, Cluster default/capz-vxy33w: [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] Jan 16 17:15:59.695: INFO: Dumping workload cluster default/capz-vxy33w kube-system pod logs Jan 16 17:16:00.015: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-6bdc9fccf6-c6qrr, container calico-apiserver Jan 16 17:16:00.015: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-6bdc9fccf6-r9dts, container calico-apiserver Jan 16 17:16:00.014: INFO: Collecting events for Pod calico-apiserver/calico-apiserver-6bdc9fccf6-c6qrr Jan 16 17:16:00.015: INFO: Collecting events for Pod calico-apiserver/calico-apiserver-6bdc9fccf6-r9dts Jan 16 17:16:00.058: INFO: Collecting events for Pod calico-system/calico-kube-controllers-6b7b9c649d-76mhp ... skipping 40 lines ... Jan 16 17:16:00.106: INFO: Collecting events for Pod kube-system/containerd-logger-xxmzh Jan 16 17:16:00.105: INFO: Collecting events for Pod kube-system/kube-scheduler-capz-vxy33w-control-plane-mlk98 Jan 16 17:16:00.143: INFO: Fetching kube-system pod logs took 447.211781ms Jan 16 17:16:00.143: INFO: Dumping workload cluster default/capz-vxy33w Azure activity log Jan 16 17:16:00.143: INFO: Creating log watcher for controller tigera-operator/tigera-operator-54b47459dd-pzpkj, container tigera-operator Jan 16 17:16:00.143: INFO: Collecting events for Pod tigera-operator/tigera-operator-54b47459dd-pzpkj Jan 16 17:16:00.172: INFO: Error starting logs stream for pod kube-system/kube-proxy-windows-n59q7, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-n59q7" is waiting to start: trying and failing to pull image Jan 16 17:16:05.927: INFO: Fetching activity logs took 5.784478725s ================ REDACTING LOGS ================ All sensitive variables are redacted cluster.cluster.x-k8s.io "capz-vxy33w" deleted /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kind-v0.17.0 delete cluster --name=capz || true Deleting cluster "capz" ... ... skipping 12 lines ...