Issued:
2021-03-22
Updated:
2021-03-22

RHBA-2021:0963 - Openshift Logging Bug Fix Release 5.0.1 -

Synopsis

Openshift Logging Bug Fix Release (5.0.1)

Type/Severity

Bug Fix Advisory None

Topic

Openshift Logging Bug Fix Release (5.0.1)

Description

You use the Red Hat OpenShift Logging product to forward, store, and visualize log data from your cluster.

Changes to the Red Hat OpenShift Logging product:

  • Previously, logs were not sent to managed storage when legacy log forwarding was enabled. This happened because the internal generation of the logforwarding configuration improperly made an either/or decision for logforwarding versus legacy logforwarding. The current release fixes this issue: Logs are sent to managed storage when the logstore is defined in the clusterlogging instance. Additionally, logs are sent to legacy logforwarding when enabled regardless if a managed logstore is enabled or not. (BZ#1911477, LOG-1172)

  • Previously, while under load, Elasticsearch responded to some requests with an HTTP 500 error, even though there was nothing wrong with the cluster. Retrying the request was successful. This release fixes the issue by updating the cron jobs to be more resilient when they encounter temporary HTTP 500 errors. They will retry a request multiple times first before failing. (LOG-1215)

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

ProductVersionArch
Red Hat OpenShift Container Platform4.7x86_64

Fixes

(none)

CVEs

(none)

References

(none)

Additional information