|
| 1 | +// Module included in the following assemblies: |
| 2 | +// cluster-logging-release-notes.adoc |
| 3 | +// logging-5-7-release-notes.adoc |
| 4 | +:_content-type: REFERENCE |
| 5 | +[id="cluster-logging-release-notes-5-7-7_{context}"] |
| 6 | += Logging 5.7.7 |
| 7 | +This release includes link:https://access.redhat.com/errata/RHSA-2023:5530[OpenShift Logging Bug Fix Release 5.7.7]. |
| 8 | + |
| 9 | +[id="openshift-logging-5-7-7-bug-fixes_{context}"] |
| 10 | +== Bug fixes |
| 11 | +* Before this update, FluentD normalized the logs emitted by the EventRouter differently from Vector. With this update, the Vector produces log records in a consistent format. (link:https://issues.redhat.com/browse/LOG-4178[LOG-4178]) |
| 12 | + |
| 13 | +* Before this update, there was an error in the query used for the *FluentD Buffer Availability* graph in the metrics dashboard created by the Cluster Logging Operator as it showed the minimum buffer usage. With this update, the graph shows the maximum buffer usage and is now renamed to *FluentD Buffer Usage*. (link:https://issues.redhat.com/browse/LOG-4555[LOG-4555]) |
| 14 | + |
| 15 | +* Before this update, deploying a LokiStack on IPv6-only or dual-stack {product-title} clusters caused the LokiStack memberlist registration to fail. As a result, the distributor pods went into a crash loop. With this update, an administrator can enable IPv6 by setting the `lokistack.spec.hashRing.memberlist.enableIPv6:` value to `true`, which resolves the issue. (link:https://issues.redhat.com/browse/LOG-4569[LOG-4569]) |
| 16 | + |
| 17 | +* Before this update, the log collector relied on the default configuration settings for reading the container log lines. As a result, the log collector did not read the rotated files efficiently. With this update, there is an increase in the number of bytes read, which allows the log collector to efficiently process rotated files. (link:https://issues.redhat.com/browse/LOG-4575[LOG-4575]) |
| 18 | + |
| 19 | +* Before this update, the unused metrics in the Event Router caused the container to fail due to excessive memory usage. With this update, there is reduction in the memory usage of the Event Router by removing the unused metrics. (link:https://issues.redhat.com/browse/LOG-4686[LOG-4686]) |
| 20 | + |
| 21 | +[id="openshift-logging-5-7-7-CVEs_{context}"] |
| 22 | +== CVEs |
| 23 | +* link:https://access.redhat.com/security/cve/CVE-2023-0800[CVE-2023-0800] |
| 24 | +* link:https://access.redhat.com/security/cve/CVE-2023-0801[CVE-2023-0801] |
| 25 | +* link:https://access.redhat.com/security/cve/CVE-2023-0802[CVE-2023-0802] |
| 26 | +* link:https://access.redhat.com/security/cve/CVE-2023-0803[CVE-2023-0803] |
| 27 | +* link:https://access.redhat.com/security/cve/CVE-2023-0804[CVE-2023-0804] |
| 28 | +* link:https://access.redhat.com/security/cve/CVE-2023-2002[CVE-2023-2002] |
| 29 | +* link:https://access.redhat.com/security/cve/CVE-2023-3090[CVE-2023-3090] |
| 30 | +* link:https://access.redhat.com/security/cve/CVE-2023-3390[CVE-2023-3390] |
| 31 | +* link:https://access.redhat.com/security/cve/CVE-2023-3776[CVE-2023-3776] |
| 32 | +* link:https://access.redhat.com/security/cve/CVE-2023-4004[CVE-2023-4004] |
| 33 | +* link:https://access.redhat.com/security/cve/CVE-2023-4527[CVE-2023-4527] |
| 34 | +* link:https://access.redhat.com/security/cve/CVE-2023-4806[CVE-2023-4806] |
| 35 | +* link:https://access.redhat.com/security/cve/CVE-2023-4813[CVE-2023-4813] |
| 36 | +* link:https://access.redhat.com/security/cve/CVE-2023-4863[CVE-2023-4863] |
| 37 | +* link:https://access.redhat.com/security/cve/CVE-2023-4911[CVE-2023-4911] |
| 38 | +* link:https://access.redhat.com/security/cve/CVE-2023-5129[CVE-2023-5129] |
| 39 | +* link:https://access.redhat.com/security/cve/CVE-2023-20593[CVE-2023-20593] |
| 40 | +* link:https://access.redhat.com/security/cve/CVE-2023-29491[CVE-2023-29491] |
| 41 | +* link:https://access.redhat.com/security/cve/CVE-2023-30630[CVE-2023-30630] |
| 42 | +* link:https://access.redhat.com/security/cve/CVE-2023-35001[CVE-2023-35001] |
| 43 | +* link:https://access.redhat.com/security/cve/CVE-2023-35788[CVE-2023-35788] |
0 commit comments