Bug 1678007

Summary:	When importing a VM override its cluster level to match the cluster it is imported to
Product:	[oVirt] ovirt-engine	Reporter:	Benny Zlotnik <bzlotnik>
Component:	BLL.Storage	Assignee:	Andrej Krejcir <akrejcir>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tamir <tamir>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.0	CC:	akrejcir, bugs, dfodor, frolland, mavital, michal.skrivanek, mtessun, rdlugyhe, sgoodman, smelamud, tnisan
Target Milestone:	ovirt-4.4.0	Flags:	tamir: needinfo+ pm-rhel: ovirt-4.4+ mtessun: planning_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-4.4.0-28	Doc Type:	Bug Fix
Doc Text:	Before this update, you could import a virtual machine from a cluster with a compatibility version lower than the target cluster, and the virtual machine's cluster version would not automatically update to the new cluster's compatibility version, causing the virtual machine's configuration to be invalid. Consequently, you could not run the virtual machine without manually changing its configuration. With this update, the virtual machine's cluster version automatically updates to the new cluster's compatibility version. You can import virtual machines from cluster compatibility version 3.6 or newer.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-05 06:10:06 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:
Bug Depends On:
Bug Blocks:	1740978

Description Benny Zlotnik 2019-02-17 14:48:02 UTC

Description of problem:
When importing a VM we should override its cluster level to match the compatibility level of the cluster it is imported to in order to have flows related to this VM behave properly and according to its cluster level


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tal Nisan 2019-04-30 06:17:37 UTC

Benny, what's the status here? The patch is pending for a month now and got a -1, do we have another suggested solution?

Comment 2 Benny Zlotnik 2019-04-30 07:37:21 UTC

Michal, should we move this to virt?

Comment 3 Michal Skrivanek 2019-04-30 07:40:52 UTC

indeed

Comment 4 RHEL Program Management 2019-09-25 20:55:52 UTC

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 5 RHV bug bot 2020-01-24 19:49:13 UTC

INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Tag 'ovirt-engine-4.4.0' doesn't contain patch 'https://gerrit.ovirt.org/104859']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.4.0

For more info please contact: infra

Comment 9 Tamir 2020-06-02 10:01:42 UTC

Verified on RHV 4.4.1-1 and RHEL 8.1 hosts. 

I ran all test cases from the attached Polarion requirement and all the tests passed.

Comment 10 Sandro Bonazzola 2020-08-05 06:10:06 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.