kubernetes-sigs/azuredisk-csi-driver PR #1699 pull-azuredisk-csi-driver-e2e-capz-windows-2019 #1619905818692423680
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | andyzhangx: fix: panic when allow-empty-cloud-config is set |
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 29m28s |
| Revision | 811840a4df93d2694ed7545ed50a580b66eaa102 |
| Refs |
1699 |
... skipping 804 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 159 lines ... Jan 30 04:06:21.223: INFO: Unable to collect logs as node doesn't have addresses Jan 30 04:06:21.223: INFO: Collecting logs for Windows node capz-s4j4dg-md-win-78djt in cluster capz-s4j4dg in namespace default Jan 30 04:10:36.737: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-s4j4dg-md-win-78djt to /logs/artifacts/clusters/capz-s4j4dg/machines/capz-s4j4dg-md-win-7bf8f8cf76-v5smh/crashdumps.tar Jan 30 04:10:38.097: INFO: Collecting boot logs for AzureMachine capz-s4j4dg-md-win-78djt Failed to get logs for Machine capz-s4j4dg-md-win-7bf8f8cf76-v5smh, Cluster default/capz-s4j4dg: [dialing from control plane to target node at capz-s4j4dg-md-win-78djt: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Jan 30 04:10:38.128: INFO: Unable to collect logs as node doesn't have addresses Jan 30 04:10:38.128: INFO: Collecting logs for Windows node capz-s4j4dg-md-win-pxh59 in cluster capz-s4j4dg in namespace default Jan 30 04:14:55.851: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-s4j4dg-md-win-pxh59 to /logs/artifacts/clusters/capz-s4j4dg/machines/capz-s4j4dg-md-win-7bf8f8cf76-zjfxr/crashdumps.tar Jan 30 04:14:57.383: INFO: Collecting boot logs for AzureMachine capz-s4j4dg-md-win-pxh59 Failed to get logs for Machine capz-s4j4dg-md-win-7bf8f8cf76-zjfxr, Cluster default/capz-s4j4dg: [dialing from control plane to target node at capz-s4j4dg-md-win-pxh59: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Jan 30 04:14:57.400: INFO: Dumping workload cluster default/capz-s4j4dg kube-system pod logs Jan 30 04:14:58.178: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-k7cpt, container coredns Jan 30 04:14:58.178: INFO: Describing Pod kube-system/coredns-bd6b6df9f-k7cpt Jan 30 04:14:58.289: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-xdvwq, container coredns Jan 30 04:14:58.289: INFO: Describing Pod kube-system/coredns-bd6b6df9f-xdvwq Jan 30 04:14:58.401: INFO: Creating log watcher for controller kube-system/etcd-capz-s4j4dg-control-plane-sqzss, container etcd ... skipping 31 lines ...