Bug 1068679

Summary:	[BUG] Create new VM from imported template, template info for VM shows template blank
Product:	[Retired] oVirt	Reporter:	Sven Kieske <s.kieske>
Component:	ovirt-engine-core	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.3	CC:	acathrow, gklein, iheim, michal.skrivanek, ofrenkel, s.kieske, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-03 14:40:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sven Kieske 2014-02-21 16:26:54 UTC

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)

Comment 1 Itamar Heim 2014-02-23 08:28:23 UTC

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.

Comment 2 Omer Frenkel 2014-02-23 11:25:18 UTC

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.

Comment 3 Sven Kieske 2014-02-24 08:26:27 UTC

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 ?

Comment 4 Sven Kieske 2014-02-24 08:27:50 UTC

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.

Comment 5 Sandro Bonazzola 2014-03-04 09:28:52 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 6 Michal Skrivanek 2014-04-03 14:40:44 UTC

yes, it fixes the issue in the backend which is common for UI and REST. It should work in 3.4:)