Here is the JS error that is being generated when I push the "Migrate" button...
DataProvider failed to fetch data SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data DataProvider.js:35:8
l _ microtask.js:18
without a reproduced you’d need to provide a bit more info. Is there anything else in the console?
It would be best to understand which requests returned invalid data, for that you can enable the network monitoring and grab the request and response perhaps? We need to see if it’s really the migration request or anything else, and what was the actual response
Please attach your browser console log and engine.log snippet when you have the problem.
If you could dive into the console and grab the actual REST API response, that would be great.
The request will be something like <engine>/api/hosts?migration_target_of=...
It sounds like a bug. I'll talk with Michal about reverting this dialog to the 4.2 version.
This happens with all the VM's, regardless of uptime. I've never tried to migrate a VM if it's not completely up.
When I select a VM and push the "Migrate" button, I never get to the "Migrate" dialog box, I just presents the error show in the attached image.
I know for a fact that manual migration did work on this cluster, unfortunately, I don't know if it ever worked in 4.3.0 or if I was still at 4.2.8 when I last used it.
What is the VM state when you try to manually migrate it? Is the VM in the beginning of the "powering up" state?
If so then please wait 1-2 seconds and then try to migrate again and see if it is reproduced.
You can't migrate a VM on "Wait for Launch" state and once the VM enters the "powering up" state then it sometimes takes time for UI to be refreshed with state and data. It was reproduced to me too.
Greg, does it sound reasonable?
Can you please send a screenshot of the "Migrate VM(s)" dialog with th