Bug 1078793

Summary:	ovirt-3.3 backport for max migration timeout introduced wrong variable name
Product:	[Retired] oVirt	Reporter:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Component:	vdsm	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Gil Klein <gklein>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.3	CC:	acathrow, bazulay, danken, eedri, flo_bugzilla, gklein, iheim, jentrena, jkt, lpeer, lyarwood, mavital, mgoldboi, michal.skrivanek, pbandark, pstehlik, rhev-integ, sbonazzo, sputhenp, vfeenstr, yeylon
Target Milestone:	---
Target Release:	3.3.5
Hardware:	All
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1069220	Environment:
Last Closed:	2014-05-08 14:17:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1069220

Description Vinzenz Feenstra [evilissimo] 2014-03-20 10:33:33 UTC

In the backport of http://gerrit.ovirt.org/#/c/25022/ there was a bug introduced by using the variable name 'migration_progress_timeout' which was not part of the backport in config.py.

This causes the Migration monitor thread to prematurely exit.

Comment 1 Sandro Bonazzola 2014-05-08 14:17:10 UTC

This is an automated message

oVirt 3.3.5 has been released:
 * should fix your issue
 * should be already available at your local mirror

If problems still persist, please make note of it in this bug report.