Mike Russell

@ibrokethecloud thanks for responding to all of those questions :smile: ! Working through this with vSphere initally I have noticed some operation failures in Tasks and opened this issue: https://github.com/harvester/harvester/issues/2879

Also working through more vSphere testing noticing this issue as well: https://github.com/harvester/harvester/issues/2880

And this seems to be a smaller issue as I don't think it's really effecting the functionality of the import: https://github.com/harvester/harvester/issues/2881

@ibrokethecloud **1. Question: Should VM Import respect the default StorageClass used? - as in, while importing a VM that VM's disk - images - volumes, they should all be using...

@ibrokethecloud for, "Question 2" from this comment the other day: https://github.com/harvester/harvester/issues/2274#issuecomment-1266220335 I opened: https://github.com/harvester/harvester/issues/2890#issue-1400437398

I'm not 100% if it's easy to reproduce but I've seen a few mixed things with importing a large OpenStack VM: > level=error msg="error syncing 'default/massive-disk-filled-vm': handler virtualmachine-import-job-change: error exporting...

@ibrokethecloud working through a few tests, I do notice that if we try to remove and rebuild a VirtualMachineImport in fairly quick order, there seems to be a bit of...

@ibrokethecloud regarding the testing, I've validated the following scenarios with v1.1.0-rc2: 1. VM Import Can Happen Successfully For Single Node w/ OpenStack 1. VM Import Can Happen Successfully For Single...

@futuretea I've been working to try to validate this. Following some of the [testing steps](https://github.com/harvester/harvester/pull/2358#issue-1263010285) that have been highlighted, I've encountered this error when trying to upgrade from v1.0.3 -...

@futuretea thank you for outlining these elements for me :smile: ### compatibility validations: As I worked through validating this - all things related to `Test Plan for copmatiblity` look good....