Bug 1588828
| Summary: | After upgrade to 3.6 some logs are not showing in the Kibana webUI | |||
|---|---|---|---|---|
| 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.9.0 | CC: | anli, aos-bugs, jcantril, jfoots, rmeggins | |
| Target Milestone: | --- | |||
| Target Release: | 3.9.z | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | logging-fluentd-container-v3.9.31-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The incoming data has a field `record["event"]` that
is a String value and not the Hash value expected by the
transform_eventrouter code.
Consequence: This causes the code to throw an error and fluentd
to emit an error like this:
```
error_class=NoMethodError error="undefined method `key?' for \"request\":String"
```
Fix: The transform_eventrouter code has been changed to only
process the `record["event"]` field if it is a Hash.
Result: Records can flow through to Elasticsearch again.
|
Story Points: | --- | |
| Clone Of: | 1588827 | |||
| : | 1588829 (view as bug list) | Environment: | ||
| Last Closed: | 2018-08-09 22:13:49 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: | 1588772, 1588827 | |||
| Bug Blocks: | 1588829 | |||
|
Comment 2
Anping Li
2018-06-19 05:42:45 UTC
Moving to modified as the dependent RPM is in the compose. Works with logging-fluentd:v3.9.40 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:2335 |