This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 7 succeeded
Started2023-01-05 16:55
Elapsed4h15m
Revisionrelease-1.5

No Test Failures!


Show 7 Passed Tests

Show 7 Skipped Tests

Error lines from build-log.txt

... skipping 586 lines ...
STEP: Collecting events for Pod kube-system/calico-node-zx6kt
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-79dbx, container coredns
STEP: Creating log watcher for controller kube-system/calico-node-zx6kt, container calico-node
STEP: Dumping workload cluster kcp-adoption-mgkzj0/kcp-adoption-a1zsu6 Azure activity log
STEP: Collecting events for Pod kube-system/kube-scheduler-kcp-adoption-a1zsu6-control-plane-0
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-lpgkl
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-a1zsu6-control-plane-0"
STEP: failed to find events of Pod "etcd-kcp-adoption-a1zsu6-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-a1zsu6-control-plane-0, container kube-controller-manager
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-79dbx
STEP: Creating log watcher for controller kube-system/kube-apiserver-kcp-adoption-a1zsu6-control-plane-0, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-controller-manager-kcp-adoption-a1zsu6-control-plane-0
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-adoption-a1zsu6-control-plane-0, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-proxy-c85mz, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-c85mz
STEP: failed to find events of Pod "kube-controller-manager-kcp-adoption-a1zsu6-control-plane-0"
STEP: failed to find events of Pod "kube-scheduler-kcp-adoption-a1zsu6-control-plane-0"
STEP: Fetching activity logs took 2.269331667s
STEP: Dumping all the Cluster API resources in the "kcp-adoption-mgkzj0" namespace
STEP: Deleting cluster kcp-adoption-mgkzj0/kcp-adoption-a1zsu6
STEP: Deleting cluster kcp-adoption-a1zsu6
INFO: Waiting for the Cluster kcp-adoption-mgkzj0/kcp-adoption-a1zsu6 to be deleted
STEP: Waiting for cluster kcp-adoption-a1zsu6 to be deleted
... skipping 89 lines ...
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-28t6mc-control-plane-krsz8
STEP: Creating log watcher for controller kube-system/etcd-mhc-remediation-28t6mc-control-plane-krsz8, container etcd
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-28t6mc-control-plane-krsz8, container kube-controller-manager
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-r6v4w
STEP: Creating log watcher for controller kube-system/kube-proxy-skfv8, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-28t6mc-control-plane-krsz8
STEP: failed to find events of Pod "kube-controller-manager-mhc-remediation-28t6mc-control-plane-krsz8"
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-s2q4x, container calico-kube-controllers
STEP: Fetching activity logs took 1.773031968s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-qcpbww" namespace
STEP: Deleting cluster mhc-remediation-qcpbww/mhc-remediation-28t6mc
STEP: Deleting cluster mhc-remediation-28t6mc
INFO: Waiting for the Cluster mhc-remediation-qcpbww/mhc-remediation-28t6mc to be deleted
... skipping 17 lines ...
  Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_selfhosted.go:107

