Bug 1368620

Summary:	Cannot set cluster to 4.0 after migration from 3.6
Product:	[oVirt] ovirt-engine	Reporter:	Jiri Belka <jbelka>
Component:	BLL.Infra	Assignee:	Martin Perina <mperina>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.0.2.7	CC:	bugs, jbelka, oourfali, ylavi
Target Milestone:	ovirt-4.0.4	Flags:	ylavi: ovirt-4.0.z? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-22 13:35:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Belka 2016-08-20 05:55:39 UTC

Description of problem:

~~~
Error while executing action Edit Cluster properties: Internal Engine Error
~~~


2016-08-20 01:43:12,955 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-15) [2024893] Correlation ID: 31c1c13e, Call Stack: null, Custom Event ID: -1, Message: Failed to
 update Host cluster (User: admin@internal)


Version-Release number of selected component (if applicable):
ovirt-engine-4.0.2.7-0.1.el7ev.noarch

How reproducible:
just happened and can't solve it

Steps to Reproduce:
1. unknown
2.
3.

Actual results:
cannot set cluster to 4.0 after migration from 3.6

Expected results:
should work

Additional info:

Comment 2 sefi litmanovich 2016-08-21 15:48:41 UTC

Hi Jiri,

Can you explain exactly what your flow was and maybe which versions?
I was able to upgrade a cluster from 3.6 to 4.0 but not after rhevm upgrade, but internally in rhevm-4.0 - created a 3.6 cluster with 3.6 hosts - then after working with some vms upgraded the hosts to 4.0 one by one and eventually set cluster to 4.0.

Comment 3 Jiri Belka 2016-08-21 21:10:20 UTC

(In reply to sefi litmanovich from comment #2)
> Hi Jiri,
> 
> Can you explain exactly what your flow was and maybe which versions?
> I was able to upgrade a cluster from 3.6 to 4.0 but not after rhevm upgrade,
> but internally in rhevm-4.0 - created a 3.6 cluster with 3.6 hosts - then
> after working with some vms upgraded the hosts to 4.0 one by one and
> eventually set cluster to 4.0.

Sure it worked even for me but this issue is mostly probably related to fact that this env used to be - IIRC - 3.0 -> 3.5, than migration from bare metal to SHE env in 3.5, then 3.5 -> 3.6 -> 4.0.

So it has its own history which probably caused all the issues, this is not only one.

Comment 4 Oved Ourfali 2016-08-22 06:07:48 UTC

Can you give us the access to the relevant environment?

Comment 6 Martin Perina 2016-08-22 13:35:18 UTC

Looking at the logs the exception is the same as in BZ1367025

*** This bug has been marked as a duplicate of bug 1367025 ***