Description of problem: The user is able to select VMware machine with snapshosts for import. This is however not supported by virt-v2v and the import will fail. The user should be notified that the selected VM has snapshots and the import should be prevented. Version-Release number of selected component (if applicable): oVirt 3.6 How reproducible: always Steps to Reproduce: 1. Select 'Virtual Machines' tab and press 'Import' 2. Select 'VMware' as source and fill in the connection information 3. Press 'Load' and from the list of machines select VM with snapshots and import it Actual results: The import will end with an error. Expected results: The import should be prevented and user has to be told that the VM contains snapshots. Additional info:
Best would be to grey out the VM names reported with snapshots. This may not make sense with lazy loading, then indeed it should not allow you to continue when such a VM is selected
(In reply to Michal Skrivanek from comment #1) > Best would be to grey out the VM names reported with snapshots. I aggree. Also it would be worth doing the same thing for the running VMs as noted in: https://bugzilla.redhat.com/show_bug.cgi?id=1296222 Better to grey things out than to hide them IMHO. > This may not > make sense with lazy loading, then indeed it should not allow you to > continue when such a VM is selected You can give the user the oportunity to select any VM in the first dialog (the one with names) and gray things out (plus prevent the import) in the second dialog (with the details). Then the user can either go back and unselect the VMs in question in the first dialog. Or stop VMs/merge snapshots in vCenter and then press 'Update' button (which we don't have now ;)) in the second dialog to refresh the state in the engine.
let's not track that as RFE, it's a small improvement
We do want to remove the filter in vdsm for Block devices on Xen and VMs that we failed to read the disks devices.
oVirt 4.1.0 GA has been released, re-targeting to 4.1.1. Please check if this issue is correctly targeted or already included in 4.1.0.
It should be targeted to 4.1.1 (it's not included in 4.1.0), thanks.
Verification build: ovirt-engine-4.1.2-0.1.el7 vdsm-4.19.11-1.el7ev.x86_64 libvirt-client-2.0.0-10.el7_3.5.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.9.x86_64 sanlock-3.4.0-1.el7.x86_64 Test case changes accordingly (added to external trackers).