RHBA-2021:3705 - Bug Fix Advisory

Topic

Openshift Logging Bug Fix Release (5.0.9)

Description

• LOG-1574 - Before this update, some log entries had unrecognized UTF-8 bytes, which caused Elasticsearch to reject the messages and block the entire buffered payload. This update resolves the issue: rejected payloads drop the invalid log entries and resubmit the remaining entries.
• LOG-1736 - Before this update, editing the `ClusterLogging` custom resource (CR) did not apply the value of the `total_limit_size` field. Instead, it applied the default value. With this update, Fluentd uses the value of the `total_limit_size` field.

Solution

For OpenShift Container Platform 4.7 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.html

For Red Hat OpenShift Logging 5.0, see the following instructions to apply this update:

https://docs.openshift.com/container-platform/4.7/logging/cluster-logging-upgrading.html

Affected Products

• Red Hat OpenShift Container Platform 4.7 for RHEL 8 x86_64

Fixes

• LOG-1574 - [release-5.0] Error "com.fasterxml.jackson.core.JsonParseException: Invalid UTF-8 start byte 0x92" in Elasticsearch/Fluentd logs
• LOG-1736 - [1976692]fluentd total_limit_size wrong values echoed

CVEs

(none)

References

• null