hypervisor selection issue at VMware migration

[ingox]

problem

I have two hypervisors in my environment (KVM1 and KVM2).
I prepared KVM1 with all the tools and packages needed for VMware to KVM migration including packages needed for Windows VMs. See here: https://www.shapeblue.com/cloudstack-vmware-to-kvm-migration-tool/
In the dialog for starting the conversion I select KVM1 for the conversion (just tick the box in front of second line - no change in the drop down field).

Right after starting the conversion I'm getting the following error:

Here you can see KVM2 was chosen.

Workaround to get it working:
I'm selecting KVM2 and then back KVM1. That makes the code to work with KVM1.

versions

4.20.1.0

The steps to reproduce the bug

1. Setup two hypervisors in your env.
2. Prepare the first HV with all the tools needed for conversion.
3. Select a VM for conversion.
4. Select option to use a specific hypervisor - don't change drop down field

...

What to do about it?

No response

[DaanHoogland]

Marking this as a UI issue as I think this is a problem of the form not copying the value from the dropdown when it has not changed yet. cc @shwstppr @nvazquez , makes sense?

[sureshanaparti]

@ingox Can you select both conversion and import host as KVM1 and check? Conversion host does the actual conversion using virt-v2v (and virtio-win required for Windows). As the conversion host not selected (as shown in the screenshot in the description), it is picking one of available hosts, so better choose it from the UI.

[ingox]

That works directly.

################################################################

[abh1sar]

@sureshanaparti does this need any work?

[sureshanaparti]

@abh1sar I think, no changes required as the conversion host is not selected before. Also, once virt-v2v is installed, agent needs to be restarted to populate the virt-v2v details in the host, with which the the right host with the tools installed is auto picked for the conversion if no host is selected.

[abh1sar]

Thanks @sureshanaparti
converting this to discussion and marking your comment as answer.

[abh1sar]

I think, no changes required as the conversion host is not selected before. Also, once virt-v2v is installed, agent needs to be restarted to populate the virt-v2v details in the host, with which the the right host with the tools installed is auto picked for the conversion if no host is selected.