Dmitri Fedotov

Just confirmed that same is happening with latest beta 3227.1.0.

Thanks for looking at this @jepio. For now I worked this around by switching to a single vsphere disk for the affected VMs. ~On the related note, is there an...

@Champ-Goblem since you have decent testing capabilities, would you mind also reproducing this with 5.15.70 kernel? Looks that it will be in the next stable release https://github.com/flatcar/coreos-overlay/commit/ea82f1873da310245cbb174ac9fa6f9908c493c6

Hi @jknipper can we also include https://github.com/sapcc/kubernikus/pull/701? Thanks!

I have a similar use case as @rsyring. Deleting the device through `device_authorization` would also work for me. We would execute the de-auth step before re-deploying the device with same...

There is a significant movement in this direction, see milestone https://github.com/kubernetes-sigs/vsphere-csi-driver/milestone/6

Worth to mention: if multiple resources are created/destroyed in a single run, users may face an error that some resources failed to be destroyed (due to device being removed already)....

same with **google_container_engine_versions**