Bug 1677361

Summary:	Unsupported custom compatibility version check for VMs is not working
Product:	[oVirt] ovirt-engine	Reporter:	Simone Tiraboschi <stirabos>
Component:	Setup.Engine	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.3.0	CC:	bugs, mtessun, stirabos
Target Milestone:	ovirt-4.3.1	Keywords:	NeedsTestCase
Target Release:	---	Flags:	aoconnor: ovirt-4.3+ mtessun: blocker+ pmatyas: testing_plan_complete- mtessun: planning_ack+ sbonazzo: devel_ack+ lsvaty: testing_ack+
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:	2019-03-01 10:20:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Simone Tiraboschi 2019-02-14 15:59:10 UTC

Description of problem:
Unsupported custom compatibility version check for VMs is not working:
the user is allowed to upgrade from 4.2 to 4.3 even with VMs with custom compatibility version 3.6 or 4.0 which are not supported anymore in 4.3.

The user cannot migrate or open the console of that VMs until he poweroff them and restart them with a supported custom compatibility version.

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


How reproducible:
100%

Steps to Reproduce:
1. deploy 4.2 with running VMs with custom compatibility version 3.6 or 4.0
2. upgrade to 4.3
3. try to migrate on of the VMs with custom compatibility version 3.6

Actual results:
The user is allowed to upgrade but the VMs are not really managed byt the engine until the got restarted with the right custom compatibility version but this is not so intuitive.

Expected results:
The user is prevented from upgrading until he set all the VMs to the right custom compatibility version.

Additional info:
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1436577

Comment 2 Petr Matyáš 2019-02-25 15:08:41 UTC

Verified on ovirt-engine-4.3.1.2-0.0.master.20190222171227.gita00fd1d.el7.noarch

Comment 4 Sandro Bonazzola 2019-03-01 10:20:18 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 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.

Comment 5 Simone Tiraboschi 2020-05-28 09:42:35 UTC

Removing old need info.