Alexander Wels
Alexander Wels
/remove-lifecycle stale
So if I understand this correctly the CSI driver cannot find the VMI, because it no longer exists due to the drain on the infra node, and a new VMI...
Okay, so if you recreate the VMI then simply ignoring the error would be correct, but if someone live migrates the node, then I am not sure if simply ignoring...
I just checked the `getVMNameByCSINodeID` [function](https://github.com/kubevirt/csi-driver/blob/main/pkg/service/controller.go#L422-L436) and it looks up the VMI by `vmi.Spec.Domain.Firmware.UUID` not by name or anything like that. So a live migration this should not error at...
Just digging a little deeper, the nodeID is the `node.Status.NodeInfo.SystemUUID` maybe we should look for `node.status.volumesAttached` instead? and if not found, should be like okay, we already detached the volume.
The name of the attached volume in the status is part csi driver name and part volume name, so I would match on both csi driver and volume name.
/remove-lifecycle stale
/remove-lifecycle rotten
/remove-lifecycle rotten
/lifecycle frozen