Bug 1111176

Summary:	Creating vm from template Menu has options that are redundant (Special Case: Crossed domain template)
Product:	[Retired] oVirt	Reporter:	Ori Gofen <ogofen>
Component:	ovirt-engine-webadmin	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED NOTABUG	QA Contact:	Aharon Canan <acanan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	acanan, acathrow, amureini, bugs, derez, ecohen, gklein, iheim, mgoldboi, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-26 15:22:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ori Gofen 2014-06-19 12:01:46 UTC

Description of problem:

This bug is a special case of BZ #1101003 (see description)

A "Crossed domain template"(not a real term just to simplify the explanation) is a template that was created from a vm which had a raw sparse disk (nfs thin disk for example) and then was copied to a Block domain.

Creating vm from a "crossed domain template" Menu has redundant option.
choosing create vm as clone on block domain should give us just one choice  (preallocated).


Version-Release number of selected component (if applicable):
alpha2 build

How reproducible:
100%

Steps to Reproduce:
1.create vm+thin file disk
2.create template from this vm
3.copy template to block domain
4.add a new vm from template,choose the "crossed domain template"
5.browse to Resource Allocation,choose the options:block domain,clone

Actual results:
Two options to create are displayed,thin and preallocate

Expected results:
Should be only one,preallocate

Additional info:

Comment 1 Tal Nisan 2014-08-26 15:22:14 UTC

The logic is when you choose to create thin provision disk in a block device, it will be created as cow sparse even if it was copied from a file domain's raw sparse disk, for preallocated it will be created as raw preallocated thus both options are legal