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

Bug 1071260

Summary:	Misleading error message reported on timed out migrations
Product:	[oVirt] vdsm	Reporter:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Component:	General	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Novotny <pnovotny>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	---	CC:	bazulay, bugs, gklein, jentrena, lpeer, mgoldboi, michal.skrivanek, srevivo
Target Milestone:	---	Flags:	ylavi: ovirt-4.0.0? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-22 14:50:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vinzenz Feenstra [evilissimo] 2014-02-28 11:43:54 UTC

Description of problem:
When a migration times out and gets cancelled a misleading message is reported.


How reproducible:
Always

Steps to Reproduce:
1. Change migration_max_time_per_gib_mem in VDSM to a smaller value (5) 
2. Start a migration
3. When it fails due to timeout you'll find the following message in the event log of the RHEVM Webadmin: 

> Migration failed due to Error: Migration not in progress (VM: a, Source: host1, Destination: host2). 

Actual results:
The error messages says that the migration failed because it is not in progress.
> Migration failed due to Error: Migration not in progress (VM: a, Source: host1, Destination: host2). 

Expected results:
Migration failed due to Error: The migration timed out and has been cancelled. (VM: a, Source: host1, Destination: host2).

Comment 1 Vinzenz Feenstra [evilissimo] 2014-02-28 11:46:12 UTC

A bit more clarification: "When a migration times out and gets cancelled"
Should be "When a migration gets cancelled because it timed out"

Comment 2 Michal Skrivanek 2014-10-30 09:48:49 UTC

didn't make 3.5

Comment 3 Michal Skrivanek 2015-09-04 10:02:04 UTC

we still didn't really figure out how to approach this

Comment 4 Michal Skrivanek 2016-04-22 14:50:04 UTC

hopefully wont' happen so much once migration improvements are done in 4.0