For host-assisted cloning, the source pod Unexpected status code 500

[mengkai514]

What happened:
When I was doing host-assisted clone, I encountered that source-pod unexpectedly exited when the progress reached 100.

What you expected to happen:
Clone succeed.

How to reproduce it (as minimally and precisely as possible):
kubectl describe xxx-source-pod Containers: cdi-clone-source: Container ID: containerd://1996ee442f46f06dd02e5252a59918af54db88c364df1b28675dc6b244f5eb6c Image: registry.paas/mengkai/cdi-cloner:v1.54.0 Image ID: registry.paas/mengkai/cdi-cloner@sha256:a78700447375afd1b1c61a59482c07e0c2896f97b1a07eac64be9177173eb234 Port: 8443/TCP Host Port: 0/TCP State: Running Started: Mon, 16 Dec 2024 16:07:44 +0800 Last State: Terminated Reason: Error Exit Code: 255 Started: Mon, 16 Dec 2024 13:54:13 +0800 Finished: Mon, 16 Dec 2024 16:07:43 +0800 Ready: True Restart Count: 1

And the logs:
I1216 08:07:39.447438 8 prometheus.go:72] 99.99
I1216 08:07:40.305556 8 clone-source.go:128] Wrote 2147483648000 bytes
I1216 08:07:40.448575 8 prometheus.go:72] 100.00
F1216 08:07:43.807066 8 clone-source.go:235] Unexpected status code 500
goroutine 1 [running]:
kubevirt.io/containerized-data-importer/vendor/k8s.io/klog/v2.stacks(0x1)
vendor/k8s.io/klog/v2/klog.go:1038 +0x8a
kubevirt.io/containerized-data-importer/vendor/k8s.io/klog/v2.(*loggingT).output(0x14b21a0, 0x3, 0x0, 0xc0003660e0, 0x0, {0x109f83b?, 0x1?}, 0xc00067ca80?, 0x0)
vendor/k8s.io/klog/v2/klog.go:987 +0x5fd
kubevirt.io/containerized-data-importer/vendor/k8s.io/klog/v2.(*loggingT).printf(0x12?, 0x4600b?, 0x0, {0x0, 0x0}, {0xd3431d, 0x19}, {0xc00067ca80, 0x1, 0x1})
vendor/k8s.io/klog/v2/klog.go:753 +0x1c5
kubevirt.io/containerized-data-importer/vendor/k8s.io/klog/v2.Fatalf(...)
vendor/k8s.io/klog/v2/klog.go:1532
main.main()
cmd/cdi-cloner/clone-source.go:235 +0xbfa

Additional context:
Add any other context about the problem here.

Environment:

• KubeVirt version (use virtctl version): N/A
• Kubernetes version (use kubectl version): N/A
• VM or VMI specifications: N/A
• Cloud provider or hardware configuration: N/A
• OS (e.g. from /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Others: N/A

[brianmcarey]

Raised at the kubevirt community meeting and appears to me more related to CDI so the issue has been transferred to CDI.

[akalenyu]

I've addressed this in the PR:
#3574 (review)
Thank you for opening the issue