Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1097332

Summary: The start time for 'migration_max_time_per_gib_mem' appears to be calculated too early.
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Vinzenz Feenstra [evilissimo] <vfeenstr>
Status: CLOSED ERRATA QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: urgent    
Version: 3.3.0CC: bazulay, flo_bugzilla, iheim, jentrena, lpeer, mavital, michal.skrivanek, mkalinin, sbonazzo, sherold, tdosek, tpoitras, yeylon
Target Milestone: ---Keywords: Regression, ZStream
Target Release: 3.4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the start time for data migrations was being captured too early. This caused data migrations to abort earlier than the configured maximum time for migrations. Now, the timer only starts once the data transfer begins. As a result, the maximum time for migration transfers is implemented accurately.
Story Points: ---
Clone Of: 1090109
: 1097341 (view as bug list) Environment:
Last Closed: 2014-06-09 13:30:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1090109, 1097298    
Bug Blocks: 1097341    

Comment 5 meital avital 2014-05-26 09:11:34 UTC
-build is av9.2 installed
-reducing the time out in order to reproduced the problem for 1gb ram.
-bug fixed.
-migration time not not expired, multiple migration pass (tested on 6 vms, as customer described).
-code fix in vm.py located.

Comment 7 errata-xmlrpc 2014-06-09 13:30:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0504.html