Bug 1090626

Summary:	[RFE] RHEV-M should report the reason for a failed migration
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Allie DeVolder <adevolder>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED CURRENTRELEASE	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	adevolder, byount, fernando, ipinto, jcall, lpeer, lsurette, mgoldboi, michal.skrivanek, mkalinin, mtessun, pbandark, ppostler, rbarry, Rhev-m-bugs, spower, sraje, sreber, srevivo
Target Milestone:	ovirt-4.3.0	Keywords:	FutureFeature
Target Release:	---	Flags:	sherold: Triaged+ lsvaty: testing_plan_complete-
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-14 11:16:53 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:
Bug Depends On:
Bug Blocks:	1203417, 1425219

Description Allie DeVolder 2014-04-23 19:20:28 UTC

[RFE] RHEV-M should report the reason for a failed migration

- Why does the customer need this? (List the business requirements here)

When a VM stalls because the VM is too busy and the process times out, the RHEV-M should report that this is what happened rather than simply reporting "Fatal Error"

- How would the customer like to achieve this? (List the functional
requirements here)

Message in audit_log/Events tab saying that the migration process timed out or stalled due to VM load

Comment 5 Michal Skrivanek 2015-04-02 10:01:25 UTC

adding a case for meaningful message in case of routing error (bug 1203417)

Comment 6 A. Fernando 2016-01-24 01:29:58 UTC

I am running rhevm-3.4.5-0.3. My source host1 is running with vdsm-4.16.20 and target host2 is running with vdsm-4.16.30.

I have a very active VM, which is trying to migrate via 1G interface; but fails after attempting to migrate nearly 28 minutes.

Only alert I find through the Event Log is as following:
"Migration failed due to Error: Migration not in progress. Trying to migrate to another Host (VM: "vmname", Source: host1. Destination, host2)"
I am finding 'vdsm.log' extremely verbose and cannot make good sense of that.

In my situation most probable the cause is the "bandwidth"; I am using single 1G pipe without any link aggregation, i.e. bonding. Indeed, it would be useful to find a meaningful indication of the failure so that I can find some clues in the vdsm.log to justify the cause is the bandwidth.

Comment 9 Tomas Jelinek 2017-05-31 08:12:46 UTC

*** Bug 1455662 has been marked as a duplicate of this bug. ***

Comment 10 Martin Tessun 2018-06-18 13:24:18 UTC

*** Bug 1183287 has been marked as a duplicate of this bug. ***

Comment 11 Martin Tessun 2018-06-18 13:25:58 UTC

*** Bug 1286708 has been marked as a duplicate of this bug. ***

Comment 12 spower 2018-07-03 10:49:16 UTC

We agreed to remove RFEs component from Bugzilla, if you feel the component has been renamed incorrectly please reach out.

Comment 13 Martin Tessun 2018-07-06 14:56:10 UTC

*** Bug 1448689 has been marked as a duplicate of this bug. ***

Comment 14 Michal Skrivanek 2018-08-17 08:24:29 UTC

the original reporting has changed significantly. Is there anything we can improve in the current version?
We will probably have to handle that on a case by case basis rather than a generic "make it all better".

Comment 17 Red Hat Bugzilla 2023-09-14 23:57:39 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days