INFO: "Should pivot the bootstrap cluster to a self-hosted cluster" started at Thu, 05 Jan 2023 17:05:56 UTC on Ginkgo node 1 of 10
STEP: Creating namespace "self-hosted" for hosting the cluster
Jan  5 17:05:56.765: INFO: starting to create namespace for hosting the "self-hosted" test spec
2023/01/05 17:05:56 failed trying to get namespace (self-hosted):namespaces "self-hosted" not found
INFO: Creating namespace self-hosted
INFO: Creating event watcher for namespace "self-hosted"
STEP: Creating a workload cluster
INFO: Creating the workload cluster with name "self-hosted-jyr1ax" using the "management" template (Kubernetes v1.23.15, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster self-hosted-jyr1ax --infrastructure (default) --kubernetes-version v1.23.15 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 78 lines ...
STEP: Collecting events for Pod kube-system/calico-node-hhfdx
STEP: Creating log watcher for controller kube-system/kube-proxy-htgnn, container kube-proxy
STEP: Collecting events for Pod kube-system/etcd-self-hosted-jyr1ax-control-plane-pzwdc
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-jyr1ax-control-plane-pzwdc
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-jyr1ax-control-plane-pzwdc, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-jyr1ax-control-plane-pzwdc
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-jyr1ax-control-plane-pzwdc"
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-jyr1ax-control-plane-pzwdc
STEP: failed to find events of Pod "kube-scheduler-self-hosted-jyr1ax-control-plane-pzwdc"
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-jyr1ax-control-plane-pzwdc, container kube-apiserver
STEP: failed to find events of Pod "etcd-self-hosted-jyr1ax-control-plane-pzwdc"
STEP: failed to find events of Pod "kube-apiserver-self-hosted-jyr1ax-control-plane-pzwdc"
STEP: Fetching activity logs took 1.927464807s
Jan  5 17:17:09.668: INFO: Dumping all the Cluster API resources in the "self-hosted" namespace
Jan  5 17:17:10.018: INFO: Deleting all clusters in the self-hosted namespace
STEP: Deleting cluster self-hosted-jyr1ax
INFO: Waiting for the Cluster self-hosted/self-hosted-jyr1ax to be deleted
STEP: Waiting for cluster self-hosted-jyr1ax to be deleted
... skipping 210 lines ...

Jan  5 17:14:05.110: INFO: Collecting logs for Windows node quick-sta-2xtnb in cluster quick-start-urtddd in namespace quick-start-k4pyfd

Jan  5 17:16:43.920: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-2xtnb to /logs/artifacts/clusters/quick-start-urtddd/machines/quick-start-urtddd-md-win-8446cf68-lr2hd/crashdumps.tar
Jan  5 17:16:47.393: INFO: Collecting boot logs for AzureMachine quick-start-urtddd-md-win-2xtnb

Failed to get logs for machine quick-start-urtddd-md-win-8446cf68-lr2hd, cluster quick-start-k4pyfd/quick-start-urtddd: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1]
Jan  5 17:16:48.619: INFO: Collecting logs for Windows node quick-sta-zxpxp in cluster quick-start-urtddd in namespace quick-start-k4pyfd

Jan  5 17:19:29.698: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-zxpxp to /logs/artifacts/clusters/quick-start-urtddd/machines/quick-start-urtddd-md-win-8446cf68-p5gtj/crashdumps.tar
Jan  5 17:19:33.164: INFO: Collecting boot logs for AzureMachine quick-start-urtddd-md-win-zxpxp

