|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// logging-5-7-release-notes.adoc |
| 4 | +// cluster-logging-release-notes.adoc |
| 5 | +:_content-type: REFERENCE |
| 6 | +[id="logging-release-notes-5-7-1_{context}"] |
| 7 | += Logging 5.7.1 |
| 8 | +This release includes: link:https://access.redhat.com/errata/RHBA-2023:3197[OpenShift Logging Bug Fix Release 5.7.1]. |
| 9 | + |
| 10 | +[id="logging-5-7-1-bug-fixes_{context}"] |
| 11 | +== Bug fixes |
| 12 | +* Before this update, the presence of numerous noisy messages within the Cluster Logging Operator pod logs caused reduced log readability, and increased difficulty in identifying important system events. With this update, the issue is resolved by significantly reducing the noisy messages within Cluster Logging Operator pod logs. (link:https://issues.redhat.com/browse/LOG-3482[LOG-3482]) |
| 13 | + |
| 14 | +* Before this update, the API server would reset the value for the `CollectorSpec.Type` field to `vector`, even when the custom resource used a different value. This update removes the default for the `CollectorSpec.Type` field to restore the previous behavior. (link:https://issues.redhat.com/browse/LOG-4086[LOG-4086]) |
| 15 | + |
| 16 | +* Before this update, a time range could not be selected in the {Product-Title} web console by clicking and dragging over the logs histogram. With this update, clicking and dragging can be used to successfully select a time range. (link:https://issues.redhat.com/browse/LOG-4501[LOG-4501]) |
| 17 | + |
| 18 | +* Before this update, clicking on the *Show Resources* link in the {Product-Title} web console did not produce any effect. With this update, the issue is resolved by fixing the functionality of the "Show Resources" link to toggle the display of resources for each log entry. (link:https://issues.redhat.com/browse/LOG-3218[LOG-3218]) |
| 19 | + |
| 20 | +[id="logging-5-7-1-CVEs_{context}"] |
| 21 | +== CVEs |
| 22 | +* link:https://access.redhat.com/security/cve/CVE-2023-21930[CVE-2023-21930] |
| 23 | +* link:https://access.redhat.com/security/cve/CVE-2023-21937[CVE-2023-21937] |
| 24 | +* link:https://access.redhat.com/security/cve/CVE-2023-21938[CVE-2023-21938] |
| 25 | +* link:https://access.redhat.com/security/cve/CVE-2023-21939[CVE-2023-21939] |
| 26 | +* link:https://access.redhat.com/security/cve/CVE-2023-21954[CVE-2023-21954] |
| 27 | +* link:https://access.redhat.com/security/cve/CVE-2023-21967[CVE-2023-21967] |
| 28 | +* link:https://access.redhat.com/security/cve/CVE-2023-21968[CVE-2023-21968] |
| 29 | +* link:https://access.redhat.com/security/cve/CVE-2023-28617[CVE-2023-28617] |
0 commit comments