This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmarosset: az capi readme and minor updates
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-09-19 22:16
Elapsed31m44s
Revisionea11ce7b75f82d9186d44ef8e474e76f1eb90147
Refs 342

No Test Failures!


Error lines from build-log.txt

... skipping 85 lines ...
WARNING: Merged "capi-manager" as current context in /root/.kube/config
WARNING: ✓ Obtained AKS credentials
WARNING: ✓ Created Cluster Identity Secret
WARNING: ✓ Initialized management cluster
WARNING: ✓ Generated workload cluster configuration at "capz-conf-2l92i4.yaml"
WARNING: ✓ Created workload cluster "capz-conf-2l92i4"
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
Error: "capz-conf-2l92i4-kubeconfig" not found in namespace "default": secrets "capz-conf-2l92i4-kubeconfig" not found
WARNING: ✓ Workload cluster is accessible
WARNING: ✓ Workload access configuration written to "capz-conf-2l92i4.kubeconfig"
WARNING: ✓ Deployed CNI to workload cluster
WARNING: ✓ Deployed Windows Calico support to workload cluster
WARNING: ✓ Deployed Windows kube-proxy support to workload cluster
WARNING: ✓ Workload cluster is ready
... skipping 364 lines ...

Sep 19 22:41:53.588: INFO: Collecting logs for Windows node capz-conf-h8klt in cluster capz-conf-2l92i4 in namespace default

Sep 19 22:45:09.791: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-h8klt to /logs/artifacts/clusters/capz-conf-2l92i4/machines/capz-conf-2l92i4-md-win-546c7bc558-ndb72/crashdumps.tar
Sep 19 22:45:11.415: INFO: Collecting boot logs for AzureMachine capz-conf-2l92i4-md-win-h8klt

Failed to get logs for machine capz-conf-2l92i4-md-win-546c7bc558-ndb72, cluster default/capz-conf-2l92i4: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, getting a new sftp client connection: ssh: subsystem request failed]
Sep 19 22:45:12.676: INFO: Collecting logs for Windows node capz-conf-bgtgv in cluster capz-conf-2l92i4 in namespace default

Sep 19 22:47:19.790: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-bgtgv to /logs/artifacts/clusters/capz-conf-2l92i4/machines/capz-conf-2l92i4-md-win-546c7bc558-r8tnq/crashdumps.tar
Sep 19 22:47:21.391: INFO: Collecting boot logs for AzureMachine capz-conf-2l92i4-md-win-bgtgv

Failed to get logs for machine capz-conf-2l92i4-md-win-546c7bc558-r8tnq, cluster default/capz-conf-2l92i4: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, getting a new sftp client connection: ssh: subsystem request failed]
STEP: Dumping workload cluster default/capz-conf-2l92i4 kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-kube-controllers-755ff8d7b5-s2xv7
STEP: Fetching kube-system pod logs took 894.878324ms
STEP: Dumping workload cluster default/capz-conf-2l92i4 Azure activity log
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-755ff8d7b5-s2xv7, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-proxy-cv5vx, container kube-proxy
STEP: Collecting events for Pod kube-system/csi-proxy-csrsf
STEP: Collecting events for Pod kube-system/etcd-capz-conf-2l92i4-control-plane-fsl74
STEP: Creating log watcher for controller kube-system/calico-node-4vbhz, container calico-node
STEP: failed to find events of Pod "etcd-capz-conf-2l92i4-control-plane-fsl74"
STEP: Creating log watcher for controller kube-system/csi-proxy-pgv86, container csi-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-zn5fb, container kube-proxy
STEP: Creating log watcher for controller kube-system/containerd-logger-2g9nk, container containerd-logger
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-2z2r5, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-zn5fb
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-2l92i4-control-plane-fsl74, container kube-apiserver
... skipping 2 lines ...
STEP: Collecting events for Pod kube-system/metrics-server-76f7667fbf-vszzz
STEP: Collecting events for Pod kube-system/calico-node-windows-4g6sp
STEP: Creating log watcher for controller kube-system/containerd-logger-rqrbh, container containerd-logger
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-2l92i4-control-plane-fsl74, container kube-scheduler
STEP: Collecting events for Pod kube-system/containerd-logger-2g9nk
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-conf-2l92i4-control-plane-fsl74
STEP: failed to find events of Pod "kube-scheduler-capz-conf-2l92i4-control-plane-fsl74"
STEP: Collecting events for Pod kube-system/calico-node-4vbhz
STEP: Creating log watcher for controller kube-system/calico-node-windows-4g6sp, container calico-node-startup
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-h2ltg
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-h2ltg, container coredns
STEP: Creating log watcher for controller kube-system/csi-proxy-csrsf, container csi-proxy
STEP: Collecting events for Pod kube-system/containerd-logger-rqrbh
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-2l92i4-control-plane-fsl74, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-proxy-windows-2z2r5
STEP: Creating log watcher for controller kube-system/calico-node-windows-dc7tj, container calico-node-felix
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-conf-2l92i4-control-plane-fsl74
STEP: failed to find events of Pod "kube-apiserver-capz-conf-2l92i4-control-plane-fsl74"
STEP: Creating log watcher for controller kube-system/calico-node-windows-dc7tj, container calico-node-startup
STEP: Collecting events for Pod kube-system/calico-node-windows-dc7tj
STEP: Creating log watcher for controller kube-system/calico-node-windows-4g6sp, container calico-node-felix
STEP: Collecting events for Pod kube-system/csi-proxy-pgv86
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-b87xc
STEP: Creating log watcher for controller kube-system/etcd-capz-conf-2l92i4-control-plane-fsl74, container etcd
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-b87xc, container coredns
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-2l92i4-control-plane-fsl74
STEP: failed to find events of Pod "kube-controller-manager-capz-conf-2l92i4-control-plane-fsl74"
STEP: Fetching activity logs took 2.242456346s
/home/prow/go/src/k8s.io/windows-testing
================ REDACTING LOGS ================
All sensitive variables are redacted
Mon, 19 Sep 2022 22:47:32 +0000: deleting cluster
+ EXIT_VALUE=1
... skipping 8 lines ...