Hide Forgot
several issues with migration has been identified based on users feedback The core algorithm dealing with migration is getting outdated (new qemu options, VMs are in general larger), this bug is tracking refactoring of the core migration functionality in vdsm and engine
*** Bug 1034871 has been marked as a duplicate of this bug. ***
*** Bug 1043809 has been marked as a duplicate of this bug. ***
*** Bug 1034893 has been marked as a duplicate of this bug. ***
adding bug 1255474 for management communication resilience in overload conditions
*** Bug 1059886 has been marked as a duplicate of this bug. ***
*** Bug 1227967 has been marked as a duplicate of this bug. ***
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
see https://access.redhat.com/solutions/744423 for more details about tuning migration until this RFE is implemented
*** Bug 1275476 has been marked as a duplicate of this bug. ***
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
*** Bug 1349530 has been marked as a duplicate of this bug. ***
*** Bug 596062 has been marked as a duplicate of this bug. ***
Verify with: Engine version: 4.0.2.3-0.1.el7ev Host: OS Version:RHEL - 7.2 - 9.el7_2.1 Kernel Version:3.10.0 - 327.22.2.el7.x86_64 KVM Version:2.3.0 - 31.el7_2.20 LIBVIRT Version:libvirt-1.2.17-13.el7_2.5 VDSM Version:vdsm-4.18.5.1-1.el7ev SPICE Version:0.12.4 - 15.el7_2.1 Test cases: Functional testing: 1. Regression: Sanity testing to verify migration works properly. 2. Web Admin: Verify the all action from RHEVM/Ovirt UI are performed as expected. 3. API: Check REST API, verify that configuration and actions are done properly via API. 4. Guest hook: Test new guest hooks, before and after migration. 5. Define custom policies / changing existed policies System integration: Test migration behavior integration with other RHEVM features. like: QoS, host/s maintenance... Performance testing - work-loads testing: Test migration under different types on memory load. In those test cases we will use pig load tool (see polarion test plan) Results : PASS