After I removed one of csi smb-node pods I got error, Volume ID is already exist

[Israel-Shav]

What happened:
I suddenly got error that liveness probe container is lost connection with unix://csi/csi.sock.
I tried to restart the pod(smb-node daemonset) by deleting it but it stucked on terminate state so I forcefully removed it.
After it has been redeployed the lost connection error is gone but when I tried to redeploy some pv that was deployed on cluster I got other error "... given Volume ID ##** already exist".
Even if I added some suffix to VolumeHandle I got same error.

What you expected to happen:
Restart daemonset will not stop the pods on terminated state

How to reproduce it:

1. Restart daemonset
2. Forcefully delete the daemonset(smd-node) pod that stuck on terminate state
3. After daemonset pods come back to life, deploy again the pv that was on cluster when daemonset pod removed

Environment:
I installed it on other namespace called csi-driver-smb

• CSI Driver version: 1.16.0
• Kubernetes version: 1.28.3+vmware.wcp

[andyzhangx]

"... given Volume ID ##** already exist". error means that the first smb mount is stuck there, you may try smb mount manually on the node to narrow down the issue.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale