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

No Test Failures!


Show 7 Passed Tests

Show 16 Skipped Tests

Error lines from build-log.txt

... skipping 676 lines ...
STEP: Creating log watcher for controller kube-system/etcd-mhc-remediation-xra2di-control-plane-f5nzl, container etcd
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-fv2qx
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-7tmgz, container calico-kube-controllers
STEP: Dumping workload cluster mhc-remediation-8opt3c/mhc-remediation-xra2di Azure activity log
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-7tmgz
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-xra2di-control-plane-f5nzl
STEP: failed to find events of Pod "kube-apiserver-mhc-remediation-xra2di-control-plane-f5nzl"
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-98t4b
STEP: Collecting events for Pod kube-system/calico-node-469m2
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-xra2di-control-plane-f5nzl, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-xra2di-control-plane-f5nzl
STEP: Creating log watcher for controller kube-system/kube-proxy-k8xm8, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-xra2di-control-plane-f5nzl, container kube-apiserver
STEP: Collecting events for Pod kube-system/calico-node-kgkjb
STEP: Collecting events for Pod kube-system/kube-proxy-k8xm8
STEP: Creating log watcher for controller kube-system/kube-proxy-t9dsk, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-node-kgkjb, container calico-node
STEP: Collecting events for Pod kube-system/kube-proxy-t9dsk
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-98t4b, container coredns
STEP: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-xra2di-control-plane-f5nzl
STEP: failed to find events of Pod "kube-scheduler-mhc-remediation-xra2di-control-plane-f5nzl"
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-fv2qx, container coredns
STEP: Collecting events for Pod kube-system/etcd-mhc-remediation-xra2di-control-plane-f5nzl
STEP: failed to find events of Pod "etcd-mhc-remediation-xra2di-control-plane-f5nzl"
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-xra2di-control-plane-f5nzl, container kube-scheduler
STEP: Fetching activity logs took 1.685359547s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-8opt3c" namespace
STEP: Deleting cluster mhc-remediation-8opt3c/mhc-remediation-xra2di
STEP: Deleting cluster mhc-remediation-xra2di
INFO: Waiting for the Cluster mhc-remediation-8opt3c/mhc-remediation-xra2di 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 Mon, 02 Jan 2023 17:03:49 UTC on Ginkgo node 8 of 10
STEP: Creating namespace "self-hosted" for hosting the cluster
Jan  2 17:03:49.253: INFO: starting to create namespace for hosting the "self-hosted" test spec
2023/01/02 17:03:49 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-f3p78v" 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-f3p78v --infrastructure (default) --kubernetes-version v1.23.15 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 77 lines ...
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-qzm2d
STEP: Collecting events for Pod kube-system/calico-node-6blfn
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-f3p78v-control-plane-xqf4s, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-f3p78v-control-plane-xqf4s
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-f3p78v-control-plane-xqf4s
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-f3p78v-control-plane-xqf4s, container kube-apiserver
STEP: failed to find events of Pod "kube-scheduler-self-hosted-f3p78v-control-plane-xqf4s"
STEP: failed to find events of Pod "kube-apiserver-self-hosted-f3p78v-control-plane-xqf4s"
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-f3p78v-control-plane-xqf4s, container etcd
STEP: Creating log watcher for controller kube-system/kube-proxy-krvtr, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-f3p78v-control-plane-xqf4s
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-f3p78v-control-plane-xqf4s"
STEP: failed to find events of Pod "etcd-self-hosted-f3p78v-control-plane-xqf4s"
STEP: Fetching activity logs took 1.105161423s
Jan  2 17:13:35.372: INFO: Dumping all the Cluster API resources in the "self-hosted" namespace
Jan  2 17:13:35.721: INFO: Deleting all clusters in the self-hosted namespace
STEP: Deleting cluster self-hosted-f3p78v
INFO: Waiting for the Cluster self-hosted/self-hosted-f3p78v to be deleted
STEP: Waiting for cluster self-hosted-f3p78v to be deleted
INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-6c76c59d6b-pr95k, container manager: http2: client connection lost
INFO: Got error while streaming logs for pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-74b6b6b77f-rnjb9, container manager: http2: client connection lost
INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-7d78ddc95f-g9jsf, container manager: http2: client connection lost
INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-7df9bc44b4-pdbxj, container manager: http2: client connection lost
Jan  2 17:18:15.944: INFO: Deleting namespace used for hosting the "self-hosted" test spec
INFO: Deleting namespace self-hosted
Jan  2 17:18:15.968: INFO: Checking if any resources are left over in Azure for spec "self-hosted"
STEP: Redacting sensitive information from logs
Jan  2 17:18:49.561: INFO: Cleaning up after "Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster" spec
STEP: Redacting sensitive information from logs
... skipping 68 lines ...

