Bug 1511719
| Summary: | operations logs lost if no ops cluster and no @OUTPUT label | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rich Megginson <rmeggins> | |
| Component: | Logging | Assignee: | Rich Megginson <rmeggins> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 3.7.0 | CC: | aos-bugs, jcantril, nhosoi, pportant, pweil, rmeggins, tkatarki | |
| Target Milestone: | --- | |||
| Target Release: | 3.7.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: When upgrading to a new version of logging, if the deployment does not use a separate OPS logging cluster, and there is no @OUTPUT label in the fluent.conf, fluentd does not know how to route the operations logs.
Consequence: The operations logs are not logged. User will see no new operations (.operations.*) logs after the upgrade.
Fix: Change the fluentd configuration to correctly handle the case both with and without the @OUTPUT label, and for the OPS and non-OPS cases.
Result: Operations logs flow uninterrupted after upgrade.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1512028 (view as bug list) | Environment: | ||
| Last Closed: | 2017-12-18 13:23:56 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: | 1512028 | |||
|
Description
Rich Megginson
2017-11-10 00:02:51 UTC
koji_builds: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=623852 repositories: brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:rhaos-3.7-rhel-7-docker-candidate-29398-20171110235311 brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:latest brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:v3.7.6 brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:v3.7.6-2 brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:v3.7 @Rich, With logging-fluentd/images/v3.7.7-1. The .operations logs can be found both mux is enabled and disabled when OUPPUT label is removed. I think the test result is pass. The bug is move from ON_QA to Modified, Is there other fix? (In reply to Anping Li from comment #3) > @Rich, > With logging-fluentd/images/v3.7.7-1. The .operations logs can be found both > mux is enabled and disabled when OUPPUT label is removed. I think the test > result is pass. > > The bug is move from ON_QA to Modified, Is there other fix? Did you deploy without OPS cluster? The bug can only be reproduced when you deploy logging without OPS cluster. If you did not deploy OPS cluster, and you could not reproduce the issue, then the bug is verified. Yes, I had Deployed without OPS cluster. so move to verified. 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-2017:3464 |