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

Bug 1354176

Summary:	[RFE] virt-v2v: Implement virt-v2v error messages in webadmin audit log.
Product:	[oVirt] ovirt-engine	Reporter:	Nisim Simsolo <nsimsolo>
Component:	Frontend.WebAdmin	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.2	CC:	bugs, gklein, michal.skrivanek
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-11 06:45:50 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 Nisim Simsolo 2016-07-10 10:37:20 UTC

Description of problem:
Currently, when import VM failed, a basic log appears in events tab (Failed to import Vm VM1 to Data Center DC1, Cluster Cluster1). 
virt-v2v error logs are very detailed and useful. It would be great to have them implemented in audit log. 

For example:
Import Windows VM with Hibernation enabled failed with the next webadmin audit log:
"Failed to import Vm win10_fast_restart to Data Center DC1, Cluster Intel1"

Observing vdsm.log for virt-v2v errors:
"virt-v2v: error: unable to mount the disk image for writing. This has 
probably happened because Windows Hibernation or Fast Restart is being used 
in this guest. You have to disable this (in the guest) in order to use 
virt-v2v."

In such case, the admin will get the correct failure message so he won't have to dig in order to find out what is the issue.

Comment 1 Michal Skrivanek 2016-07-11 06:45:50 UTC

we already work on v2v logging in bug 1350465
We're likely won't be able to display anything useful in audit log though. Well, maybe the last error.

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