Jan  2 17:11:45.930: INFO: Collecting logs for Windows node quick-sta-8nhv6 in cluster quick-start-f49tjw in namespace quick-start-ir48pk

Jan  2 17:14:15.114: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-8nhv6 to /logs/artifacts/clusters/quick-start-f49tjw/machines/quick-start-f49tjw-md-win-5dc8cf4cd5-9nzsr/crashdumps.tar
Jan  2 17:14:16.508: INFO: Collecting boot logs for AzureMachine quick-start-f49tjw-md-win-8nhv6

Failed to get logs for machine quick-start-f49tjw-md-win-5dc8cf4cd5-9nzsr, cluster quick-start-ir48pk/quick-start-f49tjw: [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  2 17:14:17.378: INFO: Collecting logs for Windows node quick-sta-mnrs8 in cluster quick-start-f49tjw in namespace quick-start-ir48pk

Jan  2 17:16:51.460: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-mnrs8 to /logs/artifacts/clusters/quick-start-f49tjw/machines/quick-start-f49tjw-md-win-5dc8cf4cd5-fc9rc/crashdumps.tar
Jan  2 17:16:53.393: INFO: Collecting boot logs for AzureMachine quick-start-f49tjw-md-win-mnrs8

Failed to get logs for machine quick-start-f49tjw-md-win-5dc8cf4cd5-fc9rc, cluster quick-start-ir48pk/quick-start-f49tjw: [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-ir48pk/quick-start-f49tjw kube-system pod logs
STEP: Fetching kube-system pod logs took 415.240411ms
STEP: Dumping workload cluster quick-start-ir48pk/quick-start-f49tjw Azure activity log
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-tmqbt
STEP: Creating log watcher for controller kube-system/calico-node-windows-48zg5, container calico-node-startup
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-tf885
... skipping 12 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-btgqj, container kube-proxy
STEP: Collecting events for Pod kube-system/containerd-logger-c25q5
STEP: Creating log watcher for controller kube-system/containerd-logger-nrm28, container containerd-logger
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-f49tjw-control-plane-k2r8d
STEP: Collecting events for Pod kube-system/etcd-quick-start-f49tjw-control-plane-k2r8d
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-f49tjw-control-plane-k2r8d, container kube-controller-manager
STEP: failed to find events of Pod "etcd-quick-start-f49tjw-control-plane-k2r8d"
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-f49tjw-control-plane-k2r8d, container kube-apiserver
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-2c2k6, container coredns
STEP: Collecting events for Pod kube-system/kube-proxy-btgqj
STEP: Creating log watcher for controller kube-system/calico-node-windows-48zg5, container calico-node-felix
STEP: Collecting events for Pod kube-system/kube-proxy-windows-kvgfb
STEP: Collecting events for Pod kube-system/kube-proxy-windows-wn2lb
... skipping 105 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-qurnz3-control-plane-9d8hs, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-proxy-m9g24
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-qurnz3-control-plane-9d8hs, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-scheduler-machine-pool-qurnz3-control-plane-9d8hs
STEP: Creating log watcher for controller kube-system/calico-node-windows-4xhsq, container calico-node-felix
STEP: Creating log watcher for controller kube-system/etcd-machine-pool-qurnz3-control-plane-9d8hs, container etcd
STEP: failed to find events of Pod "kube-scheduler-machine-pool-qurnz3-control-plane-9d8hs"
STEP: Collecting events for Pod kube-system/etcd-machine-pool-qurnz3-control-plane-9d8hs
STEP: failed to find events of Pod "etcd-machine-pool-qurnz3-control-plane-9d8hs"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-qurnz3-control-plane-9d8hs, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-apiserver-machine-pool-qurnz3-control-plane-9d8hs
STEP: failed to find events of Pod "kube-apiserver-machine-pool-qurnz3-control-plane-9d8hs"
STEP: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-qurnz3-control-plane-9d8hs
STEP: failed to find events of Pod "kube-controller-manager-machine-pool-qurnz3-control-plane-9d8hs"
STEP: Collecting events for Pod kube-system/calico-node-bvskk
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-kq2zp
STEP: Creating log watcher for controller kube-system/calico-node-fqvb9, container calico-node
STEP: Creating log watcher for controller kube-system/kube-proxy-vqsg7, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-windows-4xhsq
STEP: Creating log watcher for controller kube-system/calico-node-bvskk, container calico-node
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-7djpb
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-nrzvj, container coredns
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-7djpb, container coredns
STEP: Collecting events for Pod kube-system/calico-node-fqvb9
STEP: Creating log watcher for controller kube-system/calico-node-windows-4xhsq, container calico-node-startup
STEP: Error starting logs stream for pod kube-system/kube-proxy-m9g24, container kube-proxy: pods "machine-pool-qurnz3-mp-0000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-4xhsq, container calico-node-felix: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-nn4hj, container kube-proxy: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-4xhsq, container calico-node-startup: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-bvskk, container calico-node: pods "machine-pool-qurnz3-mp-0000002" not found
STEP: Fetching activity logs took 1.601172745s
STEP: Dumping all the Cluster API resources in the "machine-pool-2ejy48" namespace
STEP: Deleting cluster machine-pool-2ejy48/machine-pool-qurnz3
STEP: Deleting cluster machine-pool-qurnz3
INFO: Waiting for the Cluster machine-pool-2ejy48/machine-pool-qurnz3 to be deleted
STEP: Waiting for cluster machine-pool-qurnz3 to be deleted
... skipping 214 lines ...

Jan  2 17:14:59.324: INFO: Collecting logs for Windows node md-scale-t2vnn in cluster md-scale-6cqt8x in namespace md-scale-o7d66m

Jan  2 17:17:36.893: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-t2vnn to /logs/artifacts/clusters/md-scale-6cqt8x/machines/md-scale-6cqt8x-md-win-55c44756f9-njwj9/crashdumps.tar
Jan  2 17:17:38.725: INFO: Collecting boot logs for AzureMachine md-scale-6cqt8x-md-win-t2vnn

Failed to get logs for machine md-scale-6cqt8x-md-win-55c44756f9-njwj9, cluster md-scale-o7d66m/md-scale-6cqt8x: [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  2 17:17:39.523: INFO: Collecting logs for Windows node md-scale-s2jpb in cluster md-scale-6cqt8x in namespace md-scale-o7d66m

Jan  2 17:20:23.679: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-s2jpb to /logs/artifacts/clusters/md-scale-6cqt8x/machines/md-scale-6cqt8x-md-win-55c44756f9-t97d9/crashdumps.tar
Jan  2 17:20:25.880: INFO: Collecting boot logs for AzureMachine md-scale-6cqt8x-md-win-s2jpb

Failed to get logs for machine md-scale-6cqt8x-md-win-55c44756f9-t97d9, cluster md-scale-o7d66m/md-scale-6cqt8x: [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-o7d66m/md-scale-6cqt8x kube-system pod logs
STEP: Fetching kube-system pod logs took 400.214808ms
STEP: Dumping workload cluster md-scale-o7d66m/md-scale-6cqt8x Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-md-scale-6cqt8x-control-plane-jnwcx, container etcd
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-5rnv6
STEP: Collecting events for Pod kube-system/calico-node-windows-mcxjf
STEP: Collecting events for Pod kube-system/etcd-md-scale-6cqt8x-control-plane-jnwcx
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-98wd9, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-scale-6cqt8x-control-plane-jnwcx, container kube-scheduler
STEP: failed to find events of Pod "etcd-md-scale-6cqt8x-control-plane-jnwcx"
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-scale-6cqt8x-control-plane-jnwcx, container kube-apiserver
STEP: Collecting events for Pod kube-system/calico-node-6zdgn
STEP: Collecting events for Pod kube-system/kube-apiserver-md-scale-6cqt8x-control-plane-jnwcx
STEP: failed to find events of Pod "kube-apiserver-md-scale-6cqt8x-control-plane-jnwcx"
STEP: Creating log watcher for controller kube-system/kube-proxy-2vk8v, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-79p8w, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-5rnv6, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-proxy-windows-98wd9
STEP: Collecting events for Pod kube-system/calico-node-windows-jqr4h
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-6cqt8x-control-plane-jnwcx
STEP: Creating log watcher for controller kube-system/calico-node-windows-jqr4h, container calico-node-felix
STEP: failed to find events of Pod "kube-controller-manager-md-scale-6cqt8x-control-plane-jnwcx"
STEP: Collecting events for Pod kube-system/kube-proxy-windows-79p8w
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-2w55v, container coredns
STEP: Collecting events for Pod kube-system/kube-proxy-fbbx6
STEP: Collecting events for Pod kube-system/kube-proxy-2vk8v
STEP: Creating log watcher for controller kube-system/containerd-logger-qbs44, container containerd-logger
STEP: Creating log watcher for controller kube-system/coredns-bd6b6df9f-h9lzl, container coredns
... skipping 4 lines ...
STEP: Collecting events for Pod kube-system/calico-node-xf469
STEP: Collecting events for Pod kube-system/containerd-logger-qbs44
STEP: Creating log watcher for controller kube-system/kube-proxy-fbbx6, container kube-proxy
STEP: Creating log watcher for controller kube-system/containerd-logger-zchv9, container containerd-logger
STEP: Collecting events for Pod kube-system/kube-scheduler-md-scale-6cqt8x-control-plane-jnwcx
STEP: Creating log watcher for controller kube-system/csi-proxy-mlmnk, container csi-proxy
STEP: failed to find events of Pod "kube-scheduler-md-scale-6cqt8x-control-plane-jnwcx"
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-h9lzl
STEP: Collecting events for Pod kube-system/coredns-bd6b6df9f-2w55v
STEP: Collecting events for Pod kube-system/containerd-logger-zchv9
STEP: Creating log watcher for controller kube-system/csi-proxy-zl6x4, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-windows-mcxjf, container calico-node-startup
STEP: Collecting events for Pod kube-system/csi-proxy-mlmnk
... skipping 75 lines ...
STEP: Dumping logs from the "node-drain-pjem7h" workload cluster
STEP: Dumping workload cluster node-drain-3uw41e/node-drain-pjem7h logs
Jan  2 17:19:58.181: INFO: Collecting logs for Linux node node-drain-pjem7h-control-plane-g6xlx in cluster node-drain-pjem7h in namespace node-drain-3uw41e

Jan  2 17:26:33.311: INFO: Collecting boot logs for AzureMachine node-drain-pjem7h-control-plane-g6xlx

Failed to get logs for machine node-drain-pjem7h-control-plane-txffd, cluster node-drain-3uw41e/node-drain-pjem7h: dialing public load balancer at node-drain-pjem7h-b01b0366.canadacentral.cloudapp.azure.com: dial tcp 20.175.159.141:22: connect: connection timed out
STEP: Dumping workload cluster node-drain-3uw41e/node-drain-pjem7h kube-system pod logs
STEP: Fetching kube-system pod logs took 448.48662ms
STEP: Dumping workload cluster node-drain-3uw41e/node-drain-pjem7h Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-node-drain-pjem7h-control-plane-g6xlx, container etcd
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-2cl5g, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-2cl5g
... skipping 30 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:45
  Should successfully set and use node drain timeout
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:195
    A node should be forcefully removed if it cannot be drained in time
    /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.1/e2e/node_drain_timeout.go:83
------------------------------
{"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-02T20:54:52Z"}
++ 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-02T21:09:52Z"}
{"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-02T21:09:52Z"}