Bug 1442701

Summary:	Database and Admin portal are not in sync
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Nirav Dave <ndave>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED NOTABUG	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	lsurette, mavital, michal.skrivanek, ndave, rbalakri, Rhev-m-bugs, srevivo, tjelinek, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-16 10:34:42 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:

Description Nirav Dave 2017-04-17 07:48:53 UTC

Description of problem:
Upgrading RHEV environment from 3.5 to 3.6,
The VMs live migrated from RHEV host 3.5 to host 3.6(In a new cluster)  is pointing to the old cluster in host 3.5 was present.

The database points to correct cluster for the VMs migrated but in admin portal the VMs are still pointing to the cluster which is use to when it was running on RHEV host 3.5


Version-Release number of selected component (if applicable):
RHEV-M 3.5 and 3.6, RHEV-H 3.5 and 3.6

How reproducible:
----------------

1)upgrade RHEV-M to 3.6 without upgrade RHEV-H and keeping the compatibility of cluster with 3.5 ...
2)then create a new cluster with compatibility mode 3.6
3)re-install one host and move it to new cluster
4)migrate the VM one by one to this host
5)re-install the other hosts to the new version

Steps to Reproduce:
------------------
Note: These are the steps performed at Customer end and it is not reproducible in test lab.
Also Customer has performed this steps for other hosts and cluster he was able to do it successfully

1)upgrade my RHEV-M to 3.6 without upgrade RHEV-H and keeping the compatibility of cluster with 3.5 ...
2)then create a new cluster with compatibility mode 3.6
3)Migrate VMs from the host which is to be upgraded to other host(3.5) in the same cluster
4)re-install the one host and move it to new cluster
5)migrate the VM one by one to this host
6)re-install the other hosts to the new version

Actual results:
---------------
The VMs which are live migrated from host(3.5) to the host(3.6) in a new cluster are not pointing to new cluster in the admin portal but they are pointing to the old cluster in which host(3.5)


Expected results:
The migrated VMs to host in new cluster should correctly point to the new cluster.

Additional info:
Please share the location where I can attach or share the logs internally.

Thanks,
Nirav Dave

Comment 2 Nirav Dave 2017-04-17 08:26:44 UTC

Hi Yaniv,

I have shared a google drive link with you. Please confirm, if you have received the same.

The logs are in three separate file file archives xaa, xab and xac. While extracting it needs to be joined.

Let me know if in case logs are not getting extracted properly

Thanks,
Nirav Dave

Comment 3 Michal Skrivanek 2017-04-18 05:08:34 UTC

(In reply to Nirav Dave from comment #0)

> 2)then create a new cluster with compatibility mode 3.6
> 3)re-install one host and move it to new cluster
> 4)migrate the VM one by one to this host

Souns like incorrect procedure. It should be 3.5 compatibility level, not 3.6