Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSI migration doesn't work if intree PV doesn't have vmdk extension in file name #3060

Open
gnufied opened this issue Sep 23, 2024 · 2 comments

Comments

@gnufied
Copy link
Contributor

gnufied commented Sep 23, 2024

We have customers who have statically provisioned PVs without vmdk extension, but if the extension is missing then afaict CSI migration doesn't work - https://github.com/openshift/vmware-vsphere-csi-driver/blob/master/pkg/csi/service/vanilla/controller.go#L2257

cc @divyenpatel @xing-yang

@divyenpatel
Copy link
Member

divyenpatel commented Sep 26, 2024

@gnufied i think solution is to check if VolumeID is in UUID formar and if yes then is it fcd otherwise it is in-rree volume.

how many of such PVs customer has? can we help them patch disk and PV spec?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants