Skip to content

Commit 2b43db5

Browse files
committed
RHDEVDOCS-4928 - Logging 5.6.2 Release Notes
1 parent 1e9dda2 commit 2b43db5

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed

logging/cluster-logging-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ include::snippets/logging-compatibility-snip.adoc[]
1111

1212
include::snippets/logging-stable-updates-snip.adoc[]
1313

14+
include::modules/cluster-logging-rn-5.6.2.adoc[leveloffset=+1]
15+
1416
include::modules/cluster-logging-rn-5.6.1.adoc[leveloffset=+1]
1517

1618
include::modules/cluster-logging-rn-5.6.adoc[leveloffset=+1]

modules/cluster-logging-rn-5.6.2.adoc

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
//module included in cluster-logging-release-notes.adoc
2+
:_content-type: REFERENCE
3+
[id="cluster-logging-release-notes-5-6-2_{context}"]
4+
= Logging 5.6.2
5+
This release includes link:https://access.redhat.com/errata/RHBA-2023:0793[OpenShift Logging Bug Fix Release 5.6.2].
6+
7+
[id="openshift-logging-5-6-2-bug-fixes"]
8+
== Bug fixes
9+
* Before this update, the collector did not set `level` fields correctly based on priority for systemd logs. With this update, `level` fields are set correctly. (link:https://issues.redhat.com/browse/LOG-3429[LOG-3429])
10+
11+
* Before this update, the Operator incorrectly generated incompatibility warnings on {product-title} 4.12 or later. With this update, the Operator max {product-title} version value has been corrected, resolving the issue. (link:https://issues.redhat.com/browse/LOG-3584[LOG-3584])
12+
13+
* Before this update, creating a `ClusterLogForwarder` custom resource (CR) with an output value of `default` did not generate any errors. With this update, an error warning that this value is invalid generates appropriately. (link:https://issues.redhat.com/browse/LOG-3437[LOG-3437])
14+
15+
* Before this update, when the `ClusterLogForwarder` custom resource (CR) had multiple pipelines configured with one output set as `default`, the collector pods restarted. With this update, the logic for output validation has been corrected, resolving the issue. (link:https://issues.redhat.com/browse/LOG-3559[LOG-3559])
16+
17+
* Before this update, collector pods restarted after being created. With this update, the deployed collector does not restart on its own. (link:https://issues.redhat.com/browse/LOG-3608[LOG-3608])
18+
19+
* Before this update, patch releases removed previous versions of the Operators from the catalog. This made installing the old versions impossible. This update changes bundle configurations so that previous releases of the same minor version stay in the catalog. (link:https://issues.redhat.com/browse/LOG-3635[LOG-3635])
20+
21+
[id="openshift-logging-5-6-2-CVEs"]
22+
== CVEs
23+
* link:https://access.redhat.com/security/cve/CVE-2022-23521[CVE-2022-23521]
24+
* link:https://access.redhat.com/security/cve/CVE-2022-40303[CVE-2022-40303]
25+
* link:https://access.redhat.com/security/cve/CVE-2022-40304[CVE-2022-40304]
26+
* link:https://access.redhat.com/security/cve/CVE-2022-41903[CVE-2022-41903]
27+
* link:https://access.redhat.com/security/cve/CVE-2022-47629[CVE-2022-47629]
28+
* link:https://access.redhat.com/security/cve/CVE-2023-21835[CVE-2023-21835]
29+
* link:https://access.redhat.com/security/cve/CVE-2023-21843[CVE-2023-21843]

0 commit comments

Comments
 (0)