Description of problem: In Create VM wizard dialog, Import, under VMs field, VMware VMs, as well as Templates are listed. Therefore, it is more reasonable to name the field something like: "VMs & Templates". Version-Release number of selected component (if applicable): bundle-registry:v2.0.0-33
Please correct me, but I think the proposed fix could be confusing for the user, since we are in "Create VM" dialog. If source object is a VMware template (not a VM), the user could expect a "VM Template" to be imported. To fully close the gap, we should differentiate between these two by adding the "Import" to the "Create Template" wizard. That would need extra work and thinking, so I doubt such a change would be acked as bugfix, means it's out of 2.1 scope. But I might be wrong .... As a good enough fix for 2.1, we can list only VMware VMs (excluding templates). This can be filtered out on the "kubevirt-vmware" operator level.
On the second thought, recent combination of VMs and templates has been documented and removing would cause a regression. The user is in "Create Virtual Machine" wizard, so a VM is expected as a result.
Patch: https://github.com/kubevirt/web-ui-components/pull/529
Since the v2v has been removed from 2.1.0, retargeting bugs to 2.1.1 to make sure they will be verified on the right version.
Mooving to ON_QA.
please add fixed in version
Merged on Jul 30, so should be included in 4.2.0-0.ci-2019-08-02-184554/
Created attachment 1643844 [details] Screenshot (fixed)
Verified as fixed in version: CNV 2.2.0-10 VMs and templates are listed in list named: "VM or Template to Import" Attached screenshot.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0307