This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultfailure
Tests 0 failed / 0 succeeded
Started2022-09-07 18:03
Elapsed26m18s
Revision
uploadercrier

No Test Failures!


Error lines from build-log.txt

... skipping 779 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 143 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-n1h8fh-kubeconfig; do sleep 1; done"
capz-n1h8fh-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-n1h8fh-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"
No resources found
No resources found
capz-n1h8fh-control-plane-zql94   NotReady   control-plane   1s    v1.26.0-alpha.0.401+a488f4b95c7ad5
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'
Waiting for 1 control plane machine(s), 2 worker machine(s), and  windows machine(s) to become Ready
... skipping 8 lines ...
capz-n1h8fh-control-plane-zql94   Ready    control-plane   7m46s   v1.26.0-alpha.0.401+a488f4b95c7ad5   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
capz-n1h8fh-mp-0000000            Ready    <none>          2m12s   v1.26.0-alpha.0.401+a488f4b95c7ad5   10.1.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
capz-n1h8fh-mp-0000001            Ready    <none>          3m29s   v1.26.0-alpha.0.401+a488f4b95c7ad5   10.1.0.5      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
Installing cloud-provider-azure components via helm
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "https://capz-n1h8fh-78d1db45.northeurope.cloudapp.azure.com:6443/version": dial tcp 20.223.98.128:6443: i/o timeout
NAME                              STATUS   ROLES           AGE     VERSION                              INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
capz-n1h8fh-control-plane-zql94   Ready    control-plane   8m17s   v1.26.0-alpha.0.401+a488f4b95c7ad5   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
capz-n1h8fh-mp-0000000            Ready    <none>          2m43s   v1.26.0-alpha.0.401+a488f4b95c7ad5   10.1.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
capz-n1h8fh-mp-0000001            Ready    <none>          4m      v1.26.0-alpha.0.401+a488f4b95c7ad5   10.1.0.5      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
NAMESPACE     NAME                                                      READY   STATUS    RESTARTS   AGE     IP              NODE                              NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-755ff8d7b5-v7vw8                  1/1     Running   0          7m44s   192.168.36.67   capz-n1h8fh-mp-0000001            <none>           <none>
... skipping 31 lines ...
STEP: Dumping workload cluster default/capz-n1h8fh kube-system pod logs
STEP: Fetching kube-system pod logs took 1.221058787s
STEP: Dumping workload cluster default/capz-n1h8fh Azure activity log
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-755ff8d7b5-v7vw8, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-n1h8fh-control-plane-zql94
STEP: Creating log watcher for controller kube-system/calico-node-4gc7h, container calico-node
STEP: failed to find events of Pod "kube-apiserver-capz-n1h8fh-control-plane-zql94"
STEP: Collecting events for Pod kube-system/calico-node-5ljpr
STEP: Collecting events for Pod kube-system/kube-proxy-phx9z
STEP: Creating log watcher for controller kube-system/calico-node-cfggf, container calico-node
STEP: Creating log watcher for controller kube-system/kube-proxy-468wt, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-468wt
STEP: Creating log watcher for controller kube-system/kube-proxy-phx9z, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-n1h8fh-control-plane-zql94
STEP: Creating log watcher for controller kube-system/metrics-server-76f7667fbf-trv6x, container metrics-server
STEP: failed to find events of Pod "kube-scheduler-capz-n1h8fh-control-plane-zql94"
STEP: Creating log watcher for controller kube-system/kube-proxy-zhrwd, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-cfggf
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-n1h8fh-control-plane-zql94, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-4qxkc, container coredns
STEP: Collecting events for Pod kube-system/calico-kube-controllers-755ff8d7b5-v7vw8
STEP: Collecting events for Pod kube-system/calico-node-4gc7h
... skipping 5 lines ...
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-tsmt8, container coredns
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-n1h8fh-control-plane-zql94, container kube-scheduler
STEP: Creating log watcher for controller kube-system/etcd-capz-n1h8fh-control-plane-zql94, container etcd
STEP: Collecting events for Pod kube-system/etcd-capz-n1h8fh-control-plane-zql94
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-n1h8fh-control-plane-zql94, container kube-apiserver
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-tsmt8
STEP: failed to find events of Pod "kube-controller-manager-capz-n1h8fh-control-plane-zql94"
STEP: failed to find events of Pod "etcd-capz-n1h8fh-control-plane-zql94"
STEP: Fetching activity logs took 1.797404284s
================ REDACTING LOGS ================
All sensitive variables are redacted
make: Entering directory '/home/prow/go/src/sigs.k8s.io/cloud-provider-azure'
rm -rf bin .pkg_config testResults
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cloud-provider-azure'
... skipping 11 lines ...