Bug 1684048
| Summary: | Newly introduced log-rotation in fluentd not working | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Simon Reber <sreber> | |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 3.9.0 | CC: | aos-bugs, clichybi, dmoessne, mvardhan, qitang, rmeggins, smunilla | |
| Target Milestone: | --- | |||
| Target Release: | 3.9.z | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | openshift3/logging-fluentd:v3.9.73-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The files that implement the new log rotation
functionality were not being copied to the correct
fluentd directory.
Consequence: Fluentd was not using log rotation and its log
files were not being rotated.
Fix: Change the container build to inspect the fluentd
gem to find out where to install the files.
Result: The files that implement log rotation are
copied to the correct directory for fluentd to use.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1684210 (view as bug list) | Environment: | ||
| Last Closed: | 2019-04-09 14:20:18 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1684210, 1686941 | |||
|
Description
Simon Reber
2019-02-28 10:19:54 UTC
Could not reproduce with 3.11 - seems to be working fine. Will try 3.9 3.9 is definitely not working - but logging code is the same between 3.9 and 3.11 - strange . . . merged upstream release-3.9 branch https://github.com/openshift/origin-aggregated-logging/commit/612d024ab27607b0398a8609feb4392c99f729b5 Verified on logging-fluentd:v3.9.74. 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:0619 |