kubernetes-sigs/azuredisk-csi-driver PR #1704 pull-azuredisk-csi-driver-e2e-capz #1619170192917532672
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | andyzhangx: fix: switch base image to fix CVEs |
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 23m54s |
| Revision | a093a52191d3e3d9e4045b29bef24ef84b1ddc4f |
| Refs |
1704 |
... 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 127 lines ... # Wait for the kubeconfig to become available. timeout --foreground 300 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets | grep capz-1e6umr-kubeconfig; do sleep 1; done" capz-1e6umr-kubeconfig cluster.x-k8s.io/secret 1 1s # 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-1e6umr-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" error: the server doesn't have a resource type "nodes" capz-1e6umr-control-plane-8j5xp NotReady <none> 0s v1.24.6 run "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig ..." to work with the new target cluster make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME capz-1e6umr-control-plane-8j5xp NotReady control-plane 1s v1.24.6 10.0.0.4 <none> Ubuntu 20.04.5 LTS 5.15.0-1020-azure containerd://1.6.2 NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES ... skipping 9 lines ... Jan 28 03:24:22.010: INFO: Collecting boot logs for AzureMachine capz-1e6umr-control-plane-8j5xp Jan 28 03:24:22.963: INFO: Collecting logs for Linux node capz-1e6umr-md-0-jtz2b in cluster capz-1e6umr in namespace default Jan 28 03:25:28.794: INFO: Collecting boot logs for AzureMachine capz-1e6umr-md-0-jtz2b Failed to get logs for Machine capz-1e6umr-md-0-6b8886984-jhx2k, Cluster default/capz-1e6umr: [dialing from control plane to target node at capz-1e6umr-md-0-jtz2b: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Jan 28 03:25:28.821: INFO: Collecting logs for Linux node capz-1e6umr-md-0-l29fv in cluster capz-1e6umr in namespace default Jan 28 03:25:36.051: INFO: Collecting boot logs for AzureMachine capz-1e6umr-md-0-l29fv Failed to get logs for Machine capz-1e6umr-md-0-6b8886984-nf5dm, Cluster default/capz-1e6umr: Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil Jan 28 03:25:36.070: INFO: Dumping workload cluster default/capz-1e6umr kube-system pod logs Jan 28 03:25:36.512: INFO: Creating log watcher for controller kube-system/coredns-5ddbf5fb99-pfpm8, container coredns Jan 28 03:25:36.513: INFO: Describing Pod kube-system/coredns-5ddbf5fb99-pfpm8 Jan 28 03:25:36.586: INFO: Creating log watcher for controller kube-system/coredns-986f5449c-l8lcv, container coredns Jan 28 03:25:36.586: INFO: Describing Pod kube-system/coredns-986f5449c-l8lcv Jan 28 03:25:36.659: INFO: Creating log watcher for controller kube-system/coredns-986f5449c-s7982, container coredns ... skipping 3 lines ... Jan 28 03:25:36.810: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-1e6umr-control-plane-8j5xp, container kube-apiserver Jan 28 03:25:36.811: INFO: Describing Pod kube-system/kube-apiserver-capz-1e6umr-control-plane-8j5xp Jan 28 03:25:36.884: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-1e6umr-control-plane-8j5xp, container kube-controller-manager Jan 28 03:25:36.884: INFO: Describing Pod kube-system/kube-controller-manager-capz-1e6umr-control-plane-8j5xp Jan 28 03:25:37.273: INFO: Creating log watcher for controller kube-system/kube-proxy-6c7vh, container kube-proxy Jan 28 03:25:37.273: INFO: Describing Pod kube-system/kube-proxy-6c7vh Jan 28 03:25:37.325: INFO: Error starting logs stream for pod kube-system/kube-proxy-6c7vh, container kube-proxy: the server could not find the requested resource ( pods/log kube-proxy-6c7vh) Jan 28 03:25:37.674: INFO: Creating log watcher for controller kube-system/kube-proxy-hm2gx, container kube-proxy Jan 28 03:25:37.674: INFO: Describing Pod kube-system/kube-proxy-hm2gx Jan 28 03:25:38.073: INFO: Fetching kube-system pod logs took 2.002719799s Jan 28 03:25:38.073: INFO: Dumping workload cluster default/capz-1e6umr Azure activity log Jan 28 03:25:38.073: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-1e6umr-control-plane-8j5xp, container kube-scheduler Jan 28 03:25:38.073: INFO: Describing Pod kube-system/kube-scheduler-capz-1e6umr-control-plane-8j5xp ... skipping 18 lines ...