Bug 1412560

Summary: Unable to move to cluster version 4.1 with template from engine version 3.x
Product: [oVirt] ovirt-engine Reporter: Lukas Svaty <lsvaty>
Component: Backend.CoreAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, jniederm, oourfali, tjelinek
Target Milestone: ---Keywords: Regression
Target Release: ---Flags: gklein: blocker?
lsvaty: planning_ack?
lsvaty: devel_ack?
lsvaty: testing_ack?
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-12 17:24:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Log messages generated in engine.log none

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 ***