Hide Forgot
we want this in 3.4.z as it has a major impact +++ This bug was initially created as a clone of Bug #1064931 +++ Description of problem: MigrateVmCommand is transactive from some reason. When it is scheduling a host it also increases the pending resources on that host, thus locking the host in the DB until the execute phase is done. Since RunVm command will also tries to update the pending resources on the scheduled host, in case the scheduled host is destination host in migration process, it won't be possible to update them and the RunVm command will have to wait until the execute phase of the migration ends (which can be long in case of failures & reruns) Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Migrate VM to host X 2. Stop (with debugger) right after scheduling the host 3. Try to run another VM on host X Actual results: The run command won't end Expected results: The VM we try to run on host X need to start. Additional info: We need to get rid of the transaction in migrate commands
This is an automated message oVirt 3.4.3 has been released: * should fix your issue * should be available at your local mirror within two days. If problems still persist, please make note of it in this bug report.
*** Bug 1123079 has been marked as a duplicate of this bug. ***