Failed to get logs for machine quick-start-urtddd-md-win-8446cf68-p5gtj, cluster quick-start-k4pyfd/quick-start-urtddd: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1]
STEP: Dumping workload cluster quick-start-k4pyfd/quick-start-urtddd kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-rkqzl
STEP: Creating log watcher for controller kube-system/calico-node-kmc9s, container calico-node
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-rkqzl, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/csi-proxy-jvzzh, container csi-proxy
STEP: Fetching kube-system pod logs took 1.073943002s
STEP: Collecting events for Pod kube-system/calico-node-kmc9s
STEP: Creating log watcher for controller kube-system/calico-node-pbdhj, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-pbdhj
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-urtddd-control-plane-d9vqw
STEP: Creating log watcher for controller kube-system/calico-node-windows-nm5n4, container calico-node-startup
STEP: Collecting events for Pod kube-system/calico-node-windows-z2c6m
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-urtddd-control-plane-d9vqw
STEP: failed to find events of Pod "kube-scheduler-quick-start-urtddd-control-plane-d9vqw"
STEP: Creating log watcher for controller kube-system/calico-node-windows-nm5n4, container calico-node-felix
STEP: Creating log watcher for controller kube-system/containerd-logger-55hcn, container containerd-logger
STEP: Dumping workload cluster quick-start-k4pyfd/quick-start-urtddd Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-quick-start-urtddd-control-plane-d9vqw, container etcd
STEP: Creating log watcher for controller kube-system/kube-proxy-49b2d, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-bq2ph, container kube-proxy
... skipping 18 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-urtddd-control-plane-d9vqw, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-proxy-windows-bq2ph
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-wq77v
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-urtddd-control-plane-d9vqw
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-urtddd-control-plane-d9vqw, container kube-controller-manager
STEP: Collecting events for Pod kube-system/csi-proxy-jvzzh
STEP: failed to find events of Pod "kube-controller-manager-quick-start-urtddd-control-plane-d9vqw"
STEP: Fetching activity logs took 1.903228096s
STEP: Dumping all the Cluster API resources in the "quick-start-k4pyfd" namespace
STEP: Deleting cluster quick-start-k4pyfd/quick-start-urtddd
STEP: Deleting cluster quick-start-urtddd
INFO: Waiting for the Cluster quick-start-k4pyfd/quick-start-urtddd to be deleted
STEP: Waiting for cluster quick-start-urtddd to be deleted
... skipping 97 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-windows-l5dbx, container calico-node-felix
STEP: Collecting events for Pod kube-system/kube-proxy-windows-bcmw5
STEP: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-t1fmdk-control-plane-7rbw2, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-proxy-sxb8j
STEP: Collecting events for Pod kube-system/kube-scheduler-machine-pool-t1fmdk-control-plane-7rbw2
STEP: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-t1fmdk-control-plane-7rbw2, container kube-scheduler
STEP: failed to find events of Pod "etcd-machine-pool-t1fmdk-control-plane-7rbw2"
STEP: Creating log watcher for controller kube-system/etcd-machine-pool-t1fmdk-control-plane-7rbw2, container etcd
STEP: failed to find events of Pod "kube-controller-manager-machine-pool-t1fmdk-control-plane-7rbw2"
STEP: failed to find events of Pod "kube-scheduler-machine-pool-t1fmdk-control-plane-7rbw2"
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-t1fmdk-control-plane-7rbw2, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-apiserver-machine-pool-t1fmdk-control-plane-7rbw2
STEP: failed to find events of Pod "kube-apiserver-machine-pool-t1fmdk-control-plane-7rbw2"
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-bcmw5, container kube-proxy
STEP: Error starting logs stream for pod kube-system/kube-proxy-sxb8j, container kube-proxy: pods "machine-pool-t1fmdk-mp-0000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-l5dbx, container calico-node-startup: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-l5dbx, container calico-node-felix: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-gtp82, container calico-node: pods "machine-pool-t1fmdk-mp-0000002" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-bcmw5, container kube-proxy: pods "win-p-win000002" not found
STEP: Fetching activity logs took 2.237888874s
STEP: Dumping all the Cluster API resources in the "machine-pool-7mqxe7" namespace
STEP: Deleting cluster machine-pool-7mqxe7/machine-pool-t1fmdk
STEP: Deleting cluster machine-pool-t1fmdk
INFO: Waiting for the Cluster machine-pool-7mqxe7/machine-pool-t1fmdk to be deleted
STEP: Waiting for cluster machine-pool-t1fmdk to be deleted
... skipping 100 lines ...
STEP: Fetching kube-system pod logs took 1.1676794s
STEP: Dumping workload cluster node-drain-k118qa/node-drain-tcjvau Azure activity log
STEP: Creating log watcher for controller kube-system/kube-proxy-cd6s4, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-24zgt, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-cd6s4
STEP: Collecting events for Pod kube-system/kube-scheduler-node-drain-tcjvau-control-plane-lf2nn
STEP: Error starting logs stream for pod kube-system/kube-apiserver-node-drain-tcjvau-control-plane-lf2nn, container kube-apiserver: pods "node-drain-tcjvau-control-plane-lf2nn" not found
STEP: Error starting logs stream for pod kube-system/etcd-node-drain-tcjvau-control-plane-lf2nn, container etcd: pods "node-drain-tcjvau-control-plane-lf2nn" not found
STEP: Error starting logs stream for pod kube-system/kube-scheduler-node-drain-tcjvau-control-plane-lf2nn, container kube-scheduler: pods "node-drain-tcjvau-control-plane-lf2nn" not found
STEP: Error starting logs stream for pod kube-system/kube-controller-manager-node-drain-tcjvau-control-plane-lf2nn, container kube-controller-manager: pods "node-drain-tcjvau-control-plane-lf2nn" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-24zgt, container kube-proxy: pods "node-drain-tcjvau-control-plane-lf2nn" not found
STEP: Error starting logs stream for pod kube-system/calico-node-vdct2, container calico-node: pods "node-drain-tcjvau-control-plane-lf2nn" not found
STEP: Fetching activity logs took 5.081200393s
STEP: Dumping all the Cluster API resources in the "node-drain-k118qa" namespace
STEP: Deleting cluster node-drain-k118qa/node-drain-tcjvau
STEP: Deleting cluster node-drain-tcjvau
INFO: Waiting for the Cluster node-drain-k118qa/node-drain-tcjvau to be deleted
STEP: Waiting for cluster node-drain-tcjvau to be deleted
... skipping 78 lines ...

