RHDEVDOCS-4872 - Logging 5.6.1 RNs w/ SME / QE / Peer revs

Author: libander

logging/cluster-logging-release-notes.adoc

@@ -11,6 +11,8 @@ include::snippets/logging-compatibility-snip.adoc[]
 
 include::snippets/logging-stable-updates-snip.adoc[]
 
+include::modules/cluster-logging-rn-5.6.1.adoc[leveloffset=+1]
+
 include::modules/cluster-logging-rn-5.6.adoc[leveloffset=+1]
 
 include::modules/cluster-logging-rn-5.5.6.adoc[leveloffset=+1]

modules/cluster-logging-rn-5.6.1.adoc

@@ -0,0 +1,35 @@
+//module included in cluster-logging-release-notes.adoc
+:_content-type: REFERENCE
+[id="cluster-logging-release-notes-5-6-1_{context}"]
+= Logging 5.6.1
+This release includes link:https://access.redhat.com/errata/RHSA-2023:0634[OpenShift Logging Bug Fix Release 5.6.1].
+
+[id="openshift-logging-5-6-1-bug-fixes"]
+== Bug fixes
+* Before this update, the compactor would report TLS certificate errors from communications with the querier when retention was active. With this update, the compactor and querier no longer communicate erroneously over HTTP. (link:https://issues.redhat.com/browse/LOG-3494[LOG-3494])
+
+* Before this update, the Loki Operator would not retry setting the status of the `LokiStack` CR, which caused stale status information. With this update, the Operator retries status information updates on conflict. (link:https://issues.redhat.com/browse/LOG-3496[LOG-3496])
+
+* Before this update, the Loki Operator Webhook server caused TLS errors when the `kube-apiserver-operator` Operator checked the webhook validity. With this update, the Loki Operator Webhook PKI is managed by the Operator Lifecycle Manager (OLM), resolving the issue. (link:https://issues.redhat.com/browse/LOG-3510[LOG-3510])
+
+* Before this update, the LokiStack Gateway Labels Enforcer generated parsing errors for valid LogQL queries when using combined label filters with boolean expressions. With this update, the LokiStack LogQL implementation supports label filters with boolean expression and resolves the issue. (link:https://issues.redhat.com/browse/LOG-3441[LOG-3441]), (link:https://issues.redhat.com/browse/LOG-3397[LOG-3397])
+
+* Before this update, records written to Elasticsearch would fail if multiple label keys had the same prefix and some keys included dots. With this update, underscores replace dots in label keys, resolving the issue. (link:https://issues.redhat.com/browse/LOG-3463[LOG-3463])
+
+* Before this update, the `Red Hat OpenShift Logging` Operator was not available for {product-title} 4.10 clusters because of an incompatibility between {product-title} console and the logging-view-plugin.  With this update, the plugin is properly integrated with the {product-title} 4.10 admin console. (link:https://issues.redhat.com/browse/LOG-3447[LOG-3447])
+
+* Before this update the reconciliation of the `ClusterLogForwarder` custom resource would incorrectly report a degraded status of pipelines that reference the default logstore. With this update, the pipeline validates properly.(link:https://issues.redhat.com/browse/LOG-3477[LOG-3477])
+
+
+[id="openshift-logging-5-6-1-CVEs"]
+== CVEs
+* link:https://access.redhat.com/security/cve/CVE-2021-46848[CVE-2021-46848]
+* link:https://access.redhat.com/security/cve/CVE-2022-3821[CVE-2022-3821]
+* link:https://access.redhat.com/security/cve/CVE-2022-35737[CVE-2022-35737]
+* link:https://access.redhat.com/security/cve/CVE-2022-42010[CVE-2022-42010]
+* link:https://access.redhat.com/security/cve/CVE-2022-42011[CVE-2022-42011]
+* link:https://access.redhat.com/security/cve/CVE-2022-42012[CVE-2022-42012]
+* link:https://access.redhat.com/security/cve/CVE-2022-42898[CVE-2022-42898]
+* link:https://access.redhat.com/security/cve/CVE-2022-43680[CVE-2022-43680]
+* link:https://access.redhat.com/security/cve/CVE-2021-35065[CVE-2021-35065]
+* link:https://access.redhat.com/security/cve/CVE-2022-46175[CVE-2022-46175]