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

Bug 956518

Summary:	[RHEVM] [rhevm-log-collector] info message appear in stderr, instead of stdout.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ilanit Stein <istein>
Component:	ovirt-engine-log-collector	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED UPSTREAM	QA Contact:	Jiri Belka <jbelka>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	acathrow, iheim, jkt, knesenko, oschreib, pstehlik, Rhev-m-bugs, sbonazzo, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	rhevm-log-collector-3.3.0-1.el6ev	Doc Type:	Bug Fix
Doc Text:	Previously the logging system wrote all messages to the standard error. Now only errors are logged to the standard error, all other message are logged to standard output.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-16 09:06:34 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 Ilanit Stein 2013-04-25 07:02:45 UTC

Description of problem:
'rhevm-log-collector list' sends info message to stderr instead of stdout:

rc: 0
out: 
err: INFO: No hypervisors were found, therefore no hypervisor data will be listed.

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

Steps to Reproduce:
1. Run 'rhevm-log-collector list' for rhevm with no hosts.

Expected results:
Send the above info message to stdout

Comment 3 Sandro Bonazzola 2013-09-12 14:19:02 UTC

patch merged upstream master, pushed upstream 3.3

Comment 4 Sandro Bonazzola 2013-09-12 14:20:13 UTC

patch merged upstream 3.3

Comment 7 Charlie 2013-11-28 01:16:09 UTC

This bug is currently attached to errata RHBA-2013:15255. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.