kubernetes-sigs/azuredisk-csi-driver PR #1712 pull-azuredisk-csi-driver-e2e-capz-windows-2019-mainv2 #1620954125665570816
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | edreed: [V2] build: disable provenance attestation to work around docker issue |
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 37m11s |
| Revision | c39b37bd9f04265a0a5a4c10797261adac2b3d1f |
| Refs |
1712 |
... skipping 809 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 153 lines ... Feb 2 01:31:51.231: INFO: Unable to collect logs as node doesn't have addresses Feb 2 01:31:51.231: INFO: Collecting logs for Windows node capz-h72v4u-md-win-878lp in cluster capz-h72v4u in namespace default Feb 2 01:36:14.487: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-h72v4u-md-win-878lp to /logs/artifacts/clusters/capz-h72v4u/machines/capz-h72v4u-md-win-69479bcd89-64rt7/crashdumps.tar Feb 2 01:36:16.172: INFO: Collecting boot logs for AzureMachine capz-h72v4u-md-win-878lp Failed to get logs for Machine capz-h72v4u-md-win-69479bcd89-64rt7, Cluster default/capz-h72v4u: [dialing from control plane to target node at capz-h72v4u-md-win-878lp: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Feb 2 01:36:16.208: INFO: Unable to collect logs as node doesn't have addresses Feb 2 01:36:16.208: INFO: Collecting logs for Windows node capz-h72v4u-md-win-wkxfw in cluster capz-h72v4u in namespace default Feb 2 01:40:38.543: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-h72v4u-md-win-wkxfw to /logs/artifacts/clusters/capz-h72v4u/machines/capz-h72v4u-md-win-69479bcd89-9c7ql/crashdumps.tar Feb 2 01:40:40.319: INFO: Collecting boot logs for AzureMachine capz-h72v4u-md-win-wkxfw Failed to get logs for Machine capz-h72v4u-md-win-69479bcd89-9c7ql, Cluster default/capz-h72v4u: [dialing from control plane to target node at capz-h72v4u-md-win-wkxfw: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Feb 2 01:40:40.346: INFO: Unable to collect logs as node doesn't have addresses Feb 2 01:40:40.346: INFO: Collecting logs for Windows node capz-h72v4u-md-win-kbf6r in cluster capz-h72v4u in namespace default Feb 2 01:45:01.867: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-h72v4u-md-win-kbf6r to /logs/artifacts/clusters/capz-h72v4u/machines/capz-h72v4u-md-win-69479bcd89-vcfqg/crashdumps.tar Feb 2 01:45:03.791: INFO: Collecting boot logs for AzureMachine capz-h72v4u-md-win-kbf6r Failed to get logs for Machine capz-h72v4u-md-win-69479bcd89-vcfqg, Cluster default/capz-h72v4u: [dialing from control plane to target node at capz-h72v4u-md-win-kbf6r: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Feb 2 01:45:03.814: INFO: Dumping workload cluster default/capz-h72v4u kube-system pod logs Feb 2 01:45:05.459: INFO: Creating log watcher for controller kube-system/containerd-logger-88zb2, container containerd-logger Feb 2 01:45:05.459: INFO: Describing Pod kube-system/containerd-logger-88zb2 Feb 2 01:45:05.690: INFO: Creating log watcher for controller kube-system/containerd-logger-bjptb, container containerd-logger Feb 2 01:45:05.690: INFO: Describing Pod kube-system/containerd-logger-bjptb Feb 2 01:45:05.916: INFO: Creating log watcher for controller kube-system/containerd-logger-gxn89, container containerd-logger ... skipping 43 lines ...