Add Import VM functionality in more prominent location such as under the Virtual Machines tab. Currently, in order to Import a VM, the end user has to go through the Storage tab, then click on an Export domain, now click on the VM Import tab and then on the Import button Version-Release number of selected component (if applicable): 3.5 vt4 How reproducible: 100%
Einav, your two cents on this?
Created attachment 984920 [details] Import VM
(In reply to Allon Mureinik from comment #1) > Einav, your two cents on this? I was under the impression that we already have an Import VM functionality from within the VMs main tab (see attachment 984920 [details] to see the Import VM availability from the Storage main tab, as mentioned in Comment #0, as well as from the VMs main tab, as requested in Comment #0). @Allon/Gilad - am I missing something?
Created attachment 987699 [details] VM import options on the NFS export domain and the options under the Virtual Machines tab
Thanks, Gilad. @Allon - the option to Import a VM via the VMs main tab seems to be included in oVirt master (3.6) (attachment 984920 [details]) but not in RHEV 3.5 (attachment 987699 [details]) - does this feature exists only in 3.6 (if so - BZ should probably move to MODIFIED)? Only in upstream (if so - why isn't it in downstream)? thanks.
True - this was done, recently, in oVirt Engine upstream master (http://gerrit.ovirt.org/#/c/29381/). Moving to MODIFIED, as, like Einav stated, this is fixed for 3.6.
Created attachment 1021668 [details] Screenshots Added screenshots
Verified with version: ------------------------ v3.6 ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch vdsm-4.17.0-632.git19a83a2.el7.x86_64 Verified using the following scenario: --------------------------------------- Steps to reproduce: 1. Via the VM tab in the Web Admin > Find the Import option > The option is now available and when pressed opens up the Import VM dialog. Adding screenshots of the Import option which is now available in the VM tab Moving to Verified!
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://rhn.redhat.com/errata/RHEA-2016-0376.html