kubernetes-sigs/azurefile-csi-driver PR #1156 pull-azurefile-csi-driver-e2e-capz-windows-2019 #1610621537725976576
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | andyzhangx: fix: account matching issue in account search |
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 38m23s |
| Revision | d73ac16d2f16c75e8f3baf52b1d2a0a296d1ebbe |
| Refs |
1156 |
... skipping 763 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 140 lines ... # Get kubeconfig and store it locally. /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets capz-ge6stm-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig timeout --foreground 600 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done" Unable to connect to the server: dial tcp 20.106.114.235:6443: i/o timeout Unable to connect to the server: dial tcp 20.106.114.235:6443: i/o timeout Unable to connect to the server: dial tcp 20.106.114.235:6443: i/o timeout make[1]: *** [Makefile:313: create-workload-cluster] Error 124 make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make: *** [Makefile:340: create-cluster] Error 2 Unable to connect to the server: dial tcp 20.106.114.235:6443: i/o timeout Collecting logs for cluster capz-ge6stm in namespace default and dumping logs to /logs/artifacts INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-5c7c7dd58d-lfhd8, container manager INFO: Creating log watcher for controller capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager, pod capi-kubeadm-control-plane-controller-manager-7b46b747b4-lhzsj, container manager INFO: Creating log watcher for controller capi-system/capi-controller-manager, pod capi-controller-manager-d9b5f9747-xd7ff, container manager INFO: Creating log watcher for controller capz-system/capz-controller-manager, pod capz-controller-manager-676fd974f6-6wgpp, container manager ... skipping 5 lines ... Jan 4 13:22:54.555: INFO: Unable to collect logs as node doesn't have addresses Jan 4 13:22:54.555: INFO: Collecting logs for Windows node capz-ge6stm-md-win-7d4f2 in cluster capz-ge6stm in namespace default Jan 4 13:27:09.731: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-ge6stm-md-win-7d4f2 to /logs/artifacts/clusters/capz-ge6stm/machines/capz-ge6stm-md-win-6df447b959-csxkz/crashdumps.tar Jan 4 13:27:10.423: INFO: Collecting boot logs for AzureMachine capz-ge6stm-md-win-7d4f2 Failed to get logs for machine capz-ge6stm-md-win-6df447b959-csxkz, cluster default/capz-ge6stm: [dialing from control plane to target node at capz-ge6stm-md-win-7d4f2: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Jan 4 13:27:10.456: INFO: Unable to collect logs as node doesn't have addresses Jan 4 13:27:10.456: INFO: Collecting logs for Windows node capz-ge6stm-md-win-lq56j in cluster capz-ge6stm in namespace default Jan 4 13:31:24.947: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-ge6stm-md-win-lq56j to /logs/artifacts/clusters/capz-ge6stm/machines/capz-ge6stm-md-win-6df447b959-mdlfk/crashdumps.tar Jan 4 13:31:26.175: INFO: Collecting boot logs for AzureMachine capz-ge6stm-md-win-lq56j Failed to get logs for machine capz-ge6stm-md-win-6df447b959-mdlfk, cluster default/capz-ge6stm: [dialing from control plane to target node at capz-ge6stm-md-win-lq56j: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] [1mSTEP[0m: Dumping workload cluster default/capz-ge6stm kube-system pod logs [1mSTEP[0m: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-krcgq, container calico-kube-controllers [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-xbcmf, container calico-node [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-n64g6, container coredns [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-n64g6 [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-xbcmf ... skipping 2 lines ... [1mSTEP[0m: Dumping workload cluster default/capz-ge6stm Azure activity log [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-twdt8, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-ge6stm-control-plane-cdpp5, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/metrics-server-7bdcf69694-5tdks [1mSTEP[0m: Collecting events for Pod kube-system/etcd-capz-ge6stm-control-plane-cdpp5 [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-capz-ge6stm-control-plane-cdpp5 [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-capz-ge6stm-control-plane-cdpp5" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-kn9jz, container kube-proxy [1mSTEP[0m: failed to find events of Pod "etcd-capz-ge6stm-control-plane-cdpp5" [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-twdt8 [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-capz-ge6stm-control-plane-cdpp5, container etcd [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-kn9jz [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-ge6stm-control-plane-cdpp5, container kube-apiserver [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-capz-ge6stm-control-plane-cdpp5 [1mSTEP[0m: Creating log watcher for controller kube-system/metrics-server-7bdcf69694-5tdks, container metrics-server [1mSTEP[0m: failed to find events of Pod "kube-scheduler-capz-ge6stm-control-plane-cdpp5" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-ge6stm-control-plane-cdpp5, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-capz-ge6stm-control-plane-cdpp5 [1mSTEP[0m: failed to find events of Pod "kube-apiserver-capz-ge6stm-control-plane-cdpp5" [1mSTEP[0m: Fetching activity logs took 2.147580247s ================ REDACTING LOGS ================ All sensitive variables are redacted cluster.cluster.x-k8s.io "capz-ge6stm" deleted /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kind-v0.14.0 delete cluster --name=capz || true Deleting cluster "capz" ... ... skipping 12 lines ...