Bug 1084940

Summary: VM's template information is inconsistent after upgrading to 3.4
Product: Red Hat Enterprise Virtualization Manager Reporter: Raz Tamir <ratamir>
Component: ovirt-engineAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: low Docs Contact:
Priority: low    
Version: 3.4.0CC: acathrow, amureini, gklein, iheim, lpeer, mavital, michal.skrivanek, ofrenkel, Rhev-m-bugs, scohen, sherold, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: ovirt-3.5.0_rc1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-14 06:48:37 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:
Bug Depends On:    
Bug Blocks: 1142923, 1156165    

Description Raz Tamir 2014-04-07 10:43:22 UTC
Description of problem:
Cloned vm from template as thin should be updated after upgrade to 3.4 to - template_name (Thin/Dependent) in VM's general information.
New cloned vms that created in 3.4 after the upgrade are marked with - template_name (Thin/Dependent).

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


How reproducible:
100%

Steps to Reproduce:
Setup 3.3 with 1 SD, 1 host
1. Create vm (in 3.3 setup)
2. make template from this vm
3. clone new vm from this template as thin
4. Upgrade engine + host to 3.4


Actual results:
In vm's general information, template: template_name

Expected results:
In vm's general information, template: template_name (Thin/Dependent)

Additional info:

Comment 3 Gil Klein 2014-08-14 06:48:37 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA