Bug 1437882 - VMs with compatibility version can't be started
Summary: VMs with compatibility version can't be started
Keywords:
Status: CLOSED DUPLICATE of bug 1436325
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.1.1.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-31 12:08 UTC by movciari
Modified: 2017-03-31 13:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-31 13:40:56 UTC
oVirt Team: Virt
Embargoed:


Attachments (Terms of Use)

Description movciari 2017-03-31 12:08:52 UTC
Description of problem:
If a VM has compatibility version defined, it can't be started normally, even if it's 4.1 engine, with 4.1 VDSM, 4.1 DC, 4.1 cluster and VM's compatibility version is 4.1
It can still be started by run_once, but not by run.

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

How reproducible:
always

Steps to Reproduce:
1. Create a VM in 4.1 DC, and 4.1 cluster, with a host able to run this VM
2. In create/edit VM dialog, in System tab, go to advanced parameters
3. Set the compatibility version to 4.1
4. Try to run VM, it will fail... 

Actual results:
VM fails to run

Expected results:
VM should be able to run when its compatibility version is the same as cluster compatibility version

Additional info:
run once works without any changes to any parameters

tail of log from the time when VM failed to run:
2017-03-31 14:07:42,502+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (default task-16) [d5570437-ac58-4b17-88d4-e4221979853f] Lock Acquired to object 'EngineLock:{exclusiveLocks='[78845f90-2eb5-40a6-a250-90ce07cc597d=<VM, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2017-03-31 14:07:42,528+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-16) [d5570437-ac58-4b17-88d4-e4221979853f] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{runAsync='true', vmId='78845f90-2eb5-40a6-a250-90ce07cc597d'}), log id: 27e66dc7
2017-03-31 14:07:42,528+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-16) [d5570437-ac58-4b17-88d4-e4221979853f] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 27e66dc7
2017-03-31 14:07:42,768+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-6-thread-39) [d5570437-ac58-4b17-88d4-e4221979853f] Running command: RunVmCommand internal: false. Entities affected :  ID: 78845f90-2eb5-40a6-a250-90ce07cc597d Type: VMAction group RUN_VM with role type USER
2017-03-31 14:07:42,771+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-6-thread-39) [d5570437-ac58-4b17-88d4-e4221979853f] Emulated machine 'pc-i440fx-2.6' selected since Custom Compatibility Version is set for 'VM [firstvm]'
2017-03-31 14:07:42,787+02 INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (org.ovirt.thread.pool-6-thread-39) [d5570437-ac58-4b17-88d4-e4221979853f] Candidate host '60.132' ('c7ae274f-b13a-4298-b097-9d4e5af760cb') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Emulated-Machine' (correlation id: d5570437-ac58-4b17-88d4-e4221979853f)
2017-03-31 14:07:42,787+02 ERROR [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-6-thread-39) [d5570437-ac58-4b17-88d4-e4221979853f] Can't find VDS to run the VM '78845f90-2eb5-40a6-a250-90ce07cc597d' on, so this VM will not be run.
2017-03-31 14:07:42,856+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-39) [d5570437-ac58-4b17-88d4-e4221979853f] EVENT_ID: USER_FAILED_RUN_VM(54), Correlation ID: d5570437-ac58-4b17-88d4-e4221979853f, Job ID: 47c6e2c3-3028-4d81-9937-5e551a7d7f5b, Call Stack: null, Custom Event ID: -1, Message: Failed to run VM firstvm (User: admin@internal-authz).
2017-03-31 14:07:42,915+02 INFO  [org.ovirt.engine.core.bll.ProcessDownVmCommand] (org.ovirt.thread.pool-6-thread-38) [27b36115] Running command: ProcessDownVmCommand internal: true.
2017-03-31 14:07:42,960+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-6-thread-39) [d5570437-ac58-4b17-88d4-e4221979853f] Lock freed to object 'EngineLock:{exclusiveLocks='[78845f90-2eb5-40a6-a250-90ce07cc597d=<VM, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}'
2017-03-31 14:07:45,494+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler8) [353cb844] Fetched 0 VMs from VDS 'c7ae274f-b13a-4298-b097-9d4e5af760cb'

Comment 1 Michal Skrivanek 2017-03-31 13:40:56 UTC

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


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