Description of problem: when we try to import a vm that it's template no longer exists in both setup and export domain we are getting a message which does not really convey to the user that the vm cannot be used without the template and that the template does not exist in both export and setup. this is the warning that we get for a vm that has the template in the export domain but not the setup: Some imported VMs depend on one or more templates which are not available in the system. Therefore you must Import those VMs with 'collapse snapshots', another option is to Import missing templates first and then try import the VMs again this is the warning that we get for a vm that it's template no longer exist at all: One of the templates cannot be found in the system, VM(s) cannot be imported Version-Release number of selected component (if applicable): sf17 How reproducible: 100% Steps to Reproduce: 1. export a vm depended on template and remove the template from the setup and export domain 2. try to import 3. Actual results: we are getting an error: One of the templates cannot be found in the system, VM(s) cannot be imported Expected results: 1. it took me about 30 minutes to realize that the template was removed from the setup and the export domain (mainly because I have a template with a similiar name but a different UUID). 2. the use of the word "system" in case the template does not exist only in the setup and in case the template does not exist al all is very confusing... Additional info:
The GUI message of "One of the templates cannot be found in the system, VM(s) cannot be imported" is executed at ImportVmModel#onSuccess We can add the missing UUID in the warnning message, but I'm not sure the user seeing guid values is a good user experience... The other approach is to move the validation from the GUI to the backend, but that could have impact on latency (network to the server and back)
I believe this can be solved with better text (instead of adding the missing UUID or move the validation to the backend), something like: "VM(s) cannot be imported: One of the templates cannot be found. Please verify that the template exists in both setup and export domain."
Merged with the suggested solution by Sean
No issues are found Verified, tested on RHEVM 3.3 - IS6 environment: RHEVM: rhevm-3.3.0-0.9.master.el6ev.noarch VDSM: vdsm-4.12.0-rc1.12.git8ee6885.el6.x86_64 LIBVIRT: libvirt-0.10.2-18.el6_4.9.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64 SANLOCK: sanlock-2.6-2.el6.x86_64
Closing - RHEV 3.3 Released