Bug 1059886

Summary:	Provide clear info, if migration fails because of high memory writes
Product:	[Retired] oVirt	Reporter:	Markus Stockhausen <mst>
Component:	ovirt-engine-webadmin	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED DUPLICATE	QA Contact:	Israel Pinto <ipinto>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3	CC:	bugs, ecohen, gklein, istein, mgoldboi, michal.skrivanek, mst, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-04 09:31:43 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 Markus Stockhausen 2014-01-30 20:26:12 UTC

Description of problem:

This is similar to BZ 1054994. Migration may fail due to high memory writes inside the VM. BZ 919201 references a bugfix with a detection of that behaviour.
Nevertheless the webinterface only gives an abstract error message
"Migration failed due to Error: Migration not in progress (VM: ..."

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

Ovirt 3.3.2 
VDSM 4.13.2

How reproducible:

100%

Steps to Reproduce:
1. start VM 
2. start process in VM that does heavy RAM changes
3. migrate VM

Actual results:

migration aborts. abstract error is thrown

Expected results:

migration aborts, helpful message should be thrown. E.g. "Migration failed due to high VM memory write pressure..."

Comment 1 Itamar Heim 2014-02-02 08:17:03 UTC

Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-04 09:26:43 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Michal Skrivanek 2014-08-22 14:26:18 UTC

this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know

Comment 4 Sandro Bonazzola 2015-09-04 08:59:39 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 5 Michal Skrivanek 2015-09-04 09:31:43 UTC

will be address by migration convergence algorithm overhaul

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

Comment 6 Red Hat Bugzilla 2023-09-14 02:03:00 UTC

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