Jan  5 17:16:42.006: INFO: Collecting logs for Windows node md-scale-tnnbp in cluster md-scale-3uzimi in namespace md-scale-zyw5ns

Jan  5 17:19:19.136: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-tnnbp to /logs/artifacts/clusters/md-scale-3uzimi/machines/md-scale-3uzimi-md-win-d96f54988-c9gtj/crashdumps.tar
Jan  5 17:19:22.578: INFO: Collecting boot logs for AzureMachine md-scale-3uzimi-md-win-tnnbp

Failed to get logs for machine md-scale-3uzimi-md-win-d96f54988-c9gtj, cluster md-scale-zyw5ns/md-scale-3uzimi: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1]
Jan  5 17:19:24.129: INFO: Collecting logs for Windows node md-scale-8vs8x in cluster md-scale-3uzimi in namespace md-scale-zyw5ns

Jan  5 17:22:02.485: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-8vs8x to /logs/artifacts/clusters/md-scale-3uzimi/machines/md-scale-3uzimi-md-win-d96f54988-kjgww/crashdumps.tar
Jan  5 17:22:05.911: INFO: Collecting boot logs for AzureMachine md-scale-3uzimi-md-win-8vs8x

Failed to get logs for machine md-scale-3uzimi-md-win-d96f54988-kjgww, cluster md-scale-zyw5ns/md-scale-3uzimi: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1]
STEP: Dumping workload cluster md-scale-zyw5ns/md-scale-3uzimi kube-system pod logs
STEP: Fetching kube-system pod logs took 1.076393109s
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-x8tkk, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-proxy-rm568, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-2qv7v
STEP: Collecting events for Pod kube-system/kube-proxy-nwrdd
STEP: Collecting events for Pod kube-system/calico-node-windows-kgzss
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-3uzimi-control-plane-tjclj
STEP: Collecting events for Pod kube-system/containerd-logger-ldc6g
STEP: failed to find events of Pod "kube-controller-manager-md-scale-3uzimi-control-plane-tjclj"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-scale-3uzimi-control-plane-tjclj, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-node-6wlwf, container calico-node
STEP: Creating log watcher for controller kube-system/containerd-logger-65wrt, container containerd-logger
STEP: Collecting events for Pod kube-system/calico-node-6wlwf
STEP: Creating log watcher for controller kube-system/calico-node-windows-jt5cq, container calico-node-startup
STEP: Collecting events for Pod kube-system/containerd-logger-65wrt
... skipping 22 lines ...
STEP: Creating log watcher for controller kube-system/etcd-md-scale-3uzimi-control-plane-tjclj, container etcd
STEP: Collecting events for Pod kube-system/kube-proxy-rm568
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-4l2z5, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-4l2z5
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-w8k2g, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-w8k2g
STEP: failed to find events of Pod "kube-scheduler-md-scale-3uzimi-control-plane-tjclj"
STEP: failed to find events of Pod "kube-apiserver-md-scale-3uzimi-control-plane-tjclj"
STEP: failed to find events of Pod "etcd-md-scale-3uzimi-control-plane-tjclj"
STEP: Fetching activity logs took 11.943869726s
STEP: Dumping all the Cluster API resources in the "md-scale-zyw5ns" namespace
STEP: Deleting cluster md-scale-zyw5ns/md-scale-3uzimi
STEP: Deleting cluster md-scale-3uzimi
INFO: Waiting for the Cluster md-scale-zyw5ns/md-scale-3uzimi to be deleted
STEP: Waiting for cluster md-scale-3uzimi to be deleted
... skipping 9 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:45
  Should successfully scale out and scale in a MachineDeployment
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:183
    Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
    /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.1/e2e/md_scale.go:71
------------------------------
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:164","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 4h0m0s timeout","severity":"error","time":"2023-01-05T20:55:31Z"}
++ early_exit_handler
++ '[' -n 162 ']'
++ kill -TERM 162
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 12 lines ...
Cleaning up after docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
================================================================================
Done cleaning up after docker in docker.
All sensitive variables are redacted
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:254","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15m0s grace period","severity":"error","time":"2023-01-05T21:10:31Z"}
{"component":"entrypoint","error":"os: process already finished","file":"k8s.io/test-infra/prow/entrypoint/run.go:256","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Could not kill process after grace period","severity":"error","time":"2023-01-05T21:10:31Z"}