Bug 1390637 - new vm from template dialog displays "Blank -Latest" value in the Template field
Summary: new vm from template dialog displays "Blank -Latest" value in the Template field
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 15:01 UTC by Sharon Gratch
Modified: 2019-01-23 23:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-23 23:52:07 UTC
oVirt Team: Virt
tjelinek: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sharon Gratch 2016-11-01 15:01:03 UTC 
Description of problem:
In case of creating a new vm from template for the blank template (in stateless mode), one of the options to choose from in the Template listbox field is "Blank-Latest". 
This is a bug since Blank template doesn't have sub versions and therefore the "latest" version is not relevant.

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

How reproducible:
100%

Steps to Reproduce:
1.go to Templates tab->choose the Blank template and run "new vm" 
2.Open the listbox pull down menu For the Template field and see that there are two values: "Blank (0)", "Blank (latest)".

Actual results:
The "Blank (Latest)" value appears as an existing template version

Expected results:
Only the "Blank" value should appear since you can't declare subversions for Blank template

Additional info:
Comment 1 Sharon Gratch 2016-11-01 15:13:06 UTC 
The same problem also reproduced for the vms tab -> new vm dialog, in case the Stateless mode is activated for the vm.
Comment 2 Ryan Barry 2019-01-23 23:52:07 UTC 
No activity for years, and lacking field reports or capacity
Note You need to log in before you can comment on or make changes to this bug.