Bug 1677361 - Unsupported custom compatibility version check for VMs is not working
Summary: Unsupported custom compatibility version check for VMs is not working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.3.1
: ---
Assignee: Simone Tiraboschi
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-14 15:59 UTC by Simone Tiraboschi
Modified: 2020-05-28 09:42 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-01 10:20:18 UTC
oVirt Team: Integration
Embargoed:
aoconnor: ovirt-4.3+
mtessun: blocker+
pmatyas: testing_plan_complete-
mtessun: planning_ack+
sbonazzo: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 97772 0 master MERGED upgrade: correctly check for VMs custom comp. versions 2020-06-09 13:49:22 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.