Bug 1421586 - fail to migrate VMs with custom_compatibility_version=3.6 after updating engine and host to 4.1.0.4
Summary: fail to migrate VMs with custom_compatibility_version=3.6 after updating engi...
Keywords:
Status: CLOSED DUPLICATE of bug 1421174
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.0.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-13 08:01 UTC by Denis Prezhevalsky
Modified: 2017-02-13 08:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-13 08:13:15 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)

Description Denis Prezhevalsky 2017-02-13 08:01:11 UTC
Description of problem:
After upgrading engine with 4.1 and host in cluster with 4.19.4, and trying to migrate VMs with custom_compatibility_version=3.6 from other (not yet updated) hosts, getting error, i.e.:
alee-f24-ipa:
Cannot migrate VM. There is no host that satisfies current scheduling constraints. See below for details:
The host dell-r420-01 did not satisfy internal filter Compatibility-Version because it doesn't support compatibility version '3.6' which is required by the VM. Host supported compatibility versions are: 4.0,4.1..


Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0.4-0.1.el7.noarch
vdsm-4.19.4-1.el7ev.x86_64

How reproducible:
Update engine and single host with 4.1, migrate vm (which have custom_compatibility_version=3.6 set) from not updated host to updated host.

Steps to Reproduce:
1.
2.
3.

Actual results:
Cannot migrate VM. There is no host that satisfies current scheduling constraints. See below for details:
The host dell-r420-01 did not satisfy internal filter Compatibility-Version because it doesn't support compatibility version '3.6' which is required by the VM. Host supported compatibility versions are: 4.0,4.1..

Expected results:
Successfull migration.

Additional info:
The workaround is to add "3.6" to 'supportedENGINEs' in /usr/lib/python2.7/site-packages/vdsm/dsaversion.py :

version_info = {
    'version_name': version_name,
    'software_version': software_version,
    'software_revision': software_revision,
    'a': ['3.6', '4.0', '4.1'],
    'clusterLevels': ['3.6', '4.0', '4.1'],
}

Comment 1 Arik 2017-02-13 08:13:15 UTC

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


Note You need to log in before you can comment on or make changes to this bug.