Created attachment 1221410 [details] engine and vdsm logs Description of problem: Live storage migration process is failing right after auto generated snapshot creation with: 2016-11-17 00:59:36,588 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler9) [] Correlation ID: 5de9c415, Job ID: 93f696c8-b882-4d86-a07f-1d69341ef4e8, Call Stack: null, Custom Event ID: -1, Message: Snapshot 'Auto-generated for Live Storage Migration' creation for VM 'golden_env_mixed_virtio_1_0' has been completed. 2016-11-17 00:59:37,661 ERROR [org.ovirt.engine.core.bll.CommandsFactory] (DefaultQuartzScheduler8) [5de9c415] Error in invocating CTOR of command 'LiveMigrateDisk' with parameters 'LiveMigrateDiskParameters:{comma ndId='32ae22bf-4fb5-47d0-835d-f41104371662', user='null', commandType='Unknown'}': null 2016-11-17 00:59:37,677 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (DefaultQuartzScheduler8) [5de9c415] Command 'LiveMigrateVmDisks' id: '348f31e1-faa9-4c1a-8d9a-4a5b28ec91e0' failed whe n attempting to perform the next operation, marking as FAILED '[4082405c-8edc-4fed-b7fd-7bfd5d2c4380]' 2016-11-17 00:59:37,677 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (DefaultQuartzScheduler8) [5de9c415] Command 'LiveMigrateVmDisks' id: '348f31e1-faa9-4c1a-8d9a-4a5b28ec91e0' child comm ands '[4082405c-8edc-4fed-b7fd-7bfd5d2c4380]' executions were completed, status 'FAILED' 2016-11-17 00:59:38,815 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateVmDisksCommand] (DefaultQuartzScheduler5) [5de9c415] Ending command 'org.ovirt.engine.core.bll.storage.lsm.LiveMigrateVmDisksCommand' with failure. And the disks that was selected for the migration, stuck in locked state No errors in vdsm.log Checked block and file. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 1395746 ***
Raz, I've discovered this bug yesterday and opened bug 1395746, fix was already merged yesterday so it should probably be fixed in today's nightly
Thanks Tal