Bug 1698747

Summary:	container-exception-logger shows wrong command in usage
Product:	Red Hat Enterprise Linux 8	Reporter:	Martin Kyral <mkyral>
Component:	container-exception-logger	Assignee:	Martin Kutlak <mkutlak>
Status:	CLOSED ERRATA	QA Contact:	Martin Kyral <mkyral>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	mkutlak, msuchy
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	container-exception-logger-1.0.2-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 21:21:28 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 Martin Kyral 2019-04-11 07:39:01 UTC

Description of problem:
# container-exception-logger -h
Usage: abrt-container-logger [--no-tag | --tag STRING | --help]

The tool reads from standard input and writes to '/proc/1/fd/2'
#

I suppose, abrt-container-logger was the name of the tool in the past.


Version-Release number of selected component (if applicable):
https://mojo.redhat.com/docs/DOC-97363

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 errata-xmlrpc 2019-11-05 21:21:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3471