Bug 1649997 - [3.11] Fluentd pod should log its logs to /var/log/fluentd/fluentd.log by default
Summary: [3.11] Fluentd pod should log its logs to /var/log/fluentd/fluentd.log by def...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.11.z
Assignee: Noriko Hosoi
QA Contact: Qiaoling Tang
URL:
Whiteboard:
Depends On: 1643340 1650005
Blocks: 1643341
TreeView+ depends on / blocked
 
Reported: 2018-11-15 05:42 UTC by Noriko Hosoi
Modified: 2018-12-12 14:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Running "oc logs $fluentd_pod" suggests to run "oc exec <pod_name> /opt/app-root/src/utils/logs" which includes the non existing utility logs path. Consequence: "oc exec <pod_name> /opt/app-root/src/utils/logs" fails with "no such file or directory". Fix: Fixed the suggested command line to "oc exec <pod_name> -- logs" since the utility "logs" is now in the PATH and no need to specify the full path. Result: "oc logs $fluentd_pod" suggests the correct command line to show the fluentd logs.
Clone Of: 1643340
Environment:
Last Closed: 2018-12-12 14:15:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3743 0 None None None 2018-12-12 14:15:57 UTC

Comment 4 Qiaoling Tang 2018-11-30 02:02:21 UTC 
The fix isn't in ose-logging-fluentd-v3.11.44-1.
Comment 6 Qiaoling Tang 2018-12-04 02:32:05 UTC 
Fixed in ose-logging-fluentd-v3.11.50-1.
Comment 8 errata-xmlrpc 2018-12-12 14:15:49 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-2018:3743
Note You need to log in before you can comment on or make changes to this bug.