Bug 1097332 - The start time for 'migration_max_time_per_gib_mem' appears to be calculated too early.
Summary: The start time for 'migration_max_time_per_gib_mem' appears to be calculated ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.3.0
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
: 3.4.0
Assignee: Vinzenz Feenstra [evilissimo]
QA Contact: meital avital
URL:
Whiteboard: virt
Depends On: 1090109 1097298
Blocks: 1097341
TreeView+ depends on / blocked
 
Reported: 2014-05-13 15:01 UTC by rhev-integ
Modified: 2019-04-28 08:37 UTC (History)
13 users (show)

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.
Clone Of: 1090109
: 1097341 (view as bug list)
Environment:
Last Closed: 2014-06-09 13:30:49 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 869483 0 None None None Never
Red Hat Knowledge Base (Solution) 873473 0 None None None Never
Red Hat Product Errata RHBA-2014:0504 0 normal SHIPPED_LIVE vdsm 3.4.0 bug fix and enhancement update 2014-06-09 17:21:35 UTC
oVirt gerrit 27135 0 None None None Never
oVirt gerrit 27637 0 None MERGED virt: Capture migration start time after the semaphore was accquired Never

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
Note You need to log in before you can comment on or make changes to this bug.