Bug 1412560 - Unable to move to cluster version 4.1 with template from engine version 3.x
Summary: Unable to move to cluster version 4.1 with template from engine version 3.x
Keywords:
Status: CLOSED DUPLICATE of bug 1409579
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.1.0
Hardware: All
OS: All
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Tomas Jelinek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-12 09:57 UTC by Lukas Svaty
Modified: 2019-04-28 08:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 17:24:48 UTC
oVirt Team: Virt
Embargoed:
gklein: blocker?
lsvaty: planning_ack?
lsvaty: devel_ack?
lsvaty: testing_ack?

Attachments (Terms of Use)
Log messages generated in engine.log (6.46 KB, text/plain)
2017-01-12 09:57 UTC, Lukas Svaty 		no flags Details
View All

Description Lukas Svaty 2017-01-12 09:57:51 UTC 
Created attachment 1239838 [details]
Log messages generated in engine.log

Description of problem:
When using engine that was upgraded from 3.5->3.6->4.0->4.1 and still has 3.5 template engine fail upgrading cluster level compatibility to 4.1 
2017-01-12 10:53:23,297+01 WARN  [org.ovirt.engine.core.bll.UpdateVmTemplateCommand] (default task-15) [235ce1cb] Validation of action 'UpdateVmTemplate' failed for user admin@internal. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM_TEMPLATE,VMT_CANNOT_UPDATE_ILLEGAL_FIELD

Version-Release number of selected component (if applicable):
rhevm-4.1.0-0.3.beta2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Have engine that was upgraded since version 3.5 with template
2. When on version 4.0 try to put host to maintenance and change compatibility to 4.1

Actual results:
Error while executing action: Cannot edit Cluster. Template Tux is being exported.

Expected results:
Should succeed

Additional info:
Comment 1 Lukas Svaty 2017-01-12 10:08:33 UTC 
The same behaviour with 3.6 template within the engine, indeed you can just import this kind of template from export domain and reproduce this issue
Comment 2 Yaniv Kaul 2017-01-12 11:15:30 UTC 
Tomas - anyone can look at this?
Comment 3 Tomas Jelinek 2017-01-12 14:04:56 UTC 
It looks a lot like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1409579 

@Jakub, could you please have a look?
Comment 4 Lukas Svaty 2017-01-12 17:24:48 UTC 
After consultation with DEV, closing as duplicate as we were able to reproduce with 4.1 template

*** This bug has been marked as a duplicate of bug 1409579 ***
Note You need to log in before you can comment on or make changes to this bug.