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

Bug 1240224

Summary:	The start time for 'migration_max_time_per_gib_mem' appears to be calculated too early.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Alexandros Gkesos <agkesos>
Component:	vdsm	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED DUPLICATE	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.1	CC:	agkesos, bazulay, ecohen, gklein, lpeer, lsurette, michal.skrivanek, ofrenkel, ppostler, ycui, yeylon
Target Milestone:	---
Target Release:	3.5.5
Hardware:	All
OS:	All
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 07:55:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexandros Gkesos 2015-07-06 09:27:36 UTC

Description of problem:

Improvement over Bug #1090109

Even in vdsm-4.16.8.1-5, we have noticed some migrations failing due to an error similar to the following;

"The migration took 132 seconds which is exceeding the configured maximum time for migrations of 128 seconds. The migration will be aborted."


On closer inspection, it appears that the start time for this parameter may be captured too soon, i.e. in this specific case the actual data transfer had only been underway for 40 seconds before 'migration_max_time_per_gib_mem' was exceeded. The reason being that it took ~87sec between getting the semaphore and the actual migration start.

We have to start counting when the actual migration starts. (after the VM disk images are prepared in the destination Host)

Version-Release number of selected component (if applicable):

RHEV 3.5.0
RHEL-H 6.6 with vdsm-4.16.8.1-8

Comment 2 Vinzenz Feenstra [evilissimo] 2015-07-13 07:39:24 UTC

Potential duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1188543
 (3.5: https://bugzilla.redhat.com/show_bug.cgi?id=1221597)

Errata: https://rhn.redhat.com/errata/RHBA-2015-1103.html

Please ask the customer to update vdsm to vdsm-4.16.20 which includes a patch to exclude the time the target needs to prepare and starts counting after that, which effectively means that it restricts it only on the migration itself now.

Comment 3 Alexandros Gkesos 2015-07-13 09:49:34 UTC

Hello Vinzenz,

I provided that info to the customer. Let's see if he still faces any migration timeout due to that.

Comment 4 Vinzenz Feenstra [evilissimo] 2015-07-13 09:52:09 UTC

Resetting the needinfo on you until you have a reply from the customer, thanks for the understanding.

Comment 5 Michal Skrivanek 2015-07-29 11:37:58 UTC

ping, any news?

Comment 6 Alexandros Gkesos 2015-07-29 15:08:44 UTC

Hello Michal,

Customer is a bit idle at the moment. If the fix is included in vdsm-4.16.20 you can close the Bug and i will re-open it in case customer upgrades and still faces the same issue.

Thank you

Comment 7 Vinzenz Feenstra [evilissimo] 2015-08-05 07:47:03 UTC

Please keep the needinfo until the customer responds, thank you.

Comment 8 Michal Skrivanek 2015-08-05 07:55:51 UTC

ok, please reopen if still relevant

*** This bug has been marked as a duplicate of bug 1221597 ***