Hitting `Unavailable desc = transport is closing` after kubelet restarted

[LetaoCh]

What happened: After kubelet restarted, the device plugin manager is supposed to re-register itself but we are still seeing error messages like Unavailable desc = transport is closing when sending the device list to kubelet after kubelet restarts. It doesn't happen every time but approximately once every 2-3 times.

What you expected to happen: Such an error message should not happen if the re-registration is successful.

How to reproduce it (as minimally and precisely as possible): Deploy a plugin and restart kubelet.

Additional context: N/A

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

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale