Bug 1364053

Summary:	[RFE] virt-v2v traces should go only to stdout or stderr, not both
Product:	[Community] Virtualization Tools	Reporter:	Tomáš Golembiovský <tgolembi>
Component:	libguestfs	Assignee:	Richard W.M. Jones <rjones>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	ptoscano, rbalakri
Target Milestone:	---
Target Release:	---
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-08-09 07:40:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomáš Golembiovský 2016-08-04 11:47:37 UTC

Currently the virt-v2v tracing is inconsistent. Some traces/debug messages end up on stdout and some on stderr. To obtain useful log one must merge stdout and stderr streams and store both. While it is generally not a problem, this may complicate things when virt-v2v is not run manualy but is used inside some other tool.

Also since the tracing is rather aggressive it can make it difficult to find the error message among the debug messages in case of an error. It might be preferable to put all the traces to stdout and keep stderr for error reporting only. This is again mainly to simplify situation when virt-v2v is used in some other tool.

Comment 1 Richard W.M. Jones 2016-08-04 11:58:03 UTC

This is fixed upstream - please check the latest version.

Comment 2 Tomáš Golembiovský 2016-08-09 07:40:37 UTC

Confirmed. Closing the bug.