Bug 1078793 - ovirt-3.3 backport for max migration timeout introduced wrong variable name
Summary: ovirt-3.3 backport for max migration timeout introduced wrong variable name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.3
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: 3.3.5
Assignee: Vinzenz Feenstra [evilissimo]
QA Contact: Gil Klein
URL:
Whiteboard: virt
Depends On:
Blocks: 1069220
TreeView+ depends on / blocked
 
Reported: 2014-03-20 10:33 UTC by Vinzenz Feenstra [evilissimo]
Modified: 2016-02-10 19:49 UTC (History)
21 users (show)

Fixed In Version:
Clone Of: 1069220
Environment:
Last Closed: 2014-05-08 14:17:10 UTC
oVirt Team: Virt
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25929 0 None MERGED Use the correct configuration value for ovirt-3.3 Never

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