Description of problem: if you create a vm based on a template which was imported from an export domain the template which is shown under "General" tab when you select this new vm reads "Blank" when it should be e.g. "ubuntu-server-12.04" Version-Release number of selected component (if applicable): ovirt engine 3.3.3-2.el6 How reproducible: always Steps to Reproduce: 1. import template from export domain 2. create new vm based from this template 3. check the template, which is shown in info tab for the vm or check it via REST-API Actual results: wrong template "blank" is shown Expected results: the correct template name gets reported Additional info: you also can not see that these vms got deployed by using this template when you click on this template in the template overview and then select the subtab "virtual machines" This might be an regression and this might even still be in 3.4. (didn't test it yet)
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
I am guessing that you created the vm using the 'Clone' option under 'Resource Allocation' tab in the 'Add VM' dialog (this setting is marked by default if you select 'Optimized for Server' in the upper pane of this dialog. can you please confirm this? try to create VM and change the resource allocation from Clone to Thin, or choose 'Desktop' under 'Optimized for' When vm is Cloned from template, it is not linked anymore to the template disks, this is why we show 'Blank' and you don't see the vm under the template. In 3.4 we enhanced to show the original template even when Cloning, please see bug 1042784 for more info on that.
You are right, we provisioned the vm using "clone". So you might be right. Thanks for pointing to the bug which fixes this in 3.4. BTW: Is there already any planning regarding 3.4.1 ?
Additional question which comes to my mind: Does bz 1042784 also take care of the REST-API? Because you also get the blank template via REST when you query this vm.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
yes, it fixes the issue in the backend which is common for UI and REST. It should work in 3.4:)